Which two statements about Automatic Data Optimization (ADO) are true?
A.
ADO policies can automatically compress data when it qualifies.
B.
ADO policies can automatically move segments when necessary.
C.
ADO is not dependent on Heat Map, and works even if Heat Map is disabled.
D.
You cannot compress at block level, but you can compress at segment level.
E.
You can compress at row level only for QUERY LOW.
BC
AB
AB
not C because ADO depents on heat maps
see:
Oracle Advanced Compression with Oracle Database 12c
ORACLE WHITE PAPER
I believe it’s A,B
Answer : AB
Explanation :
http://www.oracle.com/technetwork/database/options/compression/advanced-compression-wp-12c-1896128.pdf
In Oracle Database 12c, several new features have been added to the Oracle Advanced Compression option
which enhances the storage management capabilities of Oracle Database. Heat Map automatically tracks
modification and query timestamps, providing detailed insights into how data is being accessed. Automatic Data
Optimization (ADO) automatically moves and compresses data based on the information collected by Heat Map.
Together, these capabilities help to implement Information Lifecycle Management (ILM) strategies.
Heat Map and ADO make it easy to use existing innovations in Oracle Database compression technologies,
which can help reduce the cost of managing large amounts of data, while also improving application and
database performance.
Heat Map is a new Oracle Database feature that collects usage information at the block and segment levels. At the segment level, Heat Map tracks the timestamps of the most recent modification and query of each table and partition in the
database. At the block level, Heat Map tracks the most recent modification timestamp. These timestamps are used by Automatic Data
Optimization to define compression and storage policies which will be automatically maintained throughout the lifecycle of the data.
Heat Map skips internal operations done for system tasks — automatically excluding Stats Gathering, DDLs, Table Redefinitions and
similar operations. In addition, Heat Map can be disabled at the session level, allowing DBA’s to exclude manual maintenance, avoiding
pollution of Heat Map data.
With the data collected by Heat Map, Oracle Database can automatically compress each partition of a table independently based on
Heat Map data, implementing compression tiering. This compression tiering can use all forms of Oracle table compression, including:
Advanced Row Compression and all levels of Hybrid Columnar Compression (HCC) if the underlying storage supports HCC. Oracle
Database can also compress individual database blocks with Advanced Row Compression based on Heat Map data.
Example ADO Policies:
In this first example, a segment-level ADO policy is created to automatically compress the entire table after there have been no
modifications for at least 30 days, using Advanced Row Compression:
ALTER TABLE employee ILM ADD POLICY ROW STORE COMPRESS ADVANCED SEGMENT
AFTER 30 DAYS OF NO MODIFICATION;
In this next example, a row-level ADO policy is created to automatically compress blocks in the table, after no rows in the block have
been modified for at least 3 days, using Advanced Row Compression:
ALTER TABLE employee ILM ADD POLICY ROW STORE COMPRESS ADVANCED ROW AFTER 3 DAYS OF
NO MODIFICATION;