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…

Question

Options

• AThe movement of all segments to a target tablespace with a higher degree of compression, on
• BSettingthetargettablespacetoread-only
• CThe movement of some segments to a target tablespace with a higher degree of compression,
• DSetting the target tablespace offline
• EThe movement of some blocks to a target tablespace with a lower degree of compression, on

• A
  12% (2)
• B
  76% (13)
• D
  6% (1)
• E
  6% (1)

Explanation

In Oracle's ILM Automatic Data Optimization (ADO), the TBS_PERCENT_USED and TBS_PERCENT_FREE thresholds act as triggers: once a tablespace exceeds 60% used or drops below 20% free, ADO can fire storage-tiering policies. B is correct because setting a cold tablespace to read-only is a supported ADO action - it signals the data is no longer actively written and can be safely tiered. C is correct because ADO selects eligible segments based on Heat Map access statistics and moves them to a more-compressed tablespace; it never blindly moves every segment.

A is wrong because ILM never moves all segments - only those identified as "cold" by the Heat Map, making "all segments" factually inaccurate. D is wrong because taking a tablespace offline makes its data completely inaccessible, which is not a valid or safe ILM action. E is wrong on two counts: ILM operates at the segment level (not individual blocks), and tiering always moves toward higher compression to reclaim space - moving to lower compression defeats the purpose.

Memory tip: Think "ILM = selective + safe." It moves some (not all) segments to higher compression, and its safest tablespace-level action is read-only (not offline, which would break access). If an answer says "all," "blocks," "lower compression," or "offline," eliminate it.

No community discussion yet for this question.