5.4 Clearing Out the System Logs

Periodically, you must clear out the dispatch and job log files. Otherwise, the files become so large that they are difficult to use as diagnostic tools and their size can impact the performance of the system.

Oracle recommends that the Oracle client establish a policy as to the frequency for clearing the logs and whether to archive them before clearing.

Note:

Caution: Before you shut down the dispatcher to clear the system logs, verify that no jobs are active.

Clearing the Dispatch Log

To clear the dispatch.log file, follow these steps:
  1. Shut down the dispatcher by following the procedure for Stopping the Dispatcher.
  2. Type cd <$KDD_PRODUCT_HOME>/logs at the system prompt, where <$KDD_PRODUCT_HOME> is your product server installation directory.
  3. Type rm dispatch.log to clear the dispatcher log.
  4. Type start_chkdisp.sh <sleep time> and press Enter to restart the dispatcher. Refer to Starting the Dispatcher for more information.

Clearing the Job Logs

To clear the job logs, follow these steps:
  1. Stop the dispatcher. (Refer to Stopping the Dispatcher for more information).
  2. Type cd <directory> at the system prompt, where <directory> is your log directory. By default, a job log resides in the directory $KDD_PRODUCT_HOME/logs. You can configure the location of this log in the <OFSAAI Installed Directory>/behavior_detection/algorithms/MTS/mantas_cfg/install.cfg file.

    If you do not know the location of the log directory, check the install.cfg file. The log.mantaslog.location property indicates the log location; the default is $KDD_PRODUCT_HOME/logs but this location is configurable.

  3. Do either of the following:
    • Type rm job<job_id>-<date>-<time>.log at the log directory prompt to clear one job log, where <job_id>-<date>-<time> is the name of a specific job log.
    • Type rm job* to clear all job logs.