The database trace is not required for normal database operation. Therefore you should activate and then deactivate it only when told to do so by Support, because the writing of a database trace has a detrimental effect on the performance of your database system.
You determine which activities of the database instance should no longer be logged or completely deactivate the database trace.
You specify which activities should no longer be logged using the command option activity_list. Separate multiple activities by a space.
By specifying ALL, you deactivate the log function for all activities, and therefore completely deactivate the database trace.
You can view the command options currently active with a description using the command trace_show verbose (Displaying the Logged Activities of the Database Trace).
You have the server authorization DBInfoRead or DBFileRead.
trace_off <activity_list> | ALL
<activity_list> :: = <activity> | <activity>
<activity_list>
Deactivate the database trace for the areas LOCK and TOPICIOMAN
dbmcli -d a74 -u dbm,dbm trace_off LOCK TOPICIOMAN
OK
The system displays an OK message.
In the event of errors, see Reply Format.