Tasks that automatically rotate message log files
A Scheduler task automatically rotates each of the common message log files (online.log, bar_act_log, and bar_debug_log). When the server rotates a log file, the server switches to a new log file and increments the ID numbers for the previous log files by one. When the maximum number of log files is reached, the log file with the highest ID is deleted.
The following table shows the tasks that automatically rotate message log files and the default frequency for when the tasks run:
| Message log file | Task that rotates the file | Default frequency for when task runs |
|---|---|---|
| online.log | online_log_rotate task | 3:00 A.M. every 30 days You can change the frequency, which is specified in the MAX_MSGPATH_VERSIONS parameter of the ph_threshold table. |
| bar_act_log | bar_act_log_rotate task | 3:00 A.M. every 30 days You can change frequency, which is specified in the MAX_BAR_ACT_LOG_VERSIONS parameter of the ph_threshold table. |
| bar_debug_log | bar_debug_log_rotate task | 3:00 A.M. every 30 days You can change frequency, which is specified in the MAX_BAR_DEBUG_LOG_VERSIONS parameter of the ph_threshold table. |
You can change the maximum number of online, ON-Bar activity, or ON-Bar debug message log files that the database server retains. This information is stored in the MAX_MSGPATH_VERSIONS, MAX_BAR_ACT_LOG_VERSIONS, and MAX_BAR_DEBUG_LOG_VERSIONS parameters of the ph_threshold table.
Before the server can run the tasks that automatically rotate message log files, you must enable each task. You only need to enable each task once.