10009 - Config and Prov db not yet synchronized

Alarm Group:

REPL

Description:

The configuration and provisioning databases are not yet synchronized. The 10009 alarm raises when DB re-initialization is attempted but fails. The re-initialization usually happens when transitioning to A state (one of the procmgr states, can get it from the pl command). DB re-initialization fails because the remote server is not in the correct state, for example, it is not in the OOS state.

This alarm can also be observed during some DSR patch installations after the DB replication is inhibited. As long as this alarm is cleared (NOT stuck) after DB replication is allowed, it is normal behavior and we expect to see the 10009 alarm when applying a patch.

Severity:

Critical

Instance:

N/A

HA Score:

Failed

Auto Clear Seconds:

This alarm does not autoclear.

OID:

oAGTCfgProvDbNoSync

Cause:

The 10009 alarm raises when DB re-initialization is attempted but fails. The re-initialization usually happens when transitioning to A state (one of the procmgr states, can get it from pl command). DB re-initialization fails because the remote server is in the incorrect state. For example, it is not in the OOS state.

This alarm also raises during a DSR patch installation after the DB replication is inhibited. As long as this alarm is cleared (NOT stuck) after DB replication is allowed, it is normal behavior andwe expect to see the 10009 alarm when applying a patch.

Diagnostic Information:

Perform the following to diagnose the alarm:

• Examine the /var/TKLC/appw/logs/Process/apwSoapServer.log file on primary NO and possibly the remote server to investigate the reasons for failure.
• Software release information.

Recovery:

1. Monitor the replication status by navigating to Status & Manage > Replication GUI.
2. If alarm persists immediately after an upgrade, reboot the server once using the sudo init 6 command on the effected server.
3. If alarm persists for more than one hour, it is recommended to contact My Oracle Support.