Deactivating the Database Trace
Use
You determine which activities of the database kernel should no longer be logged or completely deactivate the
database trace.You specify which database kernel activities should no longer be logged with the
<activity_list> option. Separate multiple activities by a space.By specifying
ALL, you deactivate the log function for all activities, and therefore completely deactivate the database trace.Prerequisites
You have the DBM operator authorization
DBInfoRead or DBFileRead.Syntax
trace_off <activity_list> | ALL
<activity_list> :: = <activity> | <activity> <activity_list>
<activity> ::
Deactivate the database trace for the areas
LOCK and TOPICIOMANdbmcli -d a74 -u dbm,dbmp trace_off LOCK TOPICIOMAN
OK
Option <activity>
Name |
ALL |
CHECK |
CHECKALLOCATOR |
CHECKCONVERTER |
CHECKDATA |
CHECKDEVSPACE |
CHECKFRAMECTRL |
CHECKIOMAN |
CHECKLOG |
CHECKMEMORY |
CHECKRUNTIME |
COMMANDS |
DEFAULT |
DELETE |
INDEX |
INSERT |
LOCK |
LONG |
OBJECT |
OBJECTADD |
OBJECTALTER |
OBJECTFREE |
OBJECTGET |
OPTIMIZER |
ORDER |
PAGES |
SELECT |
STANDARD |
TABLE |
TIME |
TOPICALLOCATOR |
TOPICCONVERTER |
TOPICDATA |
TOPICDEVSPACE |
TOPICFRAMECTRL |
TOPICIOMAN |
TOPICLOG |
TOPICMEMORY |
TOPICRUNTIME |
UPDATE |
Reply
The system outputs an OK message.
In the event of errors, see
Reply Format.