My Oracle Support Banner

ORA-19575 During RMAN Backup (Doc ID 1518129.1)

Last updated on OCTOBER 22, 2019

Applies to:

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


No problem with RMAN execution, just error derived from corrupted archivelog, which RMAN will not backup.

ORA-19575, 00000, "expected %s blocks in file %s, found %s"
// *Cause:  During a backup, restore, copy, or scan operation, the indicated
//          file did not contain as many blocks as were indicated in the file
//          header.
// *Action: The input copy or backup piece is probably corrupt.  If another
//          backup or copy exists of the file that is being restored, then the
//          corrupt file can be deleted from the recovery catalog and the
//          operation can be restarted.

Archivelog directory became full, so some archivelogs have been moved to another directory. In the process of moving in and out of the archivelog directory, one archivelog became 
corrupted and now RMAN is reporting errors during the backup of the archived redologs.

How to get past this archivelog and establish a new restore point past this file.


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

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