We are discussing the management of Oracle Database 12c in Oracle Enterprise Manager 12c. In our previous blog post on this topic, we were exploring the different tabs in the Performance Hub of Enterprise Manager Database Express 12c. Let us now look at Information Lifecycle Management (ILM) in Database 12c, and how Enterprise Manager helps with that.
Oracle Database 12c has an excellent feature known as Information Lifecycle Management (ILM) which is now fully automated in moving data between different storage, depending on data age and access. The Heat Map and Automatic Data Optimization (ADO) features of Database 12c can be used to implement your ILM strategy, along with the Partitioning, Advanced Compression, and Hybrid Columnar Compression (HCC) options/features of the Oracle Database.
The "Heat Map" feature automatically tracks access to segments (tables and partitions) and rows and blocks. The ADO feature allows you to define policies at the tablespace, table, partition, or row level. The policies contain conditions and associated actions.
The conditions are based on the data collected by Heat Map, and the actions can either be storage tiering (move the segment to another tablespace) or compression tiering (move the segment or block to a different level of compression).
The actual syntax of setting these ADO policies is not complex, but in totality, setting up many different ADO policies for storage tiering or compression tiering manually at the command line, and keeping track of those policies manually by a DBA, would work out as a complex task.
To alleviate that kind of task, Enterprise Manager would be very useful. Database 12c DBAS would want to use Enterprise Manager for this purpose.
More on the use of Enterprise Manager for ILM in the next blog post.
This blog post was originally published at this link.
No comments:
Post a Comment