TMON (PID:17611): Killing 1 Processes (PIDS:21483) (Process By Index) In Order To Remove Hung Proces
(Doc ID 2681259.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 and laterInformation in this document applies to any platform.
Symptoms
Your primary and standby databases are on the same server, but different virtual machines.
Primary alert log
===========
2020-06-10T10:08:44.109013+02:00
Errors in file <path>/trace/<sid>_tt03_9936.trc:
ORA-03113: end-of-file on communication channel
TT03 (PID:9936): Error 3113 for LNO:3 to '<standby db_unique_name>'
2020-06-10T10:08:44.138806+02:00
Errors in file <path>/trace/<sid>_tt03_9936.trc:
ORA-03113: end-of-file on communication channel
2020-06-10T10:08:44.138974+02:00
Errors in file <path>/trace/<sid>_tt03_9936.trc:
ORA-03113: end-of-file on communication channel
Standby alert log
===========
2020-06-10T10:08:09.006849+02:00
TMON (PID:29369): Process (PID:11602) hung on an I/O after 243 seconds with threshold of 240 at [krsb.c:3458]
TMON (PID:29369): WARN: Terminating process hung on an operation (PID:11602)
2020-06-10T10:08:13.123326+02:00
TMON (PID:29369): Killing 1 processes (PIDS:11602) (Process by index) in order to remove hung processes. Requested by OS process 29369
2020-06-10T10:08:13.123642+02:00
Process termination requested for pid 11602 [source = rdbms], [info = 2] [request issued by pid: 29369, uid: 5060]
Transport Lag: 9 minutes 55 seconds (computed 8 seconds ago)
Apply Lag: 9 minutes 55 seconds (computed 8 seconds ago)
ApplyLagThreshold = '900'
TransportLagThreshold = '900'
ArchiveLagTarget = '0'
Changes
This is a new data guard environment
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 |