cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to request gap sequence

Former Member
0 Kudos

Dear All,

We are configuring DR site using oracle data guard, Physical Standby maximum protection. Our Oracle

release is 11.2.0.4, and using same release for DR site. Operating system is HP-Unix. We have configured

all the parameters at primary and DR site. We have successfully mounted DR database and log shipment

is working fine but unable to start recovery on DR database.

When we execute command:

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

Following error occur:

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -

FAL[client]: Failed to request gap sequence

GAP - thread 1 sequence 51568-51568

DBID 1210060169 branch 889027849

FAL[client]: All defined FAL servers have been attempted.

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization

parameter is defined to a value that is sufficiently large

enough to maintain adequate log switch information to resolve

archivelog gaps.

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Wed Aug 10 14:54:00 2016

RFS[6348]: Possible network disconnect with primary database

Wed Aug 10 14:54:08 2016

Killing 1 processes with pids 27492 (idle RFS by thread/sequence) in order to al

low the in-transit gap to be queued. Requested by OS process 27595

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -

After the above message we have verified almost all parameter and all parameter are absolutely

accurate.

Kindly suggest the solution.

Thanks and Best Regard

Accepted Solutions (0)

Answers (1)

Answers (1)

JamesZ
Advisor
Advisor
0 Kudos

Hi Faisal,

Recently I saw many standby issues.

Can you please attach the alert logs from both standby and primary database?

Best regards,
James

Former Member
0 Kudos

Dear James,

Thanks for your reply. Kindly find the below update

I have manually sync the gap-sequence using register logfile command. Now  both Primary and dr databases are  in sync and dr started fetching the archives from the primary site but not able to fetch sequence so not able to apply the archive.

While we started command alter database recover managed standby database disconnect from session;

Following errors thrown in the alert log file of dr site:

Fetching gap sequence in thread 1, gap sequence 53505-53505

Fri Aug 19 15:29:20 2016

RFS[18]: Assigned to RFS process 9873

RFS[18]: Opened log for thread 1 sequence 53510 dbid 1210060169 branch 889027849

RFS[19]: Assigned to RFS process 9871

RFS[19]: Selected log 3 for thread 1 sequence 53509 dbid 1210060169 branch 889027849

RFS[20]: Assigned to RFS process 9865

RFS[20]: Selected log 1 for thread 1 sequence 53505 dbid 1210060169 branch 889027849

RFS[21]: Assigned to RFS process 9869

RFS[21]: Opened log for thread 1 sequence 53506 dbid 1210060169 branch 889027849

Fri Aug 19 15:35:17 2016

Killing 1 processes with pids 9859 (idle RFS by thread/sequence) in order to allow the in-transit gap to be queued. Requested by OS process 9887

Killing 1 processes with pids 9839 (idle RFS by thread/sequence) in order to allow the in-transit gap to be queued. Requested by OS process 9887

Fri Aug 19 15:35:22 2016

Primary database is in MAXIMUM PERFORMANCE mode

RFS[22]: Assigned to RFS process 9974

RFS[22]: Selected log 5 for thread 1 sequence 53513 dbid 1210060169 branch 889027849

Fri Aug 19 15:35:25 2016

Killing 1 processes with pids 9869 (idle RFS by thread/sequence) in order to retry receiving a log after reattaching. Requested by OS process 9976

Fri Aug 19 15:35:25 2016

Killing 1 processes with pids 9871 (idle RFS by thread/sequence) in order to retry receiving a log after reattaching. Requested by OS process 9978

Fri Aug 19 15:35:26 2016

Killing 1 processes with pids 9867 (idle RFS by thread/sequence) in order to retry receiving a log after reattaching. Requested by OS process 9980

Fri Aug 19 15:35:26 2016

Killing 1 processes with pids 9873 (idle RFS by thread/sequence) in order to retry receiving a log after reattaching. Requested by OS process 9982

Fri Aug 19 15:35:26 2016

