My Oracle Support Banner

DBMS_SPACE_ADMIN.ASM_TABLESPACE_VERIFY and TABLESPACE_VERIFY to Check EXTENT Inconsistency (Doc ID 2107720.1)

Last updated on AUGUST 01, 2019

Applies to:

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
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Purpose

The purpose of this document is to describe the different corruptions / inconsistencies reported by package DBMS_SPACE_ADMIN in procedures ASM_TABLESPACE_VERIFY with the ts_option=>dbms_space_admin.TS_VERIFY_BITMAPS and TABLESPACE_VERIFY.

For now this document does not detail the resolution of such inconsistencies.

This document also describes the lock acquired in versions 10g or greater. 

Scope

 

Details

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
Purpose
Scope
Details
 DBMS_SPACE_ADMIN Tablespace Verify
 Symptoms of Extent Inconsistency
 How to execute Tablespace Verify to Identify Extent Inconsistency?
 dbms_space_admin.assm_tablespace_verify
 dbms_space_admin.tablespace_verify
 How long does it take to run Tablespace Verify to Identify Extent Inconsistency?
 Locks acquired.  Can Tablespace Verify be run while there are concurrent DDL or DML?
 10g ONLY: Tablespace Verify May Report FALSE Inconsistency
 Description of Inconsistencies Reported by Tablespace Verify
 Extent Map Entry Corrupt
 Extent Map Entry Marked Partially Free in BitMap
 BitMap entry partially used with no Extent Map entry
 Extent Map Entry Overlaps with Another Extent Map Entry
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.