E2109 Cmd Rej: Database maintenance is required            

The command failed because the system detects that:

• The database is incoherent (the command requires that the database be coherent).

• The levels of source databases, during a duplex backup or repair, are not identical on the active and standby OAM fixed disks.

• The database is corrupt. An audit has detected a mismatched checksum in a subset.

Recovery

1. Determine the status of the database. Enter the rept-stat-db command.
2. If the status of the database is corrupt, determine which subset is corrupt. Enter the aud-data:display=all command.
3. If the database is incoherent or corrupt, find the conditions shown in the output of the rept-stat-db command, and execute the appropriate command. Refer to Database Administration - System Management User's Guide for assistance.
   1. If the current partition of the fixed disk is coherent and the backup partition of the fixed disk is incoherent, enter the chg-db:action=backup:dest=fixed command.
   2. If the current partition of the fixed disk is coherent and the database on the removable drive is incoherent, enter the chg-db:action=backup:dest=remove command.
   3. If the backup partition of the fixed disk is coherent and the current partition of the fixed disk is incoherent, contact My Oracle Support. See My Oracle Support (MOS).
   4. If the database on the removable drive is coherent and the current partition of the fixed disk is incoherent, contact My Oracle Support. See My Oracle Support (MOS).
   5. If the backup and current partitions on the active fixed disk are coherent and the backup and current partitions on the standby fixed disk are incoherent, use the chg-db:action=repair command.
4. If a duplex backup or restore is being performed, verify that the level of the source databases residing on both the active and standby OAM fixed disks are identical.

   Note:

   The error message text is altered for this condition and says “Database repair is required.” When the required repair to make both databases identical is performed, continue with Step 5.

5. Re-enter the command that generated this error message.
   Contact My Oracle Support if this error message appears again. See My Oracle Support (MOS).