...
- SCHEDULER_HISTORY
- SCHEDULER_ORDER_HISTORY
- SCHEDULER_ORDER_STEP_HISTORY
- DAYS_SCHEDULE
- SOSFTP_FILES
- SOSFTP_FILES_HISTORY
If nobody cares, then these tables are very large and the performance goes down or there is no more space available.
To avoid this, you should regularly run this job.
If you choose the 'Housekeeping' package while the installer then you find this job in ./config/live/sos/housekeeping/schedulercleanup_history_.
This job can
...
deletes records which are older than the parameter delete_
...
interval
...
The second function is very time consuming and generates a lot of payload.
Here, when many records are processed, it can even cause the error
...
...
COM 80020009 Exception occurred. [step] [] [Z-JAVA-105 Java exception java.lang.OutOfMemoryError ("Java heap space"), method = spooler_process () Z [], in Remote_module_instance_server :: step], method = call
It is strongly recommended that you suppress the shrink functionality and uses only the delete functionality.
Parameterization of JobSchedulerCleanupHistory since release 1.3.12.1285
| Code Block |
|---|
<?xml version="1.0" encoding="iso-8859-1"?>
<job title = "Delete log entries in Job Scheduler history">
<description>
<include file = "jobs/JobSchedulerCleanupHistory.xml"/>
</description>
<params>
<!-- strongly recommended: value=0 suppresses the cleanup -->
<param name = "cleanup_history_interval" value = "0" />
<!-- example: value=7 deletes all records older than 7 days -->
<param name = "delete_history_interval" value = "7" />
</params>
<script language = "java"
java_class = "sos.scheduler.job.JobSchedulerCleanupHistory"/>
<!-- cleanup history entries every day of the week at the given hour -->
<run_time let_run = "yes"
begin = "00:00"
end = "24:00">
<period single_start = "01:00"/>
</run_time>
</job>
|
...