What ever file it fetches automatically from primary site will not be applied.  So we used  to delete that file and again copy from the primary site to DR site, Manually register then we able to apply that archive log file manually. 

on the other hand I am trying to configure dg broker, I have successfully added primary database through data guard border. Now I am executing command “DGMGRL> add database <DB_unique_Name> as connect identifier is <Service_name> maintained as physical;

I receive error ora-16662: Network time out.

Our network team provide us  2 Mbps dedicated wan link between primary and dr site.


============


DR SITE LOG;


RFS[8]: Selected log 2 for thread 1 sequence 53508 dbid 1210060169 branch 889027849

RFS[9]: Assigned to RFS process 9719

RFS[9]: Opened log for thread 1 sequence 53506 dbid 1210060169 branch 889027849

Fri Aug 19 15:23:03 2016

Killing 1 processes with pids 9715 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 9828

Killing 1 processes with pids 9701 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 9828

Fri Aug 19 15:23:08 2016

Killing 1 processes with pids 9713 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 9831

Fri Aug 19 15:23:08 2016

Killing 1 processes with pids 9719 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 9835

Fri Aug 19 15:23:08 2016

RFS[10]: Assigned to RFS process 9833

RFS[10]: Selected log 2 for thread 1 sequence 53508 dbid 1210060169 branch 889027849

Fri Aug 19 15:23:09 2016

RFS[11]: Assigned to RFS process 9837

RFS[11]: Selected log 3 for thread 1 sequence 53509 dbid 1210060169 branch 889027849

RFS[12]: Assigned to RFS process 9831

RFS[12]: Selected log 1 for thread 1 sequence 53505 dbid 1210060169 branch 889027849

RFS[13]: Assigned to RFS process 9835

RFS[13]: Opened log for thread 1 sequence 53506 dbid 1210060169 branch 889027849

Fri Aug 19 15:23:10 2016

Primary database is in MAXIMUM PERFORMANCE mode

RFS[14]: Assigned to RFS process 9839

RFS[14]: Selected log 4 for thread 1 sequence 53511 dbid 1210060169 branch 889027849

Fri Aug 19 15:23:11 2016

RFS[15]: Assigned to RFS process 9841

RFS[15]: Opened log for thread 1 sequence 53510 dbid 1210060169 branch 889027849

Fri Aug 19 15:24:54 2016

db_recovery_file_dest_size of 30000 MB is 0.00% used. This is a

user-specified limit on the amount of space that will be used by this

database for recovery-related files, and does not reflect the amount of

space available in the underlying filesystem or ASM diskgroup.

Fri Aug 19 15:25:08 2016

Killing 1 processes with pids 9717 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 9828

Fri Aug 19 15:26:41 2016

RFS[16]: Assigned to RFS process 9859

RFS[16]: Opened log for thread 1 sequence 53507 dbid 1210060169 branch 889027849

Fri Aug 19 15:29:12 2016

Killing 1 processes with pids 9833 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 9828

Killing 1 processes with pids 9841 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 9828

Fri Aug 19 15:29:19 2016

Killing 1 processes with pids 9831 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 9865

Fri Aug 19 15:29:19 2016

RFS[17]: Assigned to RFS process 9867

RFS[17]: Selected log 2 for thread 1 sequence 53508 dbid 1210060169 branch 889027849

Fri Aug 19 15:29:19 2016

Killing 1 processes with pids 9835 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 9869

Fri Aug 19 15:29:19 2016

Killing 1 processes with pids 9837 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 9871

Fri Aug 19 15:29:19 2016

Fetching gap sequence in thread 1, gap sequence 53505-53505

Fri Aug 19 15:29:20 2016

RFS[18]: Assigned to RFS process 9873

RFS[18]: Opened log for thread 1 sequence 53510 dbid 1210060169 branch 889027849

RFS[19]: Assigned to RFS process 9871

RFS[19]: Selected log 3 for thread 1 sequence 53509 dbid 1210060169 branch 889027849

RFS[20]: Assigned to RFS process 9865

