SYSTEM TS Corruption - Zero Blocks

One of our production instances use operating system level COPY as backup method. When we tried to implement rman backups, we came to know there are some zero blocks in system tablespace. after doing a DBV on the datafile noted by rman, we found there are 12 corrupt/zero pages in system03.dbf.
We cannot go to a backup and roll forward, because we dont know since when this system03 is corrupt. The only option that comes to mind is a full export and rebuild of the database. This is an oracle applications db and pretty critical. The size is around 300GB. We cant afford that much downtime on production.
Any ideas ? so far we didnt have any reported issues due to this corruption. The corrupted object in SYS.IDL_UB1$.
++DBV LOG :-++
DBVERIFY: Release 10.2.0.3.0 - Production on Thu Dec 11 11:00:26 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
DBVERIFY - Verification starting : FILE = system03.dbf
Page 191938 is influx - most likely media corrupt
Corrupt block relative dba: 0x00c2edc2 (file 3, block 191938)
Fractured block found during dbv:
Data in bad block:
type: 0 format: 2 rdba: 0x00c2edc2
last change scn: 0x0000.00000000 seq: 0x1 flg: 0x05
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x00000000
check value in block header: 0xea00
computed block checksum: 0x1
Page 191939 is marked corrupt
Corrupt block relative dba: 0x00c2edc3 (file 3, block 191939)
Completely zero block found during dbv:
Page 191940 is marked corrupt
Corrupt block relative dba: 0x00c2edc4 (file 3, block 191940)
Completely zero block found during dbv:
Page 191941 is marked corrupt
Corrupt block relative dba: 0x00c2edc5 (file 3, block 191941)
Completely zero block found during dbv:
Page 191942 is marked corrupt
Corrupt block relative dba: 0x00c2edc6 (file 3, block 191942)
Completely zero block found during dbv:
Page 191943 is marked corrupt
Corrupt block relative dba: 0x00c2edc7 (file 3, block 191943)
Completely zero block found during dbv:
Page 191944 is marked corrupt
Corrupt block relative dba: 0x00c2edc8 (file 3, block 191944)
Completely zero block found during dbv:
Page 191945 is marked corrupt
Corrupt block relative dba: 0x00c2edc9 (file 3, block 191945)
Completely zero block found during dbv:
Page 191946 is marked corrupt
Corrupt block relative dba: 0x00c2edca (file 3, block 191946)
Completely zero block found during dbv:
Page 191947 is marked corrupt
Corrupt block relative dba: 0x00c2edcb (file 3, block 191947)
Completely zero block found during dbv:
Page 191948 is marked corrupt
Corrupt block relative dba: 0x00c2edcc (file 3, block 191948)
Completely zero block found during dbv:
Page 191949 is influx - most likely media corrupt
Corrupt block relative dba: 0x00c2edcd (file 3, block 191949)
Fractured block found during dbv:
Data in bad block:
type: 0 format: 0 rdba: 0x00000000
last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x00000001
check value in block header: 0x0
block checksum disabled
DBVERIFY - Verification complete
Total Pages Examined : 256000
Total Pages Processed (Data) : 128521
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 52973
Total Pages Failing (Index): 0
Total Pages Processed (Other): 493
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 74001
Total Pages Marked Corrupt : 12
Total Pages Influx : 2
Highest block SCN : 1191398275 (1.1191398275)
Edited by: Lakshmi Pavuluri on Dec 11, 2008 11:30 AM

I think Oracle support is playing it safe. With damaged system tablespace without backup, that's logical conclusion.
Did you try run hcheck.sql to get a report?
"hcheck.sql" script to check for known problems in Oracle8i,Oracle9i, Oracle10g and Oracle 11g
Doc ID: Note:136697.1
Do some DML on table SYS.IDL_UB1$ see you get any error.
This metalink doc has some info on fixing damaged database dictionary.
ORA-8103 Diagnostics and Solution
Doc ID: Note:268302.1
The error just mean the block has been zeroed out a common type of corruption.

