The ILM features of the Oracle Database are used in the Oracle Utilities ILM capability to implement the technical side of the solution. In Oracle 12, two new facilities were added to the already available ILM features to make the implementation of ILM easier. These features are Automatic Data Optimization (ADO) and Heat Map.
The Heat Map feature allows Oracle itself to track the use of blocks and segments in your database. Everytime a program or user touches a row in the database, such as using SELECT, UPDATE or DELETE SQL statements, Heat Map records that it was touched. This information is important as it actually helps profiles the actual usage of the data in your database. This information can be used by Automatic Data Optimization. The Heat Map is disabled by default and requires a database initialization parameter to be changed.
Automatic Data Optimization is a facility where DBA's can set ILM rules, known as Policies, to perform certain ILM actions on the data. For example: If the data is not touched, using Heat Map data, within X months then COMPRESS it to save space. If the ILM_ARCH_SW is set to Y, move the data to partition X. There are a lot of combinations and facilities in the ADO rules to allow the DBA's flexibility in their rules. ADO allows DBA's to specify the rules and then supplies a procedure that can be scheduled, at the convenience of the site, to implement the rules.
ADO and Heat Map are powerful data management tools that DBA's should get use to. They allow simple specification of rules and use features in the database to allow you to manage your data.
For more information about Heat Map and ADO refer to the following information:
- Heat Map, Automatic Data Optimization and ILM with Oracle Database
- Automatic Data Optimization whitepaper
- Oracle VLDB Guide - Includes advice on Partitioning and Time Based Data Management (ADO/HeatMap).
- Enabling and Disabling Heat Map
- Using Oracle Enterprise Manager for Managing ADO and Heat Map
- Limitations and Restrictions with ADO and Heat Map (Note: In Oracle Database 12.1, you cannot use ADO/HeatMap on a multi-tenant database. This is supported in Oracle 12.2).
- Video: Exploring Oracle 12c ADO Features
- Video: Manage ADO from Oracle Enterprise Manager Cloud Control
- Video: Manage Compression from Oracle Enterprise Manager Cloud Control
- ILM Planning Guide (Doc Id: 1682436.1)
- Oracle Training Course: Oracle Database 12c R1: New Features for Administrators Ed 2 (covers ADO and Heat Map)
- Oracle Training Course: Oracle Database 12c: Implement Partitioning Ed 1