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.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Service Manager9.51

Administer > Database administration > Case-sensitivity > Oracle case-sensitivity > Validate case-insensitive unique indexes

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:1 in the sm.inifile, located in the <SM_install_location>\Server\RUN directory.
Start Service Manager.
Check the sm.log file, 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 ------------------------------ ------------------------------ ---- ------------------------------ ----------------------------------------

Send Help Center feedback