Logging to redo

Oracle 11.0.1.7:
This is a stupid question. If we don't care about recovering the database and are only testing for functionality purposes then is there a way to not log anything in redo log. Reason is that we are seeing very slow write to redo because of resource issue and are limited with the resource issue. So I was wondering if there is a way to eliminate logging to redo logs. Are redo logs required if DBWR process is refreshing from buffer cache anyways? I do understand that we can't expect any recovery of data, but that is fine. Can someone please give more insights?
I also understand altering tablespace to NOLOGGING doesn't reduce redo generation for normal DML operations.

Here is what I am seeing:
                                                             Avg
                                        %Time Total Wait    wait    Waits   % DB
Event                             Waits -outs   Time (s)    (ms)     /txn   time
log file sync                   104,448     0        745       7      1.0   54.2
                                                             Avg
                                        %Time Total Wait    wait    Waits   % bg
Event                             Waits -outs   Time (s)    (ms)     /txn   time
log file parallel write          86,978     0        137       2      0.8   71.8
control file parallel writ        1,745     0          7       4      0.0    3.6
                           Total
Event                      Waits  <1ms  <2ms  <4ms  <8ms <16ms <32ms  <=1s   >1s
LGWR wait for redo copy     422   99.5          .2                      .2
SQL*Net message to client  1936K 100.0
SQL*Net more data from cli   57K  97.4   1.1    .8    .6    .1    .0    .0    .0

