31102 - Database replication from master failure
- Alarm Group:
- REPL
- Description:
- Database replication from a master database has failed. This alarm is generated when the replication slave finds the replication link is disconnected from the master.
- Severity:
- Minor
- Instance:
- May include AlarmLocation, AlarmId, AlarmState, AlarmSeverity, and bindVarNamesValueStr
- HA Score:
- Normal
- Auto Clear Seconds:
- 300
- OID:
- comcolDbRepFromMasterFailureNotify
- Cause:
- Alarm 31102 raises when the replication slave finds the replication link is disconnected from the master.
- Diagnostic Information
-
- Verify the path for
all services on a node:
- In a command interface, run the command, path.test -a <toNode> to test the paths for all services.
- In a command
interface, use the path test command to test the communication:
- Run the command, iqt -pE NodeInfo to get the node ID
- Run the command, path.test -a <nodeid> to test the communication path
- Examine the
Platform savelogs on all MPs, SO, and NO:
- Run the command, sudo /usr/TKLC/plat/sbin/savelogs_plat
- The plat savelogs are in the /tmpdirectory.
- Verify the path for
all services on a node:
Recovery:
-
Verify the path for all services on a node by typing
path.test –a <toNode>
in a command interface to test the paths for all services. -
Use the path test command to test the communication
between nodes by typing
iqt -pE NodeInfo
to get the node ID. Then typepath.test -a <nodeid>
to test the paths for all services. -
Examine the Platform savelogs on all MPs, SO, and
NO by typing
sudo /usr/TKLC/plat/sbin/savelogs_plat
in the command interface. The plat savelogs are in the /tmp directory. - Indicates replication subsystem is unable to contact a server, due to networking issues or because the server is not available. Investigate the status of the server and verify network connectivity.
- If no issues with network connectivity or the server are found and the problem persists, it is recommended to contact My Oracle Support.