The Database Manager GUI gives you the option of enabling the database trace if errors occur.
The database trace only adversely affects performance in liveCache database instances; in other database instances, you can use the database trace even in normal operation.
...
1.
Select the required database instance in the list of database
instances.
Connect to the
DBM server for this database instance if necessary.
2. Choose Instance ® Check ® Database Trace.
3. You can execute the log functions below either individually or group, which you can define yourself.
· On the Options tab page, select the required database trace options in the list. If the options support the selection of a trace level, the system default value is displayed in the Level column .
· Choose Actions ® Selected Items ON to activate the database trace for the chosen database trace options.
If you want to change the trace level for the selected database trace options, choose Actions ® Selected Items ON with Level... You can now select a different trace level. The higher the trace level, the greater amount of detail is provided in the information collected by the database trace.
Choose Actions ® Selected Items OFF to disable the database trace.
The database trace is written for all database sessions by default. The default setting can be changed if necessary:
4. Choose the Advanced tab page and select Trace session.
5. Decide whether the database trace is to be written for the current session or for a specific database session. In this case, enter the ID of the database session (for information about finding the ID, see Displaying Database Sessions).
6. Choose Actions ® Set Advanced Options.
7. On the Advanced tab page, select Stop on error. Enter the code of the error whose occurrence is to stop the creation of the database trace.
8. Then choose Actions ® Flush to write the information still contained in the buffer to the trace and therefore update the database trace before the log file is created.
9. On the Protocol tab page, select the required options.
10. Then choose Actions ® Flush to write the information still contained in the buffer to the trace and therefore update the database trace before the log file is created.
11. Choose Actions ® Make Protocol. The database trace is then converted to a legible format.
To open the log, choose Instance ® Check ® Diagnosis Files. Select the Kernel Trace Protocol file and choose Actions ® View.
See also:
Concepts of the Database System, Traces