Similar Messages

  • The file structure online redo log, archived redo log and standby redo log

    I have read some Oracle documentation for file structure and settings in Data Guard environment. But I still have some doubts. What is the best file structure or settings in Oracle 10.2.0.4 on UNIX for a data guard environment with 4 primary databases and 4 physical standby databases. Based on Oracle documents, there are 3 redo logs. They are: online redo logs, archived redo logs and standby redo logs. The basic settings are:
    1. Online redo logs --- This redo log must be on Primary database and logical standby database. But it is not necessary to be on physical standby database because physical standby is not open. It doesn't generate redo log. However, if don't set up online redo log on physical standby, when primary failover and switch standby as primary. How can standby perform without online redo logs? In my standby databases, online redo logs have been set up.
    2. Archived redo logs --- It is obviously that primary database, logical and physical standby database all need to have this log file being set up. Primary use it to archive log files and ship to standby. Standby use it to receive data from archived log and apply to database.
    3. Standby redo logs --- In the document, it says A standby redo log is similar to an online redo log, except that a standby redo log is used to store redo data received from another database. A standby redo log is required if you want to implement: The maximum protection and maximum availability levels of data protection and Real-time apply as well as Cascaded destinations. So it seems that this standby redo log only should be set up on standby database, not on primary database. Am my understanding correct? Because I review current redo log settings on my environment, I have found that Standby redo log directory and files have been set up on both primary and standby databases. I would like to get more information and education from experts. What is the best setting or structure on primary and standby database?

    FZheng:
    Thanks for your input. It is clear that we need 3 type of redo logs on both databases. You answer my question.
    But I have another one. In oracle ducument, it says If you have configured a standby redo log on one or more standby databases in the configuration, ensure the size of the current standby redo log file on each standby database exactly matches the size of the current online redo log file on the primary database. It says: At log switch time, if there are no available standby redo log files that match the size of the new current online redo log file on the primary database. The primary database will shut down
    My current one data gurard envirnment setting is: On primary DB, online redo log group size is 512M and standby redo log group size is 500M. On the standby DB, online redo log group size is 500M and standby redo log group size is 750M.
    This was setup by someone I don't know. Is this setting OK? or I should change Standby Redo Log on standby DB to 512M to exactly meatch with redo log size on primary?
    Edited by: 853153 on Jun 22, 2011 9:42 AM

  • Corruption of archived logs after redo resizing - URGENT

    Hello all,
    We have a RAC 9i 2-node DB, running on RHEL 3 machines.
    We resized our redo logs from 100M to 1G to avoid "Can not allocate log, archival required" messages.
    The operation was successful, but now we are facing problems with the ext3 filesystem holding the archived logs.
    Each node has its own arc location, mounted only once.
    When we run "ls" in the arc destination, we get "ls: Input/output error" messages.
    RMAN complains also about corrupted arcvhived logs.
    The day before Yesterday we reformatted one arc destination, and today the messages appeared in the other one.
    Do you have any suggestion?
    Jonathan

    Did the problem occur right after increasing the log size? Then the first thing to do would be to decrease the log size, but add more log groups to fix the "Can not allocate..." problem.
    If "ls" doesn't work, your file system is stuffed.Reformat the archive dest and do simple file copies to verify the integrity, before putting the archive logs back on.
    That's just for starters...

  • Supplemental Logging in Redo Log

    I enabled the Supplemental Logging both in database level and table level.
    Then i execute some sql statements.
    But after i dump the redo file using "alter system dump logfile", i can't see the effect from the trace file.
    In my expectation, i think the primary key value should in the OP:5.1 change.
    Does the supplemental logging can't effect if row chaining or row migration occurred? i mean OP:11.6
    Does it must be in the undo segment of update change OP:11.5?
    Black Thought

    please provide your Oracle version and how you enable supplemental logging. this presentation may >assist youThank you TongucY for response, I had already see the julian's presentation, and i know the internals.
    As you will see from Julian Dyke's presentation, the supplemental log goes into the undo change vector >(and the undo block). The last time I checked, it was not made visible in the formatted log dump.
    The only clue in the formatted trace about what had happened was that the undo change vector LEN >(and the redo record LEN) were larger.Really? I did this suspicion last weekend, I will going to check it today, thank you Lewis for notification.

  • Thread 1 advanced to log sequence (redo log)

    Hi All,
    db:oracle 10gR2(10.2.0.4)
    os:solaris10
    My alert log file shows following information all the time....can you please explain me whats going on??
    Mon Jan 30 01:40:30 2012
    Thread 1 advanced to log sequence 253305
    Current log# 2 seq# 253305 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
    Mon Jan 30 01:45:40 2012
    Thread 1 advanced to log sequence 253306
    Current log# 3 seq# 253306 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
    Mon Jan 30 01:51:21 2012
    Thread 1 advanced to log sequence 253307
    Current log# 1 seq# 253307 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
    Mon Jan 30 01:56:53 2012
    Thread 1 advanced to log sequence 253308
    Current log# 2 seq# 253308 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
    Mon Jan 30 02:01:57 2012
    Thread 1 advanced to log sequence 253309
    Current log# 3 seq# 253309 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
    Mon Jan 30 02:06:31 2012
    Thread 1 advanced to log sequence 253310
    Current log# 1 seq# 253310 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
    Mon Jan 30 02:11:37 2012
    Thread 1 advanced to log sequence 253311
    Current log# 2 seq# 253311 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
    Mon Jan 30 02:16:44 2012
    Thread 1 advanced to log sequence 253312
    Current log# 3 seq# 253312 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
    Mon Jan 30 02:21:51 2012
    Thread 1 advanced to log sequence 253313
    Current log# 1 seq# 253313 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
    Mon Jan 30 02:27:11 2012
    Thread 1 advanced to log sequence 253314
    Current log# 2 seq# 253314 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
    Mon Jan 30 02:32:31 2012
    Thread 1 advanced to log sequence 253315
    Current log# 3 seq# 253315 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
    Mon Jan 30 02:37:25 2012
    Thread 1 advanced to log sequence 253316
    Current log# 1 seq# 253316 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
    Mon Jan 30 02:42:15 2012
    Thread 1 advanced to log sequence 253317
    Current log# 2 seq# 253317 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
    Mon Jan 30 02:47:05 2012
    Thread 1 advanced to log sequence 253318
    Current log# 3 seq# 253318 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
    I appreciate your response......
    thanks.

    This information shows that the log switch has occured.
    The LGWR writes the redo information from the redo log buffer to the online redo log file. When the current online redo log file fills, LGWR begins writing to the next available online redo log file. In the mean time, the ARC process archives the contents of the filled online redo log file (If the database is in archivelog mode. If its in noarchive mode, then the filled online redo log file would not be archived). These archives are given a unique log sequence number.
    In your case 253305, 253306..are the log sequence numbers.
    You can refer http://docs.oracle.com/cd/B10501_01/server.920/a96521/onlineredo.htm for a detailed information

  • Archive logging, single redo log = archivelog?

    We are running archive log mode. I had always assumed when a redolog was full, it was written to a new archivelog file and that was it.
    However, our archivelog files are 200K and our redolog files are 20K... meaning you could fit 10 redologs into a single archivelog file.
    We have 2 groups (1 and 2) and each has 5 members redo01-05.
    Thanks

    You're completely confused bout GROUPs and MEMBERS !
    Have a look at this configuration:
    TEST> select group#, member from v$logfile order by group#;
        GROUP# MEMBER
             1 /gnxprod/logA/redo0101.log
             1 /gnxprod/logB/redo0102.log
             2 /gnxprod/logB/redo0202.log
             2 /gnxprod/logA/redo0201.log
             3 /gnxprod/logA/redo0301.log
             3 /gnxprod/logB/redo0302.log
             4 /gnxprod/logB/redo0402.log
             4 /gnxprod/logA/redo0401.log
             5 /gnxprod/logB/redo0502.log
             5 /gnxprod/logA/redo0501.log
    10 rows selected.This means that there are 5 groups, each containing 2 members. During redo log file usage, Oracle will write to one of these group, then the following, then the following.
    Note that the "next" group is not the "sequential next" - i.e. not mandatorilly 5 after 4 then 1 after 5.
    We use multiple GROUPs mainly because of archiving and redo necessity for instance crash recovery.
    We use multiple (multiplexed) group MEMBERS because of hardware failure risk.
    There's too much to tell straight away. You should rush for the manual (http://tahiti.oracle.com), it's all explained in the Conceps and Admin books.
    Yoann.

  • How to disable write to redo log file in oracle7.3.4

    in oracle 8, alter table no logged in redo log file like: alter table tablename nologging;
    how to do this in oracle 7.3.4?
    thanks.

    user652965 wrote:
    Thanks very much for your help guys. I appreciate it. unfortunately none of these commands worked for me. I kept getting error on clearing logs that redo log is needed to perform recovery so it can't be cleared. So I ended up restoring from earlier snapshot of my db volume. Database is now open.
    Thanks again for your input.And now, as a follow-up, at a minimum you should make sure that all redo log groups have at least 3 members. Then, if you lose a single redo log file, all you have to do is shutdown the db and copy one of the good members (of the same group as the lost member) over the lost member.
    And as an additional follow-up, if you value your data you will run in archivelog mode and take regular backups of the database and archivelogs. If you fail to do this you are saying that your data is not worth saving.

  • ORA-00339: archived log does not contain any redo

    Hi All,
    recently we faced 'ORA-00339: archived log does not contain any redo' issue at standby side,
    after searching on Google and from Metalink (note 30866.1 and 7197445.8 ) I find out that this is the known issue for 10g and below versions, our's is 11.2.0.3,
    Error in Alert Log :
    Errors in file /oracle/ora_home/diag/diag/rdbms/dwprd/DWPRD/trace/DWPRD_pr0a_48412.trc:
    ORA-00339: archived log does not contain any redo
    ORA-00334: archived log: '/redolog2/redo/redolog3a.log'
    Errors in file /oracle/ora_home/diag/diag/rdbms/dwprd/DWPRD/trace/DWPRD_pr0a_48412.trc (incident=190009):
    ORA-00600: internal error code, arguments: [kdBlkCheckError], [1], [56702], [6114], [], [], [], [], [], [], [], []
    Incident details in: /oracle/ora_home/diag/diag/rdbms/dwprd/DWPRD/incident/incdir_190009/DWPRD_pr0a_48412_i190009.trc
    Use ADRCI or Support Workbench to package the incident.
    See Note 411.1 at My Oracle Support for error and packaging details.
    Slave exiting with ORA-10562 exception
    Errors in file /oracle/ora_home/diag/diag/rdbms/dwprd/DWPRD/trace/DWPRD_pr0a_48412.trc:
    ORA-10562: Error occurred while applying redo to data block (file# 1, block# 56702)
    ORA-10564: tablespace SYSTEM
    ORA-01110: data file 1: '/oradata1/database/DATAFILES/system01.dbf'
    ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 2
    ORA-00600: internal error code, arguments: [kdBlkCheckError], [1], [56702], [6114], [], [], [], [], [], [], [], []
    Mon Apr 15 11:34:12 2013
    Dumping diagnostic data in directory=[cdmp_20130415113412], requested by (instance=1, osid=48412 (PR0A)), summary=[incident=190009].
    Thanks

    Hi,
    "The archived log is not the correct log.
    It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log."
    "Restore the correct log file."
    Can you say, what is last changes on your database, On log files?
    Did you copies your '/redolog2/redo/redolog3a.log' log file from other ?
    Regards
    Mahir M. Quluzade

  • 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

  • What is the purpose of standby redo log files

    Hi,
    What is the purpose of the standby redo log files in DR?
    what if the standby redo log files are created? or else not created?
    Please explain
    Thanks

    3.1.3 Configure a Standby Redo LogA standby redo log is required for the maximum protection and maximum availability modes and the LGWR ASYNC transport mode is recommended for all databases. Data Guard can recover and apply more redo data from a standby redo log than from archived redo log files alone.
    You should plan the standby redo log configuration and create all required log groups and group members when you create the standby database. For increased availability, consider multiplexing the standby redo log files, similar to the way that online redo log files are multiplexed.>
    Reference http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
    HTH
    Anand

  • Online redo logs vs standby redo logs

    Hi All,
    Oracle version : 10.2.0.4
    OS : SunOS 5.10 Generic_118855-36 i86pc i386 i86pc
    This might be a silly question for the experts :(
    We are having 2 standby databases and 1 logical database. Everything is running fine , I have one confusion : My primary server having 3 online redo log files and 3 standby redo log files (on primary local), but as per the architecture standby redo logs should be on standby server.My question is whether standby redo logs on standby are online redo logs of standby server or standby redo logs of primary server. e.g If i perform a log switch on primary then what is the role of sync and affirm, will lgwr write parallel on online redo logs ,standby redo logs (of primary) or online redo logs (of primary) and online redo logs (which is known as standby redo logs on standby ). Please help me to understand the scenerio.
    Thanks in advance!

    RFS receives redo information from the primary database.
    RFS can write the redo into standby redo logs or directly to archived redo logs. Each LNSn and ARCn process from the primary database has its own RFS process.
    A standby redo log is used only when the database is in the standby role to store redo data received from the primary database. Standby redo logs form a separate pool of log file groups.
    Configuring standby redo log files is highly recommended on all standby databases in a Data Guard configuration, including the primary database to aid in role reversal.
    A standby redo log is required to implement:
    • The maximum protection and maximum availability levels of data protection
    • Real-time apply
    • Cascaded redo log destinations
    Standby redo logs are recommended for maximum performance data protection mode. Unless you are using the real-time apply feature, standby redo logs must be archived before the data can be applied to the standby database. The standby archival operation occurs automatically.

  • How to recover from corrupt redo log file in non-archived 10g db

    Hello Friends,
    I don't know much about recovering databases. I have a 10.2.0.2 database with corrupt redo file and I am getting following error on startup. (db is non archived and no backup) Thanks very much for any help.
    Database mounted.
    ORA-00368: checksum error in redo log block
    ORA-00353: log corruption near block 6464 change 9979452011066 time 06/27/2009
    15:46:47
    ORA-00312: online log 1 thread 1: '/dbfiles/data_files/log3.dbf'
    ====
    SQL> select Group#,members,status from v$log;
    GROUP# MEMBERS STATUS
    1 1 CURRENT
    3 1 UNUSED
    2 1 INACTIVE
    ==
    I have tried this so far but no luck
    I have tried following commands but no help.
    SQL> ALTER DATABASE CLEAR UNARCHIVED LOGFILE GROUP 3;
    Database altered.
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01139: RESETLOGS option only valid after an incomplete database recovery
    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 6464 change 9979452011066 time 06/27/2009
    15:46:47
    ORA-00312: online log 1 thread 1: '/dbfiles/data_files/log3.dbf'

    user652965 wrote:
    Thanks very much for your help guys. I appreciate it. unfortunately none of these commands worked for me. I kept getting error on clearing logs that redo log is needed to perform recovery so it can't be cleared. So I ended up restoring from earlier snapshot of my db volume. Database is now open.
    Thanks again for your input.And now, as a follow-up, at a minimum you should make sure that all redo log groups have at least 3 members. Then, if you lose a single redo log file, all you have to do is shutdown the db and copy one of the good members (of the same group as the lost member) over the lost member.
    And as an additional follow-up, if you value your data you will run in archivelog mode and take regular backups of the database and archivelogs. If you fail to do this you are saying that your data is not worth saving.

  • When occurs crash recovery,why use active online redo log not archived log?

    If current redo log had archived, but it's still 'ACTIVE'. As we all know, archived log is just an archived copy of the current redo log which is still 'ACTIVE', they have the same data. But why use active online redo log not archived log for crash recovery?(I think, if crash recovery can use archived log, then whether the online redo log is 'ACTIVE' or not, it can be overwritten)
    Quote:
    Re: v$log : How redo log file can have a status ACTIVE and be already archived?
    Hemant K Chitale
    If your instance crashes, Oracle attempts Instance Recovery -- reading from the Online Redo Logs. It doesn't need ArchiveLogs for Instance Recovery.
    TanelPoder
    Whether the log is already archived or not doesn't matter here, when the instance crashes, Oracle needs some blocks from that redolog. Archivelog is just an archived copy of the redolog, so you could use either the online or achive log for the recovery, it's the same data in there (Oracle reads the log/archivelog file header when it tries to use it for recovery and validates whether it contains the changes (RBA range) in it what it needs).

    Aman.... wrote:
    John,
    Are you sure that the instance recovery (not the media recovery) would be using the archived redo logs? Since the only thing that would be lost is the isntance, there wouldn't be any archived redo log generated from the Current redo log and the previous archived redo logs, would be already checkpointed to the data file, IMHO archived redo logs won't participate in the instance recovery process. Yep, shall watch the video but tomorrow .
    Regards
    Aman....
    That's what I said. Or meant to say. If Oracle used archivelogs for instance recovery, it would not be possible to recover in noarchive log mode. So recovery relies exclusively on the online log.
    Sorry I wasted your time, I'll try to be less ambiguous in future

  • Private strand flush not complete how to find optimal size of redo log file

    hi,
    i am using oracle 10.2.0 on unix system and getting Private strand flush not complete in the alert log file. i know this is due to check point is not completed.
    I need to increase the size of redo log files or add new group to the database. i have log file switch (checkpoint incomplete) in the top 5 wait event.
    i can't change any parameter of database. i have three redo log group and log files are of 250MB size. i want to know the suitable size to avoid problem.
    select * from v$instance_recovery;
    RECOVERY_ESTIMATED_IOS     ACTUAL_REDO_BLKS     TARGET_REDO_BLKS     LOG_FILE_SIZE_REDO_BLKS     LOG_CHKPT_TIMEOUT_REDO_BLKS     LOG_CHKPT_INTERVAL_REDO_BLKS     FAST_START_IO_TARGET_REDO_BLKS     TARGET_MTTR     ESTIMATED_MTTR     CKPT_BLOCK_WRITES     OPTIMAL_LOGFILE_SIZE     ESTD_CLUSTER_AVAILABLE_TIME     WRITES_MTTR     WRITES_LOGFILE_SIZE     WRITES_LOG_CHECKPOINT_SETTINGS     WRITES_OTHER_SETTINGS     WRITES_AUTOTUNE     WRITES_FULL_THREAD_CKPT
    625     9286     9999     921600          9999          0     9     112166207               0     0     219270206     0     3331591     5707793please suggest me or tell me the way how to find out suitable size to avoid problem.
    thanks
    umesh

    How often should a database archive its logs
    Re: Redo log size increase and performance
    Please read the above thread and great replies by HJR sir. I think if you wish to get concept knowledge, you should add in your notes.
    "If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files. The optimal size can be obtained by querying the OPTIMAL_LOGFILE_SIZE column from the V$INSTANCE_RECOVERY view. You can also obtain sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control."
    Source:http://download-west.oracle.com/docs/cd/B13789_01/server.101/b10752/build_db.htm#19559
    Pl also see ML Doc 274264.1 (REDO LOGS SIZING ADVISORY) on tips to calculate the optimal size for redo logs in 10g databases
    Source:Re: Redo Log Size in R12
    HTH
    Girish Sharma

  • Why multiplex redo log group ?

    Hello,
    Why should we multiplex redo log groups if we have only file system which is already mirrored. Is there any one who had an incident when he has only one redo log member per group placed on a mirrored file system but still got corrupted and he felt better to have multiple members even if they reside on the same file system (which is mirrored)
    Thanks
    Salman

    Ansiktet wrote:
    EdStevens wrote:
    Salman Qureshi wrote:
    Hello,
    Why should we multiplex redo log groups if we have only file system which is already mirrored. Is there any one who had an incident when he has only one redo log member per group placed on a mirrored file system but still got corrupted and he felt better to have multiple members even if they reside on the same file system (which is mirrored)
    Thanks
    SalmanThe mirror won't protect you from an SA who deletes '/u01/oradata/redo01.log' because he is running out of space on /u01 and figures its safe to delete a log file.
    Or similar types of errors.
    The redo and control files are simply too critical to put all your eggs in one basket when planning their protection.:) Thats why you should not use Oracle default .log on redo, instead .dbf or .dbl can be used. THat's why I use the older (pre-10g) default of .rdo for redo logs
    However, has this happend anyone for real, that a SA delete Oracle files? Where do you think I came up with the example?
    HOw about an SA (or maybe the kind of "fresher" we often see here, Taking a look at a "log" file with notepad?
    If he is isnt stupid he should know that Oracle resides on /u01 partion (for example), and should not delete files there without consulting the DBA."should" is the operative word there. There is no accounting for corporate cultures and attitudes.
    But end the end, my example was to illustrate that not all problems with redo and control files are mitigated with disk mirroring.

Maybe you are looking for

  • Two commands suddenly greyed out in QT 7

    I have the registered version of Quicktime Player Pro 7. In the Registration window, it shows it is registered in my name and shows the Registration Code. I used to have thw two commands in the View menu in all movies, Loop and Loop Back and Forth. N

  • 12 days of gifts is a scam?

    Hello, I got the app "12 Days" from iTunes.. which should give free gifts due the christmas time. Yesterday the gifst was BBC Series "Africa" , I pressed to get this gift and today got the reciept of 12.99pound from my account. I didnt even download

  • BOM item qty does not change when header qty changes in Outbound Delivery

    Hi, We are using sales BOM and exploding it in Sales Order.  ( Item category of components as TAE ) I am creating a delivery with reference to  a sales oder ( i have maintained copy controls to copy header and item data). Now when i change BOM header

  • How to split PDF file by pages

    Is there any programming way to split PDF into pages, say one PDF file per page or specify page range to split PDF file? Thanks for your help.

  • JVM performance slowed down after

    Hello all, My java application is heavily multithreaded and its supposed to run as a 24/7 service. Its supposed to collect SMS from different servers, store in memory/flat-files and send them to clients. The application has been running for the past