![]() |
As described earlier, the Administration User Interface has an option to
remove the staged data automatically for asynchronous operations after
successful completion. A more comprehensive utility for removal of data
associated with asynchronous operations is to use the cleanup.sh/bat script
located in the SIS/bin folder. This script allows the administrator to
remove the staged data, operation or job reference, and the associated log
files.
These topics provide information on the functionality provide by the script: |
![]() |
To use the script, these variables must be set to the
correct paths:
To obtain the usage details of the script run:
This displays the following to the admin user:
Options available are:
|
![]() |
To cleanup of jobs in staging table (data), job table (job reference),
staging log files and job log files, use the command as:
The list of Job Ids can be entered in different ways:
Note: The records are deleted for only those jobs that were completely processed. |
![]() |
To cleanup staged items records from staging table only, use the command as:
Note: The staging items are deleted for those jobs that were completely
processed. This will not remove log files and the job table (job reference)
record. |
![]() |
To cleanup log files only for an asynchronous operation, use the command:
Note: The log files are deleted irrespective of status of the job and all other staged data for the job will remain. |
![]() |
To cleanup staging items as well as log files, use the command:
Note: The staging items are deleted for those jobs that were completely
processed, and the log files are deleted irrespective of status of the job. |
![]() |
Although unlikely, an occasion could occur where staged data has no job
reference and hence the data will never be processed. To cleanup unreferenced
staged item records from the staging table, use the command:
Note: This command does not require the job list. The system automatically deletes all such records that are in the staging table that have no reference records in the job table. Typically this type of records might exist in staging table due to resource exceptions while creating the job table entry. |
![]() |
To force clean the staging and job table records , use the command with
-f
option as mentioned:
This deletes all the jobs mentioned in the list irrespective of their
current state. The |
![]() |
Care should be taken while executing the cleanup command with -f
option as it might delete the currently active jobs if the wrong number is
mentioned in the list accidentally. |