Inspect Automatic Undo Management - Exercise
Objective: Replace the legacy manual rollback-segment task with an Oracle AI Database 26ai undo configuration review.
Use a lab CDB administrator account with access to the listed views. This is a read-only exercise. Do not create individual rollback segments or change undo mode. In a CDB, automatic undo management is required; local versus shared undo is a separate CDB configuration choice.
Instructions
- In CDB$ROOT, inspect
UNDO_MANAGEMENT and the LOCAL_UNDO_ENABLED database property. Explain both values without assuming local undo is enabled.
- List undo tablespaces with their container IDs from the root. Identify the active undo tablespace in an open application PDB if the CDB uses local undo; otherwise explain that shared undo is managed in the root.
- Explain why CREATE ROLLBACK SEGMENT and ROLLBACK_SEGMENTS are inappropriate for this exercise.
- Explain what UNDO_RETENTION and retention guarantee mean, including the space/transaction tradeoff. Submit queries and redacted observations, or a labeled expected-outcome plan.
Self-assessment: 20 points
Compare your response with the model solution. This page does not automatically grade free-text answers.
- Root/container and automatic undo checks (5 points).
- Local/shared distinction and active tablespace review (5 points).
- Replacement of manual rollback-segment management (5 points).
- Retention and space tradeoff with truthful observations (5 points).