6000000000000020 - Standby PDBA Falling Behind

This is an indication that there is a congestion condition affecting updates to the standby PDBA. The amount of time between an update being committed in the Active PDB and the same update being committed in the Standby PDB has reached an unacceptable level.

The EPAP attempts to automatically recover from this situation. This error can result from one of the following conditions:

• Provisioning activity is very heavy

• The provisioning network is experiencing errors or latency

• Server maintenance functions (such as backups, restores, imports, exports, etc) are occurring

Recovery

1. Periodically, verify that the level of the standby PDBA is catching up by selecting PDBA>View PDBA Status and comparing the Level of the Standby PDBA (on EPAP A in the example shown in Figure 4-15) to the Level of the Active PDBA (on EPAP B in the example).

   Figure 4-15 View PDBA Status

   
2. If the problem persists for more than two hours, run savelogs (see Saving Logs Using the EPAP GUI), and contact My Oracle Support for assistance.
3. Login to the User Interface screen of the EPAP GUI as any user who has permission to use the Set Log Levels menu item.
4. Select PDBA> Maintenance> Logs> Set Log Levels.
   The Set PDBA Log Info Levels screen displays, as shown in Figure 4-16.

   Figure 4-16 Set PDBA Log Info Levels

   
5. Verify that the Log Levels match the Log Levels of the MPS on the mated EAGLE STP.
   Figure 4-16 shows the usual settings. Correct log levels if necessary.
6. If adjustments are necessary, it is recommended that the Command Log debug level and the Debug Log debug level are lowered before adjusting the Error Log debug level.