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 |
|
- Database parameters
- alignradsensitivitywithdb
- allowunsupporteddbversion
- dbcachequery
- generateIndexDDL
- [oracle]
- [oracle_replicate]
- pgschema
- [postgresql]
- [sqlserver]
- [sqlserver_replicate]
- sqladhoccachesize
- sqlalwayson
- sqlautosort
- sqlbatchcount
- sqlcitext
- sqldb
- sqlddldirectory
- sqlddllogging
- sqldebug
- sqldictionary
- sqldictkey
- sqldicttable
- sqldirect
- sqldisconnect
- sqlfetchrows
- sqlfetchs
- sqljoinsok
- sqllibrary
- sqllimit
- sqllockretry
- sqllockwait
- sqllogin
- sqlloginretry
- sqlloginwait
- sqlnullclause
- sqlouterjoins
- sqlreuseablesql
- sqlstats
- sqltextdateformat
- sql_oracle_binary_ci
- sqltz
- sqlupper
- system_addconstraint
- system_createupperindex
- util
- wildcardcharacters
Parameter: sqlupper
Startup parameters change the behavior of the Service Manager server. You can always set a startup parameter from the server's operating system command prompt.
Parameter
sqlupper
Description
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:
-
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.
- Make sure all Service Manager server nodes are stopped.
-
Add sqlupper:1 to the sm.ini file of each server node.
-
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.
-
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.
- Restart the server nodes.
To use this feature in a new Service Manager system, follow these steps:
- Prepare a case-sensitive Oracle database.
- Install the Service Manager server.
- Add sqlupper:1 to the sm.ini file.
- Run the server configuration utility to connect to the database.
-
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?
Yes
Default value
0
Possible values
0 (Disabled)
1 (Enabled)
Example usage
Initialization file: sqlupper:1
Related topics
Oracle case-sensitivity
Enter a parameter in the sm.ini file
Parameter: system_createupperindex
