Stash requires a case-sensitive database, but the target database is case-insensitive.
Troubleshooting Installation
- 'Address already in use' when Starting up Stash
- After Configuring Stash with SSL, Application Won't Start
- All Repositories Appear Empty After an Upgrade
- A soft-locked cache entry was expired by the underlying Ehcache
- Both old and new directory exist
- Change atlassian.recovery.password when installed as a Windows service
- Change STASH_HOME when installed as a Windows service
- ClassNotFoundException: javax.servlet.ServletContext When Starting Stash WAR in Tomcat 7
- Git 1.7.1 is Not Supported by Stash
- Harmless checkThreadLocalMapForLeaks messages on catalina.out
- How to run Stash over HTTPS with a Personal Information Exchange (PFX) keystore
- Invalid Java location
- java: not found during Stash startup
- LDAP Groups are not being populated with users using FreeIPA
- Login and session conflicts with multiple Atlassian applications
- Manage add-ons - An unexpected error has occurred. Please refer to the logs for more information.
- object directory does not exist - Git operations fail after upgrade or STASH_HOME update
- OpenJDK 64-Bit Server VM is an unsupported JVM
- Push Causes Pre-Receive Hook Declined When Running Windows Server on XenServer
- Sending email fails due to 501 Syntax: HELO hostname error
- SpringMVC dispatcher could not be started
- SSH server fails to start on AWS EC2 instance
- stash.git.notfound error during installation
- Stash as a service and the database as currently configured is not accessible error
- Stash console output: INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found
- Stash Doesn't Start Due to java.lang.UnsatisfiedLinkError
- Stash does not start - After upgrade due to ClassNotFoundException org.apache.catalina.core.JasperListener
- Stash Does Not Start - No fonts found
- Stash does not start - No such file or directory
- Stash failed to Start due to Required plugin failed to start
- Stash fails to start: Perl does not seem to be installed
- Stash fails to start - BASEDIR environment variable is not defined
- Stash fails to start - Missing column
- Stash fails to start on 64-bit Windows with error 'tc-native-1.dll: Can't load IA 32-bit .dll'
- Stash Fails To Start on Windows, Please add git version 1.7.6 or higher to the PATH
- Stash Fails to Start - SEVERE: Error listenerStart
- Stash fails to start - The Spring WebApplicationContext could not be started - Unresolved constraint in bundle
- Stash fails to start - UnsupportedDirectoryOverrideException
- Stash Fails to Startup after installation when Running on OpenJDK
- Stash Fails to Start Up with java.net.UnknownHostException Exception
- Stash fails to start when the current locale is Turkish
- Stash fails to start with org.apache.catalina.core.ContainerBase.startInternal A child container failed during start
- Stash Fails to Start with the Reference to Entity "ABC123" Must End with the ';' Delimiter Error
- Stash hangs right after it starts
- Stash Home [<STASH_HOME>] cannot be created
- Stash Installer fails on Windows 2000
- Stash Install or Upgrade Fails: Error validating Perl
- Stash logo displays localhost
- Stash requires a case-sensitive database, but the target database is case-insensitive.
- Stash service (64-bit) fails to start - not a valid Win32 application
- Stash service installed as "STASH" instead of "Atlassian Stash" and fails with code 4
- Stash Stuck at Empty Repository Screen after Push When Running Windows Server on XenServer
- Stash Upgrade Fails with: tables whose names collide with Stash
- Stash Upgrade Fails with 'Permission Denied' Error
- Stash Upgrade Fails with "Table already exists" Error
- Stash Upgrade Fails with (Permission denied) Exception
- Stash Windows service fails to start - The system cannot open the file
- The database, as currently configured, is not accessible
- The Spring WebApplicationContext could not be started
- Unable to access server on fresh install on Linux
- Unable to access Stash during installation
- Unable to start Stash, with message function: not found
- Upgrading your Stash home directory for Stash 3.2 manually
- White/blank screen after upgrade
- Windows service launches old version after upgrade
このページの内容
関連コンテンツ
- 関連コンテンツがありません
症状
When trying to connect to an external database supported by Stash, the following message is displayed:
Stash requires a case-sensitive database, but the target database is case-insensitive. For information about creating a database for use with Stash, please refer to the Stash documentation.
The following screen is shown:
原因
Stash requires that the database stores its data in a case-sensitive manner for its regular operation.
ソリューション
The instructions on how to set up the database server will depend upon which database you are connecting your instance to. Please refer to the documentation for creating your database listed on Connecting Stash to an external database accordingly. Below we highlighted the commands related to the database creation that you need to make sure they were run.
SQL Server> ALTER DATABASE stash COLLATE SQL_Latin1_General_CP1_CS_AS
mysql> CREATE DATABASE stash CHARACTER SET utf8 COLLATE utf8_bin;
Note that it is important to the proper operation of Stash that the database store its data in a case-sensitive manner. By changing the values of the NLS_COMP and/or NLS_SORT variables, it is possible to cause Oracle to perform its searches in a case-insensitive manner. We therefore strongly recommend that those variables be left at their default values.
CREATE DATABASE stash WITH ENCODING='UTF8' OWNER=stashuser CONNECTION LIMIT=-1;
関連コンテンツ
- 関連コンテンツがありません