8 Replies Latest reply on Aug 13, 2015 1:12 PM by EdStevens

    RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed ORA-00349: failure obtaining block size for ' vdbcl01_data_01'

    678298

      Hi All,

       

      I am in the process of creating duplicate database on different server with different name.

       

      Both DB in same version of oracle - 11.2..0.3

      Both server/system - Oracle Solaris 11.1 SPARC

       

      Both DBs using different diskgroups.

       

      Below process i used for this work.

       

      1. Copy pfile from source db and sent to auxiliary DB machine and modify as below.

       

      *.audit_file_dest='/u01/app/oracle/admin/EW2PRD/adump'

      *.audit_trail='OS'

      *.compatible='11.2.0.3.0'

      *.control_files='+PRDCL01_DATA_01/EW2PRD/controlfile/current.669.879366659','+PRDCL01_RECO_01/EW2PRD/controlfile/current.2818.879366661'#Restore Controlfile

      *.cpu_count=2

      *.db_block_size=8192

      *.db_create_file_dest='+PRDCL01_DATA_01'

      *.db_create_online_log_dest_1='+PRDCL01_DATA_01'

      *.db_create_online_log_dest_2='+PRDCL01_RECO_01'

      *.db_domain=''

      *.db_name='EW2PRD'

      *.db_recovery_file_dest='+PRDCL01_RECO_01'

      *.db_recovery_file_dest_size=42949672960

      *.db_unique_name='EW2PRD'

      *.diagnostic_dest='/u01/app/oracle'

      *.db_file_name_convert=('+VDBCL01_DATA_01/EW1TST','+PRDCL01_DATA_01/EW2PRD')

      *.log_file_name_convert=('+VDBCL01_RECO_01/EW1TST','+PRDCL01_RECO_01/EW2PRD')

      *.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST valid_for=(ALL_LOGFILES, ALL_ROLES)'

      *.log_archive_format='%t_%s_%r.dbf'

      *.nls_territory='AUSTRALIA'

      *.open_cursors=300

      *.pga_aggregate_target=320M

      *.processes=200

      *.remote_login_passwordfile='EXCLUSIVE'

      *.resource_manager_plan='DEFAULT_MAINTENANCE_PLAN'

      *.sessions=225

      *.sga_target=498M

      *.undo_tablespace='UNDO_01'

       

       

      2. perform all required steps to get this thing work (startup nomount, tnsnames, password file etc)

       

      3. rman target sys/racqld@EW1TST auxiliary /

       

      4. duplicate target database to EW2PRD;

       

      it gives me below error ...

       

      sql statement: CREATE CONTROLFILE REUSE SET DATABASE "EW2PRD" RESETLOGS ARCHIVELOG

        MAXLOGFILES     16

        MAXLOGMEMBERS      3

        MAXDATAFILES      100

        MAXINSTANCES     8

        MAXLOGHISTORY     1266

      LOGFILE

        GROUP   1 ( '+prdcl01_reco_01', '+vdbcl01_data_01' ) SIZE 50 M  REUSE,

        GROUP   2 ( '+prdcl01_reco_01', '+vdbcl01_data_01' ) SIZE 50 M  REUSE,

        GROUP   3 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE,

        GROUP   4 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE,

        GROUP   5 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE

      DATAFILE

        '+PRDCL01_DATA_01/ew2prd/datafile/system.5002.885775461'

      CHARACTER SET WE8MSWIN1252

       

       

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

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

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

      RMAN-03002: failure of Duplicate Db command at 07/23/2015 00:46:45

      RMAN-05501: aborting duplication of target database

      RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed

      ORA-00349: failure obtaining block size for '+vdbcl01_data_01'

       

       

      I am out of idea here, what other things i need to do to get this working. please share your valuable views/suggestions/solutions. Thanks in advance.

       

      Cheers.

        • 1. Re: RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed ORA-00349: failure obtaining block size for ' vdbcl01_data_01'
          Dude!

          Is it possible that the target database uses a control file that is not mentioned in the "db_file_name_convert" parameter of your auxiliary instance, and which need to be added?

           

          When you connect to the target database via sqlplus as sysdba, what is the result of "show parameter control_files"?

          • 2. Re: RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed ORA-00349: failure obtaining block size for ' vdbcl01_data_01'
            678298

            Yes I did check as well but pfile is showing correct location.

             

            SQL> show parameter control_file;

             

             

            NAME                                 TYPE        VALUE

            ------------------------------------ ----------- ------------------------------

            control_file_record_keep_time        integer     7

            control_files                        string      +VDBCL01_DATA_01/ew1tst/contro

                                                             lfile/current.669.879366659, +

                                                             VDBCL01_RECO_01/ew1tst/control

                                                             file/current.2818.879366661

            SQL>

             

            and my pfile entry for control file is...

             

            *.control_files='+PRDCL01_DATA_01/EW2PRD/controlfile/current.669.879366659','+PRDCL01_RECO_01/EW2PRD/controlfile/current.2818.879366661'#Restore Controlfile

            • 3. Re: RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed ORA-00349: failure obtaining block size for ' vdbcl01_data_01'
              678298

              And this is what i am getting in alert.log

               

              Starting background process MARK

              Thu Jul 23 00:46:41 2015

              MARK started with pid=20, OS id=16829

              NOTE: MARK has subscribed

              Thu Jul 23 00:46:42 2015

              CREATE CONTROLFILE REUSE SET DATABASE "EW2PRD" RESETLOGS ARCHIVELOG

                MAXLOGFILES     16

                MAXLOGMEMBERS      3

                MAXDATAFILES      100

                MAXINSTANCES     8

                MAXLOGHISTORY     1266

              LOGFILE

                GROUP   1 ( '+prdcl01_reco_01', '+vdbcl01_data_01' ) SIZE 50 M  REUSE,

                GROUP   2 ( '+prdcl01_reco_01', '+vdbcl01_data_01' ) SIZE 50 M  REUSE,

                GROUP   3 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE,

                GROUP   4 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE,

                GROUP   5 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE

              DATAFILE

                '+PRDCL01_DATA_01/ew2prd/datafile/system.5002.885775461'

              CHARACTER SET WE8MSWIN1252

              WARNING: Default Temporary Tablespace not specified in CREATE DATABASE command

              Default Temporary Tablespace will be necessary for a locally managed database in future release

              NOTE: Loaded library: OSS

              NOTE: Loaded library: System

              SUCCESS: diskgroup PRDCL01_DATA_01 was mounted

              ERROR: failed to establish dependency between database EW2PRD and diskgroup resource ora.PRDCL01_DATA_01.dg

              Errors in file /u01/app/oracle/diag/rdbms/ew2prd/EW2PRD/trace/EW2PRD_ora_16836.trc:

              ORA-00349: failure obtaining block size for '+vdbcl01_data_01'

              ORA-1503 signalled during: CREATE CONTROLFILE REUSE SET DATABASE "EW2PRD" RESETLOGS ARCHIVELOG

                MAXLOGFILES     16

                MAXLOGMEMBERS      3

                MAXDATAFILES      100

                MAXINSTANCES     8

                MAXLOGHISTORY     1266

              LOGFILE

                GROUP   1 ( '+prdcl01_reco_01', '+vdbcl01_data_01' ) SIZE 50 M  REUSE,

                GROUP   2 ( '+prdcl01_reco_01', '+vdbcl01_data_01' ) SIZE 50 M  REUSE,

                GROUP   3 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE,

                GROUP   4 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE,

                GROUP   5 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE

              DATAFILE

              '+PRDCL01_DATA_01/ew2prd/datafile/system.5002.885775461'

              CHARACTER SET WE8MSWIN1252

              ...

              SUCCESS: diskgroup PRDCL01_DATA_01 was dismounted

              Thu Jul 23 00:49:47 2015

              NOTE: ASMB process exiting due to lack of ASM file activity for 182 seconds

              Stopping background process RBAL

              Stopping background process MARK

              Thu Jul 23 00:49:49 2015

              NOTE: Shutting down MARK background process

              • 4. Re: RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed ORA-00349: failure obtaining block size for ' vdbcl01_data_01'
                Hemant K Chitale

                Seems to be erroring on the DiskGroup BlockSize !

                 

                Connect to the ASM instance and check the block size (check the sector size as well)

                 

                 

                What Grid Infrastructure version is installed and running ?  (for database 11.2.0.3,  GI should be 11.2.0.3 or higher).

                 

                 

                Hemant K Chitale

                1 person found this helpful
                • 5. Re: RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed ORA-00349: failure obtaining block size for ' vdbcl01_data_01'
                  Dude!

                  I wonder about naming the controlfiles under ASM, which uses OMF. What happens if you change the following:

                   

                  *.control_files='+PRDCL01_DATA_01','+PRDCL01_DATA_01'

                  • 6. Re: RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed ORA-00349: failure obtaining block size for ' vdbcl01_data_01'
                    AJ

                    Hi

                     

                    Get rid of the db_file_name_convert and log_file_name_convert. When using OMF (asm) they are not supported. And db_create_file_dest takes presedence anyhow. Maybe the mix are giving you problems.

                     

                    "If the source database files are in the Oracle Managed Files (OMF) format, then you cannot use the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT initialization parameters or the fileNameConversionSpec clause to generate new OMF file names for the duplicate database. If you do not follow this rule, the new OMF files generated from these three methods can cause problems. For more information on OMF names, see the "Considerations When Renaming OMF Auxiliary Set Files in TSPITR" in the Oracle Database Backup and Recovery User's Guide"


                    http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#i81724

                     

                    Regards

                    AJ

                    • 7. Re: RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed ORA-00349: failure obtaining block size for ' vdbcl01_data_01'
                      Pavan Kumar

                      Hi,

                       

                      *.db_file_name_convert=('+VDBCL01_DATA_01/EW1TST','+PRDCL01_DATA_01/EW2PRD')
                      *.log_file_name_convert=('+VDBCL01_RECO_01/EW1TST','+PRDCL01_RECO_01/EW2PRD')


                        GROUP   1 ( '+prdcl01_reco_01', '+vdbcl01_data_01' ) SIZE 50 M  REUSE,
                        GROUP   2 ( '+prdcl01_reco_01', '+vdbcl01_data_01' ) SIZE 50 M  REUSE,
                        GROUP   3 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE,
                        GROUP   4 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE,
                        GROUP   5 ( '+vdbcl01_data_01', '+prdcl01_reco_01' ) SIZE 50 M  REUSE

                       

                      Why does above ORL, are abit different does both diskgroups exists  in ASM    +prdcl01_reco_01' ?

                      Is this duplicate carried out on same server ?

                       

                      - Pavan Kumar N

                      • 8. Re: RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed ORA-00349: failure obtaining block size for ' vdbcl01_data_01'
                        EdStevens

                        AJ wrote:

                         

                        Hi

                         

                        Get rid of the db_file_name_convert and log_file_name_convert. When using OMF (asm) they are not supported. And db_create_file_dest takes presedence anyhow. Maybe the mix are giving you problems.

                         

                        "If the source database files are in the Oracle Managed Files (OMF) format, then you cannot use the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT initialization parameters or the fileNameConversionSpec clause to generate new OMF file names for the duplicate database. If you do not follow this rule, the new OMF files generated from these three methods can cause problems. For more information on OMF names, see the "Considerations When Renaming OMF Auxiliary Set Files in TSPITR" in the Oracle Database Backup and Recovery User's Guide"


                        http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#i81724

                         

                        Regards

                        AJ

                        YOu should have included the next paragraph:

                         

                        The only exception to this rule is when changing only an ASM disk group name. Assume that source data files and online redo log files are stored in ASM disk group +SOURCEDSK. You want to store the duplicate database files in ASM disk group +DUPDSK. In this case, you can set the initialization parameters as follows:

                        DB_FILE_NAME_CONVERT = ("+SOURCEDSK","+DUPDSK") LOG_FILE_NAME_CONVERT = ("+SOURCEDSK","+DUPDSK")