Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| Search for | Example | Results |
|---|---|---|
| A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
|
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Oracle case-sensitivity
You can set the Oracle database to the desired case-sensitivity when you create it. Refer to Service Manager Installation 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.
Validate case-insensitive unique indexes
During the initial system load, Service Manager created a set of case-insensitive indexes for each table, based on the keys in that table.
Service Manager logs these indexes first time reads a table when the sqldebug:1 parameter is in the sm.ini file.
You can review the settings created for each table by viewing the sm.log file.
The case-insensitive unique indexes should be created as Oracle function based indexes where the Column Expression is NLSSORT("<field name>",'nls_sort=''BINARY_CI''').
To verify whether the case-insensitive unique indexes are being with the correct column expression:
- Set
sqldebug:1in thesm.inifile, located in the<SM_install_location>\Server\RUNdirectory. - Start Service Manager.
- Check the
sm.logfile, located in the <SM_install_location>\Server\logs directory.
The following entry in the log file indicates that the Oracle instance is set to case insensitive, and that you were able to connect to it successfully.
RTE I Oracle server settings for language, territory and character set: AMERICAN_AMERICA.AL32UTF8 (AL16UTF16) RTE I OCI Client settings for language, territory and character set: AMERICAN_AMERICA.AL32UTF8 (UTF16) .... RTE I Oracle instance setting for NLS_SORT is set to BINARY_CI RTE I Oracle instance setting for NLS_COMP is set to LINGUISTIC ... RTE I Oracle session is set up in CASE INSENSITIVE mode
The following information in the log file indicates that the Dbdict table has an index, DBDICTM1C989DE64, with a key called "NAME", which is case-insensitive.
RTE D Table Name: DBDICTM1
RTE D Schema Name Index Name Type Column Name Column Expression
RTE D ------------------------------ ------------------------------ ---- ------------------------------ ----------------------------------------
RTE D SMDB DBDICTM1C989DE64 U SYS_NC00003$ NLSSORT("NAME",'nls_sort=''BINARY_CI''')
RTE D ------------------------------ ------------------------------ ---- ------------------------------ ----------------------------------------
Related topics
Case-Sensitivity
JavaScript/RAD implications of a case-insensitive database environment
Load/unload implications of case-sensitivity
