Data Guard: Server Hang And Crash Because RSM0 Keeps Re-spawning
(Doc ID 1322877.1)
Last updated on OCTOBER 17, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 12.2.0.1 [Release 10.2 to 12.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Alert log shows repeated messages showing the RSM0 process being started and the corresponding Broker log (drc<instance_name>.log) will show ORA-16713 "the Data Guard broker command timed out".
For example,
ALERT.LOG:
Tue Apr 5 22:23:19 2011
LNS: Standby redo logfile selected for thread 1 sequence 125429 for destination LOG_ARCHIVE_DEST_2
RSM0 started with pid=34, OS id=13468
RSM0 started with pid=34, OS id=14457
RSM0 started with pid=34, OS id=16017
Tue Apr 5 22:42:28 2011
Thread 1 advanced to log sequence 125430 (LGWR switch)
Current log# 1 seq# 125430 mem# 0: +<diskgroup1>/<db_name>/onlinelog/group_1.257.712544401
Current log# 1 seq# 125430 mem# 1: +<diskgroup2>/<db_name>/onlinelog/group_1.257.712544403
Tue Apr 5 22:43:10 2011
LNS: Standby redo logfile selected for thread 1 sequence 125430 for destination LOG_ARCHIVE_DEST_2
RSM0 started with pid=34, OS id=18364
RSM0 started with pid=34, OS id=19782
RSM0 started with pid=34, OS id=22355
RSM0 started with pid=34, OS id=25882
LNS: Standby redo logfile selected for thread 1 sequence 125429 for destination LOG_ARCHIVE_DEST_2
RSM0 started with pid=34, OS id=13468
RSM0 started with pid=34, OS id=14457
RSM0 started with pid=34, OS id=16017
Tue Apr 5 22:42:28 2011
Thread 1 advanced to log sequence 125430 (LGWR switch)
Current log# 1 seq# 125430 mem# 0: +<diskgroup1>/<db_name>/onlinelog/group_1.257.712544401
Current log# 1 seq# 125430 mem# 1: +<diskgroup2>/<db_name>/onlinelog/group_1.257.712544403
Tue Apr 5 22:43:10 2011
LNS: Standby redo logfile selected for thread 1 sequence 125430 for destination LOG_ARCHIVE_DEST_2
RSM0 started with pid=34, OS id=18364
RSM0 started with pid=34, OS id=19782
RSM0 started with pid=34, OS id=22355
RSM0 started with pid=34, OS id=25882
DRC.LOG:
DG 2011-04-05-22:42:10 0 2 0 DMON: Process RSM0 re-created with pid = 16017
DG 2011-04-05-22:42:10 0 2 740307674 DMON: Operation CTL_GET_STATUS stalled during phase BEGIN. Error=ORA-16713
DG 2011-04-05-22:42:10 0 2 740307674 Operation CTL_GET_STATUS cancelled during phase 1, error = ORA-16713
DG 2011-04-05-22:43:48 0 2 740485164 DMON: MON_PROPERTY operation completed
DG 2011-04-05-22:43:48 0 2 740485165 DMON: GET_DRC: success. (len = 235)
DG 2011-04-05-22:43:48 0 2 740485165 DMON: GET_DRC operation completed
DG 2011-04-05-22:43:48 1000000 3 740485166 DMON: GET_SITE: success. (len = 327)
DG 2011-04-05-22:42:10 0 2 740307674 DMON: Operation CTL_GET_STATUS stalled during phase BEGIN. Error=ORA-16713
DG 2011-04-05-22:42:10 0 2 740307674 Operation CTL_GET_STATUS cancelled during phase 1, error = ORA-16713
DG 2011-04-05-22:43:48 0 2 740485164 DMON: MON_PROPERTY operation completed
DG 2011-04-05-22:43:48 0 2 740485165 DMON: GET_DRC: success. (len = 235)
DG 2011-04-05-22:43:48 0 2 740485165 DMON: GET_DRC operation completed
DG 2011-04-05-22:43:48 1000000 3 740485166 DMON: GET_SITE: success. (len = 327)
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |