Cannot read Redo log

Hi,
We have a site which is used for replication.
At this site we had a capture,propogate and the apply process.
Because of some errors we dropped the capture and propogate process.
We also droppeed the streams queue.
Then we created a new Capture and Propogate process as well as
a new streams queue.
When we start the capture process then the process gets aborted.
When we see the dump file we get the following errors.
It says that you cannot read from redo log
*** 2003-02-07 22:01:23.000
*** SESSION ID:(22.16) 2003-02-07 22:01:23.000
ORA-00333: redo log read error block 131074 count 8192
ORA-00334: archived log: 'E:\ORACLE\ORCL92\RDBMS\ARC00029.001'
ORA-27070: skgfdisp: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).
ORA-00333: redo log read error block 131074 count 8192
ORA-00334: archived log: 'E:\ORACLE\ORCL92\RDBMS\ARC00029.001'
ORA-27091: skgfqio: unable to queue I/O
ORA-27070: skgfdisp: async read/write failed
OSD-04006: ReadFile() failure, unable to read from file
O/S-Error: (OS 23) Data error (cyclic redundancy check).

OSD-04006: ReadFile() failure, unable to read from file
O/S-Error: (OS 23) Data error (cyclic redundancy check).
These errors indicate that the file is unreadable from the OS point of view.

