6 Replies Latest reply: Nov 24, 2013 7:42 AM by CKPT RSS

    Is DB_FILE_NAME_CONVERT parameter not required when using ASM ?

    martin75

      11.2.0.3 RAC on RHEL 6.2

       

      When creating standby DB using RMAN DUPLICATE , don't we have to set DB_FILE_NAME_CONVERT if we are using ASM ?

        • 1. Re: Is DB_FILE_NAME_CONVERT parameter not required when using ASM ?
          TSharma-Oracle

          It is only required(ASM or NON ASM), if you are restoring files into a different location as primary database.

           

          If you are restoring files onto different location than primary, you do need to use this parameter. It is not needed if your location is same on different server.

          • 2. Re: Is DB_FILE_NAME_CONVERT parameter not required when using ASM ?
            mseberg

            Hello;

             

            If the ASM setup on the Primary and Standby are the same then no.

             

            If they are different you might. So are your Disk Group names the same? If yes then no you don't have to set it.

             

            select name, free_mb, total_mb from v$asm_diskgroup;

             

            Best Regards

             

            mseberg

            • 3. Re: Is DB_FILE_NAME_CONVERT parameter not required when using ASM ?
              CKPT

              When creating standby DB using RMAN DUPLICATE , don't we have to set DB_FILE_NAME_CONVERT if we are using ASM ?

               

              Depends on the data files on standby where you would prefer to place , If you prefer same location then no need to set DB_FILE_NAME_CONVERT, If you prefer to place data files other locations then indeed it is requried. When the locations are different you must use "SET NEWNAME" clause.

               

              If you are using OMF(oracle managed files), when you run RMAN Duplicate when there is no any location specified then they will be created in DB_CREATE_FILE_DEST of course if you mention "SET NEWNAME" then DB_CREATE_FILE_DEST no longer it will be considered.

              • 4. Re: Is DB_FILE_NAME_CONVERT parameter not required when using ASM ?
                martin75

                1.

                The locations are different in primary and standby. If DB_CREATE_FILE_DEST takes care of it, then it is more neater that me manually creating ASM directories and setting

                *.DB_FILE_NAME_CONVERT='+DATA/cmps/','+EMS_DATA/ems/DATAFILE/'

                 

                 


                2.

                SET NEWNAME is used when you do plain RMAN backup, restore not for RMAN DUPLICATE. Right ?

                 

                BTW.. Is there a technical name for 'plain RMAN backup, restore' ?

                • 5. Re: Is DB_FILE_NAME_CONVERT parameter not required when using ASM ?
                  TSharma-Oracle

                   

                  martin75 wrote:

                   

                  1.

                  The locations are different in primary and standby. If DB_CREATE_FILE_DEST takes care of it, then it is more neater that me manually creating ASM directories and setting

                  *.DB_FILE_NAME_CONVERT='+DATA/cmps/','+EMS_DATA/ems/DATAFILE/'


                  DB_FILE_NAME_CONVERT will have precedence over DB_CREATE_FILE_DEST, So if you use db_file_name_convert, it will ignore db_file_create_dest. Your syntax is right.

                   

                   


                  2.

                  SET NEWNAME is used when you do plain RMAN backup, restore not for RMAN DUPLICATE. Right ?

                   

                  BTW.. Is there a technical name for 'plain RMAN backup, restore' ?

                   

                  I think plain RMAN backup generally means normal RMAN full backup. You are wrong, you can give 'SET NEWNAME' for RMAN duplicate also. See This link:

                   

                  RUN { SET NEWNAME FOR DATAFILE 1 TO /oracle/data/file2.f; # rename df 1 as file2.f SET NEWNAME FOR DATAFILE 2 TO /oracle/data/file1.f; # rename df 2 as file1.f DUPLICATE TARGET DATABASE TO newdb; } 

                   

                  For more info check this:

                   

                  http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmdupdb.htm

                  • 6. Re: Is DB_FILE_NAME_CONVERT parameter not required when using ASM ?
                    CKPT

                    martin75 wrote:

                     

                    1.

                    The locations are different in primary and standby. If DB_CREATE_FILE_DEST takes care of it, then it is more neater that me manually creating ASM directories and setting

                    *.DB_FILE_NAME_CONVERT='+DATA/cmps/','+EMS_DATA/ems/DATAFILE/'

                     

                     


                    2.

                    SET NEWNAME is used when you do plain RMAN backup, restore not for RMAN DUPLICATE. Right ?

                     

                    BTW.. Is there a technical name for 'plain RMAN backup, restore' ?

                     

                    I think you have answer for 1 already, for 2nd question i would like to add...

                    SET NEWNAME is used in restoring database, DB_FILE_NAME_CONVERT is the similar thing in RMAN DUPLICATE.