Information Life Cycle Management

Information Life Cycle Management  (sometimes abbreviated ILM) is basically a set of strategies for administering storage systems on computing devices.

ILM is the practice of applying certain policies to effective information management. It includes every phase of a "record" from its beginning to its end. And while it is generally applied to information that rises to the classic definition of a record (Records management), it applies to any and all informational assets. During its existence, information can become a record by being identified as documenting a business transaction or as satisfying a business need. In this sense ILM has been part of the overall approach of ECM Enterprise content management.

Oracle 12c is using this ILM with the help of newly introduced features:

1.  Heat Mapping:

http://prafulladeote.blogspot.in/2014/05/heat-map-fine-grained-data-usage.html

2.  Automatic Data Optimization:

http://prafulladeote.blogspot.in/2014/05/automatic-data-optimization-ado.html

Using these above 2 new features, we can use old low cost/speed storage effectively, which will again a part of cost saving. In this a Heat Map will keep a track of the data which is not in used/regularly updated. If the data is not getting updated/modified & is only required in database & can not be purged, ADO will move this data on the low cost storage, making room for new data which is again getting very frequently updated/modified.

Please refer above 2 URLs for more details & practical.

Heat Map: Fine-grained Data Usage Tracking

                Heat Map is an Oracle Database 12c feature that stores system-generated data usage statistics at the row and segment levels – information that can be used to automate the compression and movement of data in order to reduce storage costs, improve performance and optimize Oracle Database storage. Heat Map, used in conjunction with Automatic Data Optimization can automate compression and storage policies based on the usage of the data.

1. Segment level Heat Map tracks the time of last modification and access of tables and partitions.
2. Row level Heat Map shows modification times at the row level.

                Heat Map, once enabled, and automatically collects segment and row level statistics that can be used to define compression and storage policies which will be automatically maintained throughout the lifecycle of the data. Heat Map skips internal access done for system tasks -- automatically excluding Stats Gathering, DDLs or Table Redefinitions.

How to Enable Heat Map:

alter system set heat_map = on scope=both;

Online Data-file Movement

In earlier Version (Prior to 12c Release):

To move or rename a data file in earlier versions (9i,10g,11g) we used to perform the below steps.

a. Shutdown the database.

b. Rename the physical file on the OS using mv command on Linux/Unix.

c. Start the database in mount mode.

d. Issue the below command on sql prompt to rename the file within the Oracle dictionary.

ALTER DATABASE RENAME FILE < old_file_name/path>   to   <new_file_name/path>; 

     

                                                                 OR

ALTER DATABASE MOVE DATAFILE ‘< Source Path >‘ TO ‘< Destination Path >';

e. Open the database.

In Oracle 12c Release:

In order to rename the datafile in oracle 12c Release, there is no need to perform all above time consuming steps. life with oracle 12c is much easier. Just one step is enough. Also there is no downtime required in this activity.

ALTER DATABASE RENAME FILE < old_file_name/path>   to   <new_file_name/path>; 

                                                     

                                                                    OR

ALTER DATABASE MOVE DATAFILE ‘< Source Path >‘ TO ‘< Destination Path >';