ORA-19575

ORA-19575 During RMAN Backup (Doc ID 1518129.1)

APPLIES TO:

Oracle Server - Enterprise Edition - Version 11.1.0.7 and later
Information in this document applies to any platform.

GOAL

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 dirictory got full, so some archivelogs have been moved to another directory. In the process of moving in and out of the archivelog dir, one archivelog got
corrupted and now RMAN is reporting errors during the backup of the archived redologs.

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

FIX

1) Validate all archivelogs for corruption:

RMAN> validate archivelog all;

2) Move any corrupted archivelog to a temporary directory using an operating system command such as cp

For example:

$ mv /opt/app/oracle/oradata/ORA112/archivelog/2013_01_11/o1_mf_1_84_8gyj98c3_.arc /tmp/.

3) Then run a crosscheck command to update RMAN's repository. Any files that have been moved will now be marked as expired and RMAN will no longer attempt to back them up.

RMAN> crosscheck archivelog all;

4) You can then proceed to take a full database and archivelog backup.

WARNING !!!! Any archivelogs that are corrupted cannot be used for recovery, so the recoverability of the database is comprimised.