This content has been marked as final. Show 6 replies
1)Backup piece is corrupt
2)Backup piece is expired
For 1 run VALIDATE BACKUPSET command
For 2 run CROSSCHECK BACKUPSET
What is this file?
It does not look like a database file that RMAN would backup. How is it created?
This file is created by the backup backupset command:
RMAN>backup backupset completed after 'sysdate-12/24' format '/export/db_back/oracle/backupsets/%d_BUBS_%U.bak';
This allows you to have the backup in an additional location.
I tested with a slightly different path
On 220.127.116.11 and Linux without issue.
backup backupset completed after 'sysdate-12/24' format '/u01/export/db_back/oracle/backupsets/%d_BUBS_%U.bak';
Will try something else to recreate.
If I change the command and remove "s" from backupset I get the error above.
channel ORA_DISK_1: backup piece /u01/export/db_back/oracle/backupsets/RECOVER2_BUBS_0onvgob6_1_2.bak RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on ORA_DISK_1 channel at 01/16/2013 12:23:41 ORA-19504: failed to create file "/u01/export/db_back/oracle/backupset/RECOVER2_BUBS_0onvgob6_1_3.bak" ORA-27040: file create error, unable to create file Linux-x86_64 Error: 2: No such file or directory Additional information: 1 ORA-19600: input file is backup piece (/u01/export/db_back/oracle/backupsets/RECOVER2_BUBS_0onvgob6_1_2.bak) ORA-19601: output file is backup piece (/u01/export/db_back/oracle/backupset/RECOVER2_BUBS_0onvgob6_1_3.bak)
Any chance the path has changed slightly? So the space available is too low for the file create?
Edited by: mseberg on Jan 16, 2013 12:24 PM
Good call, but no joy. Path is correct in script and no changes made to the file structure. Right now I'm going back through logs to see if I can find when it started and see if it could have been a patch or something.
The archivelog backup piece is over 50GB and causing issues with rman moving to the NFS file system. Our archivelog directory in ASM is over 1 TB, so somewhere along the line archivelogs where not removed properly and not getting a solid backup with each level 1. We will be taking a level 0 backup, and go from there. I'll post results and steps taken when it's ready.