This script runs and poof there goes recoverability.Īnd the second which makes me cringe is the two step file removal. While it's not so common with all the safeguards we put in place for backups, but I can still imagine scenarios where archivelogs don't get backed up off the server in 2 days. The first is that someone had entrusted the OS to clean up old archivelog files older than 2 days. > cat /home/oracle/scripts/rm_old_alogstrc.shlįor the benefit of those not cringing as you read that. I was going through cleaning up files on one of the database servers. RMAN-06214: Backup Piece /u01/app/oracle/admin/scripts/restore/filetest/DB_3rn2tp0j_1_1Įventually found Oracle Support Doc ID 1111603.1 on the subject.Įssentially, no, you can't catalog a backup piece that's been restored from tape to disk because the header information will be different than the file at rest on tape. RMAN-03002: failure of catalog command at 09:37:20
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS = ORA-19587: error occurred reading 0 bytes at block number 1 ORA-19870: error while restoring backup piece /u01/app/oracle/admin/scripts/restore/filetest/DB_3rn2tp0j_1_1 Using target database control file instead of recovery catalog RMAN> catalog backuppiece '/u01/app/oracle/admin/scripts/restore/filetest/DB_3rn2tp0j_1_1' Then I attempted to catalog those pieces for a recovery attempt. Attempting to work around an issue with our backup system, I copied the backup pieces from a known-good backup from tape to disk.
0 kommentar(er)
