1 2 Previous Next 16 Replies Latest reply on Jun 6, 2014 4:00 PM by liaison1

    Error during the RAC to RAC standby setup.

    liaison1

      tried to create a 3-node RAC standby from a 3-node RAC system with ASM.   The OS is Solaris 10 Sparc 64bits and Oracle version is 10.2.0.5.

       

       

      However, we got this message during the standby restore, I think is almost at end of the restore:

       

      channel aux2: reading from backup piece /backup/PDAMLPR1/online/PDAMLPR1_20140518_847865543_6896

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

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

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

      RMAN-03002: failure of Duplicate Db command at 05/20/2014 00:00:35

      RMAN-03015: error occurred in stored script Memory Script

      RMAN-10038: database session for channel aux2 terminated unexpectedly

       

       

       

      The archive log files are shipped but not apply.   I then tried to run recover to apply.  Got this message:

      SQL> set autorecovery on

      SQL> recover standby database;

      ORA-00283: recovery session canceled due to errors

      ORA-01110: data file 1: '+DG1/pdamlpr1/datafile/system.276.706289719'

      ORA-01157: cannot identify/lock data file 1 - see DBWR trace file

      ORA-01110: data file 1: '+DG1/pdamlpr1/datafile/system.276.706289719'

       

      Checked in the ASM +DG1/pdamlpr1/datafile, there is no such file as system.276.706289719.

       

      Question, during the restore, I also run the following at the other node:

       

      startup nomunt

      alter database mount standby database;

       

      Should I do it?

      Also, I created the standby redo log file during the restore.  Should this cause any issue?

       

      Thanks for help!

        • 1. Re: Error during the RAC to RAC standby setup.
          Hemant K Chitale

          What are the messages in the alert.log for the instance you were duplicating to ?

          How are the archive logs "shipped" ?  Oracle wouldn't be doing so if the standby were not mounted, so I presume that the instance that the primary is connecting to is mounted.

          You would be / should be using only one instance to do the DUPLICATE and RECOVER commands.

           

           

          Hemant K Chitale


          • 2. Re: Error during the RAC to RAC standby setup.
            liaison1

            Here is the error in the alert/trace file:

             

            Redo Shipping Client Connected as PUBLIC

            -- Connected User is Valid

            RFS[2]: Assigned to RFS process 21199

            RFS[2]: Identified database type as 'physical standby'

            Tue May 20 00:14:11 EDT 2014

            Errors in file /oracle/admin/PDAMLPR1/bdump/pdamlpr11_dbw0_20432.trc:

            ORA-01157: cannot identify/lock data file 11 - see DBWR trace file

            ORA-01110: data file 11: '+DG1/pdamlpr1/datafile/merckapp.266.709552615'

            ORA-17503: ksfdopn:2 Failed to open file +DG1/pdamlpr1/datafile/merckapp.266.709552615

            ORA-15012: ASM file '+DG1/pdamlpr1/datafile/merckapp.266.709552615' does not exist

            Tue May 20 00:14:11 EDT 2014

            Errors in file /oracle/admin/PDAMLPR1/bdump/pdamlpr11_dbw0_20432.trc:

            ORA-01157: cannot identify/lock data file 12 - see DBWR trace file

            ORA-01110: data file 12: '+DG1/pdamlpr1/datafile/pmetstg_data01.309.718666269'

            ORA-17503: ksfdopn:2 Failed to open file +DG1/pdamlpr1/datafile/pmetstg_data01.309.718666269

            ORA-15012: ASM file '+DG1/pdamlpr1/datafile/pmetstg_data01.309.718666269' does not exist

            Tue May 20 00:14:11 EDT 2014

            Errors in file /oracle/admin/PDAMLPR1/bdump/pdamlpr11_dbw0_20432.trc:

            ORA-01157: cannot identify/lock data file 13 - see DBWR trace file

            ORA-01110: data file 13: '+DG1/pdamlpr1/datafile/pmetstg_index01.308.718666275'

            ORA-17503: ksfdopn:2 Failed to open file +DG1/pdamlpr1/datafile/pmetstg_index01.308.718666275

            ORA-15012: ASM file '+DG1/pdamlpr1/datafile/pmetstg_index01.308.718666275' does not exist

            Tue May 20 00:14:11 EDT 2014

            Errors in file /oracle/admin/PDAMLPR1/bdump/pdamlpr11_dbw0_20432.trc:

            ORA-01157: cannot identify/lock data file 14 - see DBWR trace file

            ORA-01110: data file 14: '+DG1/pdamlpr1/datafile/pmettgt_data01.307.718666281'

            ORA-17503: ksfdopn:2 Failed to open file +DG1/pdamlpr1/datafile/pmettgt_data01.307.718666281

            ORA-15012: ASM file '+DG1/pdamlpr1/datafile/pmettgt_data01.307.718666281' does not exist

            Tue May 20 00:14:11 EDT 2014

            Errors in file /oracle/admin/PDAMLPR1/bdump/pdamlpr11_dbw0_20432.trc:

            ORA-01157: cannot identify/lock data file 15 - see DBWR trace file

            ORA-01110: data file 15: '+DG1/pdamlpr1/datafile/pmettgt_index01.306.718666283'

            ORA-17503: ksfdopn:2 Failed to open file +DG1/pdamlpr1/datafile/pmettgt_index01.306.718666283

            ORA-15012: ASM file '+DG1/pdamlpr1/datafile/pmettgt_index01.306.718666283' does not exist

            Tue May 20 00:14:11 EDT 2014

            Errors in file /oracle/admin/PDAMLPR1/bdump/pdamlpr11_dbw0_20432.trc:

            ORA-01157: cannot identify/lock data file 16 - see DBWR trace file

            ORA-01110: data file 16: '+DG1/pdamlpr1/datafile/ts_aerecon_data.305.718668215'

            ORA-17503: ksfdopn:2 Failed to open file +DG1/pdamlpr1/datafile/ts_aerecon_data.305.718668215

            ORA-15012: ASM file '+DG1/pdamlpr1/datafile/ts_aerecon_data.305.718668215' does not exist

            Tue May 20 00:14:11 EDT 2014

            Errors in file /oracle/admin/PDAMLPR1/bdump/pdamlpr11_dbw0_20432.trc:

            ORA-01157: cannot identify/lock data file 17 - see DBWR trace file

            ORA-01110: data file 17: '+DG1/pdamlpr1/datafile/ts_aerecon_index.304.718668263'

            ORA-17503: ksfdopn:2 Failed to open file +DG1/pdamlpr1/datafile/ts_aerecon_index.304.718668263

            ORA-15012: ASM file '+DG1/pdamlpr1/datafile/ts_aerecon_index.304.718668263' does not exist

            Tue May 20 00:14:11 EDT 2014

            Errors in file /oracle/admin/PDAMLPR1/bdump/pdamlpr11_dbw0_20432.trc:

            ORA-01157: cannot identify/lock data file 18 - see DBWR trace file

            ORA-01110: data file 18: '+DG1/pdamlpr1/datafile/ts_consolidated_data.303.718669789'

            ORA-17503: ksfdopn:2 Failed to open file +DG1/pdamlpr1/datafile/ts_consolidated_data.303.718669789

            ORA-15012: ASM file '+DG1/pdamlpr1/datafile/ts_consolidated_data.303.718669789' does not exist

            Tue May 20 00:14:11 EDT 2014

            Errors in file /oracle/admin/PDAMLPR1/bdump/pdamlpr11_dbw0_20432.trc:

            ORA-01157: cannot identify/lock data file 19 - see DBWR trace file

             

            ... ....

            • 3. Re: Error during the RAC to RAC standby setup.
              liaison1

              Here is the rman command to do the standby restore:
               
              RUN
              {
                ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
                ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
                DUPLICATE TARGET DATABASE for standby 
              nofilenamecheck 
              dorecover;
              }
               
              Before that we run the rman command:
               
              sql 'alter system archive log current';
              backup current controlfile for standby;
              sql 'alter system archive log current';
              BACKUP ARCHIVELOG ALL NOT BACKED UP 1 TIMES;
              crosscheck backup;
              crosscheck archivelog all;
               
               

              related the parameters in the standby parameter file:
               
              *.fal_client='PRSTD'
              *.fal_server='PRPRY'
              *.log_archive_dest_1='LOCATION=+DG3'
              *.standby_archive_dest='location=+DG3/'
              *.standby_file_management='AUTO'
              *.log_archive_max_processes=8



              BTW, We were successfully created the standby used this procedure/script in UAT environment.

              • 4. Re: Error during the RAC to RAC standby setup.
                liaison1

                The current status is the archive log files can shipped over to standby. But none of them can be applied due to the wrong file name in the standby ASM.
                 
                When I tried to manual recover, got this error:
                SQL> recover standby database;
                ORA-00283: recovery session canceled due to errors
                ORA-01110: data file 1: '+DG1/pdamlpr1/datafile/system.276.706289719'
                ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
                ORA-01110: data file 1: '+DG1/pdamlpr1/datafile/system.276.706289719'
                 
                Then I checked in the primary and standby data files from ASMCMD, for example:
                 
                Standby :
                 
                DATAFILE UNPROT COARSE MAY 20 16:00:00 Y SYSTEM.360.848067261
                 
                 
                Primary:
                 
                DATAFILE UNPROT COARSE MAY 20 02:00:00 Y SYSTEM.276.706289719
                 
                We have 31 files out of 159 in this miss match file name situation. Although when I list the file name by using 'select name from v$datafile;', the file names are match between the primary and standby. I am now sure why cause this? Let me know how to fix and prevent this from happening? Thanks



                • 5. Re: Error during the RAC to RAC standby setup.
                  Hemant K Chitale

                  In ASM, Oracle uses OMF -- so it generates the file names at the new location, which may be different.

                   

                  >Although when I list the file name by using 'select name from v$datafile;', the file names are match between the primary and standby.

                  V$DATAFILE is a query on the controlfile which might still have the old names.

                   

                  You could have used SET NEWNAME (with DB_CREATE_FILE_DEST) before the DUPLICATE.  OR  DB_FILE_NAME_CONVERT.

                   

                  See the various examples under  http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmdupad.htm#CIHIJAEH

                   

                   

                  Hemant K Chitale

                  • 6. Re: Error during the RAC to RAC standby setup.
                    liaison1

                    Tried that.  I used SETNAME for the rman standby duplication process like this:

                     

                    The issue is the archive log file can be shipped over. But not apply. The reason is some files restored to standby with different name in detail. Although I used SETNAME for each file during the duplication. This is rman duplication script:
                     
                    RUN
                    {
                     
                    SET NEWNAME FOR DATAFILE 1 to '+DG1/pdamlpr1/datafile/system.276.706289719';
                    SET NEWNAME FOR DATAFILE 2 to '+DG1/pdamlpr1/datafile/undotbs1.277.706289747';
                    SET NEWNAME FOR DATAFILE 3 to '+DG1/pdamlpr1/datafile/sysaux.278.706289757';
                    SET NEWNAME FOR DATAFILE 4 to '+DG1/pdamlpr1/datafile/undotbs2.280.706289779';
                    SET NEWNAME FOR DATAFILE 5 to '+DG1/pdamlpr1/datafile/undotbs3.281.706289789';
                    SET NEWNAME FOR DATAFILE 6 to '+DG1/pdamlpr1/datafile/users.282.706289797';
                    SET NEWNAME FOR DATAFILE 7 to '+DG1/pdamlpr1/datafile/dts01.dbf';
                    SET NEWNAME FOR DATAFILE 8 to '+DG1/pdamlpr1/datafile/strmadmin_ts';
                    SET NEWNAME FOR DATAFILE 9 to '+DG1/pdamlpr1/datafile/monitor_ds';
                    SET NEWNAME FOR DATAFILE 10 to '+DG1/pdamlpr1/datafile/inform';
                    SET NEWNAME FOR DATAFILE 11 to '+DG1/pdamlpr1/datafile/merckapp.266.709552615';
                    SET NEWNAME FOR DATAFILE 12 to '+DG1/pdamlpr1/datafile/pmetstg_data01.309.718666269';
                    SET NEWNAME FOR DATAFILE 13 to '+DG1/pdamlpr1/datafile/pmetstg_index01.308.718666275';
                    SET NEWNAME FOR DATAFILE 14 to '+DG1/pdamlpr1/datafile/pmettgt_data01.307.718666281';

                    ... ...

                    ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
                      ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
                      DUPLICATE TARGET DATABASE for standby
                    nofilenamecheck
                    dorecover;
                    }


                    We still got the same error.  When I try to manually recover:


                     

                    SQL> set autorecovery on

                    SQL> recover standby database;

                    ORA-00283: recovery session canceled due to errors

                    ORA-01110: data file 1: '+DG1/pdamlpr1/datafile/system.276.706289719'

                    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file

                    ORA-01110: data file 1: '+DG1/pdamlpr1/datafile/system.276.706289719'

                     

                    I checked in the standby still have some db file miss place in name (not all of them, about 1/2).  We have total 159 db files.   For example, the system file in the standby is named as SYSTEM.406.848110067, while in the primary is SYSTEM.276.706289719. Although I used the setname in rman standby duplication as:
                     
                    SET NEWNAME FOR DATAFILE 1 to '+DG1/pdamlpr1/datafile/system.276.706289719'; 


                    Not sure why and how to fix it.   Thanks for help!

                    • 7. Re: Error during the RAC to RAC standby setup.
                      Hemant K Chitale

                      I would have used "Example 25-7 Using SET NEWNAME to Create Files in an ASM Disk Group"  and let Oracle determine the file names.

                       

                       

                      Hemant K Chitale


                      • 8. Re: Error during the RAC to RAC standby setup.
                        liaison1

                        still not understand why some files are not restored as the original name. Anything we can do to avoid it? 
                         
                        Now, I made the change in the parameter file of standby site:
                        DB_FILE_NAME_CONVERT='+DG1','+DG1'
                        LOG_FILE_NAME_CONVERT='+DG2','+DG2'
                         
                        Basically, we want to do the same layout structure for the standby from the primary.
                         
                        When I run the rman duplication for the standby restore, we have the following message shown: 
                         
                        sql statement: alter database mount standby database
                        WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
                         
                        contents of Memory Script:
                        {
                          set until scn 13195886183611;
                          set newname for tempfile 1 to 
                          "+dg1";
                          set newname for tempfile 2 to 
                          "+dg1";
                          switch clone tempfile all;
                          set newname for datafile 1 to 
                          "+dg1";
                          set newname for datafile 2 to 
                          "+dg1";
                          set newname for datafile 3 to 
                          "+dg1";
                          set newname for datafile 4 to 
                          "+dg1";
                          set newname for datafile 5 to 
                          "+dg1";
                          set newname for datafile 6 to 
                          "+dg1";
                          set newname for datafile 7 to 
                          "+DG1/pdamlpr1/datafile/dts01.dbf";
                          set newname for datafile 8 to 
                          "+DG1/pdamlpr1/datafile/strmadmin_ts";
                          set newname for datafile 9 to 
                          "+DG1/pdamlpr1/datafile/monitor_ds";
                          set newname for datafile 10 to 
                          "+DG1/pdamlpr1/datafile/inform";
                          set newname for datafile 11 to 
                          "+dg1";
                          set newname for datafile 12 to 
                          "+dg1";
                          set newname for datafile 13 to 
                          "+dg1";
                          set newname for datafile 14 to 
                          "+dg1";
                          set newname for datafile 15 to 
                          "+dg1";
                          set newname for datafile 16 to 
                          "+dg1";
                          set newname for datafile 17 to 
                          "+dg1";
                          set newname for datafile 18 to 
                          "+dg1";
                          set newname for datafile 19 to 
                          "+dg1";
                          set newname for datafile 20 to 
                          "+dg1";
                          set newname for datafile 21 to 
                          "+dg1";
                          set newname for datafile 22 to 
                          "+dg1";
                          set newname for datafile 23 to 
                          "+dg1";
                          set newname for datafile 24 to 
                          "+dg1";
                          set newname for datafile 25 to 
                          "+dg1";
                          set newname for datafile 26 to 
                          "+dg1";
                          set newname for datafile 27 to 
                          "+dg1";
                          set newname for datafile 28 to 
                          "+dg1";
                          set newname for datafile 29 to 
                          "+dg1";
                          set newname for datafile 30 to 
                          "+dg1";
                          set newname for datafile 31 to 
                          "+dg1";
                          set newname for datafile 32 to 
                          "+DG1/pdamlpr1/datafile/sysaux01";
                          set newname for datafile 33 to 
                          "+DG1/pdamlpr1/datafile/dashboard_data01";
                          set newname for datafile 34 to 
                          "+DG1/pdamlpr1/datafile/dashboard_index01";
                          set newname for datafile 35 to 
                          "+DG1/pdamlpr1/datafile/sysaux03";
                          set newname for datafile 36 to 
                          "+DG1/pdamlpr1/datafile/ddsmk082201801.dbf";
                          set newname for datafile 37 to 
                          "+dg1";
                          set newname for datafile 38 to 
                          "+dg1";
                          set newname for datafile 39 to 
                          "+dg1";
                          set newname for datafile 40 to 
                          "+dg1";
                          set newname for datafile 41 to 
                          "+DG1/pdamlpr1/datafile/ddsmk8342b057.dbf";
                          set newname for datafile 42 to 
                          "+DG1/pdamlpr1/datafile/ddsmk0431083.dbf";
                          set newname for datafile 43 to 
                          "+DG1/pdamlpr1/datafile/ddsmk0859022.dbf";
                        ... ...



                        • 9. Re: Error during the RAC to RAC standby setup.
                          liaison1

                          Here is the list of DB files in primary DB from ASMCMD.    For these files that have Sys=Y have the issue on restore different name matched. Let me know what to do on these file to correct it.


                          We have the restore name miss match issue on the files that have Sys = Y in column. 

                          Should we add alias name for them for do we missed something in the primary database?

                           

                           

                          ASMCMD> ls -l

                           

                          Type      Redund  Striped  Time             Sys  Name

                           

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    COMPASS_DATA01.300.722363497

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    COMPASS_INDEX01.298.722363505

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DASHBOARD_DATA01.261.801929039

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DASHBOARD_INDEX01.262.801929053

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSCHANGEREQUEST.340.826547861

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSIMPORT.320.824492609

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK0000218.348.827647843

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK0000267.356.829488779

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK0000298.334.826027245

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK0000303.290.824508077

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0000310.346.827495921

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK0000318.400.841880415

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0000321.378.833862155

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK0000322.355.829433391

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK0000331.389.837519235

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0431083.322.824128787

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0431260.292.824819533

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0431A170.393.838132821

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK0476513.374.832560943

                                                                      N    DDSMK0476513_01.DBF => +DG1/PDAMLPR1/DATAFILE/DDSMK0476513.374.832560943

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0476519.311.825440361

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0476520.319.824474079

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    DDSMK0517029.324.825677303

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    DDSMK0517031.370.831284661

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0518292.418.847069235

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0518295.336.826290395

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK0653C436.391.837915469

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK0663B164.349.827668469

                          DATAFILE  UNPROT  COARSE   MAY 22 10:00:00  Y    DDSMK0822018.258.820672953

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0822066.354.828991209

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    DDSMK0859019.369.830696789

                          DATAFILE  UNPROT  COARSE   MAY 22 05:00:00  Y    DDSMK0859022.321.824134869

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0859040.410.843737057

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0859042.350.827810385

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK0859050.335.826040345

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    DDSMK0859051.343.827027229

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0859057.359.830043021

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK0859058.375.832635967

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK0869219.342.826961921

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    DDSMK0887086.383.836085663

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK0991064.357.829697779

                          DATAFILE  UNPROT  COARSE   MAY 22 05:00:00  Y    DDSMK1029011.394.838170271

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK1029012.392.838091351

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK1293002.286.825149481

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK1293005.316.825291431

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    DDSMK1775001.326.825858663

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK1775004.407.843087427

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK2155195.367.830276381

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK2248001.408.843174767

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK3415A001.387.837314511

                          DATAFILE  UNPROT  COARSE   MAY 22 08:00:00  Y    DDSMK3415A002.360.830062099

                          DATAFILE  UNPROT  COARSE   MAY 22 08:00:00  Y    DDSMK3475002.272.823895415

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    DDSMK3475006.318.824147097

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK3475010.341.826854309

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK3475011.396.838911061

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK3475012.339.826541323

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK3475013.345.827450901

                          DATAFILE  UNPROT  COARSE   MAY 22 10:00:00  Y    DDSMK3475021.398.839293333

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK3475022.413.844893813

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK3475023.380.834957433

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK3475025.377.833725681

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK3475028.399.839975947

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK3475029.402.842123399

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK4305052.314.825399153

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK5172010.323.825656355

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    DDSMK5172035.293.824655009

                                                                      N    DDSMK5172035.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK5172035.293.824655009

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK5172047.347.827636999

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK5172048.417.847065359

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK5172052.404.842432021

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK5172059.414.846201525

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK5172061.420.848033861

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK5348045.419.847524123

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK5592069.352.828325347

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK7009048.385.836904939

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK7145011.415.846202117

                          DATAFILE  UNPROT  COARSE   MAY 22 05:00:00  Y    DDSMK7965012.372.832368719

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK8109001.344.827029931

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8109004.397.839282637

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK8109011.388.837393983

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    DDSMK8175A022.260.822588357

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK8189002.288.824506993

                                                                      N    DDSMK8189002.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8189002.288.824506993

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK8226003.325.825767745

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK8228027.384.836369947

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8237003.259.824216043

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8237009.327.825909031

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8242005.294.824642837

                                                                      N    DDSMK8242005.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8242005.294.824642837

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8242006.295.824566015

                                                                      N    DDSMK8242006.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8242006.295.824566015

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8259006.381.835026615

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8262001.328.825951335

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    DDSMK8342B057.267.824121985

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK8351002.331.825991171

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK8351003.268.823967465

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8408001.330.825987089

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK8408002.379.834358385

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK8408003.406.843006361

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8521002.310.825640237

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSMK8521003.364.830248365

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8591001.390.837639051

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK8591002.416.846858999

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8616076.366.830270821

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8616101.382.835226253

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8666002.337.826429733

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8666003.351.827893651

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK8669049.365.830254295

                          DATAFILE  UNPROT  COARSE   MAY 22 05:00:00  Y    DDSMK8669064.338.826514111

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8723001.363.830217637

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8831001.299.824513195

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8831002.368.830570527

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK8876003.287.824836817

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK8892002.271.823966785

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK8892003.332.826004489

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8892007.411.843774069

                          DATAFILE  UNPROT  COARSE   MAR 17 12:00:00  Y    DDSMK8892007UAT.403.842409901

                          DATAFILE  UNPROT  COARSE   MAY 22 10:00:00  Y    DDSMK8931017.317.825173463

                                                                      N    DDSMK8931017.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8931017.317.825173463

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSMK8931019.358.829989783

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSMK8931025.315.825301565

                          DATAFILE  UNPROT  COARSE   SEP 04     2013  Y    DDSTEST.312.825286493

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSV114004.386.837037885

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSV160001.371.831942209

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSV180001.329.825977931

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    DDSV211029.412.844260441

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSV212001.409.843663197

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    DDSV212011.313.825451221

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSV260024.405.842485775

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSV260035.376.833334503

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSV260060.333.826022579

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSV501110.362.830169021

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSV501122.353.828394259

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSV503002.361.830073925

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSV503006.401.841934039

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DDSV503010.373.832543691

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    DTS.269.708713647

                          DATAFILE  UNPROT  COARSE   MAY 22 07:00:00  Y    INFORM.265.709225913

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    IVRSREP_DATA.289.752767769

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    IVRSREP_INDEX.285.752767795

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    MERCKAPP.266.709552615

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    MERCKCONTIVOPILOT_DS.301.721341409

                          DATAFILE  UNPROT  COARSE   MAY 22 08:00:00  Y    MONITOR_DS.273.709225729

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    PMETSTG_DATA01.309.718666269

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    PMETSTG_INDEX01.308.718666275

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    PMETTGT_DATA01.307.718666281

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    PMETTGT_INDEX01.306.718666283

                          DATAFILE  UNPROT  COARSE   APR 25 17:00:00  Y    RAMICK.395.838307057

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    RPTIMPORT.297.727654907

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    STRMADMIN_TS.274.708779203

                          DATAFILE  UNPROT  COARSE   MAY 22 08:00:00  Y    SYSAUX.256.799608995

                          DATAFILE  UNPROT  COARSE   MAY 22 03:00:00  Y    SYSAUX.263.814267995

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    SYSAUX.278.706289757

                          DATAFILE  UNPROT  COARSE   MAY 22 08:00:00  Y    SYSTEM.276.706289719

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    TS_AECARES_DATA.257.756826279

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    TS_AECARES_INDEX.264.756826307

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    TS_AERECON_DATA.305.718668215

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    TS_AERECON_INDEX.304.718668263

                          DATAFILE  UNPROT  COARSE   MAY 22 10:00:00  Y    TS_CONSOLIDATED_DATA.303.718669789

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    TS_CONSOLIDATED_INDEX.302.718670247

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    TS_IAR_DATA.284.755026761

                          DATAFILE  UNPROT  COARSE   MAY 22 09:00:00  Y    TS_IAR_INDEX.283.755026763

                          DATAFILE  UNPROT  COARSE   MAY 22 04:00:00  Y    TS_INFORM2CTMS_DATA.296.732120283

                          DATAFILE  UNPROT  COARSE   MAY 22 06:00:00  Y    TS_INFORM2CTMS_INDEX.291.732120315

                          DATAFILE  UNPROT  COARSE   MAY 22 08:00:00  Y    UNDOTBS1.277.706289747

                          DATAFILE  UNPROT  COARSE   MAY 22 08:00:00  Y    UNDOTBS2.280.706289779

                          DATAFILE  UNPROT  COARSE   MAY 22 08:00:00  Y    UNDOTBS3.281.706289789

                          DATAFILE  UNPROT  COARSE   MAY 22 08:00:00  Y    USERS.282.706289797

                                                                      N    dashboard_data01 => +DG1/PDAMLPR1/DATAFILE/DASHBOARD_DATA01.261.801929039

                                                                      N    dashboard_index01 => +DG1/PDAMLPR1/DATAFILE/DASHBOARD_INDEX01.262.801929053

                                                                      N    ddsMK0000303.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0000303.290.824508077

                                                                      N    ddsMK8831001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8831001.299.824513195

                                                                      N    ddschangerequest.dbf => +DG1/PDAMLPR1/DATAFILE/DDSCHANGEREQUEST.340.826547861

                                                                      N    ddsimport.dbf => +DG1/PDAMLPR1/DATAFILE/DDSIMPORT.320.824492609

                                                                      N    ddsmk0000218.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0000218.348.827647843

                                                                      N    ddsmk0000267.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0000267.356.829488779

                                                                      N    ddsmk0000298.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0000298.334.826027245

                                                                      N    ddsmk0000310.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0000310.346.827495921

                                                                      N    ddsmk0000318.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0000318.400.841880415

                                                                      N    ddsmk0000321.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0000321.378.833862155

                                                                      N    ddsmk0000322.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0000322.355.829433391

                                                                      N    ddsmk0000331.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0000331.389.837519235

                                                                      N    ddsmk0431083.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0431083.322.824128787

                                                                      N    ddsmk0431260.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0431260.292.824819533

                                                                      N    ddsmk0431a170.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0431A170.393.838132821

                                                                      N    ddsmk0476519.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0476519.311.825440361

                                                                      N    ddsmk0476520.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0476520.319.824474079

                                                                      N    ddsmk0517029.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0517029.324.825677303

                                                                      N    ddsmk0517031.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0517031.370.831284661

                                                                      N    ddsmk0518292.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0518292.418.847069235

                                                                      N    ddsmk0518295.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0518295.336.826290395

                                                                      N    ddsmk0653c436.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0653C436.391.837915469

                                                                      N    ddsmk0663b164.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0663B164.349.827668469

                                                                      N    ddsmk082201801.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0822018.258.820672953

                                                                      N    ddsmk0822066.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0822066.354.828991209

                                                                      N    ddsmk0859019.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0859019.369.830696789

                                                                      N    ddsmk0859022.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0859022.321.824134869

                                                                      N    ddsmk0859040.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0859040.410.843737057

                                                                      N    ddsmk0859042.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0859042.350.827810385

                                                                      N    ddsmk0859050.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0859050.335.826040345

                                                                      N    ddsmk0859051.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0859051.343.827027229

                                                                      N    ddsmk0859057.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0859057.359.830043021

                                                                      N    ddsmk0859058.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0859058.375.832635967

                                                                      N    ddsmk0869219.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0869219.342.826961921

                                                                      N    ddsmk0887086.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0887086.383.836085663

                                                                      N    ddsmk0991064.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK0991064.357.829697779

                                                                      N    ddsmk1029011.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK1029011.394.838170271

                                                                      N    ddsmk1029012.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK1029012.392.838091351

                                                                      N    ddsmk1293002.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK1293002.286.825149481

                                                                      N    ddsmk1293005.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK1293005.316.825291431

                                                                      N    ddsmk1775001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK1775001.326.825858663

                                                                      N    ddsmk1775004.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK1775004.407.843087427

                                                                      N    ddsmk2155195.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK2155195.367.830276381

                                                                      N    ddsmk2248001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK2248001.408.843174767

                                                                      N    ddsmk3415a001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3415A001.387.837314511

                                                                      N    ddsmk3415a002.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3415A002.360.830062099

                                                                      N    ddsmk3475006.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3475006.318.824147097

                                                                      N    ddsmk3475010.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3475010.341.826854309

                                                                      N    ddsmk3475011.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3475011.396.838911061

                                                                      N    ddsmk3475012.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3475012.339.826541323

                                                                      N    ddsmk3475013.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3475013.345.827450901

                                                                      N    ddsmk3475021.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3475021.398.839293333

                                                                      N    ddsmk3475022.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3475022.413.844893813

                                                                      N    ddsmk3475023.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3475023.380.834957433

                                                                      N    ddsmk3475025.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3475025.377.833725681

                                                                      N    ddsmk3475028.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3475028.399.839975947

                                                                      N    ddsmk3475029.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK3475029.402.842123399

                                                                      N    ddsmk4305052.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK4305052.314.825399153

                                                                      N    ddsmk5172010.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK5172010.323.825656355

                                                                      N    ddsmk5172047.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK5172047.347.827636999

                                                                      N    ddsmk5172048.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK5172048.417.847065359

                                                                      N    ddsmk5172052.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK5172052.404.842432021

                                                                      N    ddsmk5172059.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK5172059.414.846201525

                                                                      N    ddsmk5172061.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK5172061.420.848033861

                                                                      N    ddsmk5348045.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK5348045.419.847524123

                                                                      N    ddsmk5592069.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK5592069.352.828325347

                                                                      N    ddsmk7009048.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK7009048.385.836904939

                                                                      N    ddsmk7145011.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK7145011.415.846202117

                                                                      N    ddsmk7965012.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK7965012.372.832368719

                                                                      N    ddsmk8109001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8109001.344.827029931

                                                                      N    ddsmk8109004.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8109004.397.839282637

                                                                      N    ddsmk8109011.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8109011.388.837393983

                                                                      N    ddsmk8226003.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8226003.325.825767745

                                                                      N    ddsmk8228027.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8228027.384.836369947

                                                                      N    ddsmk8237003.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8237003.259.824216043

                                                                      N    ddsmk8237009.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8237009.327.825909031

                                                                      N    ddsmk8259006.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8259006.381.835026615

                                                                      N    ddsmk8262001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8262001.328.825951335

                                                                      N    ddsmk8342b057.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8342B057.267.824121985

                                                                      N    ddsmk8351002.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8351002.331.825991171

                                                                      N    ddsmk8408001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8408001.330.825987089

                                                                      N    ddsmk8408002.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8408002.379.834358385

                                                                      N    ddsmk8408003.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8408003.406.843006361

                                                                      N    ddsmk8521002.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8521002.310.825640237

                                                                      N    ddsmk8521003.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8521003.364.830248365

                                                                      N    ddsmk8591001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8591001.390.837639051

                                                                      N    ddsmk8591002.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8591002.416.846858999

                                                                      N    ddsmk8616076.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8616076.366.830270821

                                                                      N    ddsmk8616101.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8616101.382.835226253

                                                                      N    ddsmk8666002.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8666002.337.826429733

                                                                      N    ddsmk8666003.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8666003.351.827893651

                                                                      N    ddsmk8669049.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8669049.365.830254295

                                                                      N    ddsmk8669064.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8669064.338.826514111

                                                                      N    ddsmk8723001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8723001.363.830217637

                                                                      N    ddsmk8831002.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8831002.368.830570527

                                                                      N    ddsmk8876003.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8876003.287.824836817

                                                                      N    ddsmk8892003.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8892003.332.826004489

                                                                      N    ddsmk8892007.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8892007.411.843774069

                                                                      N    ddsmk8892007uat.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8892007UAT.403.842409901

                                                                      N    ddsmk8931019.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8931019.358.829989783

                                                                      N    ddsmk8931025.dbf => +DG1/PDAMLPR1/DATAFILE/DDSMK8931025.315.825301565

                                                                      N    ddstest.dbf => +DG1/PDAMLPR1/DATAFILE/DDSTEST.312.825286493

                                                                      N    ddsv114004.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV114004.386.837037885

                                                                      N    ddsv160001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV160001.371.831942209

                                                                      N    ddsv180001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV180001.329.825977931

                                                                      N    ddsv211029.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV211029.412.844260441

                                                                      N    ddsv212001.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV212001.409.843663197

                                                                      N    ddsv212011.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV212011.313.825451221

                                                                      N    ddsv260024.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV260024.405.842485775

                                                                      N    ddsv260035.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV260035.376.833334503

                                                                      N    ddsv260060.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV260060.333.826022579

                                                                      N    ddsv501110.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV501110.362.830169021

                                                                      N    ddsv501122.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV501122.353.828394259

                                                                      N    ddsv503002.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV503002.361.830073925

                                                                      N    ddsv503006.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV503006.401.841934039

                                                                      N    ddsv503010.dbf => +DG1/PDAMLPR1/DATAFILE/DDSV503010.373.832543691

                                                                      N    dts01.dbf => +DG1/PDAMLPR1/DATAFILE/DTS.269.708713647

                                                                      N    inform => +DG1/PDAMLPR1/DATAFILE/INFORM.265.709225913

                                                                      N    monitor_ds => +DG1/PDAMLPR1/DATAFILE/MONITOR_DS.273.709225729

                                                                      N    ramick1.dbf => +DG1/PDAMLPR1/DATAFILE/RAMICK.395.838307057

                                                                      N    strmadmin_ts => +DG1/PDAMLPR1/DATAFILE/STRMADMIN_TS.274.708779203

                                                                      N    sysaux01 => +DG1/PDAMLPR1/DATAFILE/SYSAUX.256.799608995

                                                                      N    sysaux03 => +DG1/PDAMLPR1/DATAFILE/SYSAUX.263.814267995

                          • 10. Re: Error during the RAC to RAC standby setup.
                            liaison1

                            Tried to use SETNAME or DB_FILE_NAME_CONVERT='+DG1','+DG1' .   Still the same error.   Not work.  The same question, why oracle restore with different name.


                            For example, try to recover it looks for the file: system.276.706289719:


                            ORA-00283: recovery session canceled due to errors

                            ORA-01110: data file 1: '+DG1/pdamlpr1/datafile/system.276.706289719'

                            ORA-01157: cannot identify/lock data file 1 - see DBWR trace file

                            ORA-01110: data file 1: '+DG1/pdamlpr1/datafile/system.276.706289719'

                             

                            Buy we have the file in the different name in the standby ASM:   SYSTEM.346.848240565

                            • 11. Re: Error during the RAC to RAC standby setup.
                              liaison1

                              I checked in the v$datafile from the standby, the system datafile is +DG1/pdamlpr1/datafile/system.276.706289719.   However, we have different name in the ASM:  SYSTEM.346.848240565.

                               

                              Why??

                              • 12. Re: Error during the RAC to RAC standby setup.
                                liaison1

                                I have made 2 tries
                                 
                                1. to use DB_FILE_NAME_CONVERT='+DG1','+DG1' in the parameter file of standby database. Still the same error. Not work. 
                                 
                                2. to make the rman duplication script looks like this:
                                 
                                RUN
                                {
                                 
                                SET NEWNAME FOR DATAFILE 1 to '+DG1/pdamlpr1/datafile/system.dbf';
                                SET NEWNAME FOR DATAFILE 2 to '+DG1/pdamlpr1/datafile/undotbs1.dbf';
                                SET NEWNAME FOR DATAFILE 3 to '+DG1/pdamlpr1/datafile/sysaux.dbf';
                                SET NEWNAME FOR DATAFILE 4 to '+DG1/pdamlpr1/datafile/undotbs2.dbf';
                                SET NEWNAME FOR DATAFILE 5 to '+DG1/pdamlpr1/datafile/undotbs3.dbf';
                                SET NEWNAME FOR DATAFILE 6 to '+DG1/pdamlpr1/datafile/users.dbf';
                                SET NEWNAME FOR DATAFILE 7 to '+DG1/pdamlpr1/datafile/dts01.dbf';
                                SET NEWNAME FOR DATAFILE 8 to '+DG1/pdamlpr1/datafile/strmadmin_ts.dbf';
                                SET NEWNAME FOR DATAFILE 9 to '+DG1/pdamlpr1/datafile/monitor_ds.dbf';
                                SET NEWNAME FOR DATAFILE 10 to '+DG1/pdamlpr1/datafile/inform.dbf';
                                SET NEWNAME FOR DATAFILE 11 to '+DG1/pdamlpr1/datafile/merckapp.dbf';
                                SET NEWNAME FOR DATAFILE 12 to '+DG1/pdamlpr1/datafile/pmetstg_data01.dbf';
                                SET NEWNAME FOR DATAFILE 13 to '+DG1/pdamlpr1/datafile/pmetstg_index01.dbf';
                                SET NEWNAME FOR DATAFILE 14 to '+DG1/pdamlpr1/datafile/pmettgt_data01.dbf';
                                SET NEWNAME FOR DATAFILE 15 to '+DG1/pdamlpr1/datafile/pmettgt_index01.dbf';
                                SET NEWNAME FOR DATAFILE 16 to '+DG1/pdamlpr1/datafile/ts_aerecon_data.dbf';
                                SET NEWNAME FOR DATAFILE 17 to '+DG1/pdamlpr1/datafile/ts_aerecon_index.dbf';
                                SET NEWNAME FOR DATAFILE 18 to '+DG1/pdamlpr1/datafile/ts_consolidated_data.dbf';
                                SET NEWNAME FOR DATAFILE 19 to '+DG1/pdamlpr1/datafile/ts_consolidated_index.dbf';
                                SET NEWNAME FOR DATAFILE 20 to '+DG1/pdamlpr1/datafile/merckcontivopilot_ds.dbf';
                                SET NEWNAME FOR DATAFILE 21 to '+DG1/pdamlpr1/datafile/compass_data01.dbf';
                                SET NEWNAME FOR DATAFILE 22 to '+DG1/pdamlpr1/datafile/compass_index01.dbf';
                                SET NEWNAME FOR DATAFILE 23 to '+DG1/pdamlpr1/datafile/rptimport.dbf';
                                SET NEWNAME FOR DATAFILE 24 to '+DG1/pdamlpr1/datafile/ts_inform2ctms_data.dbf';
                                SET NEWNAME FOR DATAFILE 25 to '+DG1/pdamlpr1/datafile/ts_inform2ctms_index.dbf';
                                SET NEWNAME FOR DATAFILE 26 to '+DG1/pdamlpr1/datafile/ivrsrep_data.dbf';
                                SET NEWNAME FOR DATAFILE 27 to '+DG1/pdamlpr1/datafile/ivrsrep_index.dbf';
                                SET NEWNAME FOR DATAFILE 28 to '+DG1/pdamlpr1/datafile/ts_iar_data.dbf';
                                SET NEWNAME FOR DATAFILE 29 to '+DG1/pdamlpr1/datafile/ts_iar_index.dbf';
                                SET NEWNAME FOR DATAFILE 30 to '+DG1/pdamlpr1/datafile/ts_aecares_data.dbf';
                                SET NEWNAME FOR DATAFILE 31 to '+DG1/pdamlpr1/datafile/ts_aecares_index.dbf';
                                SET NEWNAME FOR DATAFILE 32 to '+DG1/pdamlpr1/datafile/sysaux01.dbf';
                                SET NEWNAME FOR DATAFILE 33 to '+DG1/pdamlpr1/datafile/dashboard_data01.dbf';
                                SET NEWNAME FOR DATAFILE 34 to '+DG1/pdamlpr1/datafile/dashboard_index01.dbf';
                                SET NEWNAME FOR DATAFILE 35 to '+DG1/pdamlpr1/datafile/sysaux03.dbf';
                                SET NEWNAME FOR DATAFILE 36 to '+DG1/pdamlpr1/datafile/ddsmk082201801.dbf';
                                SET NEWNAME FOR DATAFILE 37 to '+DG1/pdamlpr1/datafile/ddsmk8175a022.dbf';
                                SET NEWNAME FOR DATAFILE 38 to '+DG1/pdamlpr1/datafile/ddsmk3475002.dbf';
                                SET NEWNAME FOR DATAFILE 39 to '+DG1/pdamlpr1/datafile/ddsmk8892002.dbf';
                                SET NEWNAME FOR DATAFILE 40 to '+DG1/pdamlpr1/datafile/ddsmk8351003.dbf';
                                SET NEWNAME FOR DATAFILE 41 to '+DG1/pdamlpr1/datafile/ddsmk8342b057.dbf';
                                SET NEWNAME FOR DATAFILE 42 to '+DG1/pdamlpr1/datafile/ddsmk0431083.dbf';
                                SET NEWNAME FOR DATAFILE 43 to '+DG1/pdamlpr1/datafile/ddsmk0859022.dbf';
                                SET NEWNAME FOR DATAFILE 44 to '+DG1/pdamlpr1/datafile/ddsmk3475006.dbf';
                                .... ....
                                 
                                SET NEWNAME FOR DATAFILE 158 to '+DG1/pdamlpr1/datafile/ddsmk5348045.dbf';
                                SET NEWNAME FOR DATAFILE 159 to '+DG1/pdamlpr1/datafile/ddsmk5172061.dbf';
                                 
                                  ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
                                  ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
                                  DUPLICATE TARGET DATABASE for standby
                                nofilenamecheck
                                dorecover;
                                }
                                 
                                exit
                                 
                                Same error again. Not work either. 


                                • 13. Re: Error during the RAC to RAC standby setup.
                                  liaison1

                                  I have also tried to use standby file management = MANUAL with db file name convert.   Still not work.

                                  • 14. Re: Error during the RAC to RAC standby setup.
                                    Hemant K Chitale

                                    With the SET NEWNAME commands .... are ALL of the SET NEWNAMEs ignored ?  What if you set NEWNAME to completely different values, not being file names present at the source ?

                                     

                                     

                                    Hemant K Chitale


                                    1 2 Previous Next