Customer Responsibilities - Post Go Live
Oracle recommends that customers configure batch job streams to run the following batch jobs on a regaular basis to support ILM:
• ILM Automation - Add Partition (K1-ILMAD): This process creates partitions for ILM-enabled tables for the next month. The process splits the maximum partition into the next month (current month +1) and copies the table stats from the previous month to the new partition and the maximum partition. This is critical to ensuring performance when the next month begins. This must be run once per month but can be run more frequently without causing harm.
K1-ILMAD Sample Parameters:
Note: This batch job should be run with DIST-THD-POOL batch parameter with value of NOCACHE.
• ILM Automation - New Subretention Value (F1-ILMSV): This process creates subpartitions for Initial Measurements, Activities, and Device Events, based on specific sub-retention values defined in the ILM Configuration - MDM Sub-retention master configuration. Note that Sub-retention is optional. If used, this should be run at the same time as K1-ILMAD.
• ILM Automation - Measurement Compression (F1-ILMMC): This process changes the compression level from Advanced to Hybrid Columnar for Measurement data that is at least two months old which results in significant disk space saving. This compression job reorganizes the data and improves query performance. Parameters used by this process include: Table Owner, Degree of Parallelism, and Estimated Time Limit. This batch control should be part of monthly batch job streams so that its run once per month and during off peak / non-critical hours.
F1-ILMMC Sample Parameters:
Note: This batch job should be run with DIST-THD-POOL batch parameter with value of NOCACHE.
• ILM Automation - Non-Measurement Compression (F1-ILMNC): This process changes the compression level from Advanced to Hybrid Columnar for non-Measurement partitions at least two months old and results in significant disk space savings. Parameters used by this process include: Table Owner, Maintenance Object Codes (used to define specific maintenance objects for compression), Degree of Parallelism, and Estimated Time Limit. This batch control should be part of monthly batch job streams so that its run once per month and during off peak / non-critical hours.
F1-ILMNC Sample Parameters:
Note: This batch job should be run with DIST-THD-POOL batch parameter with value of NOCACHE.
• ILM Crawler Initiator (F1-ILMIN): The ILM Crawler Initiator process initiates the individual ILM Crawler batch controls as defined by the ILM Crawler Batch Control and ILM Retention Period in Days options on each maintenance object. his batch control should be part of monthly batch job streams so that its run once per month and during off peak / non-critical hours.
Individual ILM crawler batch controls invoke eligibility algorithms to determine if records are ready to be archived. Many maintenance objects use the ILM Eligibility Based on Status (F1-ILMELIG) algorithm to determine eligibility.
F1-ILMIN Sample Parameters:
Note: This batch job should be run with DIST-THD-POOL batch parameter with value of NOCACHE.
• To copy the archived data to Oracle Cloud Object Storage and to drop the partition, customer is required to raise a Service Request with Oracle Support.
Refer to Information Lifecycle Management in the Administrative User Guide for more details regarding ILM.