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 |
|
- Status and notifications
Dynamic debugging of user sessions or schedulers
The dynamic debugging feature enables administrators to enable or disable the debugging or tracing information for a user/scheduler session, without the need to restart the server. When enabled, relevant debugging information of that session/scheduler will be written to the server log (sm.log). Once you have finished troubleshooting, you can then disable some debugging information for that user session or scheduler, using dynamic debugging; however some debugging information cannot be disabled using dynamic debugging, and in this case the user needs to reconnect to the server or an administrator needs to manually stop and then restart the scheduler, to disable such debugging information.
Caution If multiple sessions exist for one user account or scheduler (for example, one user logs in simultaneously from different clients or multiple instances of one scheduler have been started), the dynamic debugging settings specified for one of these sessions will take effect for all of the sessions of this user account or scheduler.
Dynamic debugging supported parameters
The following table lists the debugging parameters that can be enabled and disabled or can only be enabled in dynamic debugging.
| Parameters can be enabled and disabled in dynamic debugging | Parameters can be enabled but cannot be disabled in dynamic debugging |
|---|---|
| dbmonitorfiles: [file1],[file2]… | dbtriggertrace |
| debugca:n | dbstats |
| debughttp | debugattachments |
| debugdiagnostics | debugjni |
| debugscauto | debugjavascript |
| debugvmmap | debugadhocsql |
| debuglk | debugfileio |
| debugstartup | debugshutdown |
| debugrs | debugprocesses |
| ir_trace | debugdbtypes |
| rtm | debugdbquery |
| sqldebug |
Note Once you have completed debugging of a user session or scheduler using any of those parameters that cannot be disabled in dynamic debugging, you are recommended to re-connect the session or restart the scheduler to disable the parameters.
Related topics