RFS[20]: Selected log 1 for thread 1 sequence 53505 dbid 1210060169 branch 889027849

RFS[21]: Assigned to RFS process 9869

RFS[21]: Opened log for thread 1 sequence 53506 dbid 1210060169 branch 889027849

Fri Aug 19 15:35:17 2016

Killing 1 processes with pids 9859 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 9887

Killing 1 processes with pids 9839 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 9887

Fri Aug 19 15:35:22 2016

Primary database is in MAXIMUM PERFORMANCE mode

RFS[22]: Assigned to RFS process 9974

RFS[22]: Selected log 5 for thread 1 sequence 53513 dbid 1210060169 branch 889027849

Fri Aug 19 15:35:25 2016

Killing 1 processes with pids 9869 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 9976

Fri Aug 19 15:35:25 2016

Killing 1 processes with pids 9871 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 9978

Fri Aug 19 15:35:26 2016

Killing 1 processes with pids 9867 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 9980

Fri Aug 19 15:35:26 2016

Killing 1 processes with pids 9873 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 9982

Fri Aug 19 15:35:26 2016

RFS[23]: Assigned to RFS process 9984

RFS[23]: Opened log for thread 1 sequence 53507 dbid 1210060169 branch 889027849

RFS[24]: Assigned to RFS process 9976

RFS[24]: Opened log for thread 1 sequence 53506 dbid 1210060169 branch 889027849

Fri Aug 19 15:35:26 2016

RFS[25]: Assigned to RFS process 9986

RFS[25]: Selected log 4 for thread 1 sequence 53511 dbid 1210060169 branch 889027849

Fri Aug 19 15:35:26 2016

RFS[26]: Assigned to RFS process 9988

RFS[26]: Opened log for thread 1 sequence 53512 dbid 1210060169 branch 889027849

RFS[27]: Assigned to RFS process 9978

RFS[27]: Selected log 3 for thread 1 sequence 53509 dbid 1210060169 branch 889027849

RFS[28]: Assigned to RFS process 9980

RFS[28]: Selected log 2 for thread 1 sequence 53508 dbid 1210060169 branch 889027849

RFS[29]: Assigned to RFS process 9982

RFS[29]: Opened log for thread 1 sequence 53510 dbid 1210060169 branch 889027849

Fri Aug 19 15:36:21 2016

Killing 1 processes with pids 9865 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 9887

Fri Aug 19 15:36:24 2016

RFS[30]: Assigned to RFS process 9992

RFS[30]: Selected log 1 for thread 1 sequence 53505 dbid 1210060169 branch 889027849

Fri Aug 19 15:41:26 2016

Killing 1 processes with pids 9976 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 9887

Killing 1 processes with pids 9988 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 9887

Fri Aug 19 15:41:36 2016

Killing 1 processes with pids 9980 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10005

Fri Aug 19 15:41:36 2016

Killing 1 processes with pids 9982 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10007

Fri Aug 19 15:41:36 2016

Killing 1 processes with pids 9984 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10011

Fri Aug 19 15:41:36 2016

Killing 1 processes with pids 9978 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10009

RFS[31]: Assigned to RFS process 10005

RFS[31]: Selected log 2 for thread 1 sequence 53508 dbid 1210060169 branch 889027849

Fri Aug 19 15:41:37 2016

Killing 1 processes with pids 9986 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10015

Fri Aug 19 15:41:37 2016

RFS[32]: Assigned to RFS process 10013

RFS[32]: Opened log for thread 1 sequence 53506 dbid 1210060169 branch 889027849

RFS[33]: Assigned to RFS process 10007

RFS[33]: Opened log for thread 1 sequence 53510 dbid 1210060169 branch 889027849

Fri Aug 19 15:41:37 2016

RFS[34]: Assigned to RFS process 10017

RFS[34]: Opened log for thread 1 sequence 53512 dbid 1210060169 branch 889027849

RFS[35]: Assigned to RFS process 10011

RFS[35]: Opened log for thread 1 sequence 53507 dbid 1210060169 branch 889027849

