6 Replies Latest reply: Jan 16, 2013 1:54 PM by lm_oradba RSS

    RMAN backup backupset fails

    lm_oradba
      Using 11gR2 w/RAC for database

      Running backup backupset continually fails with the following errors:

      ORA-19504: failed to create file "/export/db_back/oracle/backupsets/BUBS_2mnvhkgi_1_2.bak"
      ORA-27048: skgfifi: file header information is invalid
      Additional information: 16
      ORA-19600: input file is backup piece (+FLASH/mcat2/backupset/annnf0_warm_arch_20130116t050000_0.1097.804835859)
      ORA-19601: output file is backup piece (/export/db_back/oracle/backupsets/BUBS_2mnvhkgi_1_2.bak)

      No file permission issues.
      What can be causing this failure? I've searched for what the Additional information:16 is but have found nothing.

      Edited by: user520981 on Jan 16, 2013 9:07 AM
        • 1. Re: RMAN backup backupset fails
          vlethakula
          could be

          1)Backup piece is corrupt

          2)Backup piece is expired


          For 1 run VALIDATE BACKUPSET command

          For 2 run CROSSCHECK BACKUPSET
          • 2. Re: RMAN backup backupset fails
            mseberg
            Hello;

            What is this file?
            /export/db_back/oracle/backupsets/BUBS_2mnvhkgi_1_2.bak
            It does not look like a database file that RMAN would backup. How is it created?

            Best Regards

            mseberg
            • 3. Re: RMAN backup backupset fails
              lm_oradba
              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.
              • 4. Re: RMAN backup backupset fails
                mseberg
                Thanks.

                I tested with a slightly different path
                backup backupset completed after 'sysdate-12/24' format '/u01/export/db_back/oracle/backupsets/%d_BUBS_%U.bak';
                On 11.2.0.3 and Linux without issue.

                Will try something else to recreate.

                Second test
                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)
                If I change the command and remove "s" from backupset I get the error above.

                Any chance the path has changed slightly? So the space available is too low for the file create?

                Best Regards

                mseberg

                Edited by: mseberg on Jan 16, 2013 12:24 PM
                • 5. Re: RMAN backup backupset fails
                  lm_oradba
                  Thanks
                  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.
                  • 6. Re: RMAN backup backupset fails
                    lm_oradba
                    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.