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.
|A single word
|Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
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.
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
cat ^ mouse
|A combination of search types
( ) parentheses
- Modifying a Key
Modify keys: Convert the first unique key to primary key
You can run the
sm command together with
system_addconstraint parameter to convert the first unique key of a table to a primary key. When you run this command, Service Manager first modifies the fields of the first unique keys to be
NOT NULL (as if you ran
system_addconstraint:0 as described in Modify keys: Add Not Null constraints to the first unique key in a table) and then applies a primary constraint to those keys.
To convert the first unique key to a primary key by using the command line, use one of the following methods:
Run the following
system_addconstraint command with a value of
1. You can use this method with an Oracle or DB2 database. You cannot use this with a SQL Server database.
In this example, <target> represents the name of the Service Manager table on which you wish to add the constraint, and
1 indicates that you wish to convert the first unique key of the <target> to a primary key.
Caution If Service Manager fails to perform the conversion by using the command in Method 1, or if you have a Microsoft SQL Server database, use the following method. However, you should note the following dangers when using this method:
- Data loss will occur if you run this method on a unique index that contains null values.
- This method invokes a full-table-copy operation, which may take a long time.
- Any database exception error that occurs during the operation can cause unexpected results.
To use this method, follow these steps:
- Make sure that you have no null values on any unique index.
- Execute the following command:
Note Regardless of which method you use, an attempt to revert from a primary key to a unique key may cause unpredictable results.