Which three tasks can be automatically performed by the Automatic Data Optimization feature of
Information lifecycle Management (ILM)?
A.
Tracking the most recent read time for a table segment in a user tablespace
B.
Tracking the most recent write time for a table segment in a user tablespace
C.
Tracking insert time by row for table rows
D.
Tracking the most recent write time for a table block
E.
Tracking the most recent read time for a table segment in the SYSAUX tablespace
F.
Tracking the most recent write time for a table segment in the SYSAUX tablespace
Explanation:
*You can specify policies for ADO at the row, segment, and tablespace level when creating and
altering tables with SQL statements.
* (Not E, Not F)When Heat Map is enabled, all accesses are tracked by the in-memory activity
tracking module. Objects in theSYSTEMandSYSAUXtablespaces are not tracked.
* To implement your ILM strategy, you can use Heat Map in Oracle Database to track data access
and modification.
Heat Map provides data access tracking at the segment-level and data modification tracking at the
segment and row level.
* To implement your ILM strategy, you can use Heat Map in Oracle Database to track data access
and modification. You can also use Automatic Data Optimization (ADO) to automate the
compression and movement of data between different tiers of storage within the database.
Reference: Automatic Data Optimization with Oracle Database 12c
with Oracle Database 12c
D – FALSE – not tracking on block level but on row, segment
E, F – FALSe
Objects in the SYSTEM and SYSAUX tablespaces are not tracked.
http://docs.oracle.com/database/121/VLDBG/part_lifecycle.htm#VLDBG1338
The Heat Map tracks data modification times at the block level and data access statistics at the segment level.
Following is an outline of how ADO works:
1. Enable the Heat Map, which tracks the block- and segment-level activity, by activating the collection of segment access and row and segment modification.
2. Create ADO policies on the segments.
3. Customize the scheduling of the ADO policy evaluation. By default, segmentlevel statistics are evaluated and executed during the maintenance window.
4. View the ADO execution results using the DBA_ILM_EVALUATIONDETAILS and DBA_ILMRESULTS views.
5. Verify that the blocks or the segments were compressed, using the COMPRESSION_STAT$ table, and verify whether the segments were moved to the correct tablespace you defined in the ADO policy.
See: OCP Upgrade to Oracle Database 12c Exam Guide (Exam 1Z0-060)
Heat Map
Heat Map is an Oracle Database 12c feature that stores system-generated data usage statistics at the block 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 tiering policies based on the actual usage of the data. Segment level Heat Map tracks the time of last modification and access of tables and partitions. Row level Heat Map tracks modification times for individual rows (aggregated to the block level). The statistics collected 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.
See: http://www.oracle.com/technetwork/database/enterprise-edition/index-090321.html
A,B,D.
ABC looks better if I have to choose 4 I will choose D as 4th option
A B and C appears to be more logical.
I would choose D instead of C (Insert time is not separately tracked but modification time is . Modification covers inserts, updates, deletes. ).
ABD
D:
SELECT segment_name, tablespace_name, block_id, writetime
FROM table(dbms_heat_map.block_heat_map
(‘HR’,’EMPLOYEES’,NULL,8,’ASC’));
ABD
example,which proves D:
SELECT segment_name, tablespace_name, block_id, writetime
FROM table(dbms_heat_map.block_heat_map
(‘HR’,’EMPLOYEES’,NULL,8,’ASC’));
ABD looks more logical as changes for read write is actually tracked at block level even some time we say at row level. which means all rows in a block.
https://docs.oracle.com/database/121/REFRN/refrn10342.htm#REFRN10342
A,B,D
ABD
Tracking is for table segment and row levels only and not at the block level. Hence we can rule out D. Objects in the SYSTEM and SYSAUX tablespaces are never tracked. E and F are ruled out.
A,B,C are correct answers.
The scope of work for Activity tracking and Automatic Data Optimization (ADO) is
— Tablespace leve
— Group level
— Segment level (Table,partition,sub-partition & clustered table)
— Row level
No block level tracking
And the operations to track is:
— Creation
— Access
— Modification
So A,B,C are correct answers.
http://www.oracle.com/technetwork/database/enterprise-edition/automatic-data-optimization-wp-12c-1896120.pdf
Data modification times are tracked at the row level and aggregated to the block level, and
modification times, full table scan times, and index lookup times are tracked at the segment level.
Because aggregated to the block level so: D is right.
C is wrong because we cannot identify is the modification is insert or update.
ABD
I think D because :
http://www.oracle.com/technetwork/issue-archive/2015/15-jan/o15ocp-2398998.html
Which two actions will be automatically supported in your session?
a. Creation of Automatic Data Optimization policies based on Heat Map statistics
b. Creation of Automatic Data Optimization policies based on user-defined conditions
c. Tracking of segment-level reads and writes
d. Tracking of block-level reads and writes
e. Tracking of index lookups and full-table scans
The correct answers are C and E.
Answer C is correct because enabling Heat Map causes the database to track read and write access of segments. Answer E is correct because enabling Heat Map causes the database to collect statistics on all reads performed on objects in a session. Answers A and B are incorrect because Heat Map must be enabled at the system level to allow usage of Automatic Data Optimization policies. Answer D is incorrect because Heat Map tracks only writes but not reads at the block level.
Dear Myself,
how many questions did u get from this question bank ???
LC
ABC – my certification preparation book clearly tells:
… under which data modifications are tracked at the row level (so C). Besides managing row level statistics the database also tracks segment-level access (so A) and modifications (so B).
ABD are the correct choices
Heatmap/ILM tracks writes to block level
Look at following
DBA Table: DBA_HEAT_MAP_SEGMENT
– This tracks read, write, fulltablescan and lookup times
DBA functions
dbms_heat_map.block_heat_map: track block ID and Writetime
dbms_heat_map.extent_heat_map:Tracks min/max/avg writetimes.
ABD
Block level track writetime with dbms_heat_map.block_heat_map function
segment read and write with DBA_HEAT_MAP_SEGMENT view
ABD
C isn’t 100% correct because of the word “insert” (should be “change” or “write”).
But neither is D fully true due to the word “track” – for ILM nothing is tracked at block level; the dbms_heat_map.block_heat_map function just derives its return value from the row values in het block.
I think ABC is the intended answer
New answers
A. tracking the most recent read time for a table segment in a user tablespace
B. tracking the most recent write time for a table segment in a user tablespace
C. tracking insert time by row for table rows
D. tracking the most recent write time for each block in a table segment
E. tracking the most recent read time for a table segment in the sysauxtablespace
F. tracking the most recent write time for a table segment in the sysauxtablespace
A,B,D
AB & D is correct.
http://www.oracle.com/technetwork/issue-archive/2015/15-jan/o15ocp-2398998.html
Which two actions will be automatically supported in your session?
a. Creation of Automatic Data Optimization policies based on Heat Map statistics
b. Creation of Automatic Data Optimization policies based on user-defined conditions
c. Tracking of segment-level reads and writes
d. Tracking of block-level reads and writes
e. Tracking of index lookups and full-table scans
The correct answers are C and E.
Answer C is correct because enabling Heat Map causes the database to track read and write access of segments. Answer E is correct because enabling Heat Map causes the database to collect statistics on all reads performed on objects in a session. Answers A and B are incorrect because Heat Map must be enabled at the system level to allow usage of Automatic Data Optimization policies. Answer D is incorrect because Heat Map tracks only writes but not reads at the block level.