My Oracle Support Banner

Taking RMAN Backup Caused This Message In The Standby Database "POSSIBLE NETWORK DISCONNECT WITH PRIMARY DATABASE" (Doc ID 878557.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.3 to 11.1.0.7 [Release 10.2 to 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 27-Sep-2012***


Symptoms

During RMAN Archivelog Backup on primary, the LNS process on primary is restarted and standby detects possible network disconnect with primary.

Alert Log from Primary Database:
--------------------------------

Tue Jul 14 10:38:24 2009
Starting control autobackup
Control autobackup written to DISK device
handle '/<path>/<sid>/fra/<sid>/autobackup/2009_07_14/<name of backuppiece>.bkp'
Tue Jul 14 10:38:44 2009
Thread 1 cannot allocate new log, sequence 18252
Private strand flush not complete
Current log# 3 seq# 18251 mem# 0: /oracle/oradata/<sid>/redo/name1.log
Current log# 3 seq# 18251 mem# 1: /oracle/oradata/<sid>/redo/name2.log
LNS1 started with pid=129, OS id=32146
Tue Jul 14 10:38:47 2009
Thread 1 advanced to log sequence 18252
Current log# 4 seq# 18252 mem# 0: /oracle/oradata/<sid>/redo/name3.log
Current log# 4 seq# 18252 mem# 1: /oracle/oradata/<sid>/redo/name4.log
Tue Jul 14 10:38:48 2009
LNS: Standby redo logfile selected for thread 1 sequence 18252 for destination LOG_ARCHIVE_DEST_2
Tue Jul 14 10:38:48 2009
ARC1: Standby redo logfile selected for thread 1 sequence 18251 for destination LOG_ARCHIVE_DEST_2
Tue Jul 14 10:38:52 2009
Starting control autobackup
Control autobackup written to DISK device
handle '/oracle/oradata01/<sid>/fra/<sid>/autobackup/2009_07_14/<name of backuppiece>.bkp' Tue Jul 14 10:39:10 2009
alter database backup controlfile to trace
Tue Jul 14 10:39:10 2009
Completed: alter database backup controlfile to trace
Tue Jul 14 10:39:13 2009
Thread 1 cannot allocate new log, sequence 18253
Private strand flush not complete
Current log# 4 seq# 18252 mem# 0: /oracle/oradata/<sid>/redo/name5.log
Current log# 4 seq# 18252 mem# 1: /oracle/oradata/<sid>/redo/name6.log
LNS1 started with pid=129, OS id=328




Alert Log From The Standby Database:
-------------------------------------

Tue Jul 14 10:38:42 2009
RFS[2380]: Possible network disconnect with primary database

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

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