nerdexam
Oracle

1Z0-060 · Question #179

In your database, the TBS PERCENT USED parameter is set to 60 and the TBS PERCENT FREE parameter is set to 20. Which two storage-tiering actions might be automated when using information Lifecycle…

The correct answer is C. The movement of some segments to a target tablespace with a higher degree of compression, on D. Setting the target tablespace to read-only after the segments are moved. Oracle ILM automated data movement (ADO) operates at the segment level and can automatically move qualifying segments to a higher-compression tablespace and set the target tablespace to read-only once movement completes.

New Features for Storage

Question

In your database, the TBS PERCENT USED parameter is set to 60 and the TBS PERCENT FREE parameter is set to 20. Which two storage-tiering actions might be automated when using information Lifecycle Management (ILM) to automate data movement?

Options

  • AThe movement of all segments to a target tablespace with a higher degree of compression, on a
  • BThe movement of some blocks to a target tablespace with a lower degree of compression, on a
  • CThe movement of some segments to a target tablespace with a higher degree of compression, on
  • DSetting the target tablespace to read-only after the segments are moved
  • ETaking the target tablespace offline after the segments are moved

How the community answered

(52 responses)
  • A
    6% (3)
  • B
    17% (9)
  • C
    69% (36)
  • E
    8% (4)

Why each option

Oracle ILM automated data movement (ADO) operates at the segment level and can automatically move qualifying segments to a higher-compression tablespace and set the target tablespace to read-only once movement completes.

AThe movement of all segments to a target tablespace with a higher degree of compression, on a

ILM moves only segments that match the defined policy criteria based on access heat maps, not all segments; moving every segment regardless of access patterns would negate the purpose of automated tiered storage management.

BThe movement of some blocks to a target tablespace with a lower degree of compression, on a

Oracle ILM ADO operates at the segment (object) level, not at the individual block level; block-level automated movement between tablespaces is not a supported action within the ILM storage tiering framework.

CThe movement of some segments to a target tablespace with a higher degree of compression, onCorrect

ILM evaluates each segment individually against the defined policy criteria - when TBS_PERCENT_USED (60%) is reached, only segments that meet the heat map activity thresholds are moved to a target tablespace with higher compression, not all segments indiscriminately.

DSetting the target tablespace to read-only after the segments are movedCorrect

Oracle ADO supports a post-movement action of setting the target tablespace to read-only, enforcing the tiered storage policy by preventing further writes to the colder, compressed tier after data migration completes.

ETaking the target tablespace offline after the segments are moved

After automated data movement, ILM sets the target tablespace to read-only status - not offline; taking a tablespace offline would render the moved data completely inaccessible to database users and applications.

Concept tested: Oracle ILM ADO automated storage tiering thresholds and post-move actions

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/vldbg/ilm-strategy-heatmap-ado.html

Topics

#ILM storage tiering#TBS_PERCENT_USED#automated data movement#tablespace compression

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 1Z0-060 Practice