My Oracle Support Banner

Apply Logical Standby Database failed with LOGMINER: Error 308 encountered, failed to read logfile (Doc ID 1368946.1)

Last updated on OCTOBER 27, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Primary and Logical Standby database are at 11.2.0.2




Symptoms


1) When started logical apply on standby side, it says in the alert.log file that it is waiting for a log :


LOGMINER: Error 308 encountered, failed to read logfile /<path>/arch1/arch_<sid>_1_26991_735324869.arc




 On primary Db side  :
*** 2011-10-09 07:51:17.760
Log read is SYNCHRONOUS though disk_asynch_io is enabled!



2) the archive logs from primary database are properly sent to standby location, but SQL APPLY doesn't apply anything and so it doesn't erase applied redo logs.


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.