About the DBMS_REPAIR Package

This section describes the procedures contained in the DBMS_REPAIR package and notes some limitations and restrictions on their use.

DBMS_REPAIR Procedures

The following table lists the procedures included in the DBMS_REPAIR package.

Procedure Name	Description
`ADMIN_TABLES`	Provides administrative functions (create, drop, purge) for repair or orphan key tables. Note: These tables are always created in the `SYS` schema.
`CHECK_OBJECT`	Detects and reports corruptions in a table or index
`DUMP_ORPHAN_KEYS`	Reports on index entries that point to rows in corrupt data blocks
`FIX_CORRUPT_BLOCKS`	Marks blocks as software corrupt that have been previously identified as corrupt by the `CHECK_OBJECT` procedure
`REBUILD_FREELISTS`	Rebuilds the free lists of the object
`SEGMENT_FIX_STATUS`	Provides the capability to fix the corrupted state of a bitmap entry when segment space management is `AUTO`
`SKIP_CORRUPT_BLOCKS`	When used, ignores blocks marked corrupt during table and index scans. If not used, you get error `ORA-1578` when encountering blocks marked corrupt.

These procedures are further described, with examples of their use, in "DBMS_REPAIR Examples".

DBMS_REPAIR procedures have the following limitations:

Tables with LOB datatypes, nested tables, and varrays are supported, but the out of line columns are ignored.
Clusters are supported in the SKIP_CORRUPT_BLOCKS and REBUILD_FREELISTS procedures, but not in the CHECK_OBJECT procedure.
Index-organized tables and LOB indexes are not supported.
The DUMP_ORPHAN_KEYS procedure does not operate on bitmap indexes or function-based indexes.
The DUMP_ORPHAN_KEYS procedure processes keys that are no more than 3,950 bytes long.