Optimize 10.7 | webMethods Optimize Documentation | Administering webMethods Optimize | For Database Administrators | Purging Data from Optimize Database Components | Configuring Data Purge | Setting Purge Operation Parameters
 
Setting Purge Operation Parameters
*To set the purge operation parameters
1. Set the following parameters directly in the OPERATION_PARAMETER table:
*Mail host for e-mail notifications (Oracle only).
*Whether to drop old tables after the purge operation.
*Time to wait for the purge operation to complete before the job times out.
*Whether stale purge jobs should be removed.
*Number of days to retain data in the OPERATION_LOG table.
Note:
If you installed the Analysis and Process Tracker database component sets in different database schemas, you set these parameters by editing two OPERATION_PARAMETER tables, one in each database schema. For more information, see Installing Optimize Database Component Sets
The OPERATION_PARAMETER table in the Analysis and Process Tracker database components contains a row for every database table and parameter associated with the purge operation.
The following table explains how the OPERATION_PARAMETER table in each database component looks.
PARA METER _ID
OPERATION _CD
PARAMETER _GROUP_CD
PARAMETER_ CD
PARAMETER_DSCR
PARAMETER_ VALUE
1
OPERATION MGMT
MAILHOST
Mail host (server) through which to send notifications (e-mail messages) that indicate purge success or failure
host.com
2
MASSIVE DATA PURGE
DROP OLD TABLES
Flag to determine whether the old table should be dropped after a successful purge operation
YES
3
MASSIVE DATA PURGE
JOB TIMEOUT
Time in seconds to wait for the purge operation to complete; if time exceeded, operation will stop and send notification that job has timed out
10800
4
MASSIVE DATA PURGE
REMOVE STALE JOBS
Flag to identify whether stale purge jobs should be removed
YES
5
MASSIVE DATA PURGE
CONTROL DATE
OPERATION_ LOG
Number of days to retain data in OPERATION_ LOG table
14
6
MASSIVE DATA PURGE
WHERE CLAUSE
BAM_FACT_ DTHNDLR_V1
Where clause for retaining data in BAM_FACT_ DTHNDLR_V1 table
ENTRY_ TIME> 11332971000
7
MASSIVE DATA PURGE
WHERE CLAUSE
BAM_FACT_ FCT4VNT_V1
Where clause for retaining data in BAM_FACT_ FCT4VNT_V1 table
ENTRY_ TIME> 11247387600
8
MASSIVE DATA PURGE
WHERE CLAUSE
BAM_PT_PROC ESS_INST
Where clause for retaining data in BAM_PT_ PROCESS_INST table
PROCESS_ INST_ID> 63110
9
MASSIVE DATA PURGE
WHERE CLAUSE
BAM_PT_STEP _INST
Where clause for retaining data in BAM_PT_STEP_ INST table
PROCESS_ INST_ID> 63110
10
MASSIVE DATA PURGE
WHERE CLAUSE
BAM_PT_STEP _STAGE
Where clause for retaining data in BAM_PT_STEP_ STAGE table
PROCESSED_ FL ! = 1
11
SWAP OPS
DEGREE OF PARALLELISM
DEGREE OF PARALLELISM
Degree of parallelism (DOP) for MDL statements used by MDP
<NUMERIC_VALUE>
The PARAMETER_DSCR column describes each parameter, while the PARAMETER_VALUE column contains the value for each parameter.
The following table indicates how each value is set by Optimize or by you.
Row
Value
1
You set this value. It functions only with Oracle. In the OPERATION_MGR table, you can identify people to receive e-mail alerts when the Oracle purge operation completes or encounters an error. You identify the mail host to use in this row. For instructions, see Specifying People to Notify about the Oracle Purge Operation.
2-4
These rows have values you can change if necessary.
5
You can set this value. It controls the number of days retained in the OPERATION_LOG table. For information on the OPERATION_LOG table, see Viewing Purge Operation Events.
6-7
Calculated by Optimize based on the Business Days To Retain attribute. See Setting Data Purge Attributes for the Analytic Engine.
8-10
Calculated by Optimize based on the Days To Retain Processes attribute. See Setting Data Purge Attributes for the Analytic Engine.
11
You set this value. It only functions with Oracle. This parameter controls the maximum number of parallel processes for DML statements, which Massive Data Purge uses to retain data.
Note:
By default, this entry does not exist in OPERATION_PARAMETER. As a result, DML statements will not explicitly define a DOP value; i.e. deferred to Oracle database configuration.