1 2 3 Previous Next 41 Replies Latest reply: May 15, 2013 3:33 AM by okKarol Go to original post RSS
      • 30. Re: RMAN-05501: aborting duplication of target database
        okKarol
        ################################################################

        ###### SQL> alter database recover managed standby database cancel;

        *
        ERROR at line 1:
        ORA-16136: Managed Standby Recovery not active
        SQL> alter database recover managed standby database using current logfile
        2 disconnect;
        alter database recover managed standby database using current logfile
        *
        ERROR at line 1:
        ORA-01153: an incompatible media recovery is active
        ###### SQL> select type, name from v$logfile;

        SQL> select type,substr(member,1,45) from v$logfile;

        TYPE SUBSTR(MEMBER,1,45)
        ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
        ONLINE /mcelnetapp/data1/oracle/CMOVP/redo01g3.rdo
        ONLINE /mcelnetapp/data2/oracle/CMOVP/redo02g3.rdo
        ONLINE /mcelnetapp/data2/oracle/CMOVP/redo02g2.rdo
        ONLINE /mcelnetapp/data1/oracle/CMOVP/redo01g2.rdo
        ONLINE /mcelnetapp/data1/oracle/CMOVP/redo01g1.rdo
        ONLINE /mcelnetapp/data2/oracle/CMOVP/redo02g1.rdo
        STANDBY /data1/oracle/CMOVP/Stbyredo01g4.rdo
        STANDBY /data2/oracle/CMOVP/Stbyredo01g5.rdo
        STANDBY /data1/oracle/CMOVP/Stbyredo01g6.rdo
        STANDBY /data2/oracle/CMOVP/Stbyredo01g7.rdo

        10 rows selected.
        ###### oracle@cmovel-db01:~$ cd /mcelnetapp/data2/oracle/CMOVP/
        ###### oracle@cmovel-db01:/mcelnetapp/data2/oracle/CMOVP$ ls -lrt

        oracle@cmovel-db01:/mcelnetapp/data2/oracle/CMOVP$ ls -lrt
        total 92885547
        -rw-r----- 1 oracle oinstall 52429312 2013-05-05 16:28 redo02g1.rdo
        -rw-r----- 1 oracle oinstall 52429312 2013-05-05 16:30 redo02g3.rdo
        -rw-r----- 1 oracle oinstall 52429312 2013-05-06 10:58 redo02g2.rdo >>>>> G2
        -rw-r----- 1 oracle oinstall 1073750016 2013-05-06 11:34 WEB01.dbf
        -rw-r----- 1 oracle oinstall 22423805952 2013-05-06 11:34 undotbs01.dbf
        -rw-r----- 1 oracle oinstall 3221233664 2013-05-06 11:34 TUM01.dbf
        -rw-r----- 1 oracle oinstall 1226842112 2013-05-06 11:34 system01.dbf
        -rw-r----- 1 oracle oinstall 1321213952 2013-05-06 11:34 sysaux01.dbf
        -rw-r----- 1 oracle oinstall 104865792 2013-05-06 11:34 datamart.dbf
        -rw-r----- 1 oracle oinstall 4294975488 2013-05-06 11:34 DATAMART04.dbf
        -rw-r----- 1 oracle oinstall 4294975488 2013-05-06 11:34 DATAMART02.dbf
        -rw-r----- 1 oracle oinstall 1073750016 2013-05-06 11:34 BULKPAYMENT01.dbf
        -rw-r----- 1 oracle oinstall 4294975488 2013-05-06 11:34 ASCAS01.dbf
        -rw-r----- 1 oracle oinstall 21348352 2013-05-06 11:48 control02CMOVPdg.ctl

        ######## SQL> select open_mode from v$database; --- if mount

        SQL> select open_mode from v$database;

        OPEN_MODE
        MOUNTED

        SQL>
        ######## SQL> alter database open;

        SQL> alter database open;
        alter database open
        *
        ERROR at line 1:
        ORA-10458: standby database requires recovery
        ORA-01152: file 1 was not restored from a sufficiently old backup
        ORA-01110: data file 1: '/mcelnetapp/data2/oracle/CMOVP/system01.dbf'
        ######## oracle@cmovel-db01:~$ cd /mcelnetapp/data2/oracle/CMOVP/
        ######## oracle@cmovel-db01:/mcelnetapp/data2/oracle/CMOVP$ ls -lrt
        SQL> !
        oracle@cmovel-db01:/mcelnetapp/data2/oracle/CMOVP$
        oracle@cmovel-db01:/mcelnetapp/data2/oracle/CMOVP$
        oracle@cmovel-db01:/mcelnetapp/data2/oracle/CMOVP$ ls -lrt
        total 92885547
        -rw-r----- 1 oracle oinstall 52429312 2013-05-05 16:28 redo02g1.rdo
        -rw-r----- 1 oracle oinstall 52429312 2013-05-05 16:30 redo02g3.rdo
        -rw-r----- 1 oracle oinstall 52429312 2013-05-06 10:58 redo02g2.rdo

        ######## SQL> alter database recover managed standby database using current logfile disconnect from session;

        SQL> alter database recover managed standby database using current logfile disconnect from session;
        alter database recover managed standby database using current logfile disconnect from session
        *
        ERROR at line 1:
        ORA-01153: an incompatible media recovery is active
        • 31. Re: RMAN-05501: aborting duplication of target database
          okKarol
          select * from v$archive_gap; -- standby

          SQL> select * from v$archive_gap;

          no rows selected >>>>>>>>>>>> !!!!

          SQL> select process,status from v$managed_standby;

          PROCESS STATUS
          --------- ------------
          ARCH CONNECTED
          ARCH CONNECTED
          ARCH CONNECTED
          ARCH CONNECTED
          MRP0 WAIT_FOR_GAP >>>> !!!!


          select * from v$managed_standby -- both side

          PRIMARY SITE

          PROCESS PID STATUS CLIENT_P CLIENT_PID CLIENT_DBID GROUP# RESETLOG_ID THREAD# SEQUENCE# BLOCK# BLOCKS DELAY_MINS KNOWN_AGENTS ACTIVE_AGENTS
          --------- ---------- ------------ -------- ---------------------------------------- ---------------------------------------- ---------------------------------------- ----------- ---------- ---------- ---------- ---------- ---------- ------------ -------------
          ARCH 4235 CLOSING ARCH 4235 987374273 3 810397891 1 16711 32768 1967 0 0 0
          ARCH 4237 CLOSING ARCH 4237 987374273 2 810397891 1 16712 30720 1165 0 0 0
          ARCH 4239 CLOSING ARCH 4239 987374273 N/A 810397891 1 12669 118785 4053 0 0 0
          ARCH 4241 CLOSING ARCH 4241 987374273 1 810397891 1 16713 30720 1071 0 0 0
          ARCH 18951 CLOSING ARCH 18951 987374273 3 810397891 1 16714 30720 1044 0 0 0


          SECONDARY SITE


          SQL> select * from v$managed_standby ;

          PROCESS PID STATUS CLIENT_P CLIENT_PID CLIENT_DBID GROUP# RESETLOG_ID THREAD# SEQUENCE# BLOCK# BLOCKS DELAY_MINS KNOWN_AGENTS ACTIVE_AGENTS
          --------- ---------- ------------ -------- ---------------------------------------- ---------------------------------------- ---------------------------------------- ----------- ---------- ---------- ---------- ---------- ---------- ------------ -------------
          ARCH 21487 CONNECTED ARCH 21487 987374273 N/A 0 0 0 0 0 0 0 0
          ARCH 21489 CONNECTED ARCH 21489 987374273 N/A 0 0 0 0 0 0 0 0
          ARCH 21491 CONNECTED ARCH 21491 987374273 N/A 0 0 0 0 0 0 0 0
          ARCH 21493 CONNECTED ARCH 21493 987374273 N/A 0 0 0 0 0 0 0 0
          MRP0 21507 WAIT_FOR_GAP N/A N/A N/A N/A 810397891 1 16064 0 0 0 9 9



          alter system switch logfile;

          select max(sequence#) from v$archived_log; -- primary
          select max(sequence#) from v$archived_log; -- standby
          select max(sequence#) from v$archived_log where applied='YES'; -- standby

          SQL> select max(sequence#) from v$archived_log where applied='YES';

          MAX(SEQUENCE#)
          --------------




          select current_scn from v$database; --- both side
          • 32. Re: RMAN-05501: aborting duplication of target database
            Mahir M. Quluzade
            You have gap on sequence# : 16064 archived redo log.
            Do you have backup of 16064 sequence# archived log?
            • 33. Re: RMAN-05501: aborting duplication of target database
              Mahir M. Quluzade
              What is result ?
              select max(sequence#) from v$archived_log; -- primary
              select max(sequence#) from v$archived_log; -- standby
              select max(sequence#) from v$archived_log where applied='YES'; -- standby
              
              
              show parameter log_archive_dest_state_2 -- primary
              • 34. Re: RMAN-05501: aborting duplication of target database
                okKarol
                STBY
                SQL> select max(sequence#) from v$archived_log;

                MAX(SEQUENCE#)
                --------------
                16124

                PRIMARY

                SQL> select max(sequence#) from v$archived_log;

                MAX(SEQUENCE#)
                --------------
                16819


                SQL> select max(sequence#) from v$archived_log where applied='YES';

                MAX(SEQUENCE#)
                --------------


                SQL> show parameter log_archive_dest_state_2 -- primary

                NAME TYPE VALUE
                ------------------------------------ ----------- ------------------------------
                log_archive_dest_state_2 string ENABLE
                log_archive_dest_state_20 string enable
                log_archive_dest_state_21 string enable
                log_archive_dest_state_22 string enable
                log_archive_dest_state_23 string enable
                log_archive_dest_state_24 string enable
                log_archive_dest_state_25 string enable
                log_archive_dest_state_26 string enable
                log_archive_dest_state_27 string enable
                log_archive_dest_state_28 string enable
                log_archive_dest_state_29 string enable
                SQL> show parameter loag_arch_dest_2


                FYI

                Lets Recap :
                This issue cames after the Active Standby duplication with RMAN ... RMAN does not recreate the redo logs and that's why we can't recover the DB.
                After Recraete Manually with your script the missing redo log group was created but the DB still not applying the Logs.

                Anyway there's a huge problem with this

                The Instance status is showing as Primary Isnatnce!!!!
                SQL> select * from v$instance;

                INSTANCE_NUMBER INSTANCE_NAME HOST_NAME VERSION STARTUP_T STATUS PAR THREAD# ARCHIVE LOG_SWITCH_WAIT LOGINS SHU DATABASE_STATUS INSTANCE_ROLE ACTIVE_ST BLO
                --------------- ---------------- ---------------------------------------------------------------- ----------------- --------- ------------ --- ---------- ------- --------------- ---------- --- ----------------- ------------------ --------- ---
                1 CMOVP cmovel-db01 11.2.0.3.0 06-MAY-13 MOUNTED NO 1 STARTED ALLOWED NO ACTIVE PRIMARY_INSTANCE <<<< NORMAL NO
                • 35. Re: RMAN-05501: aborting duplication of target database
                  okKarol
                  Checking on the wrong view

                  SQL> select STANDBY_BECAME_PRIMARY_SCN,DATABASE_ROLE from v$database;

                  STANDBY_BECAME_PRIMARY_SCN DATABASE_ROLE
                  -------------------------- ----------------
                  0 PHYSICAL STANDBY
                  • 36. Re: RMAN-05501: aborting duplication of target database
                    Mahir M. Quluzade
                    okKarol wrote:
                    Checking on the wrong view

                    SQL> select STANDBY_BECAME_PRIMARY_SCN,DATABASE_ROLE from v$database;

                    STANDBY_BECAME_PRIMARY_SCN DATABASE_ROLE
                    -------------------------- ----------------
                    0 PHYSICAL STANDBY
                    You archived redo logs is not shipped.

                    On Primary
                     show parameter log_archive_dest_2
                     select process from v$managed_standby;
                    Mahir

                    p.s. Can you write to me from email?
                    • 37. Re: RMAN-05501: aborting duplication of target database
                      okKarol
                      No

                      I still didn't configure the Dataguard Process ... as teh logs are not applied,
                      But I've alredy done it and the logshipping works fine, the issue is with this bloody recover process that doesn't turns on ....
                      And I can recreate the standby again, but with this issue with the redologs that are not copied ... I don't have any clues ..
                      • 38. Re: RMAN-05501: aborting duplication of target database
                        okKarol
                        Absolutely,

                        Mail : carlos.carvlh@gmail.com

                        Cheers
                        Carlos
                        • 39. Re: RMAN-05501: aborting duplication of target database
                          Hemant K Chitale
                          but with this issue with the redologs that are not copied
                          A Standby database does not have Online Redo Logs. It has only Standby Redo Logs. The Online Redo Logs are initialized and created when you ACTIVATE and OPEN RESETLOGS the database.


                          Hemant K Chitale
                          • 40. Re: RMAN-05501: aborting duplication of target database
                            okKarol
                            Ok, But The Online Redologs should be duplicated too.
                            I've used another way. Instead of using "DORECOVER" i just did the active duplication and then I took care of shipping the logs and configure Dataguard.
                            This time the redologs and standby redologs where duplicated

                            DISK 1
                            oracle@cmovel-db01:/archives/CMOVP/stby$ ls -lrt /mcelnetapp/data1/oracle/CMOVP/
                            total 87320824
                            -rw-r----- 1 oracle oinstall 52429312 2013-05-10 12:19 redo01g1.rdo >>>>>
                            -rw-r----- 1 oracle oinstall 52429312 2013-05-10 12:19 redo01g2.rdo >>>>>
                            -rw-r----- 1 oracle oinstall 52429312 2013-05-10 12:19 redo01g3.rdo >>>>>>>>
                            -rw-r----- 1 oracle oinstall 104858112 2013-05-10 12:19 Stbyredo01g6.rdo >>>>>> stby redo
                            -rw-r----- 1 oracle oinstall 4294975488 2013-05-10 15:01 ZAP01.dbf
                            -rw-r----- 1 oracle oinstall 362422272 2013-05-10 15:01 example01.dbf
                            -rw-r----- 1 oracle oinstall 4294975488 2013-05-10 15:01 AGENTCOMM01.dbf

                            DISK 2
                            -rw-r----- 1 oracle oinstall 104858112 2013-05-10 15:17 Stbyredo01g4.oracle@cmovel-db01:/archives/CMOVP/stby$ ls -lrt /mcelnetapp/data2/oracle/CMOVP/
                            total 97087383
                            -rw-r----- 1 oracle oinstall 52429312 2013-05-10 12:19 redo02g1.rdo >>>> 3 Groups of online
                            -rw-r----- 1 oracle oinstall 52429312 2013-05-10 12:19 redo02g2.rdo
                            -rw-r----- 1 oracle oinstall 52429312 2013-05-10 12:19 redo02g3.rdo
                            -rw-r----- 1 oracle oinstall 104858112 2013-05-10 12:19 Stbyredo01g7.rdo >>>>> STBY >>>>> 3 + 1 for STBY
                            .
                            .
                            -rw-r----- 1 oracle oinstall 104858112 2013-05-10 15:19 Stbyredo01g5.rdo >>>> STBy
                            rdo >>>>> stby redo



                            Here are the Results :

                            The script:
                            run
                            {
                            allocate channel prm1 type disk;
                            allocate auxiliary channel stby1 type disk;
                            DUPLICATE TARGET DATABASE
                            FOR STANDBY
                            FROM ACTIVE DATABASE
                            NOFILENAMECHECK;
                            }

                            Result : I dont have the output anymore but it completed without errors but Without recover (Just the Clone )

                            Then I Copied the Miising archivelogs from Primary Site into Secondary Site - OK

                            Then I configured the Dataguard : OK

                            The Logs start being transfered : OK

                            Then I Start Recovery Managed standby Database using current logfile disconnect from session ;
                            Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE
                            Errors in file /app/oracle/diag/rdbms/cmovpdg/CMOVP/trace/CMOVP_pr00_9374.trc (incident=520375):
                            ORA-00353: log corruption near block 2048 change 1597005754 time 05/10/2013 10:34:10
                            ORA-00334: archived log: '/archives/CMOVP/archivelogs/1_24829_810397891.arc'
                            Incident details in: /app/oracle/diag/rdbms/cmovpdg/CMOVP/incident/incdir_520375/CMOVP_pr00_9374_i520375.trc
                            2013-05-10 15:01:09.108000 +02:00
                            MRP0: Background Media Recovery terminated with error 354
                            Errors in file /app/oracle/diag/rdbms/cmovpdg/CMOVP/trace/CMOVP_pr00_9374.trc:
                            ORA-00354: corrupt redo log block header
                            ORA-00353: log corruption near block 2048 change 1597005754 time 05/10/2013 10:34:10
                            ORA-00334: archived log: '/archives/CMOVP/archivelogs/1_24829_810397891.arc'
                            Managed Standby Recovery not using Real Time Apply
                            Sweep [inc2][520397]: completed
                            Recovery interrupted!
                            Recovered data files to a consistent state at change 1597005628
                            MRP0: Background Media Recovery process shutdown (CMOVP)
                            Sweep [inc][520375]: completed
                            Dumping diagnostic data in directory=[cdmp_20130510150109


                            DGMGRL> show database verbose 'CMOVPDG';

                            Database - CMOVPDG

                            Role: PHYSICAL STANDBY
                            Intended State: APPLY-ON
                            Transport Lag: 0 seconds
                            Apply Lag: 4 hours 42 minutes 17 seconds
                            Real Time Query: OFF
                            Instance(s):
                            CMOVP

                            Database Error(s):
                            ORA-16766: Redo Apply is stopped

                            Properties:
                            DGConnectIdentifier = 'CMOVPDG'
                            ObserverConnectIdentifier = ''
                            LogXptMode = 'ASYNC'
                            DelayMins = '0'
                            Binding = 'optional'
                            MaxFailure = '0'
                            MaxConnections = '1'
                            ReopenSecs = '300'
                            NetTimeout = '15'
                            RedoCompression = 'DISABLE'
                            LogShipping = 'ON'
                            PreferredApplyInstance = ''
                            ApplyInstanceTimeout = '0'
                            ApplyParallel = 'AUTO'
                            StandbyFileManagement = 'AUTO'
                            ArchiveLagTarget = '0'
                            LogArchiveMaxProcesses = '5'
                            LogArchiveMinSucceedDest = '1'
                            DbFileNameConvert = '/data1/oracle/CMOVP, /mcelnetapp/data1/oracle/CMOVP, /data2/oracle/CMOVP, /mcelnetapp/data2/oracle/CMOVP'
                            LogFileNameConvert = '/data1/oracle/CMOVP, /mcelnetapp/data1/oracle/CMOVP, /data2/oracle/CMOVP, /mcelnetapp/data2/oracle/CMOVP'
                            FastStartFailoverTarget = ''
                            InconsistentProperties = '(monitor)'
                            InconsistentLogXptProps = '(monitor)'
                            SendQEntries = '(monitor)'
                            LogXptStatus = '(monitor)'
                            RecvQEntries = '(monitor)'
                            SidName = 'CMOVP'
                            StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.6.4)(PORT=1522))(CONNECT_DATA=(SERVICE_NAME=CMOVPDG_DGMGRL)(INSTANCE_NAME=CMOVP)(SERVER=DEDICATED)))'
                            StandbyArchiveLocation = '/archives/CMOVP/stby'
                            AlternateLocation = ''
                            LogArchiveTrace = '0'
                            LogArchiveFormat = '%t_%s_%r.arc'
                            TopWaitEvents = '(monitor)'

                            Database Status:
                            ERROR

                            DGMGRL>

                            So I still don't get this iisue
                            And it generates an incident
                            Incident details in: /app/oracle/diag/rdbms/cmovpdg/CMOVP/incident/incdir_520375/CMOVP_pr00_9374_i520375.trc
                            But the details are vague.

                            Any Ideas?

                            Thxs for your reply.
                            • 41. Re: RMAN-05501: aborting duplication of target database
                              okKarol
                              .
                              .
                              .
                              contents of Memory Script:
                              {
                              set until scn 1638816629;
                              recover
                              standby
                              clone database
                              delete archivelog
                              ;
                              }
                              executing Memory Script

                              executing command: SET until clause

                              Starting recover at 14-MAY-13

                              starting media recovery

                              archived log for thread 1 with sequence 32196 is already on disk as file /archives/CMOVP/stby/1_32196_810397891.arc
                              archived log for thread 1 with sequence 32197 is already on disk as file /archives/CMOVP/stby/1_32197_810397891.arc
                              archived log for thread 1 with sequence 32198 is already on disk as file /archives/CMOVP/stby/1_32198_810397891.arc
                              archived log for thread 1 with sequence 32199 is already on disk as file /archives/CMOVP/stby/1_32199_810397891.arc
                              archived log for thread 1 with sequence 32200 is already on disk as file /archives/CMOVP/stby/1_32200_810397891.arc
                              archived log for thread 1 with sequence 32201 is already on disk as file /archives/CMOVP/stby/1_32201_810397891.arc
                              archived log for thread 1 with sequence 32202 is already on disk as file /archives/CMOVP/stby/1_32202_810397891.arc
                              archived log for thread 1 with sequence 32203 is already on disk as file /archives/CMOVP/stby/1_32203_810397891.arc
                              archived log for thread 1 with sequence 32204 is already on disk as file /archives/CMOVP/stby/1_32204_810397891.arc
                              archived log for thread 1 with sequence 32205 is already on disk as file /archives/CMOVP/stby/1_32205_810397891.arc
                              archived log for thread 1 with sequence 32206 is already on disk as file /archives/CMOVP/stby/1_32206_810397891.arc
                              archived log for thread 1 with sequence 32207 is already on disk as file /archives/CMOVP/stby/1_32207_810397891.arc
                              archived log for thread 1 with sequence 32208 is already on disk as file /archives/CMOVP/stby/1_32208_810397891.arc
                              archived log for thread 1 with sequence 32209 is already on disk as file /archives/CMOVP/stby/1_32209_810397891.arc
                              archived log for thread 1 with sequence 32210 is already on disk as file /archives/CMOVP/stby/1_32210_810397891.arc
                              archived log for thread 1 with sequence 32211 is already on disk as file /archives/CMOVP/stby/1_32211_810397891.arc
                              archived log for thread 1 with sequence 32212 is already on disk as file /archives/CMOVP/stby/1_32212_810397891.arc
                              archived log for thread 1 with sequence 32213 is already on disk as file /archives/CMOVP/stby/1_32213_810397891.arc
                              archived log for thread 1 with sequence 32214 is already on disk as file /archives/CMOVP/stby/1_32214_810397891.arc
                              archived log for thread 1 with sequence 32215 is already on disk as file /archives/CMOVP/stby/1_32215_810397891.arc
                              archived log for thread 1 with sequence 32216 is already on disk as file /archives/CMOVP/stby/1_32216_810397891.arc
                              archived log for thread 1 with sequence 32217 is already on disk as file /archives/CMOVP/stby/1_32217_810397891.arc
                              archived log for thread 1 with sequence 32218 is already on disk as file /archives/CMOVP/stby/1_32218_810397891.arc
                              archived log for thread 1 with sequence 32219 is already on disk as file /archives/CMOVP/stby/1_32219_810397891.arc
                              archived log for thread 1 with sequence 32220 is already on disk as file /archives/CMOVP/stby/1_32220_810397891.arc
                              archived log for thread 1 with sequence 32221 is already on disk as file /archives/CMOVP/stby/1_32221_810397891.arc
                              archived log for thread 1 with sequence 32222 is already on disk as file /archives/CMOVP/stby/1_32222_810397891.arc
                              archived log for thread 1 with sequence 32223 is already on disk as file /archives/CMOVP/stby/1_32223_810397891.arc
                              archived log file name=/archives/CMOVP/stby/1_32196_810397891.arc thread=1 sequence=32196
                              released channel: prm1
                              released channel: stby1
                              RMAN-00571: ===========================================================
                              RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
                              RMAN-00571: ===========================================================
                              RMAN-03002: failure of Duplicate Db command at 05/14/2013 01:11:33
                              RMAN-05501: aborting duplication of target database
                              RMAN-03015: error occurred in stored script Memory Script
                              ORA-00283: recovery session canceled due to errors
                              RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/archives/CMOVP/stby/1_32196_810397891.arc'
                              ORA-00283: recovery session canceled due to errors
                              ORA-00354: corrupt redo log block header
                              ORA-00353: log corruption near block 2048 change 1638686297 time 05/13/2013 22:42:03
                              ORA-00334: archived log: '/archives/CMOVP/stby/1_32196_810397891.arc'

                              What I did:

                              Rma target /
                              RMAN>catalog archivelog '/archives/CMOVP/stby/1_32196_810397891.arc';

                              Rman target / catalog rman/rman@rman auxiliary
                              RMAN> run
                              {
                              set until scn 1638816629;
                              recover
                              standby
                              clone database
                              delete archivelog
                              ;
                              }


                              And The recover process Complted Sucessfully this Time.

                              Does anyone can tell me how it could happened !!!!!
                              1 2 3 Previous Next