Similar Messages

  • Third party tools for redo log

    Dear,
    Any third party tools can read redo log for oracle9i?
    ManyThanks

    Most 3rd parties gave up when they realized that
    a) Oracle now owns, and includes for free, the logminer, and
    b) Oracle is free - and willing to - change the contents of the log files at any time, including patch releases.

  • Read redo logon

    Dear,
    I need to read redo log from oracle9i. The redolog file is copy from production machine. I have copy to same version oracle testing machine. How can i to see the log information.
    Regards

    Ah ok if you only want to read them (but not create a copy of a DB) just read the docs there is a step-by-step intruduction how to can handle this using logminer: http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14215/logminer.htm#sthref1882
    Dim

  • Emergency: cannot start database because redo logs have been deleted

    Hi. Ok, so the redo logs are deleted and I don't have a backup. Fine, whatever. I am trying to just start my database and start the logging from scratch.
    ORA-00320: cannot read file header from log 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u01/oradata/orcl/redo01.log'
    ORA-27069: attempt to do I/O beyond the range of the file
    Here's what my log files look like:
    select group#, thread#, status from v$log;
    GROUP# THREAD# STATUS
    1 1 ACTIVE
    4 1 UNUSED
    3 1 UNUSED
    2 1 CURRENT
    I have group 3 and 4 just sitting there. I would love to switch logging from group 1 to group 4 (which I just created) so I can drop the corrupted group 1 but when I try:
    SQL> alter system switch logfile;
    alter system switch logfile
    ERROR at line 1:
    ORA-01109: database not open
    Of course the database is not open because I can't get it started. So, I'm in kind of a catch 22.

    I think you need to restore your database. http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/osadvsce.htm#CACFFJFB says:
    >
    Losing an Active Online Redo Log Group
    If the database is still running and the lost active redo log is not the current log, then issue the ALTER SYSTEM CHECKPOINT statement. If the operation is successful, then the active redo log becomes inactive, and you can follow the procedure in "Losing an Inactive Online Redo Log Group". If the operation is unsuccessful, or if your database has halted, then perform one of procedures in this section, depending on the archiving mode.
    The current log is the one LGWR is currently writing to. If a LGWR I/O operation fails, then LGWR terminates and the instance fails. In this case, you must restore a backup, perform incomplete recovery, and open the database with the RESETLOGS option.

  • ORA-00333: redo log read error block

    ORA-01033: ORACLE initialization or shutdown in progress ...
    / as sysdba
    SQL> shutdown immediate;
    SQL> startup nomount;
    SQL> alter database mount;
    SQL> alter database open;
    ORA-00333: redo log read error block 8299 count 8192
    SQL> SELECT * FROM V$VERSION;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Product
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    SQL> select group#,members,THREAD, STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE# from v$log;
    GROUP# MEMBERS,THREAD,STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE#
    1 1 1 CURRENT NO 52428800 29-FEB-12 1597643 57
    2 1 1 INACTIVE NO 52428800 29-FEB-12 1573462 56
    Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
    Wed Feb 29 19:46:38 2012
    Recovery of Online Redo Log: Thread 1 Group 1 Seq 56 Reading mem 0
    Mem# 0 errs 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_7LZYZK8S_.LOG
    Wed Feb 29 19:46:40 2012
    Completed redo application
    Wed Feb 29 19:46:40 2012
    Completed crash recovery at
    Thread 1: logseq 56, block 6568, scn 1597642
    270 data blocks read, 270 data blocks written, 1460 redo blocks read
    Wed Feb 29 19:46:43 2012
    Thread 1 advanced to log sequence 57
    Thread 1 opened at log sequence 57
    Current log# 2 seq# 57 mem# 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
    Successful open of redo thread 1
    Wed Feb 29 19:46:43 2012
    SMON: enabling cache recovery
    Wed Feb 29 19:46:55 2012
    Successfully onlined Undo Tablespace 1.
    Wed Feb 29 19:46:55 2012
    SMON: enabling tx recovery
    Wed Feb 29 19:46:56 2012
    Database Characterset is AL32UTF8
    replication_dependency_tracking turned off (no async multimaster replication found)
    Starting background process QMNC
    QMNC started with pid=19, OS id=3024
    Wed Feb 29 19:47:09 2012
    Completed: alter database open
    Wed Feb 29 19:47:14 2012
    db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Wed Feb 29 20:33:30 2012
    MMNL absent for 1537 secs; Foregrounds taking over
    Wed Feb 29 20:33:31 2012
    MMNL absent for 1540 secs; Foregrounds taking over
    Wed Feb 29 20:33:31 2012
    MMNL absent for 1540 secs; Foregrounds taking over
    MMNL absent for 1540 secs; Foregrounds taking over
    Wed Feb 29 20:33:32 2012
    MMNL absent for 1540 secs; Foregrounds taking over
    Wed Feb 29 20:33:33 2012
    MMNL absent for 1540 secs; Foregrounds taking over
    Wed Feb 29 21:45:24 2012
    MMNL absent for 4318 secs; Foregrounds taking over
    MMNL absent for 4318 secs; Foregrounds taking over
    MMNL absent for 4322 secs; Foregrounds taking over
    Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
    Wed Feb 29 22:30:01 2012
    ORACLE V10.2.0.1.0 - Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Windows XP Version V5.1 Service Pack 3, v.3244
    CPU : 2 - type 586, 2 Physical Cores
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:3097M/3546M, Ph+PgF:5143M/5429M, VA:1943M/2047M
    Wed Feb 29 22:30:01 2012
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 2
    Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =10
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
    sessions = 49
    __shared_pool_size = 201326592
    __large_pool_size = 8388608
    __java_pool_size = 4194304
    __streams_pool_size = 0
    spfile = C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA
    sga_target = 805306368
    control_files = C:\ORACLEXE\ORADATA\XE\CONTROL.DBF
    __db_cache_size = 587202560
    compatible = 10.2.0.1.0
    db_recovery_file_dest = C:\oraclexe\app\oracle\flash_recovery_area
    db_recovery_file_dest_size= 10737418240
    undo_management = AUTO
    undo_tablespace = UNDO
    remote_login_passwordfile= EXCLUSIVE
    dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
    shared_servers = 4
    local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=winsp3ue)(PORT=1522))
    job_queue_processes = 4
    audit_file_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP
    background_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\BDUMP
    user_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\UDUMP
    core_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\CDUMP
    db_name = XE
    open_cursors = 300
    os_authent_prefix =
    pga_aggregate_target = 268435456
    PMON started with pid=2, OS id=2176
    PSP0 started with pid=3, OS id=2204
    MMAN started with pid=4, OS id=2208
    DBW0 started with pid=5, OS id=2212
    LGWR started with pid=6, OS id=2220
    CKPT started with pid=7, OS id=2240
    SMON started with pid=8, OS id=2460
    RECO started with pid=9, OS id=2464
    CJQ0 started with pid=10, OS id=2480
    MMON started with pid=11, OS id=2484
    Wed Feb 29 22:30:02 2012
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    MMNL started with pid=12, OS id=2492
    Wed Feb 29 22:30:02 2012
    starting up 4 shared server(s) ...
    Oracle Data Guard is not available in this edition of Oracle.
    Wed Feb 29 22:30:02 2012
    alter database mount exclusive
    Wed Feb 29 22:30:06 2012
    Setting recovery target incarnation to 2
    Wed Feb 29 22:30:06 2012
    Successful mount of redo thread 1, with mount id 2657657770
    Wed Feb 29 22:30:06 2012
    Database mounted in Exclusive Mode
    Completed: alter database mount exclusive
    Wed Feb 29 22:30:07 2012
    alter database open
    Wed Feb 29 22:30:07 2012
    Beginning crash recovery of 1 threads
    Wed Feb 29 22:30:07 2012
    Started redo scan
    Wed Feb 29 22:30:15 2012
    Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
    ORA-00333: redo log read error block 10347 count 6144
    ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
    ORA-27070: async read/write failed
    OSD-04016: Error queuing an asynchronous I/O request.
    O/S-Error: (OS 23) Data error (cyclic redundancy check).
    Waiting for Help
    Regards

    Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
    ORA-00333: redo log read error block 10347 count 6144
    ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
    ORA-27070: async read/write failed
    OSD-04016: Error queuing an asynchronous I/O request.
    O/S-Error: (OS 23) Data error (cyclic redundancy check).Might your redo log file is corrupted or not exist, check physically. -> C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
    is it archivelog mode?
    perform fake recovery and open resetlogs.

  • Ora-00333 redo log read error block on 11g express

    Hi all
    I have error
    ora-00333 redo log read error block
    is there any solution for this?
    And I was type
    SQL> recovery database until cancel;
    but error still exist?
    any idea
    regards
    Gordan

    1. Check the OS for performance issues > CentOS 5.6 64 bytes (Space use 9Gbytes of 250gBytes) (Virtual Machine )
    decrease the size of the redo logs > ? How to do this? -- any reference
    set disk_async_io= false in the pfile > ? How to do this? -- any reference
    regards
    Gordan
    Edited by: useruseruser on Oct 25, 2011 9:24 PM
    Edited by: useruseruser on Oct 25, 2011 9:25 PM

  • ORA-00333: redo log read error block 69855 count 8192

    Hello Guys,
    where importing a dump to newly created database 10gR2 on Linux i got this error:
    ORA-00333: redo log read error block 69855 count 8192
    By searching this error, i found that I need to do recovery, but i don't have any backup of this database.
    Is there any easy solution for this error?
    Regards, Imran

    misterimran wrote:
    Hello Guys,
    where importing a dump to newly created database 10gR2 on Linux i got this error:
    ORA-00333: redo log read error block 69855 count 8192
    By searching this error, i found that I need to do recovery, but i don't have any backup of this database.
    Is there any easy solution for this error?no
    00333, 00000, "redo log read error block %s count %s"
    // *Cause:  An IO error occurred while reading the log described in the
    //          accompanying error.
    // *Action: Restore accessibility to file, or get another copy of the file.what additional clues exist with alert_SID.log file?
    do as below so we can know complete Oracle version & OS name.
    Post via COPY & PASTE complete results of
    SELECT * from v$version;

  • ORA-00333: redo log read error block 283081 count 8192

    I am starting the database..it mount but after that it gives me this error
    ORA-00333: redo log read error block 283081 count 8192
    Below are the contents of alert Log.._Please advice_
    Completed: ALTER DATABASE MOUNT
    Tue Jan 20 10:24:45 2009
    ALTER DATABASE OPEN
    Tue Jan 20 10:24:45 2009
    Beginning crash recovery of 1 threads
    parallel recovery started with 2 processes
    Tue Jan 20 10:24:45 2009
    Started redo scan
    Tue Jan 20 10:25:00 2009
    Errors in file /d01/oracle/PROD1/db/tech_st/10.2.0/admin/PROD1_prod1/udump/prod1_ora_32356.trc:
    ORA-00333: redo log read error block 283081 count 8192
    ORA-00312: online log 2 thread 1: '/d01/oracle/PROD1/db/apps_st/data/log02a.dbf'
    ORA-27072: File I/O error
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 4
    Additional information: 283081
    Additional information: 257536
    Tue Jan 20 10:25:16 2009
    Errors in file /d01/oracle/PROD1/db/tech_st/10.2.0/admin/PROD1_prod1/udump/prod1_ora_32356.trc:
    ORA-00333: redo log read error block 283081 count 8192
    ORA-00312: online log 2 thread 1: '/d01/oracle/PROD1/db/apps_st/data/log02a.dbf'
    ORA-27091: unable to queue I/O
    ORA-27072: File I/O error
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 4
    Additional information: 283081
    Additional information: 257536
    Tue Jan 20 10:25:31 2009

    I did what Prabhu told me..But i recovered using backup controlfile and when i was asked to apply logs..i applied my oldest logs and it worked
    Like i have two groups with two members each
    I applied log1a.dbf and it said media recovery completee
    I opened the database But then it started giving me errors for undo tablespace
    I made another undo tablespace..tried dropping the old one but it did not permitted as it had some segments with status "needs recovery"
    Than i added this parameter in pfile with the correupted segment and than tried to drop the segment but it still did not permit
    corruptedrollback_segments =(corrupted_undo segment_name)
    Next what i did was I mounted the database, ran another session of media recovery and opened the databse using resetlogs
    Than i dropped the old undo and it went through successfully..
    If you think anything i did wrong than please advice..
    I hope this action plans helps you in case you come across same errors some day
    I would be very thankful if you can refer me a document of recovery which covers all kinds of recoveries and scenarios and commands too
    Thanks alot

  • ORA-00333: redo log read error block 65538 count 8192

    Hi,
    I wanted to alter user hr's password, but I couldn't open the database first. What should I do? Here is my demo: Thank you for your response.
    C:\>sqlplus /nolog
    SQL*Plus: Release 9.2.0.1.0 - Production on Sun May 16 12:12:43 2004
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    SQL> connect sys/oracle as sysdba
    Connected.
    SQL> show user
    USER is "SYS"
    SQL> select * from v$controlfile;
    STATUS
    NAME
    C:\ORACLE\ORADATA\SARAH\CONTROL01.CTL
    C:\ORACLE\ORADATA\SARAH\CONTROL02.CTL
    C:\ORACLE\ORADATA\SARAH\CONTROL03.CTL
    SQL> select * from dba_users;
    select * from dba_users
    ERROR at line 1:
    ORA-01219: database not open: queries allowed on fixed tables/views only
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-00333: redo log read error block 65538 count 8192
    SQL> desc v$instance
    Name Null? Type
    INSTANCE_NUMBER NUMBER
    INSTANCE_NAME VARCHAR2(16)
    HOST_NAME VARCHAR2(64)
    VERSION VARCHAR2(17)
    STARTUP_TIME DATE
    STATUS VARCHAR2(12)
    PARALLEL VARCHAR2(3)
    THREAD# NUMBER
    ARCHIVER VARCHAR2(7)
    LOG_SWITCH_WAIT VARCHAR2(11)
    LOGINS VARCHAR2(10)
    SHUTDOWN_PENDING VARCHAR2(3)
    DATABASE_STATUS VARCHAR2(17)
    INSTANCE_ROLE VARCHAR2(18)
    ACTIVE_STATE VARCHAR2(9)
    SQL> select instance_name, status from v$instance;
    INSTANCE_NAME STATUS
    sarah MOUNTED
    SQL>
    *******************************

    I did what Prabhu told me..But i recovered using backup controlfile and when i was asked to apply logs..i applied my oldest logs and it worked
    Like i have two groups with two members each
    I applied log1a.dbf and it said media recovery completee
    I opened the database But then it started giving me errors for undo tablespace
    I made another undo tablespace..tried dropping the old one but it did not permitted as it had some segments with status "needs recovery"
    Than i added this parameter in pfile with the correupted segment and than tried to drop the segment but it still did not permit
    corruptedrollback_segments =(corrupted_undo segment_name)
    Next what i did was I mounted the database, ran another session of media recovery and opened the databse using resetlogs
    Than i dropped the old undo and it went through successfully..
    If you think anything i did wrong than please advice..
    I hope this action plans helps you in case you come across same errors some day
    I would be very thankful if you can refer me a document of recovery which covers all kinds of recoveries and scenarios and commands too
    Thanks alot

  • Reads on redo logs when on file system

    I was concentrated on redo tuning problems and am surprised by the fact that when I have the redo logs on file system (jfs2, aix 5.3, Oracle 10.1.0.4) I see in IOSTAT reads on the device. I have verified that there's no other process to touch these drives except LGWR.
    If I move the redo logs on raw devices I do not have these reads - they are zero.
    How can we explain this?
    There's no archiving or replication going on at all.
    Is there something I could do to prevent the reads on FS?
    I did not find anything on the web or in Metalink for this issue.
    Thanks a lot,mj

    Probably because using raw devices bypasses any operating system handling. Oracle accesses the files on raw devices directly, therefore iostat doesn't know about it. In fact I'd be surprised if iostat knows much of anything about raw devices at all. Try looking for info on using raw devices on AIX. It's more of an operating system issue than an Oracle issue. In a nutshell, if you're using cooked files, the operating system has to get involved in order for any application to access the files.

  • Behaviuor in reading logs from DB13 - redo log backup for DB

      Hi all,
    I have a question ,
    We have scheduled redo log backup using HP DP Tool.
    When I am reading a backup log from DB13 , I am facing the weird behavior.
    copy, delete, save
    0000
    aeomzyok.cds
    copy, delete, save
    0001
    aeomzyoh.cds
    Where ever the RC is 000 I am able to read the log files available at OS level . But not able to read the log for other RC.
    Please help me to understand this
    Thanks,
    Gnana

    Hi Gnana.
    Use the latest BR*Tools as there were problems with permission issues while creating logfiles. In the latest BR*Tools version, the different logfiles are created with predefined permission levels that suits to SAP needs.
    Also it worth to check if the BR*Tools executables hav the correct ownership.
    113747 Owners and authorizations for BR*Tools
    Regards,
    János

  • Lost seq of redo log due to corruption and cannot recover database.

    Hi!
    This db I am working on is a test database running 10.2.0.3 on OEL5. Unfortunately due to some human error, we lost the redo log sequence 1_28_xxxxxx.redo. As this was a non-critical db, we didn't plan any backups for the db... and now whenever I try to open the db I get the error:
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/opt/app/oracle/oradata/tadb1/system01.dbf'
    SQL> recover until cancel
    ORA-00279: change 510956 generated at 08/31/2010 22:00:17 needed for thread 1
    ORA-00289: suggestion :
    /opt/app/oracle/oradata/tadb1/archive/1_28_728336713.dbf
    ORA-00280: change 510956 for thread 1 is in sequence #28
    SQL> recover database until time '31-AUG-2010 22:00:00';
    ORA-00283: recovery session canceled due to errors
    ORA-00314: log 1 of thread 1, expected sequence# 28 doesn't match 0
    ORA-00312: online log 1 thread 1: '/opt/app/oracle/oradata/tadb1/redo01.log'
    Is there a way to open the database!?
    Thanks,
    AB007

    Sorry for the late response guys... had called it a night earlier... well, I tried your suggestion... but still, the database can't recover -
    SQL> recover database using backup controlfile until cancel;
    ORA-00279: change 510958 generated at 09/02/2010 23:56:37 needed for thread 1
    ORA-00289: suggestion : /opt/app/oracle/oradata/tadb1/archive/1_1_728697397.dbf
    ORA-00280: change 510958 for thread 1 is in sequence #1
    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: '/opt/app/oracle/oradata/tadb1/system01.dbf'
    ORA-01112: media recovery not started
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ALERT LOG
    ALTER DATABASE RECOVER database using backup controlfile until cancel
    Fri Sep 3 10:14:22 2010
    Media Recovery Start
    WARNING! Recovering data file 1 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 2 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 3 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    WARNING! Recovering data file 4 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    parallel recovery started with 2 processes
    ORA-279 signalled during: ALTER DATABASE RECOVER database using backup controlfile until cancel ...
    Fri Sep 3 10:14:25 2010
    ALTER DATABASE RECOVER CANCEL
    ORA-1547 signalled during: ALTER DATABASE RECOVER CANCEL ...
    Fri Sep 3 10:14:26 2010
    ALTER DATABASE RECOVER CANCEL
    ORA-1112 signalled during: ALTER DATABASE RECOVER CANCEL ...
    Fri Sep 3 10:14:43 2010
    alter database open resetlogs
    Fri Sep 3 10:14:43 2010
    RESETLOGS is being done without consistancy checks. This may result
    in a corrupted database. The database should be recreated.
    RESETLOGS after incomplete recovery UNTIL CHANGE 510958
    Resetting resetlogs activation ID 2129258410 (0x7ee9e7aa)
    Online log /opt/app/oracle/oradata/tadb1/redo02.log: Thread 1 Group 2 was previously cleared
    Online log /opt/app/oracle/oradata/tadb1/redo03.log: Thread 1 Group 3 was previously cleared
    Fri Sep 3 10:14:45 2010
    Setting recovery target incarnation to 3
    Fri Sep 3 10:14:45 2010
    Assigning activation ID 2129271722 (0x7eea1baa)
    Thread 1 opened at log sequence 1
    Current log# 1 seq# 1 mem# 0: /opt/app/oracle/oradata/tadb1/redo01.log
    Successful open of redo thread 1
    Fri Sep 3 10:14:45 2010
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Fri Sep 3 10:14:45 2010
    SMON: enabling cache recovery
    Fri Sep 3 10:14:45 2010
    Errors in file /opt/app/oracle/admin/tadb1/udump/tadb1_ora_5949.trc:
    ORA-00600: internal error code, arguments: [4000], [6], [], [], [], [], [], []
    Fri Sep 3 10:14:45 2010
    Errors in file /opt/app/oracle/admin/tadb1/udump/tadb1_ora_5949.trc:
    ORA-00704: bootstrap process failure
    ORA-00704: bootstrap process failure
    ORA-00600: internal error code, arguments: [4000], [6], [], [], [], [], [], []
    Fri Sep 3 10:14:45 2010
    Error 704 happened during db open, shutting down database
    USER: terminating instance due to error 704
    Instance terminated by USER, pid = 5949
    ORA-1092 signalled during: alter database open resetlogs...

  • Why not use Redo log for consistent read

    Oracle 11.1.0.7:
    This might be a stupid question.
    As I understand if a select was issued at 7:00 AM and the data that select is going to read has changed at 7:10 AM even then Oracle will return the data that existed at 7:00 AM. And for this Oracle needs the data in Undo segments.
    My question is since redo also has past and current information why can't redo logs be used to retreive that information? Why is undo required when redo already has all that information.

    user628400 wrote:
    Thanks. I get that piece but isn't it the same problem with UNDO? It's written as it expires and there is no guranteee until we specifically ask oracle to gurantee the UNDO retention? I guess I am trying to understand that UNDO was created for effeciency purposes so that there is less performance overhead as compared to reading and writing from redo.And this also you said,
    >
    If data was changed to 100 to 200 wouldn't both the values be there in redo logs. As I understand:
    1. Insert row with value 100 at 7:00 AM and commit. 100 will be writen to redo log
    2. update row to 200 at 8:00 AM and commit. 200 will be written to redo log
    So in essence 100 and 200 both are there in the redo logs and if select was issued at 7:00 data can be read from redo log too. Please correct me if I am understanding it incorrectly.I guess you didnt understand the explaination that I did. Its not the old data that is kept. Its the changed vector of Undo that is kept which is useful to "recover" it when its gone but not useful as such for a select statement. Whereas in an Undo block, the actual value is kept. You must remember that its still a block only which can contain data just like your normal block which may contain a table like EMP. So its not 100,200 but the change vectors of these things which is useful to recover the transaction based on their SCN numbers and would be read in that order as well. And to read the data from Undo, its quite simple for oracle to do so using an Undo block as the transaction table which holds the entry for the transaction, knows where the old data is kept in the Undo Segment. You may have seen XIDSEQ, XIDUSN, XIDSLOT in the tranaction id which are nothing but the information that where the undo data is kept. And to read it, unlke redo, undo plays a good role.
    About the expiry of Undo, you must know that only INACTIVE Undo extents are marked for expiry. The Active Extents which are having an ongoing tranaction records, are never marked for it. You can come back after a lifetime and if undo is there, your old data would be kept safe by oracle since its useful for the multiversioning. Undo Retention is to keep the old data after commit, something which you need not to do if you are on 11g and using Total Recall feature!
    HTH
    Aman....

  • GoldenGate Extract Process will not read from redo log with manual help

    Here is my issue.
    I have GoldenGate replication successfully setup one-way from 1 Source to Many Targets. There is 1 source extract on the DB and many pumps that push the trail file data to the Targets. Replication does work but after manual help with starting up the Source Extract process.
    If I execute the command:
    GGSCI> alter extract <source extract name> begin now
    GGSCI> view report <source extract name>
    The extract starts and reads the source trail file but will not process data, I continually see in the ggserr.log file "OGG-01515: Positioning to begin time MMM DD, YYYY, HH:MM:SS" The date and time are irrevelant for this problem.
    When I see this, I SQ*Plus into the database and look in the v$log table for the current log and sequence #.
    I return to GGSCI and issue the following command:
    GGSCI> alter extract <source extract name> thread 1 extseqno <sequence # from v$log query>
    GGSCI> start <source extract name>
    It then works as expected. Why is this so? I thought the alter extract <source extract name> begin now would do the same output.
    We do use ASM but like I said when I issue the:
    GGSCI> alter extract <source extract name> thread 1 extseqno <sequence # from v$log query>
    It works like it should.
    Very weird.
    - Jason

    Yes, supplemental logging is enabled on both the source and the targets, but why would supplemental logging on the targets have any affect on why the Source Extract on the source can't read from the source redo log?
    This is not a RAC database, rather single-instance with one thread. Also, we are using DBLOGREADER functionality as it is an 11.2.0.3 database.
    My issue is simply, when I start the source extract from being down, meaning it isn't running, I issue this command:
    alter <source extract> begin now
    start <source extract>
    view report <source extract>
    OGG-01515 Positioning to begin time <today's date and time> ie Mar 4, 2013, 3:26:39 PM. (this is repeated over and over and over)
    If I perform a
    info <source extract> detail---> I see the following:
    Log Read Checkpoint Oracle Redo Logs 2013-03-04 15:26:39 Thread 1, Seqno 0, RBA 0 (why is it showing 0, becuase it can't read the redo, WHY NOT?)
    Extract Source BEGIN END
    Not Available <today's date> <today's date> (repeat....)
    However, if I retreive the Redo Log number and I issue:
    alter spe thread 1 extseqno (redo log sequence #)
    start spe.
    Then it works okay. I have to manually tell it what redo log to begin reading from. Why?
    - Jason
    Edited by: 924317 on Mar 4, 2013 9:03 AM

  • Reading Orcle current online redo logs

    Hi,
    We are able to read the SQL Server Transactional Log. We are trying to do that in case Oracle. Can anyone put some light on this?
    Is there any third party tools doing this? Is this a feasible idea or not.
    Regards,
    Kalyan

    You can use Logminer to look into the archived redo logs.
    Why do you want to look at this though?

Maybe you are looking for