Oracle case-sensitivity (2024)

You can set the Oracle database to the desired case-sensitivity when you create it. Refer to the HPE Service Manager Installation Guide for instructions.

Refer to the Case-sensitivity section of the Service Manager Support Matrix for versions of Oracle for which Service Manager supports case-insensitive mode.

Requirements for using a case-insensitive Oracle database

If you want to use a case-insensitive Oracle database with Service Manager instead of using the sqlupper:1 solution, you must meet the following requirements:

• NLS_SORT=BINARY_CI and NLS_COMP=LINGUISTIC must be set in the Oracle instance level.
  • If these values are set as given above, Service Manager will issue an ALTER SESSION statement to match the NLS_SORT and NLS_COMP session parameter with the NLS_SORT and NLS_COMP instance parameter.
  • If these values are not set or are different from the given values, Service Manager will treat it as case-sensitive Oracle and issue an ALTER SESSION statement to modify those parameters to be NLS_SORT=BINARY and NLS_COMP=BINARY.
  
  This ensures that all Service Manager server processes within a horizontal or vertical scaling group have consistent Oracle case-sensitivity settings.
• All unique keys in Service Manager tables must have a matching case-insensitive unique index.

Limitations of case-insensitive Oracle

You will not be able to rename or change a column size of keyed fields from the Service Manager Dbdict Utility when using a case-insensitive Oracle instance. Instead, select generate DDL when modifying columns from Dbdict Utility. An Oracle database administrator can then drop affected function based index, apply the DDL, and recreate the function based index on the Oracle database.