Does Redo Log include CLOB Columns Blocks?

Hi All,
Please help me in understanding how oracle handle redo logs on ENABLE IN ROW STORAGE CLOB's. How redo log behave on table with DISABLE IN ROW STORAGE ?
for following table if I update column other than D_CLOB does Redo log stores the D_CLOB column blocks as well. Is there any way to find if D_CLOB column blocks are included/excluded from redo log.
create table T
D_INT INTEGER,
D_CHAR CHAR(30),
D_DATE DATE,
D_CLOB CLOB
I performed following test but give no indication whether blocks of D_Clob Columns is inculded or not ..
SQL> update t
2 set d_char='Testing'
3 where rownum<500;
499 rows updated
SQL> commit;
Commit complete
SQL> select A.name,(b.value)/(1024*1024) MB
2 from v$statname a, v$mystat b
3 where a.statistic#=b.statistic#
4 and a.name='redo size'
5 /
NAME MB
redo size 5.59245300

I found this information for the Oracle Guru "Burleson", maybe that helps : http://www.dba-oracle.com/t_logging_clob_blob_lob.htm

Similar Messages

  • What does redo log buffer holds, changed value or data block?

    Hello Everyone,
    i am new to database side and have one query as i know redo log buffer contain change information , my doubt is does it store the value only or the changed data block? because if we can see data buffer cache size is more as it holds data block and redo log buffer size is less .

    The Redo Log buffer contains OpCodes that represent the SQL commands, the "address" (file,block,row) where the change is to be made and the nature of the change.
    It does NOT contain the data block.
    (the one exception is when you run a User Managed Backup with ALTER DATABASE BEGIN BACKUP or ALTER TABLESPACE BEGIN BACKUP : The first time a block is modified when in BEGIN BACKUP mode, the whole block is written to the redo stream).
    The log buffer can be and is deliberately smaller than the blocks buffer cache. Entries in the redo log buffer are quickly written to disk (at commits, when it is 1/3rd or 1MB full, every 3seconds, before DBWR writes a modified data block).
    Hemant K Chitale

  • When changing redo-logs on Primary, do I need to change my standby also?

    Hi, I need to resize my redo logs on a primary db which has a physical standby attached. Do I need to modify this standby or will the change propagate. It seems unlikely to me.
    thanx

    Only clue that I have found is at
    http://download-east.oracle.com/docs/cd/B12037_01/server.101/b10726/configbp.htm
    Section "Use Multiplexed Standby Redo Logs and Configure Size Appropriately"
    >>
    The remote file server (RFS) process for the standby database writes only to an SRL whose size is identical to the size of an online redo log for the production database. If it cannot find an appropriately sized SRL, then RFS creates an archived redo log file directly instead and logs the following message in the alert log:
    No standby redo log files of size <#> blocks available.
    >>

  • 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-00368 checksum error in redo log block

    We are running small database in oracle 9i in non archive mode .Database is not opening up with following error ora-00368 checksum error in redo log block.
    How to do the incomplete database recovery and open the database.
    Regards
    Arun

    For more details
    Here is what I am Doing.
    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: 'M:\ORACLE\ORADATA\mail\SYSTEM01.DBF'
    SQL> alter database recover datafile
    'M:\ORACLE\ORADATA\mail\SYSTEM01.DBF';
    alter database recover datafile 'M:\ORACLE\ORADATA\mail\SYSTEM01.DBF'
    ERROR at line 1:
    ORA-00283: recovery session canceled due to errors
    ORA-00368: checksum error in redo log block
    ORA-00353: log corruption near block 103414 change 5082448355423 time
    04/22/2003 04:30:11
    ORA-00312: online log 3 thread 1: 'M:\ORACLE\ORADATA\mail\REDO03.LOG'
    What can be done to start the database??
    Regards
    Arun

  • Standby redo log does not exist...

    Hello,
    Oracle 11.2.0.2, running on Solaris
    This is kind of a continuation of a previous thread, but this is a different question:
    I have a DG configuration, with the primary database having 2 redo logs per redo log group.
    And, it has 2 redo logs for the standby redo log groups.
    But I just found out something very strange:
    For the standby redo log group, even though the database shows it has two redo log files per group, the second file does not actually exist on the file system.
    And, I have no idea where it is, or why the database is not complaining about it.
    See below:
    SQL> select * from v$logfile;
             GROUP# STATUS    TYPE    MEMBER                                        IS_
                 11           STANDBY /opt/oracle/oradata2/PROD/REDO01A_STDBY.log NO
                 11           STANDBY /opt/oracle/oradata3/PROD/REDO01B_STDBY.log NO    <== does not exist on file system
                 12           STANDBY /opt/oracle/oradata2/PROD/REDO02A_STDBY.log NO
                 12           STANDBY /opt/oracle/oradata3/PROD/REDO02B_STDBY.log NO    <== does not exist on file system
                 13           STANDBY /opt/oracle/oradata2/PROD/REDO03A_STDBY.log NO
                 13           STANDBY /opt/oracle/oradata3/PROD/REDO03B_STDBY.log NO    <== does not exist on file system
                 14           STANDBY /opt/oracle/oradata2/PROD/REDO04A_STDBY.log NO
                 14           STANDBY /opt/oracle/oradata3/PROD/REDO04B_STDBY.log NO    <== does not exist on file system
                 15           STANDBY /opt/oracle/oradata2/PROD/REDO05A_STDBY.log NO
                 15           STANDBY /opt/oracle/oradata3/PROD/REDO05B_STDBY.log NO    <== does not exist on file system
                  5           ONLINE  /opt/oracle/oradata1/PROD/REDO05A.log       NO
                  5           ONLINE  /opt/oracle/oradata2/PROD/REDO05B.log       NO
                  6           ONLINE  /opt/oracle/oradata1/PROD/REDO06A.log       NO
                  6           ONLINE  /opt/oracle/oradata2/PROD/REDO06B.log       NO
                  7           ONLINE  /opt/oracle/oradata1/PROD/REDO07A.log       NO
                  7           ONLINE  /opt/oracle/oradata2/PROD/REDO07B.log       NO
                  8           ONLINE  /opt/oracle/oradata1/PROD/REDO08A.log       NO
                  8           ONLINE  /opt/oracle/oradata2/PROD/REDO08B.log       NO
    18 rows selected.
    Notice below that the "B" redo logs do not exist.
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO01B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO01B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO02B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO02B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO03B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO03B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO04B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO04B_STDBY.log: No such file or directory
    SQL> !ls -l /opt/oracle/oradata3/PROD/REDO05B_STDBY.log
    /opt/oracle/oradata3/PROD/REDO05B_STDBY.log: No such file or directory
    But here, you can see that the "A" redo logs actually do exist.
    SQL> !ls -l /opt/oracle/oradata2/PROD/REDO01A_STDBY.log
    -rw-r-----   1 oracle   dba      536871424 Jan  7  2011 /opt/oracle/oradata2/PROD/REDO01A_STDBY.log

    Hello;
    I'm able to recreate
    SQL> select * from v$logfile;
        GROUP# STATUS  TYPE    MEMBER                                             IS_
             3         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_3_8gtxxrl6_.log
             2         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_2_8gtxxr4f_.log
             1         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_1_8gtxxqng_.log
             4         STANDBY /u01/app/oracle/oradata/RECOVER2/redo04.log        NO
             5         STANDBY /u01/app/oracle/oradata/RECOVER2/redo05.log        NO
             6         STANDBY /u01/app/oracle/oradata/RECOVER2/redo06.log        NOAnd then
    SQL> !ls -al /u01/app/oracle/oradata/RECOVER2/redo04.log
    ls: /u01/app/oracle/oradata/RECOVER2/redo04.log: No such file or directoryChecking... *Not there, but Oracle ( 11.2.0.3 ) allows clean up without barking. Had only one member so I did GROUP drop.
    SQL> ALTER DATABASE DROP LOGFILE GROUP 4;
    Database altered.
    SQL> select * from v$logfile;
        GROUP# STATUS  TYPE    MEMBER                                             IS_
             3         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_3_8gtxxrl6_.log
             2         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_2_8gtxxr4f_.log
             1         ONLINE  /u01/app/oracle/flash_recovery_area/RECOVER2/onlin YES
                               elog/o1_mf_1_8gtxxqng_.log
             5         STANDBY /u01/app/oracle/oradata/RECOVER2/redo05.log        NO
             6         STANDBY /u01/app/oracle/oradata/RECOVER2/redo06.log        NO
    SQL> Best Regards
    mseberg

  • ORA-00354: corrupt redo log block header

    Hi Guys,
    Need your support to resolve one of the oracle issues,
    Below are errors visible in alert.log in oracle,
    ORA-16038: log 24 sequence# 660467 cannot be archived
    ORA-00354: corrupt redo log block header
    ORA-00312: online log 24 thread 1: '/oracle/PRD/origlogB/log_g24_m1.dbf'...
    2010-10-03 07:26:12.835 20195 kcrr.c
    ORA-16014: log 24 sequence# 660467 not archived, no available
    destinations
    Below is o/p of archive log list seems to be bit strange,
    SQL> archive log list
    Database log mode              Archive Mode
    Automatic archival             Enabled
    Archive destination            /oracle/PRD/saparch/PRDarch
    Oldest online log sequence     660467
    Next log sequence to archive   660467
    Current log sequence           660576
    And some more info,
    SQL> SELECT GROUP#, STATUS, MEMBER FROM V$LOGFILE;
        GROUP# STATUS  MEMBER
            28         /oracle/PRD/origlogB/log_g28_m1.dbf
            28         /oracle/PRD/mirrlogB/log_g28_m2.dbf
            27         /oracle/PRD/origlogA/log_g27_m1.dbf
            27         /oracle/PRD/mirrlogA/log_g27_m2.dbf
            26         /oracle/PRD/origlogB/log_g26_m1.dbf
            26         /oracle/PRD/mirrlogB/log_g26_m2.dbf
            25         /oracle/PRD/origlogA/log_g25_m1.dbf
            25         /oracle/PRD/mirrlogA/log_g25_m2.dbf
            24         /oracle/PRD/origlogB/log_g24_m1.dbf
            24         /oracle/PRD/mirrlogB/log_g24_m2.dbf
            23         /oracle/PRD/origlogA/log_g23_m1.dbf
            23         /oracle/PRD/mirrlogA/log_g23_m2.dbf
            22         /oracle/PRD/origlogB/log_g22_m1.dbf
            22         /oracle/PRD/mirrlogB/log_g22_m2.dbf
            21         /oracle/PRD/origlogA/log_g21_m1.dbf
            21         /oracle/PRD/mirrlogA/log_g21_m2.dbf
    16 rows selected.
    SQL> SELECT GROUP#, SEQUENCE#, MEMBERS, ARCHIVED, STATUS, FIRST_CHANGE# FROM V$LOG;
        GROUP#  SEQUENCE#    MEMBERS ARC STATUS           FIRST_CHANGE#
            21     660571          2 NO  INACTIVE            2.9116E+10
            22     660572          2 NO  INACTIVE            2.9116E+10
            23     660570          2 NO  INACTIVE            2.9116E+10
            24     660467          2 NO  INACTIVE            2.9114E+10
            25     660573          2 NO  ACTIVE              2.9116E+10
            26     660574          2 NO  CURRENT             2.9116E+10
            27     660568          2 NO  INACTIVE            2.9116E+10
            28     660569          2 NO  INACTIVE            2.9116E+10
    8 rows selected.
    All file exists but still facing issue, no backup is running
    Regards,
    Yash

    Hi,
    Instead of the logfile name, try the command with the logfile integer as mentioned below.
    alter database clear unarchived logfile group <integer>;
    You can get the logfile integer using the view, v$log.
    select GROUP#,MEMBERS,STATUS from v$log;
    The value for the parameter GROUP# is the logfile integer.
    Hope this helps.
    Regards,
    Varadharajan M

  • 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

  • [DG Physical] ORA-00368: checksum error in redo log block

    Hi all,
    I'm building a DR solution with 1 primary & 2 DR site (Physical).
    All DBs use Oracle 10.2.0.3.0 on Solaris 64bit.
    The first one ran fine for some days (6), then I installed the 2nd. After restoring the DB (DUPLICATE TARGET DATABASE FOR STANDBY) & ready to apply redo. The DB fetched missing arc gaps & I got the following error:
    ==================
    Media Recovery Log /global/u04/recovery/billhcm/archive/2_32544_653998293.dbf
    Errors with log /global/u04/recovery/billhcm/archive/2_32544_653998293.dbf
    MRP0: Detected read corruption! Retry recovery once log is re-fetched...
    Wed Jan 27 21:46:25 2010
    Errors in file /u01/oracle/admin/billhcm/bdump/billhcm1_mrp0_12606.trc:
    ORA-00368: checksum error in redo log block
    ORA-00353: log corruption near block 1175553 change 8236247256146 time 01/27/2010 18:33:51
    ORA-00334: archived log: '/global/u04/recovery/billhcm/archive/1_47258_653998293.dbf'
    Managed Standby Recovery not using Real Time Apply
    Recovery interrupted!
    Recovered data files to a consistent state at change 8236247255373
    ===================
    I see that may be RFS get the file incorrectly so I ftp to get this file & continue the apply, it pass. Comparison the RFS file & ftp is difference. At that time, I think that something wrong with the RFS because the content of arc is not right. (I used BACKUP VALIDATE ARCHIVELOG SEQUENCE BETWEEN N1 AND N2 THREAD X to check all arcs the RFS fetched, there was corrupt in every file);
    I restore the DR DB again & apply incremental backup from the primary, now it run well. I don't know what's happening as I did the same procedures for all DR DB.
    Yesterday night, I have to stop & restart DR site 1. Today, I check and it got the same error as the 2nd site, with corrupted redo. I try to delete the arcs, & let RFS to reget it, but the files were corrupt too.
    If this continue to happen with the 2nd site again, that'll be a big problem.
    The DR site 1 & Primary is linked by a GB switch, site 2 by a 155Mbps connection (far enough for my db load at about 1.5MB/s avg apply rate).
    I seach Oracle support (metalink) but no luck, there is a case but it mentions max_connection>1 (mine is default =1)
    Can someone show me how to troubleshooting/debug/trace this problem.
    That would be a great help!
    Thank you very much.

    This (Replication) is the wrong forum for your posting.
    Please post to the "Database - General" forum at
    General Database Discussions
    But, first, log an SR with Oracle Support.
    Hemant K Chitale

  • Logmnr/capure error b'coz of corruption of redo log block

    Hi,
    We all know that capture process reads the REDO entries from redo log files or archived log files. Therefore we need to ahev db in ARCHIVELOG mode.
    In alert log file, I found error saying :
    Creating archive destination LOG_ARCHIVE_DEST_1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION01\1_36.ARC'
    ARC0: Log corruption near block 66922 change 0 time ?
    ARC0: All Archive destinations made inactive due to error 354
    Fri Apr 04 12:57:44 2003
    Errors in file e:\oracle\admin\repf\bdump\trishul_arc0_1724.trc:
    ORA-00354: corrupt redo log block header
    ORA-00353: log corruption near block 66922 change 0 time 04/04/2003 11:05:40
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    As a normal practice, we do have multiplexing of redo log files at diff location, but even that second copy of redo log is of no use to recover the redo log. This explains redo log could not be archived, since it can't be read. Same is true even for Logmnr process, it could not read the redo log file and it failed. Now, we have wae to recover from this situation (as far as DB is concern, not Stream Replication), since the shutdown after this error was IMMEDIATE causing checkpoing, and rollback/rollforward is not required during system startup. (No instance recovery) We can make db NOARCHIVELOG mode, drop that particular group, and create new one, and turn db to ARCHIVELOG mode This will certainly serve the purpose as far as consistency of DB is concern.
    Here is a catch for Stream Replication. The redo log that got corrupted must be having few transaction which are not being archived, and each will be having corresponding SCN. Now, Capture Process read the info sequentially in order of SCN. Few transaction are now missed, and Capture process can't jump to next SCN skipping few SCN in between. So, we have to re-instantiate the objects on the another system which has no erros, and start working on it. My botheration is what will happen to those missed transaction on the another database. It's absolete loss of the data. In development I can manage that. But in real time Production stage, this is a critical situation. How to recover from this situation to get back the corrupted info from redo log ?
    I have not dropped any of the log group yet. B'coz I would like to recover from this situation without LOSS of data.
    Thanx, & regards,
    Kamlesh Chaudhary
    Content of trace files :
    Dump file e:\oracle\admin\repf\bdump\trishul_arc0_1724.trc
    Fri Apr 04 12:57:31 2003
    ORACLE V9.2.0.2.1 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.2.0 - Production
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Instance name: trishul
    Redo thread mounted by this instance: 1
    Oracle process number: 16
    Windows thread id: 1724, image: ORACLE.EXE
    *** SESSION ID:(13.1) 2003-04-04 12:57:31.000
    - Created archivelog as 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION02\1_36.ARC'
    - Created archivelog as 'E:\ORACLE\ORADATA\REPF\ARCHIVE\LOCATION01\1_36.ARC'
    *** 2003-04-04 12:57:44.000
    ARC0: All Archive destinations made inactive due to error 354
    *** 2003-04-04 12:57:44.000
    kcrrfail: dest:2 err:354 force:0
    *** 2003-04-04 12:57:44.000
    kcrrfail: dest:1 err:354 force:0
    ORA-00354: corrupt redo log block header
    ORA-00353: log corruption near block 66922 change 0 time 04/04/2003 11:05:40
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    *** 2003-04-04 12:57:44.000
    ARC0: Archiving not possible: error count exceeded
    ORA-16038: log 2 sequence# 36 cannot be archived
    ORA-00354: corrupt redo log block header
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG'
    ORA-16014: log 2 sequence# 36 not archived, no available destinations
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\REDO02.LOG'
    ORA-00312: online log 2 thread 1: 'E:\ORACLE\ORADATA\REPF\ARCHIVE\REDO02.LOG
    Dump file e:\oracle\admin\repf\udump\trishul_cp01_2048.trc
    Fri Apr 04 12:57:27 2003
    ORACLE V9.2.0.2.1 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Oracle9i Enterprise Edition Release 9.2.0.2.1 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.2.0 - Production
    Windows 2000 Version 5.0 Service Pack 2, CPU type 586
    Instance name: trishul
    Redo thread mounted by this instance: 1
    Oracle process number: 30
    Windows thread id: 2048, image: ORACLE.EXE (CP01)
    *** 2003-04-04 12:57:28.000
    *** SESSION ID:(27.42) 2003-04-04 12:57:27.000
    TLCR process death detected. Shutting down TLCR
    error 1280 in STREAMS process
    ORA-01280: Fatal LogMiner Error.
    OPIRIP: Uncaught error 447. Error stack:
    ORA-00447: fatal error in background process
    ORA-01280: Fatal LogMiner Error
    **********************

    I have the similar problem - I am using Steams environment, and have got this
    "ORA-00353: log corruption near block" errors in the alert.log file
    during capture the changes on the primary database, and Capture
    process became aborted after that.
    Was that transactions lost, or after i've started the Capture process
    again the were captured and send to the target database?
    Have anyone solved that problem?
    Can you help me with it?

  • Asynch Hot Log mode does not use hot (online) redo logs

    Version 10.2
    We have just set up a test of the Asynch Hot Log replication according to Chap 16 of the Data Warehousing guide.
    We can see data put into the change table. However, it seems that data gets written to the change table ONLY after a log switch. This would suggest that the capture process is not reading the online logs, but is only reading the archived logs.
    I don't think this can be correct behavior because the docs indicate that Oracle "seamlessly switches" between the online and the archived redo logs.
    Is there a flag or something to set to cause the online logs to be available to the capture process? Or is this a bug? Has anyone else observed this behavior?
    Thanks for any insight.
    -- Chris Curzon

    According to the 10g Dataguard docs, section 2.5.1:
    "Physical standby databases do not use an online redo log, because physical standby databases are not opened for read/write I/O."yes, those are used when database is open.
    You should not perform any changes in Standby. Even if those exist online redo log files, whats the difficulty you have seen?
    These will be used whenever you performed switchover/failover. So nothing to worry on this.
    Is this a case of the STANDBY needing at least a notion of where the REDO logs will need to be should a failover occur, and if the files are already there, the standby database CONTROLFILE will hold onto them, as they are not doing any harm anyway?Then oracle functionality itself harm if you think in that way. When they not used in open then what the harm with that?
    Standby_File_management --> for example if you add any datafile, those information will be in archives/redos once they applied on standby those will be added automatically when it is set to AUTO if its manual, then it creates a unnamed file in $ORACLE_HOME/dbs location later you have to rename that file and recovery need to perform .
    check this http://docs.oracle.com/cd/B14117_01/server.101/b10755/initparams206.htm
    HTH.

  • To where does the LGWR write information in redo log buffer ?

    Suppose my online redo logfiles are based on filesystems .I want to know to where the LGWR writes information in redo log buffer ? Just write to filesystem buffer or directly write to disk ? And the same case is associated with the DBWR and the datafiles are based on filesystems too ?

    It depends on the filesytem. Normally there is also a filesystem buffer too, which is where LGWR would write.Yes but a redo log write must always be a physical write.
    From http://asktom.oracle.com/pls/ask/f?p=4950:8:15501909858937747903::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:618260965466
    Tom, I was thinking of a scenario that sometimes scares me...
    **From a database perspective** -- theoretically -- when data is commited it
    inevitably goes to the redo log files on disk.
    However, there are other layers between the database and the hardware. I mean,
    the commited data doesn't go "directly" to disk, because you have "intermediate"
    structures like i/o buffers, filesystem buffers, etc.
    1) What if you have commited and the redo data has not yet "made it" to the redo
    log. In the middle of the way -- while this data is still in the OS cache -- the
    OS crashes. So, I think, Oracle is believing the commited data got to the redo
    logs -- but is hasn't in fact **from an OS perspective**. It just "disapeared"
    while in the OS cache. So redo would be unsusable. Is it a possible scenario ?
    the data does go to disk. We (on all os's) use forced IO to ensure this. We
    open files for example with O_SYNC -- the os does not return "completed io"
    until the data is on disk.
    It may not bypass the intermediate caches and such -- but -- it will get written
    to disk when we ask it to.
    1) that'll not happen. from an os perspective, it did get to disk
    Message was edited by:
    Pierre Forstmann

Maybe you are looking for

  • Re: Windows 8 constant BSOD

    Hello friends. I am having a major problem with my bootcamp partition. I just installed windows 8 as an upgrade from windows 7 after a successful installation. However, when i booted up the partition it gives me the BSOD error almost every time i boo

  • Netflix damage iPad screen?

    Hi, I've heard and read that diaplaying static images could cause damage a screen, and that's my concern Hi, Recently got an iPad 2 mainly to watch netflix and also bought an Apple Digital AV adapter today so I can watch it on my TV. The thing is tha

  • Is it possible to inspect lot if inspection lot is rejected at quality end?

    If inspection lot is rejected by quality team can RR /UD be done again for same lot if there are no long term MIC's. If yes How and if NO where does the material goes? Edited by: Trident India on Dec 4, 2010 8:11 AM

  • Self Password management in SAP 4.7

    Hi Techies, Is there any way to enable self password management in SAP 4.7 (ABAP)? My requirement is user have to Unlock/Reset his own SAP ID and get confirmation to his own mail address mapped in SAP. This is just to avoid the routine activity of He

  • Itunes says i dont have enough space to sync my iphone but i do

    When I try to sync my Iphone to Itunes it states more space is required but I have 3 times the space it is saying is needed. Please help.