Summary:
Make UNDO tablespace truncation crash safe without relying on a local marker file.
Problem:
UNDO tablespace truncation currently uses a local undo_space_number_trunc.log file to detect incomplete truncation after crash. This creates dependency on an external local file.
Proposed approach:
Persist “UNDO truncation in progress” state in the UNDO tablespace header itself. During crash restart, recover the state from the tablespace and roll forward the truncation.
Expected benefits:
• Crash-safe UNDO truncation
• Removes dependency on local marker files
• More self-contained recovery state
• Improved reliability during startup recovery
Summary:
Make UNDO tablespace truncation crash safe without relying on a local marker file.
Problem:
UNDO tablespace truncation currently uses a local undo_space_number_trunc.log file to detect incomplete truncation after crash. This creates dependency on an external local file.
Proposed approach:
Persist “UNDO truncation in progress” state in the UNDO tablespace header itself. During crash restart, recover the state from the tablespace and roll forward the truncation.
Expected benefits:
• Crash-safe UNDO truncation
• Removes dependency on local marker files
• More self-contained recovery state
• Improved reliability during startup recovery