4000000000004000 - RTDB Reload Is Required

This message indicates that the RTDB reload is required for one of the following reasons:

• The PDB Birthday on the EPAP reporting the error does not match the mate EPAP’s PDB Birthday.

• The transaction logs did not contain enough information to resynchronize the databases (the transaction logs may be too small).

Caution:

If both sides are reporting this error, contact My Oracle Support (MOS).

If only one side is reporting this error, use the following procedure.

Recovery

1. Log in to the User Interface screen of the EPAP (see 4000000000004000 - RTDB Reload Is Required)
2. Check the banner information above the menu to verify that you are logged into the EPAP that is reporting the problem.
   If it is necessary to switch to the problem EPAP, click the Select Mate menu item.
3. From the menu, select RTDB>View RTDB Status to display status information about the RTDBs.
   Figure 4-5 shows an example.

   Figure 4-5 RTDB Status

   
4. If the RTDB birthdays for both the local RTDB and the mate RTDB are the same, you can copy the mate’s RTDB to the local RTDB.
   If the RTDB birthdays are not the same, go to step 5.
5. Before attempting to copy the RTDB, you must stop the software on both sides by doing the following:

   Caution:

   If you do not stop the software on both sides, as directed in substeps 5a through 5c, the RTDBs 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.
   5. Repeat substeps 5.a through 5.c on the other side.
   6. Select Select Mate from the menu to return to the EPAP that is reporting the problem.
6. Verify that you are logged in to the side that is reporting the problem.
7. Select RTDB>Maintenance>Reload from Remote.
   The screen shown in Figure 4-6 shows this function.

   Figure 4-6 Reload RTDB from Mate EPAP

   
8. Make sure that the Mate radio button is filled in, as shown in Figure 4-6 and click the Begin RTDB Reload from Remote button.
9. When the reload has completed, start the software on both sides 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 (this item applies only if performing this procedure on Side A):

      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.
   3. Select Select Mate from the menu.
   4. Repeat substeps 9.a and 9.b on the other side.
10. If you wish to increase the size of the transaction logs, select PDBA> Maintenance > Transaction Log Params > Change Params as shown in Figure 4-7.

    Figure 4-7 Changing Transaction Log Parameters

    
11. If the problem persists, contact My Oracle Support (MOS).