My Oracle Support Banner

ORA-16198 Timeout Incurred On Internal Channel During Remote Archival when Standby is Rebuild (Doc ID 2888060.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 21.7 [Release 12.1 to 21.0]
Information in this document applies to any platform.

Symptoms

Data Guard environment with two physical standby databases in the broker: ISI2REC and ISI2PRA_RAC.
ISI2REC is rebuilt twice a week.
The ORA-16198 errors appear on all nodes of our primary database for 2 hours during ISI2REC is rebuild.

 

DRC log shows this error message

05/24/2022 22:21:47
Database ISI2REC4 successfully removed
05/25/2022 04:55:07
Redo transport problem detected: redo transport to database ISI2REC has the following error:
ORA-16198: timeout incurred on internal channel during remote archival
Data Guard Broker Status Summary:
Type Name Severity Status
Configuration isi2_prd Warning ORA-16607
Primary Database ISI2PRD Error ORA-16778
Physical Standby Database ISI2REC4 Success ORA-00000
Physical Standby Database ISI2PRA_RAC Success ORA-00000

 Primary alert.log:

ORACLE DB 12.1.0.2 on linux, received following error in alert log
2022-05-25 04:54:10.801000 +02:00
WARN: ARCH: Terminating process hung on an operation (PID:21565)
2022-05-25 04:54:15.126000 +02:00
Killing 1 processes (PIDS:21565) (Process by index) in order to remove hung processes. Requested by OS process 9999 on instance 1
2022-05-25 04:54:17.134000 +02:00
ARCH: krsv_hung_process_check: Error 16198 due to hung I/O operation to LOG_ARCHIVE_DEST_3
ARCH: Detected ARCH process failure

 

 

Changes

 Standby ISI2REC is rebuilt using RMAN.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.