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 |
|
- Troubleshooting: Common database errors
- Messages: Cannot Find SQL Server, Error Connecting to servername
- Message: Corresponding Join Not Defined
- Messages: Error opening the Core.ir file in read mode
- Troubleshooting: Database debug
- Troubleshooting: Interpreting debugdbquery output
- Troubleshooting: Power outages and hardware failure
- Troubleshooting: Slow execution of queries
- Troubleshooting lister
- Troubleshooting: ODBC error when running Crystal Reports
Troubleshooting: Interpreting debugdbquery output
Output from the Database debug query parameter, debugdbquery, writes to the sm.log file. The messages written to the sm.log file contain several fields, each separated by a caret (^) character. The sm.log file is located in the following directory:
..\..\Micro Focus\ Service Manager\Server\logs
Sample debugdbquery 999 output to the sm.log file:
223 02/05/2007 17:39:51 DBFIND^F^scmessage(Oracle)^1^0.000000^F^0^0.000000^“syslanguage=“en”
and class=“us” and message.id=“1””^ ^0.000000^0.000000 ( [ 0] apm.get.inbox.by.name start )
223 02/05/2007 17:39:51 DBQUERY^F^probsummary(Oracle)^18^1.000000^F^0^0.020000^“hot.tic#true”^
{“category”}^0.000000^0.000000 ( [ 0] sc.manage select )
The following table describes the output fields for the database debug query (debugdbquery) parameter.
| Field | Description |
|---|---|
| who | DBFIND or DBQUERY |
| where | F = foreground or B = background |
| file | The file name followed by database type: Oracle, DB2, SQL server or LDAP, or JOIN. If you add a letter I suffix, then the file name is case-insensitive. |
| key | The number of the selected key. If an asterisk character (*) follows the key number, Service Manager selected that key based on sort requirements, not query requirements. The system first uses a key that satisfies the sort criteria because a physical sort of the data is not required. |
| weight | The calculated weight for the key Service Manager selects for that specific query. For additional information, see the Key selection algorithms Help topic. |
| keytype | P = Partially keyed, I = IR expert search |
| record count | The number of records that satisfy the query. The system adds the DBQUERY entry to the log after processing the select panel and then returns the first 128 records that satisfy that query. |
| seconds till result came back | The amount of time required to satisfy the query. |
| query | The actual query from the user. |
| sortfields | The sort order in which the records are requested. |
| extracttime | The time required to read data records and extract the key values needed for sorting. This is only necessary if a key satisfying the requested sort order does not exist. |
| sorttime | The time required to sort all data records matching the query. This is only necessary if a key satisfying the requested sort order does not exist. |
Debugging parameters
Parameter: debugdbquery
Troubleshooting: Database debug
Tuning: Improving query speed
Tuning: Key selection algorithms
Tuning: Number of fields in files
