Parameter: sqlupper

Startup parameters change the behavior of the HPE Service Manager server. You can always set a startup parameter from the server's operating system command prompt.




This parameter enables the Service Manager server to convert new tables in an Oracle database to use UPPER indexes and to implement case-insensitive search behavior in Service Manager. This feature can implement case-insensitive search behavior on a case-sensitive Oracle database, and therefore eliminates the need to use a case-insensitive Oracle database which might slow down your system performance.

Note In sqlupper mode, the records are divided into groups according to their names when you use grouping. If the names of two records differ only in the case of the letter, then the records will be divided into different groups. For example, the "application" records and "Application" records in the database are divided to the "Application" group and the "application" group. To get a better view, you can unify the record names as "application" or "Application" in the database.

To use this feature in an existing Service Manager system, follow these steps:

  1. Make sure your Oracle database is case-sensitive. If not, convert your Oracle database from case-insensitive to case-sensitive.

    Note To make Service Manager treat your Oracle database as case-sensitive, make sure you have not NLS_SORT=BINARY_CI and NLS_COMP=LINGUISTIC configured in your Oracle. For example, you can configure NLS_SORT=BINARY and NLS_COMP=BINARY to make it case-sensitive. For more information, see Oracle case-sensitivity.

  2. Make sure all Service Manager server nodes are stopped.
  3. Add sqlupper:1 to the sm.ini file of each server node.

  4. In a server’s command prompt, run the system_createupperindex:all command to convert all existing tables to use UPPER indexes.

    Note Every time after you run the system_createupperindex command, a message appears in the console that indicates if any tables are not successfully converted.

  5. If any tables fail to be converted, run the system_createupperindex:<list of tables, separated by a comma> command to convert these tables again.

    Note You can run this command multiple times as needed until all tables are successfully converted.

  6. Restart the server nodes.

To use this feature in a new Service Manager system, follow these steps:

  1. Prepare a case-sensitive Oracle database.
  2. Install the Service Manager server.
  3. Add sqlupper:1 to the sm.ini file.
  4. Run the server configuration utility to connect to the database.
  5. Load the Service Manager out-of-box tables and demonstration data.

    All tables are loaded with UPPER indexes. All new tables that you may create later will also use UPPER indexes.

Valid if set from

Initialization file (sm.ini)

Requires restart of the Service Manager server?


Default value


Possible values

0 (Disabled)

1 (Enabled)

Example usage

Initialization file: sqlupper:1