My Oracle Support Banner

Common Causes for ORA-19625 (Doc ID 1369271.1)

Last updated on MARCH 11, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 8.1.7.0 and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.

Purpose

This document describes known root-causes for the combinations of errors :

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
RMAN-6059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625 "error identifying file %s"


In case you may want or need more about your current topic - please also access the Backup & Recover Community of Customers and Oracle Specialists directly via:
https://community.oracle.com/community/support/oracle_database/database_backup_and_recovery

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 1 General information
 2 Common checks
 3 Generic solutions
 4) Defect related
 4.1) <Bug 10172453>  RMAN Duplicate with incremental backups may fail with ORA-19625
 4.2) <Bug 8327220>  RMAN INSERTS DUPLICATE ROWS IN V$ARCHIVED_LOG CAUSING NEXT BACKUP TO FAIL
 4.3) <BUG 4354225>  DUPLICATE ARCHIVELOG ENTRY IN STANDBY CONTROLFILE
 4.4) <Bug 3633269>  STANDBY DATABASE, MISSING ARCHIVELOGS WHEN IN CATALOG MODE
 4.5) <Bug 10199473>  ORA-19625 ARCHIVELOG BACKUP FAILS AFTER FLASHBACK DB / OPEN RESETLOGS.,
 4.6) <BUG:7594309>  INCORRECT PLATFORM ID IN FILE HEADERS FOLLOWING TRANSPORTABLE DATABASE
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.