Archive logs are shipped to a Downstream Database but they are not registered automatically to the Capture process (Doc ID 1609104.1)

Last updated on DECEMBER 18, 2013

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.2.0 [Release 11.2]
Information in this document applies to any platform.

Symptoms

Archived redo logs are no longer being automatically registered by the RFS LogMiner Client to the Downstream Capture process after making dynamic parameter changes to

log_archive_dest_2
log_archive_dest_state_2
log_archive_config

the upstream database in a previously working environment.

The issue in <Note 1511410.1> does not apply in this case. 

Log archive tracing set to log_archive_trace=2322 reveals the following in downstream RFS process trace file

krsr_client_dispatch: Entering RFS client dispatcher (opcode = 0x20)
krsr_client_dispatch: Checking RFS client (RFS physical client callback)
krsr_client_dispatch:   rfslp->flag_krfsl = 0x1001da4
krsr_client_dispatch: Skipping this inactive RFS client
krsr_client_dispatch: Checking RFS client (RFS client callback - debug)
krsr_client_dispatch:   rfslp->flag_krfsl = 0xfffff
krsr_client_dispatch: Skipping this inactive RFS client
krsr_client_dispatch: Checking RFS client (RFS LogMiner Client)
krsr_client_dispatch:   rfslp->flag_krfsl = 0x3f97
krsr_client_dispatch: Skipping this inactive RFS client <<<<<<<<<<<<<<<< Inactive
krsr_pic_stall: No-stall I/O completion check nump_krsrbx=0

Namely that the RFS LogMiner Client (part of the RFS infrastructure) is inactive.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms