REPAIR

The REPAIR online utility repairs data. The data can be your own data or data that you would not normally access, such as space map pages and index entries.

You use REPAIR to replace invalid data with valid data. Be extremely careful when using REPAIR. Improper use can damage the data even further.

You can use the REPAIR utility to:

Test database definitions (DBDs)
Repair DBDs
Reset a pending status on a table space or index
Verify the contents of data areas in table spaces and indexes
Replace the contents of data areas in table spaces and indexes
Delete a single row from a table space
Produce a hexadecimal dump of an area in a table space or index
Delete an entire LOB from a LOB table space
Dump LOB pages
Rebuild object descriptors (OBDs) for a LOB table space
Manage version numbers
Turn on or off Persistent Read Only (PRO) restricted status for table space partitions
Update the CURRENT_VERSION or OLDEST_VERSION column of the SYSIBM.SYSTABLESPACE table when the data in the table space is at a different versions from the versions that are recorded in the catalog.

Output

The output from the REPAIR utility can consist of one or more modified pages in the specified DB2® table space or index and a dump of the contents.

Authorization required

To execute this utility, you must use a privilege set that includes one of the following authorities:

REPAIR privilege for the database
DBADM or DBCTRL authority for the database. If the object on which the utility operates is in an implicitly created database, DBADM authority on the implicitly created database or DSNDB04 is required.
DATAACCESS authority
SYSCTRL or SYSADM authority

An ID with installation SYSOPR authority can also execute REPAIR, but only on a table space in the DSNDB01 or DSNDB06 database.

To execute REPAIR with the DBD option, you must use a privilege set that includes SYSADM, SYSCTRL, or installation SYSOPR authority.

REPAIR should be used only by a person that is knowledgeable in DB2 and your data. Grant REPAIR authorization only to the appropriate people.

Execution phases of REPAIR

The phases for REPAIR are:

Phase: Description
UTILINIT: Performs initialization
REPAIR: Repairs data
UTILTERM: Performs cleanup

Syntax and options of the REPAIR control statement
The REPAIR utility control statement, with its multiple options, defines the function that the utility job performs.
Before running REPAIR
Certain activities might be required before you run the REPAIR utility, depending on your situation.
Resetting table space status
In most cases, resetting the COPY-pending restriction by taking a full image copy is preferable to using REPAIR. This is because RECOVER cannot be executed successfully until an image copy has been made.
Resetting index space status
Running COPY INDEXSPACE to reset the informational COPY-pending status is preferable to using the REPAIR utility to reset the status.
Repairing a damaged page
You can use the REPAIR utility to repair a damaged page.
Repairing DBDs
You can check and repair database definitions (DBDs) in the catalog and directory by using the REPAIR utility with the DBD statement.
Locating rows by key
If you use LOCATE TABLESPACE KEY, a number of rows might satisfy the condition. In this case, REPAIR returns only the RIDs of the rows and does not perform any VERIFY, REPLACE, DELETE, or DUMP actions which might be coded in that LOCATE block.
Using VERIFY with REPLACE and DELETE operations
If any data area does not contain the value that is required by a VERIFY statement, all REPLACE and DELETE operations in the same locate block are inhibited. VERIFY and REPLACE statements that follow the next LOCATE statement are not affected.
Repairing critical catalog table spaces and indexes
An ID with a granted authority receives message DSNT500I RESOURCE UNAVAILABLE, while trying to repair a table space or index in the catalog or directory if table space DSNDB06.SYSDBASE or DSNDB06.SYSUSER is unavailable.
Termination or restart of REPAIR
You can terminate the REPAIR utility, but you cannot restart the REPAIR utility.
Review of REPAIR output
The output from the REPAIR utility can consist of any modified pages in the specified DB2 table space or index. Alternatively, the REPAIR utility can produce a complete dump of the content of the table space.
After running REPAIR
Certain activities might be required after you run the REPAIR utility, depending on your situation.
Sample REPAIR control statements
Use the sample control statements as models for developing your own REPAIR control statements.

Parent topic: DB2 online utilities