RFS[36]: Assigned to RFS process 10009

RFS[36]: Selected log 3 for thread 1 sequence 53509 dbid 1210060169 branch 889027849

RFS[37]: Assigned to RFS process 10015

RFS[37]: Selected log 4 for thread 1 sequence 53511 dbid 1210060169 branch 889027849

Fri Aug 19 15:42:36 2016

Killing 1 processes with pids 9992 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10019

RFS[38]: Assigned to RFS process 10019

RFS[38]: Selected log 1 for thread 1 sequence 53505 dbid 1210060169 branch 889027849

Fri Aug 19 15:48:05 2016

Killing 1 processes with pids 10005 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 10026

Killing 1 processes with pids 9974 (idle RFS by thread/sequence) in order to allow the

in-transit gap to be queued. Requested by OS process 10026

Fri Aug 19 15:48:12 2016

Primary database is in MAXIMUM PERFORMANCE mode

RFS[39]: Assigned to RFS process 10032

RFS[39]: No standby redo logfiles available for thread 1

RFS[39]: Opened log for thread 1 sequence 53515 dbid 1210060169 branch 889027849

Fri Aug 19 15:48:13 2016

Killing 1 processes with pids 10009 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10034

Fri Aug 19 15:48:13 2016

Killing 1 processes with pids 10011 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10036

Fri Aug 19 15:48:13 2016

Killing 1 processes with pids 10007 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10038

Fri Aug 19 15:48:13 2016

Killing 1 processes with pids 10015 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10040

Fri Aug 19 15:48:14 2016

RFS[40]: Assigned to RFS process 10042

RFS[40]: Selected log 2 for thread 1 sequence 53508 dbid 1210060169 branch 889027849

Fri Aug 19 15:48:14 2016

Killing 1 processes with pids 10013 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10044

Fri Aug 19 15:48:14 2016

Killing 1 processes with pids 10017 (idle RFS by thread/sequence) in order to retry

receiving a log after reattaching. Requested by OS process 10046

Fri Aug 19 15:48:14 2016

RFS[41]: Assigned to RFS process 10048

RFS[41]: Selected log 5 for thread 1 sequence 53513 dbid 1210060169 branch 889027849

Fri Aug 19 15:48:14 2016

RFS[42]: Assigned to RFS process 10050

RFS[42]: Opened log for thread 1 sequence 53514 dbid 1210060169 branch 889027849

RFS[43]: Assigned to RFS process 10034

RFS[43]: Selected log 3 for thread 1 sequence 53509 dbid 1210060169 branch 889027849

RFS[44]: Assigned to RFS process 10036

RFS[44]: Opened log for thread 1 sequence 53507 dbid 1210060169 branch 889027849

RFS[45]: Assigned to RFS process 10040

RFS[45]: Selected log 4 for thread 1 sequence 53511 dbid 1210060169 branch 889027849

RFS[46]: Assigned to RFS process 10038

RFS[46]: Opened log for thread 1 sequence 53510 dbid 1210060169 branch 889027849

RFS[47]: Assigned to RFS process 10044

RFS[47]: Opened log for thread 1 sequence 53506 dbid 1210060169 branch 889027849

RFS[48]: Assigned to RFS process 10046

RFS[48]: Opened log for thread 1 sequence 53512 dbid 1210060169 branch 889027849

Primary Site:


WARN: ARCc: Terminating pid 128 hung on an I/O operationKilling 1 processes with pids 128

(Process by index) in order to remove hung processes. Requested by OS process 1307

WARN: ARCc: Terminating pid 28454 hung on an I/O operation

Killing 1 processes with pids 28454 (Process by index) in order to remove hung processes.

Requested by OS process 1309

ARCn: Archival started

ARC4: Detected ARCH process failureWARN: ARCn: Terminating pid 28454 hung on an I/O

operation

ARC4: STARTING ARCH PROCESSES COMPLETE

ARCn: Detected ARCH process failure

ARCn: STARTING ARCH PROCESSES

