1 2 Previous Next 17 Replies Latest reply: Jan 9, 2013 9:48 AM by zedd RSS

    RMAN Restore Issues

    940673
      Hi All,

      I have performing a Production to a Dev server refresh. I have taken a full backup from production and trying to restore it in dev setup..

      I have shipped the backup from production to dev box... I have created a database and put it in nomount mode..

      Then I am trying to restore the controlfile but I am gettign the below error:


      RMAN> restore controlfile from '/orabackup/bkp_030113/controlprod.ctl';

      Starting restore at 04-JAN-13
      using target database control file instead of recovery catalog
      allocated channel: ORA_DISK_1
      channel ORA_DISK_1: SID=198 device type=DISK

      RMAN-00571: ===========================================================
      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
      RMAN-00571: ===========================================================
      RMAN-03002: failure of restore command at 01/04/2013 17:50:35
      RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece


      Please suggest.

      Regards,
      Arijit
        • 1. Re: RMAN Restore Issues
          Fran
          you must be sure that rman knows of this backup.

          rman> CATALOG START WITH '/.../..../.../your_full_backup';
          rman> list backup summary; --check the backup
          rman> restore controlfile from '/orabackup/bkp_030113/controlprod.ctl';

          also check and set if needed the correct incarnation

          rman> list incarnation;
          if needed:
          rman> reset database to incarnation 1;
          • 2. Re: RMAN Restore Issues
            Troll35
            Hello,

            Was the file controlprod.ctl generated with RMAN, or is it a simple copy of your production controlfile?
            It is a strange name for a file generated by RMAN.

            Regards,
            • 3. Re: RMAN Restore Issues
              940673
              HI,

              While taking the backup I have mentioned the control name to be like this.. Please check my below backup script:-

              run {
              allocate channel t1 type disk;
              allocate channel t2 type disk;
              allocate channel t3 type disk;
              allocate channel t4 type disk;
              allocate channel t5 type disk;
              backup current controlfile format '/orabackup/bkp_030113/controlprod.ctl';
              backup database format '/orabackup/bkp_030113/data_%d_%t_%s.dbf';
              backup archivelog all format '/orabackup/bkp_030113/arch_%d_%t_%s.dbf';
              release channel t1;
              release channel t2;
              release channel t3;
              release channel t4;
              release channel t5;
              }


              Regards,
              Arijit
              • 4. Re: RMAN Restore Issues
                Troll35
                Hello,

                What is your Oracle version?

                Regards,
                • 5. Re: RMAN Restore Issues
                  940673
                  Oracle Version 11.2.0.1
                  • 6. Re: RMAN Restore Issues
                    Troll35
                    Ok.

                    Could you go on your production system, and run the following
                    rman target /
                    show all;
                    and post the results?

                    Regards.
                    • 7. Re: RMAN Restore Issues
                      940673
                      My OS Version is Linux blrdlvremoradb01 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
                      • 8. Re: RMAN Restore Issues
                        940673
                        HI,

                        RMAN> show all;

                        using target database control file instead of recovery catalog
                        RMAN configuration parameters for database with db_unique_name RACDB are:
                        CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
                        CONFIGURE BACKUP OPTIMIZATION OFF; # default
                        CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
                        CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
                        CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
                        CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
                        CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
                        CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
                        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


                        Regards,
                        Arijit
                        • 9. Re: RMAN Restore Issues
                          940673
                          Hi All,

                          Just want to let you know whether I can restore a production database which is in Sun OS to Linux box??
                          • 10. Re: RMAN Restore Issues
                            Troll35
                            Hi,

                            I have never tried to restore without autobackup for controlfile, but the documentation says that in that case, you should specify DBID.

                            You can find DBID when you connect to your production database with RMAN. It should display something like that :
                            Recovery Manager: Release 11.2.0.1.0 - Production on Ven. Janv. 4 11:56:20 2013
                            
                            Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
                            
                            connectected to target database : XXXXXX (DBID=12345678)
                            Then on your dev system, in RMAN, you type (replace 12345678 with your DBID, of course) :
                            set DBID 12345678;
                            Then try your restore command.

                            Regards.
                            • 11. Re: RMAN Restore Issues
                              940673
                              Hi,

                              I have set the DBID and tried to do the restore operation. But the error persists.. Please suggest.

                              Regards,
                              Arijit
                              • 12. Re: RMAN Restore Issues
                                Troll35
                                Hello,

                                If the OS are not the same between dev and prod system, I think this is the cause of your error.

                                RMAN provides some CONVERT function, however. I have never used them, but here is the link to the documentation :
                                http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta012.htm#ABC27858558SRI12345

                                Hope it will help.

                                Regards.
                                • 13. Re: RMAN Restore Issues
                                  Aman....
                                  Did you try what Fran has suggested earlier to you?

                                  Aman....
                                  • 14. Re: RMAN Restore Issues
                                    CKPT
                                    RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece
                                    Can you check the permission of the backup file after you moved from production to development box?
                                    $ls -ltr /orabackup/bkp_030113/controlprod.ctl
                                    And ensure you set DBID of production database.

                                    BTW, FRA is configured?
                                    As work around you can try disable and after successful restore, Again you can enable FRA.
                                    1 2 Previous Next