Similar Messages

  • System and sysaux file block corruption

    Errors in file /u01/app/oracle/diag/rdbms/pdent/pdent/trace/pdent_smon_3135.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01578: ORACLE data block corrupted (file # 1, block # 91607)
    ORA-01110: data file 1: '/u01/app/oracle/oradata/pdent/system01.dbf'
    I am unable to take r man backup, as well as export using datapump. i tried to recover it using rman blockrecover but still same. here is detail
    SQL> SELECT * FROM V$DATABASE_BLOCK_CORRUPTION;
    FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
    1 91607 1 0 CHECKSUM
    2 58710 1 0 CHECKSUM
    5 1202316 1 0 CHECKSUM
    SQL> SELECT
    tablespace_name,
    segment_type,
    owner,
    segment_name
    FROM dba_extents
    WHERE file_id = 1
    AND BETWEEN block_id AND block_id + blocks - 1; 2 3 4 5 6 7 8
    TABLESPACE_NAME SEGMENT_TYPE OWNER
    SEGMENT_NAME
    SYSTEM INDEX SYS
    I_OBJ2
    alter system dump datafile 1 block 344;
    SQL> SELECT
    tablespace_name,
    segment_type,
    owner,
    segment_name
    FROM dba_extents
    WHERE file_id = 2
    AND 58710 BETWEEN block_id AND block_id + blocks - 1; 2 3 4 5 6 7 8
    TABLESPACE_NAME SEGMENT_TYPE OWNER
    SEGMENT_NAME
    SYSAUX INDEX PARTITION SYS
    WRH$_OSSTAT_PK
    SQL> ALTER INDEX I_OBJ2 REBUILD ONLINE;
    ALTER INDEX I_OBJ2 REBUILD ONLINE
    ERROR at line 1:
    ORA-00701: object necessary for warmstarting database cannot be altered
    need immediate help.
    thanks in advance

    user11914238 wrote:
    Errors in file /u01/app/oracle/diag/rdbms/pdent/pdent/trace/pdent_smon_3135.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01578: ORACLE data block corrupted (file # 1, block # 91607)
    ORA-01110: data file 1: '/u01/app/oracle/oradata/pdent/system01.dbf'
    I am unable to take r man backup, as well as export using datapump. i tried to recover it using rman blockrecover but still same. here is detail
    SQL> SELECT * FROM V$DATABASE_BLOCK_CORRUPTION;
    FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
    1 91607 1 0 CHECKSUM
    2 58710 1 0 CHECKSUM
    5 1202316 1 0 CHECKSUM
    SQL> SELECT
    tablespace_name,
    segment_type,
    owner,
    segment_name
    FROM dba_extents
    WHERE file_id = 1
    AND BETWEEN block_id AND block_id + blocks - 1; 2 3 4 5 6 7 8
    TABLESPACE_NAME SEGMENT_TYPE OWNER
    SEGMENT_NAME
    SYSTEM INDEX SYS
    I_OBJ2
    alter system dump datafile 1 block 344;
    SQL> SELECT
    tablespace_name,
    segment_type,
    owner,
    segment_name
    FROM dba_extents
    WHERE file_id = 2
    AND 58710 BETWEEN block_id AND block_id + blocks - 1; 2 3 4 5 6 7 8
    TABLESPACE_NAME SEGMENT_TYPE OWNER
    SEGMENT_NAME
    SYSAUX INDEX PARTITION SYS
    WRH$_OSSTAT_PK
    SQL> ALTER INDEX I_OBJ2 REBUILD ONLINE;
    ALTER INDEX I_OBJ2 REBUILD ONLINE
    ERROR at line 1:
    ORA-00701: object necessary for warmstarting database cannot be altered
    need immediate help.
    Immediate help can be only provided by Oracle Support Services. So if you need that, please raise a Sev1 SR . For your issue, as others have suggested already, if you have a valid backup and you are in the archive log mode, using RMAN's BMR(Block Media Recovery) , the issue can be resolved provided there is nothing wrong with the hardware of yours. If that's the case, recovery wouldn't yield any benefits.
    Aman....

  • Zero Block Corruption in SE Environment.

    Environment: 11g Using Standard Edition of Rracle in Windows environment.
    I'm having difficulties finding any article or support documents for Zero block corruption issues at logical level.
    If i took Export of the full database, and have no errors. does that count as safe data.
    Does EXPDP skip the such error like block corruption. What are the option beyond the expdp to find any block level corruption

    >What are the option beyond the expdp to find any block level corruption
    run dbv against desired datafile
    [oracle@localhost ~]$ dbv
    DBVERIFY: Release 11.2.0.2.0 - Production on Tue Apr 21 12:39:28 2015
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    Keyword     Description                    (Default)
    FILE        File to Verify                 (NONE)
    START       Start Block                    (First Block of File)
    END         End Block                      (Last Block of File)
    BLOCKSIZE   Logical Block Size             (8192)
    LOGFILE     Output Log                     (NONE)
    FEEDBACK    Display Progress               (0)
    PARFILE     Parameter File                 (NONE)
    USERID      Username/Password              (NONE)
    SEGMENT_ID  Segment ID (tsn.relfile.block) (NONE)
    HIGH_SCN    Highest Block SCN To Verify    (NONE)
                (scn_wrap.scn_base OR scn)          
    [oracle@localhost ~]$

  • SYSTEM Tablespace corrupt blocks !!!!!!!!!

    Hi,
    Oracle version 10gR2 - 10.2.0.1.0
    The database which i am running in 10g is having few corrupt data blocks in system data files. I have no backup of full database and neither the database is in archive log mode. I know the situation of my development database has very less chance of getting to open mode.
    I have checked in metalink in for any hidden parameters, But my funny questions do u think there is any hidden parameter to get out of this issue. please suggest any metalink doc or any parameter to overcome this issue :-)
    Thanks
    Edited by: user11981262 on Dec 15, 2011 8:41 AM

    I don't know any helping secret parameter for you. As I see this your data is lost.
    What you can do is documented in [url https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=BULLETIN&id=28814.1]Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g/11g ID 28814.1 Read carefully and try database recovery (from online logs)... submit your results here.

  • Interpration of DBVerify zero block  errors

    Hello Oracle-experts,
    after DBVerify check on my Oracle DB 10.2.0.2 i get the several following errors:
    Completely zero block found during dbv:
    Page 286685 is marked corrupt
    After these warnings I get the error:
    BR0398E DBVERIFY detected corrupted blocks in /oracle/<sid>/sapdata4/sr3_8/sr3.data8
    Question:
    1) How should these zero block errors be interpreted?  Is my database therefore corrupt or can these errors be neglected?  If not, what is the approach to solve these errors?
    The problem is that I have a lot of these errors and do not have a valid backup.
    Any helpful information information will be very appreciated!

    Hi Holger,
    didn't you like the replies of your other threads?
    Block Corruption (BR0398E DBVERIFY detected corrupted blocks in /oracle/TS2
    BR0398E DBVERIFY detected corrupted blocks in TS SAPSR3
    Honestly, handling corruptions is really not that difficult.
    You figure out what kind of data is supposed to be stored in the corrupted blocks and take your actions accordingly.
    So if you can regenerate the content (like you can do that by rebuilding indexes), you do that.
    If you cannot regenerate the content, you need a backup.
    That's it. It's all lengthly described in the SAP notes on corruptions. Maybe you should read them ...
    > Question:
    > 1) How should these zero block errors be interpreted?  Is my database therefore corrupt or can these errors be neglected?  If not, what is the approach to solve these errors?
    > The problem is that I have a lot of these errors and do not have a valid backup.
    Ok, having no backups always puts you in dire straits. It's the single one error no DBA is allowed to make.
    However, what you should do is to perform a FULL consistency check.
    That is:
    run ANALYZE TABLE VALIDATE STRUCTURE CASCADE on ALL tables
    run a FULL db export to /dev/nul
    run DBVerify/RMAN validate on the complete database (looks like you've already done that)
    Don't skip a check, don't shortcut - just do them.
    Maybe the "completely zero filled blocks* don't belong to any object and you've no data loss.
    Then you may (as I already told you in the other thread) reorganize the tablespace to get rid of the warnings.
    If there was some data in these blocks that you cannot regenerate then you have to face it: you lost that data.
    It's gone and won't come back.
    regards,
    Lars

  • Log corruption near block 1737

    hi,
    i am getting an error while open the db
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-00368: checksum error in redo log block
    ORA-00353: log corruption near block 1737 change 16680088 time 12/22/2008
    10:40:13
    ORA-00312: online log 2 thread 1: 'G:\ORACLE\ORADATA\HOTEST\REDO02.LOG'while doing an incomplete recovery it is asking for an archived file which i am not having i.e ARC_801_1.ARC.........
    SQL> recover database until cancel;
    ORA-00279: change 16679127 generated at 12/22/2008 10:37:11 needed for thread 1
    ORA-00289: suggestion : G:\ORACLE\ARCH\ARC_801_1.ARC
    ORA-00280: change 16679127 for thread 1 is in sequence #801
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: 'G:\ORACLE\ORADATA\HOTEST\SYSTEM01.DBF'
    ORA-01112: media recovery not startedpls suggest me for the same....

    I am not having a archived log of sequence no. 801 neither i am having backup, is there any other way to up the db....
    SMON: enabling tx recovery
    Mon Dec 22 10:37:16 2008
    Database Characterset is WE8MSWIN1252
    replication_dependency_tracking turned off (no async multimaster replication found)
    Completed: alter database open
    Corrupt block relative dba: 0x0300cc4b (file 12, block 52299)
    Bad check value found during buffer read
    Data in bad block -
    type: 6 format: 2 rdba: 0x0300cc4b
    last change scn: 0x0000.000fa127 seq: 0x1 flg: 0x06
    consistency value in tail: 0xa1270601
    check value in block header: 0x8f85, computed block checksum: 0xcf00
    spare1: 0x0, spare2: 0x0, spare3: 0x0
    Reread of rdba: 0x0300cc4b (file 12, block 52299) found valid data
    Corrupt block relative dba: 0x0300cdfb (file 12, block 52731)
    Bad check value found during buffer read
    Data in bad block -
    type: 6 format: 2 rdba: 0x0300cdfb
    last change scn: 0x0000.000fa128 seq: 0x1 flg: 0x04
    consistency value in tail: 0xa1280601
    check value in block header: 0x446b, computed block checksum: 0x3200
    spare1: 0x0, spare2: 0x0, spare3: 0x0
    Reread of rdba: 0x0300cdfb (file 12, block 52731) found valid data
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         Dump file g:\oracle\admin\hotest\bdump\alert_hotest.log
    Mon Dec 22 10:41:29 2008
    ORACLE V9.2.0.4.0 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.1 Service Pack 2, CPU type 586
    Mon Dec 22 10:41:29 2008
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 2
    Using log_archive_dest parameter default value
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.4.0.
    System parameters with non-default values:
      processes                = 150
      timed_statistics         = TRUE
      shared_pool_size         = 50331648
      large_pool_size          = 8388608
      java_pool_size           = 33554432
      control_files            = G:\oracle\oradata\hotest\CONTROL01.CTL, G:\oracle\oradata\hotest\CONTROL02.CTL, G:\oracle\oradata\hotest\CONTROL03.CTL
      db_block_size            = 8192
      db_cache_size            = 25165824
      compatible               = 9.2.0.0.0
      log_archive_start        = TRUE
      log_archive_dest_1       = location=G:\oracle\arch
      log_archive_dest_2       = SERVICE=stand LGWR ASYNC
      log_archive_dest_state_1 = ENABLE
      log_archive_dest_state_2 = ENABLE
      fal_server               = STAND
      fal_client               = HOTEST
      log_archive_format       = arc_%s_%t.arc
      db_file_multiblock_read_count= 16
      fast_start_mttr_target   = 300
      undo_management          = AUTO
      undo_tablespace          = UNDOTBS1
      undo_retention           = 10800
      remote_login_passwordfile= EXCLUSIVE
      db_domain                =
      instance_name            = hotest
      dispatchers              = (PROTOCOL=TCP) (SERVICE=hotestXDB)
      job_queue_processes      = 10
      hash_join_enabled        = TRUE
      background_dump_dest     = G:\oracle\admin\hotest\bdump
      user_dump_dest           = G:\oracle\admin\hotest\udump
      core_dump_dest           = G:\oracle\admin\hotest\cdump
      sort_area_size           = 524288
      db_name                  = hotest
      open_cursors             = 300
      star_transformation_enabled= FALSE
      query_rewrite_enabled    = FALSE
      pga_aggregate_target     = 25165824
      aq_tm_processes          = 1
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    CJQ0 started with pid=8
    QMN0 started with pid=9
    Mon Dec 22 10:41:36 2008
    starting up 1 shared server(s) ...
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=12
    ARC0: Archival started
    ARC1 started with pid=13
    Mon Dec 22 10:41:37 2008
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Mon Dec 22 10:41:37 2008
    ARC0: Thread not mounted
    Mon Dec 22 10:41:38 2008
    ARC1: Archival started
    Mon Dec 22 10:41:38 2008
    ARC1: Thread not mounted
    Mon Dec 22 10:41:38 2008
    alter database mount exclusive
    Mon Dec 22 10:41:43 2008
    Successful mount of redo thread 1, with mount id 1003521250.
    Mon Dec 22 10:41:43 2008
    Database mounted in Exclusive Mode.
    Completed: alter database mount exclusive
    Mon Dec 22 10:41:43 2008
    alter database open
    Mon Dec 22 10:41:44 2008
    Beginning crash recovery of 1 threads
    Mon Dec 22 10:41:44 2008
    Started first pass scan
    ORA-368 signalled during: alter database open...
    Mon Dec 22 10:42:35 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Dump file g:\oracle\admin\hotest\bdump\alert_hotest.log
    Mon Dec 29 10:14:22 2008
    ORACLE V9.2.0.4.0 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.1 Service Pack 2, CPU type 586
    Mon Dec 29 10:14:22 2008
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 2
    Using log_archive_dest parameter default value
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.4.0.
    System parameters with non-default values:
      processes                = 150
      timed_statistics         = TRUE
      shared_pool_size         = 50331648
      large_pool_size          = 8388608
      java_pool_size           = 33554432
      control_files            = G:\oracle\oradata\hotest\CONTROL01.CTL, G:\oracle\oradata\hotest\CONTROL02.CTL, G:\oracle\oradata\hotest\CONTROL03.CTL
      db_block_size            = 8192
      db_cache_size            = 25165824
      compatible               = 9.2.0.0.0
      log_archive_start        = TRUE
      log_archive_dest_1       = location=G:\oracle\arch
      log_archive_dest_2       = SERVICE=stand LGWR ASYNC
      log_archive_dest_state_1 = ENABLE
      log_archive_dest_state_2 = ENABLE
      fal_server               = STAND
      fal_client               = HOTEST
      log_archive_format       = arc_%s_%t.arc
      db_file_multiblock_read_count= 16
      fast_start_mttr_target   = 300
      undo_management          = AUTO
      undo_tablespace          = UNDOTBS1
      undo_retention           = 10800
      remote_login_passwordfile= EXCLUSIVE
      db_domain                =
      instance_name            = hotest
      dispatchers              = (PROTOCOL=TCP) (SERVICE=hotestXDB)
      job_queue_processes      = 10
      hash_join_enabled        = TRUE
      background_dump_dest     = G:\oracle\admin\hotest\bdump
      user_dump_dest           = G:\oracle\admin\hotest\udump
      core_dump_dest           = G:\oracle\admin\hotest\cdump
      sort_area_size           = 524288
      db_name                  = hotest
      open_cursors             = 300
      star_transformation_enabled= FALSE
      query_rewrite_enabled    = FALSE
      pga_aggregate_target     = 25165824
      aq_tm_processes          = 1
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    CJQ0 started with pid=8
    QMN0 started with pid=9
    Mon Dec 29 10:14:28 2008
    starting up 1 shared server(s) ...
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=12
    ARC0: Archival started
    ARC1 started with pid=13
    ARC1: Archival started
    Mon Dec 29 10:14:30 2008
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Mon Dec 29 10:14:30 2008
    ARC1: Thread not mounted
    Mon Dec 29 10:14:31 2008
    ARC0: Thread not mounted
    Mon Dec 29 10:14:32 2008
    alter database mount exclusive
    Mon Dec 29 10:14:37 2008
    Successful mount of redo thread 1, with mount id 1004122632.
    Mon Dec 29 10:14:37 2008
    Database mounted in Exclusive Mode.
    Completed: alter database mount exclusive
    Mon Dec 29 10:14:37 2008
    alter database open
    Mon Dec 29 10:14:37 2008
    Beginning crash recovery of 1 threads
    Mon Dec 29 10:14:38 2008
    Started first pass scan
    ORA-368 signalled during: alter database open...
    Mon Dec 29 10:15:29 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 10:20:44 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 10:25:54 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 10:31:09 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 10:36:24 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 10:41:40 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 10:46:55 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 10:52:10 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 10:57:26 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 11:02:41 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 11:07:56 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 11:13:05 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 11:18:15 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 11:23:30 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 11:28:39 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 11:33:49 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 11:39:04 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 11:44:19 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 11:49:35 2008
    Restarting dead background process QMN0
    QMN0 started with pid=9
    Mon Dec 29 11:54:44 2008
    Restarting dead background process QMN0
    QMN0 started with pid=15
    Mon Dec 29 11:59:59 2008
    Restarting dead background process QMN0
    QMN0 started with pid=14
    Mon Dec 29 12:03:06 2008
    alter database open
    Mon Dec 29 12:03:06 2008
    Beginning crash recovery of 1 threads
    Mon Dec 29 12:03:07 2008
    Started first pass scan
    ORA-368 signalled during: alter database open...
    Mon Dec 29 12:05:09 2008
    Restarting dead background process QMN0
    QMN0 started with pid=15
    Mon Dec 29 12:05:14 2008
    ALTER DATABASE RECOVER  database until cancel 
    Mon Dec 29 12:05:14 2008
    Media Recovery Start
    Starting datafile 1 recovery in thread 1 sequence 801
    Datafile 1: 'G:\ORACLE\ORADATA\HOTEST\SYSTEM01.DBF'
    Starting datafile 2 recovery in thread 1 sequence 801
    Datafile 2: 'G:\ORACLE\ORADATA\HOTEST\UNDOTBS01.DBF'
    Starting datafile 3 recovery in thread 1 sequence 801
    Datafile 3: 'G:\ORACLE\ORADATA\HOTEST\CWMLITE01.DBF'
    Starting datafile 4 recovery in thread 1 sequence 801
    Datafile 4: 'G:\ORACLE\ORADATA\HOTEST\DRSYS01.DBF'
    Starting datafile 5 recovery in thread 1 sequence 801
    Datafile 5: 'G:\ORACLE\ORADATA\HOTEST\EXAMPLE01.DBF'
    Starting datafile 6 recovery in thread 1 sequence 801
    Datafile 6: 'G:\ORACLE\ORADATA\HOTEST\INDX01.DBF'
    Starting datafile 7 recovery in thread 1 sequence 801
    Datafile 7: 'G:\ORACLE\ORADATA\HOTEST\ODM01.DBF'
    Starting datafile 8 recovery in thread 1 sequence 801
    Datafile 8: 'G:\ORACLE\ORADATA\HOTEST\TOOLS01.DBF'
    Starting datafile 9 recovery in thread 1 sequence 801
    Datafile 9: 'G:\ORACLE\ORADATA\HOTEST\USERS01.DBF'
    Starting datafile 10 recovery in thread 1 sequence 801
    Datafile 10: 'G:\ORACLE\ORADATA\HOTEST\XDB01.DBF'
    Starting datafile 11 recovery in thread 1 sequence 801
    Datafile 11: 'G:\ORACLE\ORADATA\HOTEST\CADATA3.ORA'
    Starting datafile 12 recovery in thread 1 sequence 801
    Datafile 12: 'G:\ORACLE\ORADATA\HOTEST\CADATA.ORA'
    Starting datafile 13 recovery in thread 1 sequence 801
    Datafile 13: 'G:\ORACLE\ORADATA\HOTEST\CADATAWRO.ORA'
    Starting datafile 14 recovery in thread 1 sequence 801
    Datafile 14: 'G:\ORACLE\ORADATA\HOTEST\CADATANRO.ORA'
    Starting datafile 15 recovery in thread 1 sequence 801
    Datafile 15: 'G:\ORACLE\ORADATA\HOTEST\CADATACRO.ORA'
    Starting datafile 16 recovery in thread 1 sequence 801
    Datafile 16: 'G:\ORACLE\ORADATA\HOTEST\CADATAOTH.ORA'
    Starting datafile 17 recovery in thread 1 sequence 801
    Datafile 17: 'G:\ORACLE\ORADATA\HOTEST\CADATAERO.ORA'
    Starting datafile 18 recovery in thread 1 sequence 801
    Datafile 18: 'G:\ORACLE\ORADATA\HOTEST\CADATAHO.ORA'
    Starting datafile 19 recovery in thread 1 sequence 801
    Datafile 19: 'G:\ORACLE\ORADATA\HOTEST\CADATASRO.ORA'
    Starting datafile 20 recovery in thread 1 sequence 801
    Datafile 20: 'G:\ORACLE\ORADATA\HOTEST\PAYROLL.ORA'
    Starting datafile 21 recovery in thread 1 sequence 801
    Datafile 21: 'G:\ORACLE\ORADATA\HOTEST\ORION.ORA'
    Starting datafile 22 recovery in thread 1 sequence 801
    Datafile 22: 'G:\ORACLE\ORADATA\HOTEST\ATHENA.ORA'
    Starting datafile 23 recovery in thread 1 sequence 801
    Datafile 23: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2004.ORA'
    Starting datafile 24 recovery in thread 1 sequence 801
    Datafile 24: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2005.ORA'
    Starting datafile 25 recovery in thread 1 sequence 801
    Datafile 25: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2006.ORA'
    Starting datafile 26 recovery in thread 1 sequence 801
    Datafile 26: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2007.ORA'
    Starting datafile 27 recovery in thread 1 sequence 801
    Datafile 27: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2008.ORA'
    Starting datafile 28 recovery in thread 1 sequence 801
    Datafile 28: 'G:\ORACLE\ORADATA\HOTEST\CAL_YEAR_2009.ORA'
    Starting datafile 29 recovery in thread 1 sequence 801
    Datafile 29: 'G:\ORACLE\ORADATA\HOTEST\EXAMPLE02.DBF'
    Starting datafile 30 recovery in thread 1 sequence 801
    Datafile 30: 'G:\ORACLE\ORADATA\HOTEST\EXAMPLE02.RAW'
    Media Recovery Log
    ORA-279 signalled during: ALTER DATABASE RECOVER  database until cancel  ...
    Mon Dec 29 12:06:24 2008
    ALTER DATABASE RECOVER    CANCEL 
    Mon Dec 29 12:06:24 2008
    ORA-1547 signalled during: ALTER DATABASE RECOVER    CANCEL  ...
    Mon Dec 29 12:06:24 2008
    ALTER DATABASE RECOVER CANCEL
    ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...
    Mon Dec 29 12:06:40 2008
    alter database open resetlogs
    Mon Dec 29 12:06:41 2008
    ORA-1194 signalled during: alter database open resetlogs...
    Mon Dec 29 12:06:47 2008
    alter database open noresetlogs
    Mon Dec 29 12:06:48 2008
    Beginning crash recovery of 1 threads
    Mon Dec 29 12:06:48 2008
    Started first pass scan
    ORA-368 signalled during: alter database open noresetlogs...
    Mon Dec 29 12:10:24 2008
    Restarting dead background process QMN0
    QMN0 started with pid=15
    Mon Dec 29 12:15:39 2008
    Restarting dead background process QMN0
    QMN0 started with pid=15
    Mon Dec 29 12:20:55 2008
    Restarting dead background process QMN0
    QMN0 started with pid=15
    Mon Dec 29 12:26:10 2008

  • Corrupting the block to continue recovery in physical standby

    Hi,
    Just like to inquire how I will be able to corrupt the block to be able to continue the recovery in the physical standby.
    DB Version: 11.1.0.7
    Database Type: Data Warehouse
    The setup we have is primary database and standby database, we are not using dataguard, and our standby setup is another physical copy of production which act as standby and being sync using script that being run from time to time to apply the archive log came from production (its not configured to sync using ARCH or LGWR and its corresponding configurations).
    Then, the standby database is not sync due to errors encountered while trying to apply the archive log, error is below:
    Fri Feb 11 05:50:59 2011
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log /u01/archive/<sid>/1_50741_651679913.arch
    Fri Feb 11 05:52:06 2011
    Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0, kdr9ir2rst0()+326]
    Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc (incident=631460):
    ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
    Incident details in: /u01/app/oracle/diag/rdbms/<sid>/<sid>/incident/incdir_631460/<sid>pr0028085_i631460.trc
    Fri Feb 11 05:52:10 2011
    Trace dumping is performing id=[cdmp_20110211055210]
    Fri Feb 11 05:52:14 2011
    Sweep Incident[631460]: completed
    Fri Feb 11 05:52:17 2011
    Slave exiting with ORA-10562 exception
    Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc:
    ORA-10562: Error occurred while applying redo to data block (file# 36, block# 1576118)
    ORA-10564: tablespace <tablespace name>
    ORA-01110: data file 36: '/u02/oradata/<sid>/<datafile>.dbf'
    ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 14877145
    ORA-00607: Internal error occurred while making a change to a data block
    ORA-00602: internal programming exception
    ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
    Based on the error log it seems we are hitting some bug from metalink (document id 460169.1 and 882851.1)
    my question is, the datafile # is given, block# is known too and the data object is also identified. I just verified that object is not that important, is there a way to set the block# to corrupted to be able the recovery to continue? Then I will just drop the table from production so that will also happen in standby, and the block corrupted will be gone too. Is this feasible?
    If its not, can you suggest what's next I can do so the the physical standby will be able to sync again to prod aside from rebuilding the standby?
    Please take note that I also tried to dbv the file to confirm if there is marked as corrupted and the result for that datafile is also good:
    dbv file=/u02/oradata/<sid>/<datafile>_19.dbf logfile=dbv_file_36.log blocksize=16384
    oracle@<server>:[~] $ cat dbv_file_36.log
    DBVERIFY: Release 11.1.0.7.0 - Production on Sun Feb 13 04:35:28 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    DBVERIFY - Verification starting : FILE = /u02/oradata/<sid>/<datafile>_19.dbf
    DBVERIFY - Verification complete
    Total Pages Examined : 3840000
    Total Pages Processed (Data) : 700644
    Total Pages Failing (Data) : 0
    Total Pages Processed (Index): 417545
    Total Pages Failing (Index): 0
    Total Pages Processed (Other): 88910
    Total Pages Processed (Seg) : 0
    Total Pages Failing (Seg) : 0
    Total Pages Empty : 2632901
    Total Pages Marked Corrupt : 0
    Total Pages Influx : 0
    Total Pages Encrypted : 0
    Highest block SCN : 3811184883 (1.3811184883)
    Any help is really appreciated. I hope to hear feedback from you.
    Thanks

    damorgan, i understand the opinion.
    just new with the organization and just inherit a data warehouse database without rman backup. I am still setting up the rman backup thats why i can't use rman to resolve the issue, the only i have is physical standby and its not a standby that automatically sync using dataguard or standard standby setup, i am just checking solution that is applicable in the current situation

  • Mail   I inherited an iMac, OS X 20.6.8. The Mail system is corrupted.  I cannot close mail formats that opened to be written and sent.  I just get an unpleasant noise when I try to close these.  Also, I don't know what the outgoing mail link should be.

    RE: Mail  
    I inherited an iMac, OS X 10.6.8. The Mail system is corrupted.  I cannot close blank mail formats that opened to be written and sent.  I just get an unpleasant noise when I try to close these.  Also, I don't know what the outgoing mail link should be.
    Please help!
    M. Levine

    Quit Mail, Trash this file...
    Safe Boot , (holding Shift key down at bootup), use Disk Utility from there to Repair Permissions, test if things work OK in Safe Mode.
    Then move these files to the Desktop for now...
    /Users/YourUserName/Library/Preferences/com.apple.finder.plist
    /Users/YourUserName/Library/Preferences/com.apple.systempreferences.plist
    /Users/YourUserName/Library/Preferences/com.apple.desktop.plist
    /Users/YourUserName/Library/Preferences/com.apple.recentitems.plist
    /Users/YourUserName/Library/Preferences/com.apple.mail.plist
    Reboot & test.
    PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.

  • ITunes.exe - System error / corrupt file

    I purchased an iPod nano about a month ago. Since then about every week my entire iPod content is erased while i transfer music to iTunes. All of a sudden it disconnects and says "iTunes.exe - System error / Corrupt file". Each time this happens I need to restore my iPod, which does not help either. I have the latest iTunes version and I downloaded the iPod updater, however none of them make a difference in the situation. I would really like to know whether this can be solved or I need to return the device to the store.
    iPod Nano 2GB   Windows XP  

    Have a look at this informative link by forum member Da Gopha: Da Gopha - If Windows displays an iTunes.exe corrupt file/chkdsk message

  • Unable to drop materialized view with corrupted data blocks

    Hi,
    The alert log of our database is giving this message
    Wed Jan 31 05:23:13 2007
    ORACLE Instance mesh (pid = 9) - Error 1578 encountered while recovering transaction (6, 15) on object 13355.
    Wed Jan 31 05:23:13 2007
    Errors in file /u01/app/oracle/admin/mesh/bdump/mesh_smon_4369.trc:
    ORA-01578: ORACLE data block corrupted (file # 5, block # 388260)
    ORA-01110: data file 5: '/u03/oradata/mesh/mview.dbf'
    No one is using this mview still oracle is trying to recover this transaction (6, 15).
    when i tried to drop this mview it gives me this error
    ERROR at line 1:
    ORA-01578: ORACLE data block corrupted (file # 5, block # 388260)
    ORA-01110: data file 5: '/u03/oradata/mesh/mview.dbf'
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2255
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2461
    ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2430
    ORA-06512: at line 1
    I have tried to fix the corrupted data blocks by using dbms_repair package, but of no use.
    I have marked this block to be skipped by using dbms_repair.skip_block but still unable to drop it.
    Please suggest what should I do?
    Thanks in advance
    Anuj

    You are lucky if only your undesirable MV is affected by theese corrupted blocks. This is an advice to do a complete-super-full-hot-cold-middle backup of ypur database and search for any disk for a "possible replace".
    God save us!

  • Etc/system file corrupted how to recover it?

    etc/system file corrupted how to recover it?

    with boot -a you can only specify new /etc/system during boot , e.g. /dev/null
    but if you want to recover it , you can do it from live kernel ( if you didn't reboot after /etc/system was corrupted )
    with
    echo ::system|mdb -k
    or from previous crash dump simmilar way
    cd /var/crash/`uname -n`
    cho ::system|mdb unix.[x] vmcore.[y]

  • Systeme Preference Corruption for All Users!

    In one of my user account, I can't get the scroll bars to show!!!
    I want in preference-general and select ''Always'' under Show Scroll Bars, but I can't see them in Safari, Mail...
    When I close Preference, my ''Always'' selection is gone and it return to '' Automatically based on input device''
    Also, issue with Screen Saver. I can select any Apple default screen saver. My iMac always play my iPhoto Library.
    I'm suspecting Systeme Preference Corruption in all my users.
    In previous post, Frank recommended to boot from recovery disk, go to terminal, rset paasword window and slect ''Reset Home Folder Permissions and ACLs''
    This is what I did, exept, it was running after 24 hrs of waiting and I decide to quit. It did the same with all users...
    Do you have a solution to this issue?
    NOTE: Lions was reinstalled and HD erase. Repair Disk Permission done, Safe boot done.
    What do I got left?

    Repairing the permissions of a home folder in Lion is a complicated procedure. I don’t know of a simpler one that always works.
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the page that opens.
    Drag or copy – do not type – the following line into the Terminal window, then press return:
    chmod -R -N ~
    The command will take a noticeable amount of time to run. When a new line ending in a dollar sign ($) appears below what you entered, it’s done. You may see a few error messages about an “invalid argument” while the command is running. You can ignore those. If you get an error message with the words “Permission denied,” enter this:
    sudo !!
    You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up.
    Next, boot from your recovery partition by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
    When the recovery desktop appears, select Utilities ▹ Terminal from the menu bar.
    In the Terminal window, enter “resetpassword” (without the quotes) and press return. A Reset Password window opens.
    Select your boot volume if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select  ▹ Restart from the menu bar.

  • Block corruption에서 physial block corruption과 soft block corruption 의 차이점

    어느 분께서 저에게 block corruption에 대한 질문을 하셨는데
    그래서 솔루션을 제시해주었고 block dump를 보니 아래와 같았습니다.
    (1번덤프) 제가 잘못 진단한 block dump(soft corrupt로 판단했는데 raid5의
    디스크가 나간 physical corrupt이네요)
    *** 2007-03-06 09:54:33.103
    Start dump data blocks tsn: 6 file#: 6 minblk 102032 maxblk 102032
    buffer tsn: 6 rdba: 0x01818e90 (6/102032)
    scn: 0x056c.f689329c seq: 0x01 flg: 0x06 tail: 0xa0cf0000
    frmt: 0x02 chkval: 0x7675 type: 0x06=trans data
    Hex dump of corrupt header 2 = BROKEN
    이었습니다.
    그런데 저는 이미 이전에 physical block corruption을 경험 한 후
    아래와 같이 dump를 떠서 확인한 결과 여러문서를 찾아본 후
    이와같이 판단하였습니다.
    (2번 덤프) physical corrupt로 확인된 덤프
    - 아래의 scn: 0x0000.00000000 seq: 0xff flg: 0x00 tail: 0x000006ff
    에서 SCN이 0x0000 이고 seq값이 UB1MAXVAL-1 이 아니므로
    physical block corruption 임을 확인
    *** SESSION ID:(25.59041) 2005-12-12 11:41:13.132
    Start dump data blocks tsn: 7 file#: 8 minblk 169994 maxblk 169994
    buffer tsn: 7 rdba: 0x0202980a (8/169994)
    scn: 0x0000.00000000 seq: 0xff flg: 0x00 tail: 0x000006ff
    frmt: 0x02 chkval: 0x0000 type: 0x06=trans data
    Block header dump: 0x0202980a
    Object id on Block? Y
    seg/obj: 0xef9 csc: 0x00.8c13d2b itc: 2 flg: O typ: 2 - INDEX
    fsl: 2 fnx: 0x2024b0f ver: 0x01
    Itl Xid Uba Flag Lck Scn/Fsc
    0x01 xid: 0x0001.052.0001888b uba: 0x00c07725.2482.02 C--- 0 scn 0x0000.083a0f80
    0x02 xid: 0x0007.038.0001a196 uba: 0x00c07574.1f28.0b ---- 232 fsc 0x0f57.00000000
    질문..
    physial block corruption과 soft block corruption 인지의 여부를 block dump를
    통해서 알고 싶은데요. 기존에 제가 잘못 알고 있는 것 같습니다.

    좀 이상한 부분이 있어서 직접 login 하여서 조사해보았습니다.
    alert 에러 코드는
    Errors in file /app/oracle/product/10.2.0/admin/TEST_T_ktrp4vpe/bdump/test_t_smon_12714.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01578: ORACLE data block corrupted (file # 2, block # 2714)
    ORA-01110: data file 2: '/test_tdata/SYSTEM04.dbf'
    상기로 메타 링크를 찾아보면...
    제목: FAQ: Physical Corruption
    문서 ID: 공지:403747.1 유형: FAQ
    (a) ORA-01578 - This error explains physical structural damage with a particular block.
    (b) ORA-08103 - This error is a logical corruption error for a particular data block.
    (c) ORA-00600 [2662] - This error is related to block corruption , and occurs due to a higher SCN than of database SCN.
    -- 좀 이상한게 physical corruption 이란 문서내에
    physical corrupt 와 logical corrupt 를 분류하는게 좀 이상한데 ㅡ_ㅡ;
    a 항목이라, physical structual damage ... 자연스럽게 physcial corrupt 로 보입니다. dump 내용으로 제가 판독이 안되고, alert 의 error code 로는
    physical corrupt 로 보이는데..
    alert 의 error code 와 dump 의 내용이 상이 할수 있는건가요 ?
    글 수정:
    darkturtle

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

    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

    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
    CarlosHi,
    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

  • My system is corrupt.

    My system is corrupt, when I download adobe it covers all icons with an adobe symbol

    What Adobe product are you using: Adobe Reader or Acrobat?  If so, see http://helpx.adobe.com/acrobat/kb/application-file-icons-change-acrobat.html how to fix it.

Maybe you are looking for