Maintenance Batch Details
The Maintenance batch configures and creates table partitions for Common Staging Area and Transaction Monitoring business tables. This batch is run to enhance performance and maintainability.
This batch is run to enhance performance, maintainability and to support archival/retention (planned for future release) implementation.
Note:
- The Maintenance batch creates the partition on FIC_MIS_DATE and DATA ORIGIN (wherever applicable). Oracle will internally handle auto-partition creation on FIC_MIS_DATE. You only need to provide Data Origin as an input parameter.
- This out of box batch should only be used during the Maintenance window and should not be copied or customized.
- Execution of this batch is mandatory before any other batches are executed.
- Skipping this Maintenance batch may impact performance and batch execution.
To run the Maintenance batch in an existing or upgrading implementation, you must provide a downtime maintenance window and run the Maintenance batch so that historical business and staging data is partitioned. To add a new data origin at another time, run the Maintenance batch in the downtime maintenance window, giving the new data origin as the input parameter.
New implementations should run the Maintenance batch after installation with the respective data origin as input to create partitions. To add a new data origin at another time, run the Maintenance batch in the downtime maintenance window, giving the new data origin as the input parameter.
Table 19-53 Maintenance Batch Details
Sequence | Tasks for Maintenance Batch | Jobs for Maintenance Batch | Pipelines for Maintenance Batch |
---|---|---|---|
1 | StartBatch | Not Applicable | Not Applicable |
2 | Partition_Maintenance | Partition Maintenance | Partition Maintenance |
3 | EndBatch | Not Applicable | Not Applicable |