Fri Aug 19 15:35:51 2016

ARCd started with pid=54, OS id=1358

Fri Aug 19 15:35:52 2016

ARCo started with pid=64, OS id=1360

ARCd: Archival started

Reclaiming FAL entry from dead process [pid 28454]

FAL[server, ARCd]: FAL archive failed, see trace file.

Reclaiming FAL entry from dead process [pid 128]

Archived Log entry 49773 added for thread 1 sequence 53512 ID 0x48203989 dest 1:

Reclaiming FAL entry from dead process [pid 126]

ARCo: Archival started

ARCn: STARTING ARCH PROCESSES COMPLETE

Reclaiming FAL entry from dead process [pid 124]

Reclaiming FAL entry from dead process [pid 28452]

ARC3: Standby redo logfile selected for thread 1 sequence 53511 for destination

LOG_ARCHIVE_DEST_2

Fri Aug 19 15:35:55 2016

ARC6: Standby redo logfile selected for thread 1 sequence 53509 for destination

LOG_ARCHIVE_DEST_2

ARCo: Standby redo logfile selected for thread 1 sequence 53508 for destination

LOG_ARCHIVE_DEST_2

Fri Aug 19 15:36:51 2016

ARC7: Standby redo logfile selected for thread 1 sequence 53505 for destination

LOG_ARCHIVE_DEST_2

Fri Aug 19 15:40:39 2016

NSV1 started with pid=65, OS id=2135

Fri Aug 19 15:40:53 2016

Completed checkpoint up to RBA [0xd109.2.10], SCN: 376362848

Fri Aug 19 15:41:53 2016

FAL[server, ARC5]: FAL archive failed, see trace file.

ARCH: FAL archive failed. Archiver continuing

ORACLE Instance SID - Archival Error. Archiver continuing.

Fri Aug 19 15:41:55 2016

FAL[server, ARC1]: FAL archive failed, see trace file.

ARCH: FAL archive failed. Archiver continuing

ORACLE Instance SID - Archival Error. Archiver continuing.

Killing 1 processes with pids 1307 (Process by index) in order to remove hung processes.

Requested by OS process 27831

Fri Aug 19 15:41:57 2016

Reclaiming FAL entry from dead process [pid 1307]

Fri Aug 19 15:41:58 2016

Killing 1 processes with pids 29004 (Process by index) in order to remove hung processes.

Requested by OS process 28400

Fri Aug 19 15:41:59 2016

Killing 1 processes with pids 1311 (Process by index) in order to remove hung processes.

Requested by OS process 28402

Fri Aug 19 15:42:00 2016

Killing 1 processes with pids 28462 (Process by index) in order to remove hung processes.

Requested by OS process 28415

Fri Aug 19 15:42:00 2016

Killing 1 processes with pids 1360 (Process by index) in order to remove hung processes.

Requested by OS process 1309

Fri Aug 19 15:42:00 2016

ARCs: Detected ARCH process failure

ARCs: Detected ARCH process failure

ARCs: Detected ARCH process failure

ARCs: Detected ARCH process failure

ARCs: Detected ARCH process failure

ARCs: STARTING ARCH PROCESSES

Fri Aug 19 15:42:00 2016

ARC3 started with pid=53, OS id=2521

Fri Aug 19 15:42:00 2016

ARC6 started with pid=58, OS id=2523

Fri Aug 19 15:42:00 2016

ARCn started with pid=64, OS id=2525

Fri Aug 19 15:42:01 2016

ARCo started with pid=72, OS id=2527

Fri Aug 19 15:42:01 2016

ARC3: Archival startedARCt started with pid=110, OS id=2529

ARC6: Archival started

ARCn: Archival started

ARCo: Archival started

Reclaiming FAL entry from dead process [pid 29004]

Reclaiming FAL entry from dead process [pid 1360]

Reclaiming FAL entry from dead process [pid 1311]

Reclaiming FAL entry from dead process [pid 28462]

ARCt: Archival started

