12 Replies Latest reply on Jun 30, 2016 12:33 PM by Dude!

    ORA-19502: write error on file... - it looks like backup file has strange name

    MartinTomcik

      Hi guys

       

      Archive log location in my environment is full. I tried backup and delete archive logs by command

       

      BACKUP ARCHIVELOG ALL DELETE INPUT;

       

      but I got following error:

       

      RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/30/2016 04:49:19

      ORA-19502: write error on file "/oracle/ORAREPP/backup/ORAREPP/backupset/2016_06_30/o1_mf_annnn_TAG20160630T044827_cq924bwx_.bkp", block number 143361 (block size=512)

      ORA-27072: File I/O error

      Linux-x86_64 Error: 5: Input/output error

      Additional information: 4

      Additional information: 143361

      Additional information: -1

      channel ORA_DISK_1 disabled, job failed on it will be run on another channel

      RMAN-00571: ===========================================================

      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

      RMAN-00571: ===========================================================

      RMAN-03009: failure of backup command on ORA_DISK_2 channel at 06/30/2016 04:49:19

      ORA-19502: write error on file "/oracle/ORAREPP/backup/ORAREPP/backupset/2016_06_30/o1_mf_annnn_TAG20160630T044827_cq924ffw_.bkp", block number 114689 (block size=512)

      ORA-27072: File I/O error

      Linux-x86_64 Error: 5: Input/output error

      Additional information: 4

      Additional information: 114689

      Additional information: -1

       

      After that I checked backup location and found files:

       

      ls: cannot access o1_mf_annnn_TAG20160630T044505_cq91xrhd_.bkp: Input/output error

      ls: cannot access o1_mf_annnn_TAG20160630T044505_cq91xs9d_.bkp: Input/output error

      total 8

      -????????? ? ?      ?      ?            ? o1_mf_annnn_TAG20160630T044505_cq91xs9d_.bkp

      -????????? ? ?      ?      ?            ? o1_mf_annnn_TAG20160630T044505_cq91xrhd_.bkp

      drwxr-x--- 5 oracle dba 4096 Jun 30 00:00 ..

      drwxr-x--- 2 oracle dba 4096 Jun 30 04:45 .

       

      Any suggestion?

        • 1. Re: ORA-19502: write error on file... - it looks like backup file has strange name
          top.gun

          I don;t know what these flles are, so just do a check:

          rman> list archivelog all;

           

          Also do a crosscheck - maybe these files are not important:

          rman> crosscheck copy;

          • 2. Re: ORA-19502: write error on file... - it looks like backup file has strange name
            Hemant K Chitale

            You have an I/O error on the filesystem.  The OS can't read the directory entry properly for the two files.

             

            The filenames aren't strange.  They are automatically generated as filenames for BackupPieces for ArchiveLogs if you don't specify a FORMAT clause in the BACKUP command.

             

            Hemant K Chitale

            1 person found this helpful
            • 3. Re: ORA-19502: write error on file... - it looks like backup file has strange name
              Pavan Kumar

              Archive log location in my environment is full. I tried backup and delete archive logs by command

               

              BACKUP ARCHIVELOG ALL DELETE INPUT;

              When you FRA or Archive log location is full, how come backup command would work since its referring to same location --default to FRA (does it in that location ?)

              You need to take backup to different location and clean-up

               

              - Pavan Kumar N

              • 4. Re: Re: ORA-19502: write error on file... - it looks like backup file has strange name
                MartinTomcik

                I also executed this commands:

                crosscheck archivelog all;
                crosscheck backup;
                delete noprompt obsolete;
                delete noprompt expired archivelog all;
                delete noprompt expired backup;

                 

                And all inputs was not helpfull, there was not any obsolete or archived archive logs or expired backup.

                 

                What is idfference between this commands and yours?

                list archivelog all;

                crosscheck copy;

                • 5. Re: Re: ORA-19502: write error on file... - it looks like backup file has strange name
                  Pavan Kumar

                  And all inputs was not helpfull, there was not any obsolete or archived archive logs or expired backup.

                  all depends on your retention policy, what is the policy ? have you glanced or verified ?

                   

                  - Pavan Kumar N

                  • 6. Re: Re: ORA-19502: write error on file... - it looks like backup file has strange name
                    MartinTomcik

                    Problem was that backup which I wanted to backup was larger than backup location which I had.

                    • 7. Re: Re: ORA-19502: write error on file... - it looks like backup file has strange name
                      MartinTomcik

                      Location of archive logs is /oracle/ORAREPP/arch

                      Location of backup is /oracle/ORAREPP/backup.

                       

                      Two different filesystems. After extension of these filesystems, this command is working properly.

                      • 8. Re: Re: Re: ORA-19502: write error on file... - it looks like backup file has strange name
                        MartinTomcik

                        This is whole output of show all command:

                        RMAN> show all;

                         

                         

                        using target database control file instead of recovery catalog

                        RMAN configuration parameters for database with db_unique_name ORAREPP are:

                        CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 90 DAYS;

                        CONFIGURE BACKUP OPTIMIZATION OFF; # default

                        CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

                        CONFIGURE CONTROLFILE AUTOBACKUP ON;

                        configuration for DISK channel 3 is ignored

                        configuration for DISK channel 4 is ignored

                        configuration for DISK channel 5 is ignored

                        configuration for DISK channel 6 is ignored

                        configuration for DISK channel 7 is ignored

                        configuration for DISK channel 8 is ignored

                        CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default

                        CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;

                        CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

                        CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default

                        CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 35 G;

                        CONFIGURE CHANNEL 1 DEVICE TYPE DISK MAXPIECESIZE 35 G;

                        CONFIGURE CHANNEL 2 DEVICE TYPE DISK MAXPIECESIZE 35 G;

                        CONFIGURE CHANNEL 3 DEVICE TYPE DISK MAXPIECESIZE 35 G;

                        CONFIGURE CHANNEL 4 DEVICE TYPE DISK MAXPIECESIZE 35 G;

                        CONFIGURE CHANNEL 5 DEVICE TYPE DISK MAXPIECESIZE 35 G;

                        CONFIGURE CHANNEL 6 DEVICE TYPE DISK MAXPIECESIZE 35 G;

                        CONFIGURE CHANNEL 7 DEVICE TYPE DISK MAXPIECESIZE 35 G;

                        CONFIGURE CHANNEL 8 DEVICE TYPE DISK MAXPIECESIZE 35 G;

                        CONFIGURE MAXSETSIZE TO UNLIMITED; # default

                        CONFIGURE ENCRYPTION FOR DATABASE OFF; # default

                        CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default

                        CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default

                        CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

                        CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oraexe/product/11.2.0.3/dbs/snapcf_ORAREPP.f'; # default

                        Retention policy is set up to 90 days but only last day there was generated huge files.

                        • 9. Re: Re: Re: ORA-19502: write error on file... - it looks like backup file has strange name
                          Pavan Kumar

                          Retention policy is set up to 90 days but only last day there was generated huge files.

                          1. So your all backups are below the recovery window 90 days

                          2. when you want to backup more than required size then you should allocate the size of filesystem

                          3. Next you are giving format to specified location : its doesn't into FRA location

                           

                          . If you do not specify a value for the FORMAT parameter, then RMAN either creates the backup in the flash recovery area if it is enabled, or in a platform-specific directory (for example, ?/dbs on UNIX) if a flash recovery area is not enabled. In either case, RMAN uses the variable %U to name the backup

                           

                          Due to that its out auto-managed either archives or backups

                           

                          4. You need to adjust your retention policy and clean-up -- to resolve the issue (else look for another File system for backups)

                           

                          - Pavan Kumar N

                          1 person found this helpful
                          • 10. Re: ORA-19502: write error on file... - it looks like backup file has strange name
                            MartinTomcik

                            Thanks for very helpful advises. I`m a little bit confused because before problem, filesystem for backup has only 15GB and it was enough. Then storage colleague extend this location to 150GB but used space now is 45GB. Its 30GB+

                             

                            How its possible if all backups before extension was less than 15GB? I think I have to talk with backup team

                            • 11. Re: ORA-19502: write error on file... - it looks like backup file has strange name
                              Pavan Kumar

                              Very much possible

                              1. What is your db size ? for example let's say or consider you database is 10GB and your last backup size was File system is 15GB (currently its filled up)

                              2. Now,as you trying to take backup -- if its totally different copy from earlier then it entirely fresh backup of database --so another 10G came in and archives logs 5GB --so its comes around to 15GB fresh only

                              existing 10 GB + 15GB == 25GB

                              3. Since your backups aren't

                              -- image copy or backup (of different tags)  + not roll-forwarded  (not sure since we didn't knew your type of backups carried out) + archives logs  ---- all duplicates copies reside under one umbrella of 90 days

                              -- As you are trying multiple times --duplicated backups

                               

                              - Pavan Kumar N

                              1 person found this helpful
                              • 12. Re: ORA-19502: write error on file... - it looks like backup file has strange name
                                Dude!

                                Looking at your RMAN configuration, you have configured multiple disk channels but configured parallelism to 2, which I think is the reason for "configuration for DISK channel 3 is ignored", etc. So perhaps your previous backups were going to separate destinations, which is silly, but may explain why you have run out of space and see an I/O error writing the backup.

                                 

                                What happens if you type the following:

                                 

                                RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM  9;

                                RMAN> SHOW ALL;