How to identify the SEGMENT reported by dbms_space_admin.TABLESPACE_VERIFY
(Doc ID 887263.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.1 to 12.1.0.2 [Release 9.2 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Information in this document applies to any platform.
Goal
How to identify the SEGMENT reported by a trace file generated by
dbms_space_admin.TABLESPACE_VERIFY or dbms_space_admin.ASSM_TABLESPACE_VERIFY
When these procedures report an inconsistency, they generate a trace file with information related to the affected segments. Trace file example for an inconsistency related to Overlapped Extents in tablespace USERS:
execute dbms_space_admin.TABLESPACE_VERIFY('<Tablespace name>')
It generated a trace file with 2 affected segments:
The goal of this note is to identify the affected objects using the Relative Block Address (rdba) information.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Identify the Segment using DBA_SEGMENTS |
| Identify the Segment using DBA_EXTENTS |