This section describes the product approach to implementing ILM for its maintenance objects (MOs).
Age is the starting point of the ILM product implementation for some of its high volume data. In general "old" records are considered eligible to be archived. In the product solution, maintenance objects (MOs) that are enabled for ILM have an ILM date on the primary table and the date is set to the record's creation date. For implementations that want to use ILM to manage the records in the MO, the ILM date is used for defining partitions for the primary table.
However, there are cases where a record's age is not the only factor in determining whether or not it is eligible to be archived. There may be some MOs where an old record is still 'in progress' or 'active' and should not be archived. There may be other MOs where certain records should never be archived. To evaluate archive eligibility using information other than the ILM date, the ILM enabled MOs include an ILM Archive switch that is used to explicitly mark records that have been evaluated and should be archived.
Evaluating records to determine their archive eligibility should still occur on “old” records. The expectation is that a large percentage of the old records will be eligible for archiving. The small number that may be ineligible could be updated with a more recent ILM date. This may cause the records to move into a different partition and can delay any further evaluation of those records until more time has passed.
The decision of how old a record is has to be performed before it is evaluated for archive eligibility. This can be determined by a system-wide setting, or uniquely for each maintenance object.
Referential Integrity: The recommended partitioning strategy for child tables in a maintenance object is referential partitioning. In order to implement this, database referential integrity features must be enabled. For information about the process to implement referential integrity, see the Oracle Utilities Application Framework: Database Administration Guide.
Partitioning: This provides a way in which the data can segregate into multiple table partitions and will help in better manageability of the lifecycle of the data. For information about partitioning, see the Oracle Utilities Application Framework: Database Administrator’s Guide.
Special Table Columns: Maintenance objects that support ILM include two specific columns: ILM Archive Switch (ILM_ARCH_SW) and ILM Date (ILM_DT).
Maintenance Object Options: There are MO options that include configuration related to ILM.
Master Configuration: An ILM master configuration record defines system wide ILM information.
Batch Processes: Batch processes are defined to execute the ILM eligibility algorithm.
ILM Algorithm: Each maintenance object that is configured for ILM defines an eligibility algorithm that executes the logic to set the ILM Archive switch appropriately.
Copyright © 2000, 2015, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.19.2015 16:18:51 [F1_1424305131000]