Failures on the RACF database

In the unlikely event of I/O failures against the device upon which the RACF® database resides, as described in Quiescing database I/O activity, or in the case of RACF database corruption, one of the following situations might apply:

The primary database is in error; the backup database is unaffected.
The backup database is in error; the primary database is unaffected.
The primary database is in error; there is no backup database.
Both primary and backup databases are in error.

Sample recovery procedures are provided below for each situation.

In the event of a failure due to insufficient space in the RACF database, you can use the IRRUT400 utility to copy the data set having the problem to a larger data set, or, if fragmentation alone is the problem, to another data set the same size. As the utility copies the data set, it rebuilds it and repairs any fragmentation. See Monitoring the usable space in your RACF database for information on how to foresee and prevent an "insufficient space" condition.