My Oracle Support Banner

Applied Archivelogs Are Not Deleted On Physical Standby Site from Flash Recovery Area (Doc ID 404338.1)

Last updated on NOVEMBER 19, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 02-JUL-2015***



Symptoms

Standby DB applies the archivelogs with a time lag of 4 hours. When the flash recovery area on the standby site is 100% full, the standby DB stops applying logs instead of automatically deleteting old (already applied) archive logs from the flash recovery area. We have to delete the old archivelogs manually in this case, although archivelog deletion policy is set to "APPLIED ON STANDBY".

Alertlog on physical standby shows:
ORA-19502: write error on file
"/<path>/<DBNAME>/<DBUNIQUENAME>/<archive_directory>/<archivelogname_thread#_<seqno>_<dbid>.arc",  blockno 2027521 (blocksize=512)
ORA-27063: number of bytes read/written is incorrect
IBM AIX RISC System/6000 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576

Changes

Customer increased db_recovery_file_dest_size to 80G (85899345920 Bytes) on physical standby database, which was 40G before.

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