4000000000000100 - RTDB Inconsistent

This message indicates one or more of the following conditions:

The real-time database for one or more Service Module cards is inconsistent with the current real-time database on the Active EPAP fixed disks
RTDBs detect that it is ahead of an ACTIVE PDBA that it just connected to (probably a PDBA switchover has occurred, or a restore from a backup of PDB with a previous db level)
RTDB timestamp of most recent level does not match the PDBAs record of that timestamp.

Recovery

Log in to the User Interface screen of EPAP A (see Accessing the EPAP GUI)
Check the banner information above the menu to verify that you are logged into the EPAP A that is reporting the problem.
If it is necessary to switch to EPAP B, click the Select Mate menu item.
From the menu, select RTDB>View RTDB Status to display status information about the RTDBs.

Figure 1 shows an example of two Inconsistent RTDBs.
Inconsistent RTDB Status

If one RTDB is inconsistent and the other is coherent in a mated pair setup, proceed to 4. If both RTDBs on an EPAP paired setup are inconsistent, reload from the nearest EPAP site with a coherent RTDB. If all RTDBs are inconsistent, additional steps may be required to reload one RTDB from PDB and backup the new RTDB, then restore the remaining RTDBs.
Verify the PDB information on the RTDB Status view is correct before continuing.
Before attempting to copy the RTDB, the EPAP A software must be stopped by doing the following:

CAUTION: If the software is not stopped as directed in 5.a through 5.c, the RTDB will become corrupted.
1. Select Process Control>Stop Software to stop the software.
  The following warning appears:
```
CAUTION: This action will stop all EPAP software processes, and will prevent the selected EPAP from updating the RTDB until the EPAP software is re-started (by executing the Start Software menu item).
```
2. On the Stop EPAP Software screen, make sure the following item on the screen is checked: Check if you want the software to automatically start on reboot.
3. Select the Stop EPAP Software button to stop the software.
4. Select Select Mate from the menu to return to the EPAP that is reporting the problem.
Select RTDB>Maintenance>Reload from Remote.
The screen shown in Figure 2 shows this function.
Reload RTDB from Mate EPAP
Make sure that the Mate radio button is filled in, as shown in Figure 2 and click the Begin RTDB Reload from Remote button.
Click the Reload button as shown in Figure 2.
When the reload has completed, start the software on EPAP A by doing the following:
1. Select Process Control > Start Software to start the software again.
  
  Make sure the following item on the screen is checked:
  
  Check if you want to start the PDBA software along with the EPAP software
2. Select the Start EPAP Software button to start the software.
If the problem persists, capture the log files on both EPAPs (see Saving Logs Using the EPAP GUI) and contact My Oracle Support (MOS).