ARCs: STARTING ARCH PROCESSES COMPLETE

ARC6: Standby redo logfile selected for thread 1 sequence 53508 for destination

LOG_ARCHIVE_DEST_2

ARC3: Standby redo logfile selected for thread 1 sequence 53509 for destination

LOG_ARCHIVE_DEST_2

ARCt: Standby redo logfile selected for thread 1 sequence 53511 for destination

LOG_ARCHIVE_DEST_2

Fri Aug 19 15:42:30 2016

Killing 1 processes with pids 122 (Process by index) in order to remove hung processes.

Requested by OS process 28390

Fri Aug 19 15:42:30 2016

NSA2 started with pid=137, OS id=2641

Fri Aug 19 15:42:35 2016

Beginning log switch checkpoint up to RBA [0xd10a.2.10], SCN: 376371016

Thread 1 advanced to log sequence 53514 (LGWR switch)

  Current log# 40 seq# 53514 mem# 0: /oracle/SID/origlogD/log_g104.dbf

  Current log# 40 seq# 53514 mem# 1: /oracle/SID/mirrlogD/log_g1m4.dbf

Fri Aug 19 15:42:36 2016

Archived Log entry 49774 added for thread 1 sequence 53513 ID 0x48203989 dest 1:

Fri Aug 19 15:42:57 2016

Killing 1 processes with pids 29006 (Process by index) in order to remove hung processes.

Requested by OS process 28382

ARC0: Detected ARCH process failure

ARC0: STARTING ARCH PROCESSES

Fri Aug 19 15:42:59 2016

ARC7 started with pid=44, OS id=2729

ARC7: Archival started

ARC0: STARTING ARCH PROCESSES COMPLETE

Reclaiming FAL entry from dead process [pid 29006]

ARC7: Standby redo logfile selected for thread 1 sequence 53505 for destination

LOG_ARCHIVE_DEST_2

Fri Aug 19 15:43:43 2016

DMON: Killing process NSV1 (PID=2135)

Fri Aug 19 15:43:44 2016

NSV1 started with pid=130, OS id=2862

Fri Aug 19 15:46:48 2016

DMON: Killing process NSV1 (PID=2862)

Fri Aug 19 15:47:40 2016

Completed checkpoint up to RBA [0xd10a.2.10], SCN: 376371016

Fri Aug 19 15:47:48 2016

NSV1 started with pid=65, OS id=3510

Fri Aug 19 15:48:32 2016

FAL[server, ARC6]: FAL archive failed, see trace file.

ARCH: FAL archive failed. Archiver continuing

ORACLE Instance SID - Archival Error. Archiver continuing.

Killing 1 processes with pids 2521 (Process by index) in order to remove hung processes.

Requested by OS process 2523

Fri Aug 19 15:48:36 2016

Reclaiming FAL entry from dead process [pid 2521]

Killing 1 processes with pids 28415 (Process by index) in order to remove hung processes.

Requested by OS process 2523Fri Aug 19 15:48:36 2016

Killing 1 processes with pids 28415 (Process by index) in order to remove hung processes.

Requested by OS process 792

Fri Aug 19 15:48:37 2016

Killing 1 processes with pids 2525 (Process by index) in order to remove hung processes.

Requested by OS process 28398

Fri Aug 19 15:48:38 2016

Killing 1 processes with pids 1358 (Process by index) in order to remove hung processes.

Requested by OS process 130

Fri Aug 19 15:48:39 2016

Killing 1 processes with pids 2527 (Process by index) in order to remove hung processes.

Requested by OS process 28442

Fri Aug 19 15:48:39 2016

Beginning log switch checkpoint up to RBA [0xd10b.2.10], SCN: 376375576

Thread 1 advanced to log sequence 53515 (LGWR switch)

  Current log# 10 seq# 53515 mem# 0: /oracle/SID/origlogA/log_g101.dbf

  Current log# 10 seq# 53515 mem# 1: /oracle/SID/mirrlogA/log_g1m1.dbf

Fri Aug 19 15:48:39 2016

