How to identify the SEGMENT reported by dbms_space_admin.TABLESPACE_VERIFY

(Doc ID 887263.1)

Last updated on JANUARY 01, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.1 to 12.1.0.2 [Release 9.2 to 12.1]
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('USERS')

It generated a trace file with 2 affected segments:

Extent Map Entry Overlaps with Another Extent Map Entry
SegDBA: 0x0fc3e832 : ExtNo 3 UetDBA 0x2ec00091: ExtNbk: 32
SegDBA: 0x1000c8d0 : ExtNo 212 UetDBA 0x2ec00011: ExtNbk: 1280


The goal of this note is to identify the affected objects using the Relative Block Address (rdba) information.



Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms