Streams Capture Processes a Log Every 15 Minutes, State is 'Waiting on Redo' and Continues to Fall Behind. Remote Archival Errors from Physical Standby Are In Alert Log. (Doc ID 564677.1)

Last updated on FEBRUARY 08, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.3 [Release 10.1 to 11.2]
Information in this document applies to any platform.


Symptoms

In an Oracle 10g Streams bidirectional replication environment, the capture process on one of the sites is observed to be moving very slowly. This site is also the primary database for a physical standby database. The logminer process for capture only seems to be processing about one log every 15 minutes, but once it starts processing a log, it processes it very quickly. 

Every time logminer processes a log, it is observed to be preceded by errors in the alert log similar to the following:

Errors in file /opt/Oracle/DB10gR2/cbs3000/admin/bdump/cbs3000_arc0_2280.trc:

ORA-16099: internal error ORA-00600 occurred at standby database
Tue Apr 22 16:31:31 2010
FAL[server, ARC0]: FAL archive failed, see trace file.
Tue Apr 22 16:31:31 2010
Errors in file /opt/Oracle/DB10gR2/cbs3000/admin/bdump/cbs3000_arc0_2280.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Tue Apr 22 16:31:31 2010
ORACLE Instance cbs3000 - Archival Error. Archiver continuing.

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