Killing 1 processes with pids 2529 (Process by index) in order to remove hung processes.

Requested by OS process 28444

Killing 1 processes with pids 2529 (Process by index) in order to remove hung processes.

Requested by OS process 792

Killing 1 processes with pids 2529 (Process by index) in order to remove hung processes.

Requested by OS process 2523

Fri Aug 19 15:48:39 2016

ARCk: Detected ARCH process failure

ARCk: Detected ARCH process failure

ARCk: Detected ARCH process failure

ARCk: Detected ARCH process failure

ARCk: Detected ARCH process failure

ARCk: Detected ARCH process failure

ARCk: STARTING ARCH PROCESSES

Fri Aug 19 15:48:39 2016

ARC3 started with pid=52, OS id=3886

Fri Aug 19 15:48:39 2016

ARCb started with pid=53, OS id=3888

Fri Aug 19 15:48:39 2016

ARCd started with pid=54, OS id=3890

Fri Aug 19 15:48:39 2016

ARCn started with pid=64, OS id=3892

Fri Aug 19 15:48:39 2016

ARCo started with pid=72, OS id=3894

Fri Aug 19 15:48:40 2016

ARCt started with pid=110, OS id=3896

ARC3: Archival started

ARCb: Archival started

ARCd: Archival started

ARCn: Archival started

ARCo: Archival started

Reclaiming FAL entry from dead process [pid 2527]

Reclaiming FAL entry from dead process [pid 2525]

Reclaiming FAL entry from dead process [pid 2529]

ARCt: Archival started

ARCk: STARTING ARCH PROCESSES COMPLETE

Reclaiming FAL entry from dead process [pid 1358]

Reclaiming FAL entry from dead process [pid 28415]

Archived Log entry 49775 added for thread 1 sequence 53514 ID 0x48203989 dest 1:

ARCn: Standby redo logfile selected for thread 1 sequence 53508 for destination

LOG_ARCHIVE_DEST_2

ARCi: Standby redo logfile selected for thread 1 sequence 53513 for destination

LOG_ARCHIVE_DEST_2

ARCd: Standby redo logfile selected for thread 1 sequence 53509 for destination

LOG_ARCHIVE_DEST_2

ARCo: Standby redo logfile selected for thread 1 sequence 53511 for destination

LOG_ARCHIVE_DEST_2

Fri Aug 19 15:49:36 2016

Killing 1 processes with pids 2729 (Process by index) in order to remove hung processes.

Requested by OS process 28382

ARC0: Detected ARCH process failure

ARC0: STARTING ARCH PROCESSES

Fri Aug 19 15:49:39 2016

ARC7 started with pid=44, OS id=4060

ARC7: Archival started

ARC0: STARTING ARCH PROCESSES COMPLETE

Reclaiming FAL entry from dead process [pid 2729]

ARC7: Standby redo logfile selected for thread 1 sequence 53505 for destination

LOG_ARCHIVE_DEST_2

Thanks and Best Regards

JamesZ
Advisor
Advisor
0 Kudos

Hi Faisal,


You mean log shipping has been working fine?

But we can see following error in the pr alert log:

Fri Aug 19 15:48:32 2016

FAL[server, ARC6]: FAL archive failed, see trace file.

ARCH: FAL archive failed. Archiver continuing

ORACLE Instance SID - Archival Error. Archiver continuing.

Killing 1 processes with pids 2521 (Process by index) in order to remove hung processes.

FAL is working after loss of communication between pr and dr, you may need to check archiver log in pr side to check any problem on archiver.

If possible, try to zip alert log from both pr and dr, archiver log and attach into this discussion

Best regards,
James

Former Member
0 Kudos

Dear James,

Thanks for your reply.

I am not able to attach log files due to size limitation. Could you share your email so that I can forward logs.

Thanks and Best Regards,

Faisal

JamesZ
Advisor
Advisor
0 Kudos

Hi Faisal,

In this case, are you able to attach archiver trace?

Best regards,

James