Staging Column Details

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:

Clean-Up Script Usage

To use the script, these variables must be set to the correct paths:
  • XJS_ROOT = <Explore Java Server Home (CES/ExploreJS)>
  • JAVA_HOME = <Java Installation>
  • SIS_HOME = <SIS Installation (SIS/application)>
  • WEBLOGIC_HOME = <WebLogic Installation (/bea/weblogic81)>

To obtain the usage details of the script run:

cleanup -help

This displays the following to the admin user:

USAGE : cleanup -j <jobids> [options]

Options available are:

-j = <list of jobids, example 1,2,3,4 or 1-5,3,5 or 1,4-50,54,55>

-f = Force clean - Deletes the jobs irrespective of their current state

-l = Delete staging log files and job log files only

-s = Delete staging table records only

-u = deletes all unreferenced records in staging table

Cleaning all Data for Completed Jobs

To cleanup of jobs in staging table (data), job table (job reference), staging log files and job log files, use the command as:

cleanup -j <list of job IDs>

The list of Job Ids can be entered in different ways:

cleanup -j 1,2,3,55,66,77 deletes the jobs 1, 2, 3, 55, 66 and 77

cleanup -j 1-5,6,88-95,101 deletes the jobs 1 to 5 and 6 and 88 to 95 and 101

Note: The records are deleted for only those jobs that were completely processed.

Removing Staged Data for Completed Jobs

To cleanup staged items records from staging table only, use the command as:

cleanup -j <list of job IDs> -s

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.

Removing Only Log Files

To cleanup log files only for an asynchronous operation, use the command:

cleanup -j <list of Job IDs> -l

Note: The log files are deleted irrespective of status of the job and all other staged data for the job will remain.

Removing Staged Data and Log Files

To cleanup staging items as well as log files, use the command:

cleanup -j <list of job IDs> -s -l

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.

Removing Unreferenced Staged Data

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:

cleanup -u

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.

Forcing Cleaning of Jobs

To force clean the staging and job table records , use the command with -f option as mentioned:

cleanup -j <list of jobIDs> -f

This deletes all the jobs mentioned in the list irrespective of their current state. The -f option can also be used in conjunction with the options above to force execution.

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.