I did a little bit of research on our database being case sensitive or not. I used couple of queries on user=bitbucketuser, the database checks out to be sensitive as asked by Bitbucket.
I used below queries :
SELECT CASE WHEN 'A' = 'a' THEN 'Insensitive' ELSE 'Sensitive' END from dual;
SELECT CASE WHEN COUNT(*) = 2 THEN 'Insensitive' ELSE 'Sensitive' ENDFROM NLS_SESSION_PARAMETERSWHERE (PARAMETER = 'NLS_COMP' AND VALUE = 'LINGUISTIC') OR (PARAMETER = 'NLS_SORT' AND VALUE = 'BINARY_CI');
Also as the troubleshooting bitbucket server installations link https://confluence.atlassian.com/bitbucketserverkb/bitbucket-server-requires-a-case-sensitive-database-but-the-target-database-is-case-insensitive-779171550.html suggests that "Note that it is important to the proper operation of Bitbucket Server 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."
On running the query "select * from nls_session_parameters;" and referring to oracle documenation of NLS_COMP and NLS_SORT, I find that default values remain intact and thereby further making us sure, our oracle database remain case sensitive contrary to what you suggest.
Hello Nancy
Did you follow our Connecting Bitbucket Server to Oracle document in order to create the Oracle database?
As mentioned in our instructions for connecting Bitbucket to Oracle, you need to set the collation for the database to a case sensitive collation. As per our document above, AL32UTF8 or UTF8 is the one we have tested and we recommend using it.
Regards
Rodrigo
Hello Rodrigo,
Firstly connecting Bitbucket server to Oracle is giving me 404 - page not found error.
And below are the screenshots of the queries I ran against my database which bitbucket is interacting.
It looks good to me, Let me know if you wanted to change anything and try.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Nancy
I think we may have some confusion around here. I will try to address the points you mentioned in the description:
I did a little bit of research on our database being case sensitive or not.
Indeed, as per our Connecting Bitbucket Server to Oracle documentation, Bitbucket requires it database to store data in a case-sensitive manner.
Also as the troubleshooting bitbucket server installations link https://confluence.atlassian.com/bitbucketserverkb/bitbucket-server-requires-a-case-sensitive-database-but-the-target-database-is-case-insensitive-779171550.html suggests that "Note that it is important to the proper operation of Bitbucket Server 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."
Following the Connecting Bitbucket Server to Oracle documentation, the NLS_COMP and/or NLS_SORT variables will be created as their default values. In addition to that, Atlassian reinforces that changing the values of these variables may cause Oracle to perform its searches in a case-insensitive manner. That's the reason we strongly recommend that those variables be left at their default values.
On running the query "select * from nls_session_parameters;" and referring to oracle documenation of NLS_COMP and NLS_SORT, I find that default values remain intact and thereby further making us sure, our oracle database remain case sensitive contrary to what you suggest.
Ok, your DB is case sensitive, as per Connecting Bitbucket Server to Oracle documentation.
Considering the documents we point out above and the information mentioned by you, we can't see any contradictory information suggested by our side.
Moving on, are you facing issues migrating to an Oracle database? Do you see any errors on the logs/UI?
Regards
Rodrigo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is the error log I am seeing:
Bitbucket requires a case-sensitive database, but the target database is case-insensitive. For information about creating a database for use with Bitbucket, please refer to the Bitbucket documentation.
com.atlassian.stash.internal.db.DefaultDatabaseManager.validateConfiguration(DefaultDatabaseManager.java:226)
com.atlassian.stash.internal.migration.DefaultMigrationService.validateConfiguration(DefaultMigrationService.java:85)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Rodrigo M What my concern is If my database is case-sensitive as per the information I have provided why is it giving a error message Bitbucket requires a case-sensitive database?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Nancy
We have created a support ticket since we need additional information for the investigation.
Regards
Rodrigo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here is the Full screenshot of the Bitbucket when I attempt to connect to Oracle DB,
And I couldn't Enable debug mode to get logs for the bit bucket. Can you be more clear where or any pictures/video that how to enable the debug mode ?
Thanks
Manoj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manoj
You should have received an email regarding this issue.
You can enable DEBUG logs following the instructions here.
This issue is being attended at https://getsupport.atlassian.com/browse/SSP-30353.
Regards
Rodrigo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.