![]() |
![]() |
Task | Required Privilege Class |
---|---|
Request information from the activity log | Any administrator |
Set the activity log retention period | System |
Change the size of the activity log | System or unrestricted storage |
The activity log contains all messages normally sent to the system log during server operation. The only exceptions are responses to commands entered at the console, such as responses to QUERY commands.
Examples of messages sent to the activity log include:
Any error messages sent to the server console are also stored in the activity log.
Use the following sections to adjust the size of the activity log, set an activity log retention period, and request information about the activity log.
You can request information stored in the activity log. To minimize processing time when querying the activity log, you can:
For example, to review messages generated on May 30 between 8 a.m. and 5 p.m., enter:
query actlog begindate=05/30/2000 enddate=05/30/2000 begintime=08:00 endtime=17:00
To request information about messages related to the expiration of files from the server storage inventory, enter:
query actlog msgno=0813
Refer to Messages for message numbers.
You can also request information only about messages logged by one or all clients. For example, to search the activity log for messages from the client for node JEE:
query actlog originator=client node=jee
Use the SET ACTLOGRETENTION command to specify how long activity log information is kept in the database. The server automatically deletes messages from the activity log once the day that was specified with the SET ACTLOGRETENTION command has passed. At installation, the activity log retention period is set to one day. To change the retention period to 10 days, for example, enter:
set actlogretention 10
To disable activity log retention, set the SET ACTLOGRETENTION command to zero. To display the current retention period for the activity log, query the server status.
Because the activity log is stored in the database, the size of the activity log should be factored into the amount of space allocated for the database. Allow at least 1MB of additional space for the activity log.
The size of your activity log depends on how many messages are generated by daily processing operations and how long you want to retain those messages in the activity log. When retention time is increased, the amount of accumulated data also increases, requiring additional database storage.
When there is not enough space in the database or recovery log for activity log records, the server stops recording and sends messages to the system log. If you increase the size of the database or recovery log, the server starts activity log recording again.
If you do not have enough space in the database for the activity log, you can do one of the following: