1 2 3 4 Previous Next 45 Replies Latest reply: Mar 20, 2013 5:40 AM by cliff64 Go to original post RSS
      • 30. Re: RMAN again?
        yxes2013
        Thanks dear :)

        By the way, my boss ask me to put on-hold this RMAN test and prioritize the Active/Passive failover test :( Do you have any docs about it?

        Can I test it using VMbox? I have a sample test config of RAC using VMbox given to me by my friend. Do you know how to make it Active/Passive?
        It is like the shared disk is mounted at one node only and not accessing by the other node. The RAC setup given by my friend is both active/active :(

        Helppp....


        Thanksssss
        • 31. Re: RMAN again?
          Hemant K Chitale
          I have a sample test config of RAC using VMbox given to me by my friend. Do you know how to make it Active/Passive?
          No.


          Hemant K Chitale
          • 32. Re: RMAN again?
            yxes2013
            Hi Hem and all,

            Back to RMAN backup....

            I was able now to backup my db using rman, and I checked the output files...
            oracleprod cd /u01/app/oracle/flash_recovery_area/ORCL/backupset/2013_03_20
             ls -l
            total 4990728
            -rw-r----- 1 oracle oinstall    4908032 2013-03-20 19:20 o1_mf_annnn_TAG20130320T192051_8nm6wmcj_.bkp
            -rw-r----- 1 oracle oinstall 5100584960 2013-03-20 19:20 o1_mf_nnndf_TAG20130320T191641_8nm6nsfs_.bkp
            I guess the big gfile is my db backup, what is this smaller file?


            Thanks,
            • 33. Re: RMAN again?
              Hemant K Chitale
              You didn't bother to read the messages that RMAN presented or spool them or redirect them to a log file which you could view ?
              The messages would have told you "which is which".

              Hemant K Chitale
              • 34. Re: RMAN again?
                yxes2013
                Thanks :)

                I tried running backup again, but I got this error :(
                sql statement: ALTER SYSTEM ARCHIVE LOG CURRENT
                
                Starting backup at 20-MAR-13
                current log archived
                using channel ORA_DISK_1
                RMAN-00571: ===========================================================
                RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
                RMAN-00571: ===========================================================
                RMAN-03002: failure of backup command at 03/20/2013 22:48:03
                RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
                ORA-19625: error identifying file /u01/app/oracle/product/10g/db_1/dbs/arch1_152_808421649.dbf
                ORA-27037: unable to obtain file status
                Linux-x86_64 Error: 2: No such file or directory
                Additional information: 3
                
                Recovery Manager complete.
                Why is it looking for this lost archive log when it is not needed in the recovery because I am doing a current backup.

                Thanks,
                • 35. Re: RMAN again?
                  Hemant K Chitale
                  Read the RMAN documentation to find out what "BACKUP ARCHIVELOG ALL" actually does and read the RMAN documentation to find out how CROSSCHECK and DELETE EXPIRED can handle deleted archivelogs.

                  That should force you to read the documentation that you find difficult/confusing.

                  Hemant K Chitale
                  • 36. Re: RMAN again?
                    yxes2013
                    Yeah... I tried that cross check and delete obsolete, but still the error persist.

                    How do I know if my database has a corresponding standby Db which is waiting for this missing log? Is there a V$ view if a standby db was created?

                    My issue is similar to Dan's
                    Re: ORA-19625: error identifying file
                    Thanks a lot,

                    Edited by: yxes2013 on 20.3.2013 0:57
                    • 37. Re: RMAN again?
                      Hemant K Chitale
                      DELETE OBSOLETE or DELETE EXPIRED ? Know the difference between OBSOLETE and EXPIRED.


                      Hemant K Chitale
                      • 38. Re: RMAN again?
                        yxes2013
                        ok wait I try it again.

                        have you tried setting up standby? is there a tied up cohesion for the two databases? I mean the other can not just get free alone?

                        Hello....I tried the delete expired but still I got error :(
                        RMAN-06207: WARNING: 4 objects could not be deleted for DISK channel(s) due
                        RMAN-06208:          to mismatched status.  Use CROSSCHECK command to fix status
                        RMAN-06210: List of Mismatched objects
                        RMAN-06211: ==========================
                        RMAN-06212:   Object Type   Filename/Handle
                        RMAN-06213: --------------- ---------------------------------------------------
                        RMAN-06214: Backup Piece    /usr/tmp/GS/test1/X.dbvisit.abc124.test1.standbycontrolfile
                        RMAN-06214: Backup Piece    /usr/tmp/GS/test1/X.dbvisit.abc123.test1.standbycontrolfile
                        RMAN-06214: Backup Piece    /usr/tmp/GS/test1/X.dbvisit.abc126.test1.standbycontrolfile
                        RMAN-06214: Backup Piece    /usr/tmp/GS/test1/X.dbvisit.abc125.test1.standbycontrolfile
                        Edited by: yxes2013 on 20.3.2013 1:11
                        • 39. Re: RMAN again?
                          yxes2013
                          connected to target database: TEST1 (DBID=1185464014)
                          
                          RMAN> run {
                          2>      crosscheck archivelog all;
                          3>      delete noprompt expired archivelog all;
                          4>      delete obsolete;
                          5>      }
                          6>
                          using target database control file instead of recovery catalog
                          allocated channel: ORA_DISK_1
                          channel ORA_DISK_1: sid=144 devtype=DISK
                          validation succeeded for archived log
                          archive log filename=/u01/app/oracle/flash_recovery_area/TEST1/archivelog/2013_03_20/o1_mf_1_721_8nmo95l7_.arc recid=660 stamp=810602789
                          validation succeeded for archived log
                          archive log filename=/u01/app/oracle/flash_recovery_area/TEST1/archivelog/2013_03_20/o1_mf_1_722_8nmo95wo_.arc recid=661 stamp=810602790
                          Crosschecked 2 objects
                          
                          
                          released channel: ORA_DISK_1
                          allocated channel: ORA_DISK_1
                          channel ORA_DISK_1: sid=144 devtype=DISK
                          specification does not match any archive log in the recovery catalog
                          
                          RMAN retention policy will be applied to the command
                          RMAN retention policy is set to redundancy 1
                          using channel ORA_DISK_1
                          Deleting the following obsolete backups and copies:
                          Type                 Key    Completion Time    Filename/Handle
                          -------------------- ------ ------------------ --------------------
                          Backup Set           5      27-FEB-13
                            Backup Piece       5      27-FEB-13          /usr/tmp/GS/test1/X.dbvisit.abc124.test1.standbycontrolfile
                          Backup Set           4      27-FEB-13
                            Backup Piece       4      27-FEB-13          /usr/tmp/GS/test1/X.dbvisit.abc123.test1.standbycontrolfile
                          Backup Set           7      01-MAR-13
                            Backup Piece       7      01-MAR-13          /usr/tmp/GS/test1/X.dbvisit.abc126.test1.standbycontrolfile
                          Backup Set           6      01-MAR-13
                            Backup Piece       6      01-MAR-13          /usr/tmp/GS/test1/X.dbvisit.abc125.test1.standbycontrolfile
                          
                          RMAN-06207: WARNING: 4 objects could not be deleted for DISK channel(s) due
                          RMAN-06208:          to mismatched status.  Use CROSSCHECK command to fix status
                          RMAN-06210: List of Mismatched objects
                          RMAN-06211: ==========================
                          RMAN-06212:   Object Type   Filename/Handle
                          RMAN-06213: --------------- ---------------------------------------------------
                          RMAN-06214: Backup Piece    /usr/tmp/GS/test1/X.dbvisit.abc124.test1.standbycontrolfile
                          RMAN-06214: Backup Piece    /usr/tmp/GS/test1/X.dbvisit.abc123.test1.standbycontrolfile
                          RMAN-06214: Backup Piece    /usr/tmp/GS/test1/X.dbvisit.abc126.test1.standbycontrolfile
                          RMAN-06214: Backup Piece    /usr/tmp/GS/test1/X.dbvisit.abc125.test1.standbycontrolfile
                          
                          
                          Recovery Manager complete.
                          • 40. Re: RMAN again?
                            Hemant K Chitale
                            Do you really think that "X.dbvisit.abc124.test1.standbycontrolfile" is an Archivelog or a Backup of an Archivelog ?
                            What did you CROSSCHECK ? Archivelogs.
                            So what would be expired ? Archivelogs.
                            What is "X.dbvisit.abc124.test1.standbycontrolfile" ? Not an Archivelog.


                            Hemant K Chitale
                            • 41. Re: RMAN again?
                              yxes2013
                              I thought only acrhivelogs are crosschecked :(

                              is there CROSSCHECK ALL?
                              • 42. Re: RMAN again?
                                Hemant K Chitale
                                Do yourself a favour. Lookup the documentation.

                                See "maintSpec" in the CROSSCHECK command http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta015.htm#i81077


                                Hemant K Chitale
                                • 43. Re: RMAN again?
                                  yxes2013
                                  I dont understand the docs :(

                                  My issue is similar to this, but I do not know how to do the correct syntax.
                                  Here's the right command to CROSSCHECK a single CONTROLFILECOPY - this will be 
                                  our template:
                                  
                                     RMAN> crosscheck controlfilecopy "/scratch/oradata/DBNAME/backups/2005_07_21.backup.ctl";
                                     
                                     using target database controlfile instead of recovery catalog
                                     allocated channel: ORA_DISK_1
                                     channel ORA_DISK_1: sid=35 devtype=DISK
                                     validation failed for controlfile copy
                                     controlfile copy filename=/scratch/oradata/DBNAME/backups/2005_07_21.backup.ctl recid=25 stamp=564271666
                                     Crosschecked 1 objects
                                  How do i relate to this?
                                  • 44. Re: RMAN again?
                                    cliff64
                                    Hi

                                    This issue is about a archive log deleted but required to restore the database.
                                    If such archive log is deleted you can not restore unless you restore to point in time before the archivelog (not always possible) was created
                                    eg If the archivelog was created during the backup restore is not possible.
                                    If you can take another backup and make sure you never delete archivelogs if you need to delete archivelogs do it in RMAN
                                    As for the extra file that is smaller in size in the backup dir is probably a backup of your controlfile.
                                    You can check by checking the log file of your backup.
                                    Also check your RMAN setting by typing show all;
                                    The following is default setting but should be changed
                                    show all;
                                    CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
                                    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
                                    Change the CONTROLFILE AUTOBACKUP OFF; to ON
                                    and you can either leave the second parameter like is thus backup the control file to the same location as other backup files
                                    or
                                    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u1/backups/controlfiles/my_db_%F'; # default

                                    Remember if you don't use a recovery catalog and loose your controlfiles and backups of the control file restore is impossible
                                    one example to delete archivelog backup is to issue 'delete archivelog absolete'

                                    Hope this helps a bit

                                    Archivelog EXPIRED (RMAN can not access it probably deleted)
                                    Archivelog OBSOLTE (File exsist but not needed (check retention policy)
                                    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default (id you have space change to 2 or even 3)
                                    If retention policy=1 all files older than the last backup is obsolete.

                                    Here is a example of how I delete the archivelogs
                                    backup
                                    as backupset
                                    format '\\10.1.1.18\e$\backup\rman\server1\db1\arch\mydb1_rman_arch_%U'
                                    tag 'MYDB_ARCH'
                                    archivelog all not backed up 1 times
                                         delete input;

                                    41> crosscheck backupset;
                                    42> crosscheck archivelog all;
                                    43> delete noprompt obsolete device type disk;
                                    44> delete noprompt expired backupset device type disk;

                                    Cliff Nel

                                    Edited by: cliff64 on Mar 20, 2013 3:35 AM