1 Reply Latest reply: May 15, 2013 3:55 AM by Mahir M. Quluzade RSS

    RMAN-05501: RMAN-11003 ORA-00353: log corruption near block 2048 change

    okKarol
      Hi Gurus,


      I've posted few days ago an issue I got while recreating my Dataguard.
      The Main issue was while duplicating target from active database I got this errors during the recovery process.
      The Restore Process Went fine, RMAN Copied the Datafiles very well, but stop when at the moment to start the recovery process from the auxiliary db

      Yesterday I took one last try,
      I follow same procedure, the one described in all Oracle Docs, Google and so on ... it's not a secret I guess.

      The I got the same issue, same errors.

      I read soemthing about archivelogs, and the Block corruption and so on, I've tried so many things (register the log... etc etc ), and than I read something about "catalog the logfile)
      and that's waht I did.

      But I was just connect to the target db.
      .
      .
      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';

      The I connect to target and Auxiliary again :
      Rman target / catalog rman/rman@rman auxiliary
      and I run the last content of the failing memory script:
      RMAN> run
      {
      set until scn 1638816629;
      recover
      standby
      clone database
      delete archivelog
      ;
      }


      And The DB start the recovery Process and my Standby complete the recovery very weel with message "Recovery Finnish or Termintaed or Completed"
      The I could configure Datagurd
      And I check the process and the Log Apply was on and running fine, no gaps, perfect!!!!!

      How !!! Just Cataloging an "Supposed Corrupted"archive log !!!!!!
      If Any ideas, that ould be great to understand this.

      Rgds
      Carlos
        • 1. Re: RMAN-05501: RMAN-11003 ORA-00353: log corruption near block 2048 change
          Mahir M. Quluzade
          okKarol wrote:
          Hi Gurus,


          I've posted few days ago an issue I got while recreating my Dataguard.
          The Main issue was while duplicating target from active database I got this errors during the recovery process.
          The Restore Process Went fine, RMAN Copied the Datafiles very well, but stop when at the moment to start the recovery process from the auxiliary db

          Yesterday I took one last try,
          I follow same procedure, the one described in all Oracle Docs, Google and so on ... it's not a secret I guess.

          The I got the same issue, same errors.

          I read soemthing about archivelogs, and the Block corruption and so on, I've tried so many things (register the log... etc etc ), and than I read something about "catalog the logfile)
          and that's waht I did.

          But I was just connect to the target db.
          .
          .
          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';

          The I connect to target and Auxiliary again :
          Rman target / catalog rman/rman@rman auxiliary
          and I run the last content of the failing memory script:
          RMAN> run
          {
          set until scn 1638816629;
          recover
          standby
          clone database
          delete archivelog
          ;
          }


          And The DB start the recovery Process and my Standby complete the recovery very weel with message "Recovery Finnish or Termintaed or Completed"
          The I could configure Datagurd
          And I check the process and the Log Apply was on and running fine, no gaps, perfect!!!!!

          How !!! Just Cataloging an "Supposed Corrupted"archive log !!!!!!
          If Any ideas, that ould be great to understand this.

          Rgds
          Carlos
          Hi,

          Can you change standby database archive destination from /archives/CMOVP/stby/ other disk?
          I think this problem on your disk.

          Mahir

          p.s. I remember you before thread, too