My Oracle Support Banner

REDO transport issue from FarSYNC database (Doc ID 2802033.1)

Last updated on SEPTEMBER 01, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 18.6.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Primary ship REDO to standby in SYNC mode and farSYNC configured to ship REDO to standby.

Configuration details :

Primary --(SYNC)- > FarSYNC --(ASYNC)- > Standby

FarSync Alert log,

2021-08-23T02:26:48.515272-07:00
ORACLE Instance orafarsync, archival error, archiver continuing <<< archival error
2021-08-23T02:26:48.515487-07:00
ORA-16055: FAL request rejected
2021-08-23T02:26:48.515822-07:00
Errors in file <Trace Dump>/<farsync_SID>_arc1_31506.trc:
ORA-16055: FAL request rejected
2021-08-23T02:27:48.929957-07:00
ARC3 (PID:31510): FAL: Archive not allowed because media recovery disabled
ARC3 (PID:31510): FAL archive failed with error 3 (see trace for details)
ARC3 (PID:31510): FAL archive failed, archiver continuing

 

No errors reported in FARSYNC but the logs are not shippied to standby.

 

Standby

PROCESS STATUS THREAD# SEQUENCE# DELAY_MINS ACTIVE_AGENTS CLIENT_P

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

ARCH CONNECTED 0 0 0 0 ARCH

DGRD ALLOCATED 0 0 0 0 N/A

DGRD ALLOCATED 0 0 0 0 N/A

RFS IDLE 1 0 0 0 Archival

MRP0 WAIT_FOR_GAP 1 4511 0 3 N/A

 

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
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.