Nor more Checkpoints at every log-switch in 10.2 ?

Hi,
i working with Oracle about 12 years but i havn´t seen this before:
REM There is no work/application in the database now:
select group#,status from v$log;
GROUP# STATUS
1 CURRENT
2 ACTIVE
4 ACTIVE
5 ACTIVE
6 ACTIVE
First as i know only one or two (for a short time) shiould be active.
OK wait 90 seconds:
SQL> /
GROUP# STATUS
1 CURRENT
2 ACTIVE
4 ACTIVE
5 ACTIVE
6 ACTIVE
Try a log switch:
alter system switch logfile;
SQL> select group#,status from v$log;
GROUP# STATUS
1 ACTIVE
2 CURRENT
4 ACTIVE
5 ACTIVE
6 ACTIVE
How can i now drop one of the redo-logs ?
=> Solution:
alter system checkpoint;
select group#,status from v$log;
GROUP# STATUS
1 INACTIVE
2 CURRENT
4 INACTIVE
5 INACTIVE
6 INACTIVE
Does anybody know what Oracle changed here ?
Thanks in advance
Marco

hi,
welcome to Oracle10g:
show paramater FAST_START_MTTR_TARGET
if it is '0', then auto-checking-pointing is DISABLED, this happens to be the default on Oracle XE (under review)
By default, Oracle 10g supports automatic checkpoint tuning by making the best effort to write out SGA buffer cache dirty buffers w/o impacting the throughput of runtime physical I/O, thus achieving reasonable crash recovery time.
Setting the FAST_START_MTTR_TARGET parameter to a non-zero value or not setting this parameter enables automatic checkpoint tuning. The STATISTICS_LEVEL must be TYPICAL OR ALL. After a period of time, see V$MTTR_TARGET_ADVICE for various value for this parameter.

Similar Messages

  • Forcing log switch every minute.

    Hi,
    I want to force a log switch every one minute how can i do it?
    What should be the value of fast_start_mttr_target?
    Does a checkpoint force a log switch?
    Do i need to only reduce the size of redo log to a small size?
    How can i make sure that a log switch will happen after a particular time period for ex. 1Minute,2 minute.
    I want to force a log switch every minute because i want to send the archive redo log to standby database so that not more than 1 minute changes in database are lost. I am using 10g R2 on windows 2003 server.
    I am unable to find a solution. Any help?

    Hi,
    I want to force a log switch every one minute how
    can i do it? yes with archive_lag_target parameter
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/onlineredo.htm#sthref934
    What should be the value of fast_start_mttr_target?incremental or normal checkpoint "fast instance recovery/downtime concerned" introduced from oracle 8, this feature is enabled with the initialization parameter FAST_START_MTTR_TARGET in 9i.
    fast_start_mttr_target to database writer tries to keep the number of dirty blocks in the buffer cache low enough to guarantee rapid recovery in the event of a crash. It frequently updates the file headers to reflect the fact that there are not dirty buffers older than a particular SCN.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmtunin004.htm#sthref1110
    Does a checkpoint force a log switch? log switch force to checkpoint ,checkpoint never force to log switch.
    Do i need to only reduce the size of redo log to a
    small size?depends yours SLA how far you can risk the data ,but it will effect yours database performance ,recommended to set the size of log which should imply the log swtich after filling to 20 mins,its a trade off risk vs perofrmance.
    How can i make sure that a log switch will happen
    after a particular time period for ex. 1Minute,2
    minute.
    want to force a log switch every minute because i
    want to send the archive redo log to standby database
    so that not more than 1 minute changes in database
    are lost. I am using 10g R2 on windows 2003 server.
    am unable to find a solution. Any help?
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/onlineredo.htm#sthref934Khurram

  • Private_strands 39 at log switch

    Hi to All,
    After upgrading from 8i 8.1.7.4 to 10R1 on windows 2003 sp2 we are getting this below message on every log switch when I google it I find some thing that increase the size of redo logs my 8i database redo log size is 10mb and now I increase it to 50mb but same message is coming on evry log switch.Can any body help me plz.....
    "Private_strands 39 at log switch
    Thread 1 advanced to log sequence 391
    Current log# 1 seq# 391 mem# 0: F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROS\REDO01.LOG"
    Regards,
    Dxb_Dba

    Oracle 10g has some major changes in the mechanisms for redo (and undo), which seem to be aimed at reducing contention.
    Instead of redo being recorded in real time, it can be recorded 'privately' and pumped into the redo log buffer on comit.
    The message you get is related to internal Cache Redo File management.
    A "strand" is new terminology for 10g and it deals with latches for redo .
    Strands are a mechanism to allow multiple allocation latches for processes to write redo more efficiently in the redo buffer and is related to the log_parallelism parameter present in 9i.
    The concept of a strand is to ensure that the redo generation rate for an instance is optimal and that when there is some kind of redo contention then the number of strands is dynamically adjusted to compensate.
    You can disregard these messages as normal messages.
    When you switch logs all private strands have to be flushed to the current log before the switch is allowed to proceed.
    also refer to 372557.1 document

  • Checkpoint occuring for every log transfer

    Thanks for taking my question!
    I have a new server and not much is running except exports, imports and rman backups. Problem is every redo transfer gets a checkpoint. Is this normal occurrence while doing backups and loads?
    Thanks!
    Kathie
    My server is 11.1.0.7 windows 2008.
    I have archive logging on.
    I had 3 log groups with two members each.
    redo size is 100m.
    I just added a fourth group to see if that will help but it seems strange to get a checkpoint everytime the log transfers.
    hread 1 cannot allocate new log, sequence 148
    Checkpoint not complete
    Current log# 3 seq# 147 mem# 0: F:\ORACLE\11.1.0\ORADATA\CS90QAP\REDO03.LOG
    Current log# 3 seq# 147 mem# 1: E:\ORACLE\11.1.0\ORADATA\CS90QAP\REDO03A.LOG
    Thread 1 advanced to log sequence 148 (LGWR switch)
    Current log# 1 seq# 148 mem# 0: F:\ORACLE\11.1.0\ORADATA\CS90QAP\REDO01.LOG
    Current log# 1 seq# 148 mem# 1: E:\ORACLE\11.1.0\ORADATA\CS90QAP\REDO01A.LOG
    Fri Apr 03 08:07:18 2009
    Thread 1 cannot allocate new log, sequence 149
    Checkpoint not complete
    Current log# 1 seq# 148 mem# 0: F:\ORACLE\11.1.0\ORADATA\CS90QAP\REDO01.LOG
    Current log# 1 seq# 148 mem# 1: E:\ORACLE\11.1.0\ORADATA\CS90QAP\REDO01A.LOG

    >
    Laura,
    Please don't take it as nitpick , this is just a little more elaborated view of what you said.Checkpoint is initiated with the log switch and keeps on getting completed. Oracle does it on its own pace. With log switch, checkpoint doesn't need to get completed but before thesae log is requested , it must be completed. I agree with You, I was just explaining that it's normal that it occurs and not going into details why there is message about Checkpoint not complete
    But probably should have ...

  • Checkpoint and log switch

    I would like to know if when a redo log is filled, the new redo log can be written in parallel with the chekpoint.
    Or simply, what's the sequence for log switching:
    1 - redo log is filled -> checkpoint -> new log writes. or
    2 - redo log is filled -> checkpoint/new log writes (in parallel)
    Best Regards,
    Rogerio C. Schreiner
    null

    I'm tempted to say 'don't worry about it', because L_C_T has been deprecated since 9i: instead use FAST_START_MTTR_TARGET to control the rate of checkpointing.
    But that aside, L_C_T essentially says: "if a block was dirtied (changed) by a transaction whose redo was generated more that X seconds ago -where X is the number of seconds LCT is set to- then that block will be flushed to disk the next time DBWR wakes up on the '3 second rule'"
    L_C_INTERVAL means something similar: "If a block was dirtied by a transaction whose redo can be found in the redo log more than Y redo blocks away from the current checkpoint marker, where Y is the setting for LCI, flush it next time DBWR wakes up"
    A checkpoint does not always result in a log switch, but a log switch always results in a checkpoint.
    You can't really answer your third question, because the LCT parameter doesn't mean "Every 1800 seconds, flush everything to disk" (as it used to in version 8.0). But if a block was dirtied more than 1800 seconds ago, it will be a candidate for flushing to disk next time DBWR wakes up. But that doesn't tell us when a log switch will occur: that will only happen when the redo log fills up and we have to switch to the next log to keep going. I can't tell anything about the size of your logs or the rate at which they will fill up from the parameters you list.
    A parameter does exist which will force a log switch every so often. It's called ARCHIVE_LAG_TARGET, and it's set to a number of seconds. If that was set to 1800, I could say with confidence that you'd log switch every half hour. But that's not what you had in your question, of course!
    You might care to read this slightly more technical description of the parameters:
    http://www.jlcomp.demon.co.uk/faq/log_checkpoint.html
    (though I think Jonathan's timelines are wrong, because the change to the effect of the parameters came in with 8i).
    Message was edited by:
    howardjr

  • Log switch must occur every 15 to 30 minutes: good practice or myth?

    I often heard that it is recommended to size redo log files in a way that Oracle performs a log switch every 15 to 30 minutes.
    I would like to know if it is true or if it is a myth ?
    I would like to know the best way for sizing redo log files ?
    What happen exactly in the database when a log switch occurs ?
    Please help me to clarify these concepts.

    So we can say that a log switch induces a full checkpoint. That's correct ?Well, no :-) . Indeed with a log switch the checkpoint event is generated requesting DBWR to flush the buffers from the checkpoint-queue to the data files but this is not a full checkpoint and it would not update the datafile and control file headers. The Full Checkpoint happens with the alter system checkpoint ( as shown) , database being shutdown properly.
    Please see the below code which shows the same,
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
    7 rows selected.
    SQL> select * from V$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
             1          1         91   52428800          1 NO  CURRENT
          3507399 13-APR-10
             2          1         89   52428800          1 NO  INACTIVE
          3486253 13-APR-10
             3          1         90   52428800          1 NO  INACTIVE
          3486256 13-APR-10
    SQL> alter system switch logfile;
    System altered.
    SQL> select * from V$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
             1          1         91   52428800          1 NO  ACTIVE
          3507399 13-APR-10
             2          1         92   52428800          1 NO  CURRENT
          3507906 13-APR-10
             3          1         90   52428800          1 NO  INACTIVE
          3486256 13-APR-10
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
    7 rows selected.
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
               3507400
    7 rows selected.
    SQL> alter system checkpoint;
    System altered.
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               3507936
               3507936
               3507936
               3507936
               3507936
               3507936
               3507936
    7 rows selected.
    SQL>HTH
    Aman....

  • Log switch checkpoint

    Hello
    Assume I have two redologs.
    Log1-->current
    Log2->inactive
    After log switch, it becomes.
    log1 -->active
    log2-->current
    The thing is after log switch; checkpoint must be issued and the log1 should be inactive. Why does it show active?
    If I manually issue
    "alter system checkpoint"
    Log1 becomes inactive immeidately.

    Mathias Delgado wrote:
    Mr sb;
    I have also read some other docs.
    Please confirm wheter my understanding is correct.
    After alter system switch logfile, checkpoint is initiated, not finished.
    However when I issue,
    "alter system checkpoint"
    Checkpoint is issued immediately and therefore the status is of redolog is changed from active to inactive immediately.No , your understanding is incorrect.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> select * from V$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
             1          1         65   52428800          1 YES INACTIVE
          2254888 25-JUN-09
             2          1         66   52428800          1 YES INACTIVE
          2279864 26-JUN-09
             3          1         67   52428800          1 NO  CURRENT
          2300530 27-JUN-09
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               2300531
               2300531
               2300531
               2300531
               2300531
               2300531
               2300531
               2300531
    8 rows selected.
    SQL> alter system checkpoint;
    System altered.
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               2302787
               2302787
               2302787
               2302787
               2302787
               2302787
               2302787
               2302787
    8 rows selected.
    SQL> select * from V$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
             1          1         65   52428800          1 YES INACTIVE
          2254888 25-JUN-09
             2          1         66   52428800          1 YES INACTIVE
          2279864 26-JUN-09
             3          1         67   52428800          1 NO  CURRENT
          2300530 27-JUN-09
    SQL> alter system checkpoint;
    System altered.
    SQL> select * from V$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
             1          1         65   52428800          1 YES INACTIVE
          2254888 25-JUN-09
             2          1         66   52428800          1 YES INACTIVE
          2279864 26-JUN-09
             3          1         67   52428800          1 NO  CURRENT
          2300530 27-JUN-09
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               2302798
               2302798
               2302798
               2302798
               2302798
               2302798
               2302798
               2302798
    8 rows selected.
    SQL> alter system switch logfile;
    System altered.
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               2302798
               2302798
               2302798
               2302798
               2302798
               2302798
               2302798
               2302798
    8 rows selected.
    SQL> select * from V$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
             1          1         68   52428800          1 NO  CURRENT
          2302807 27-JUN-09
             2          1         66   52428800          1 YES INACTIVE
          2279864 26-JUN-09
             3          1         67   52428800          1 YES ACTIVE
          2300530 27-JUN-09
    SQL> alter system checkpoint;
    System altered.
    SQL> select * from V$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
    FIRST_CHANGE# FIRST_TIM
             1          1         68   52428800          1 NO  CURRENT
          2302807 27-JUN-09
             2          1         66   52428800          1 YES INACTIVE
          2279864 26-JUN-09
             3          1         67   52428800          1 YES INACTIVE
          2300530 27-JUN-09
    SQL> select checkpoint_change# from V$datafile;
    CHECKPOINT_CHANGE#
               2302817
               2302817
               2302817
               2302817
               2302817
               2302817
               2302817
               2302817
    8 rows selected.
    SQL>What you see here, can you try to interpret it?
    Alter checkpoint command merely pushes the writing and gets the checkpointing write complete. Its only the log switch which is going to do a complete checkpoint. Active means that the checkpointing for that group is started. The time perilod for which you see this status would depend on the size of the redo log file and also the contents that are there in it when it was switched. After checkpoining is complete for this group, the file be completely empty and would be marked as inactive.
    HTH
    Aman....

  • Entire Mac slows down every day, especially if more than one user logged in

    Mac runs fine at the start of each day (after turning it on), but slows down by evening. iPhoto is typically at a crawl at that point, and I can't have more than one user logged in at a time, or the whole system takes forever to do anything. I've restarted, repaired disk, repaired disk permissions, run Cocktail, checked for viruses (VirusBarrier). It's easy to restore normal speed with these moves, but same problem every day. I have 24 GB left on this hard drive--is that too little?
    Should I try erasing hard drive and restoring from Time Machine? Should I reload Mac OS X from discs?
    Advice much appreciated. Thanks.

    Robert Fishman1 wrote:
    I have 24 GB left on this hard drive--is that too little?
    you do the math
    this will help:
    Your Mac needs adequate hard drive space to operate normally. How full can a drive be before it's too full? There is no hard and fast rule that says “X” amount or “%” of free drive space is needed. A low amount of RAM requires more drive space for Virtual Memory’s swap files.
    Problems from insufficient RAM and free hard disk space are discussed in this link
    http://www.thexlab.com/faqs/lackofram.html
    Here’s some general guidelines for minimum hard drive free space:
    1. As a general rule, your available space should be 5GB as an absolute minimum as it generally requires that much free space to perform an Archive and Install of Mac OS X and still preserve some free space for VM swap files.
    2. Some say that your hard drive should have at least 5% of it's capacity available for use. Still others say 10% to 15%. If you routinely process complex graphics and videos, even more space is required.
    Look at these links about freeing up more space.
    Where did my disk space go?
    _*http://www.macfixitforums.com/showflat.php?Cat=&Board=Forum38&Number=770243*_
    Download & use WhatSize described in this link or Disk Inventory X @ _*http://www.derlien.com/*_
    Freeing space on your Mac OS X startup disk
    _*http://www.thexlab.com/faqs/freeingspace.html*_
    Amazing Disappearing Drive Space
    _*http://www.pinkmutant.com/articles/TigerMisc.html*_
    Increase HD Free Space
    _*http://macosx.com/forums/howto-faqs/275191-how-easily-increase-hd-free-space-lap top.html*_
    How to free up my disk space
    http://www.macmaps.com/diskfull.html
    JGG

  • Log switch and checkpoint - Oracle 11g

    Hi
    I've read a documentations and forum, but I can't find clean explanation. I'd like to ask - does switch log trigger checkpoint? I've heard, that from 8i version checkpoint doesn't occur on log switch, but can't find information
    in documentation.
    Thanks awfully for help.
    Regards

    before 8i , logfile switch caused full checkpoint
    8i and above , logfile switch no longer causes full checkpoint , it causes a "log switch checkpoint"
    A log switch checkpoint write the contents of "some" dirty buffers to the disk

  • Checkpoint _change# &&log switch

    Hey
    When I issue alter system switch logfile a checkpoint must be issued and therefore checkpoint change # of the datafiles should be incremented.
    However sometimes checkpoint change # of the datafiles doesnt change after the log switch....
    Why?
    ie:
    SQL> select substr(name,1,50) fname,checkpoint_change#,last_change#,status
    from v$datafile;
    FNAME
    CHECKPOINT_CHANGE# LAST_CHANGE# STATUS
    C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
    219513 SYSTEM
    C:\ORACLEXE\ORADATA\XE\UNDO.DBF
    219513 ONLINE
    C:\ORACLEXE\ORADATA\XE\SYSAUX.DBF
    219513 ONLINE
    FNAME
    CHECKPOINT_CHANGE# LAST_CHANGE# STATUS
    C:\ORACLEXE\ORADATA\XE\USERS.DBF
    219399 219399 OFFLINE
    SQL> alter system switch logfile;
    System altered.
    select substr(name,1,50) fname,checkpoint_change#,last_change#,status
    from v$datafile;
    FNAME
    CHECKPOINT_CHANGE# LAST_CHANGE# STATUS
    C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
    219513 SYSTEM
    C:\ORACLEXE\ORADATA\XE\UNDO.DBF
    219513 ONLINE
    C:\ORACLEXE\ORADATA\XE\SYSAUX.DBF
    219513 ONLINE
    FNAME
    CHECKPOINT_CHANGE# LAST_CHANGE# STATUS
    C:\ORACLEXE\ORADATA\XE\USERS.DBF
    219399 219399 OFFLINE

    ALTER SYSTEM SWITCH LOGFILE may take some time to complete its job. if you wait a couple of seconds after each statement to switch log, it looks OK:
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Express 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 log_mode from v$database;
    LOG_MODE
    NOARCHIVELOG
    SQL> select file#, checkpoint_change# from v$datafile;
         FILE# CHECKPOINT_CHANGE#
             1             758989
             2             758989
             3             758989
             4             758989
             5             758989
    SQL>
    SQL> alter system switch logfile;
    Système modifié.
    SQL> host pause
    Appuyez sur une touche pour continuer...
    SQL> select file#, checkpoint_change# from v$datafile;
         FILE# CHECKPOINT_CHANGE#
             1             758994
             2             758994
             3             758994
             4             758994
             5             758994
    SQL> alter system switch logfile;
    Système modifié.
    SQL> host pause
    Appuyez sur une touche pour continuer...
    SQL> select file#, checkpoint_change# from v$datafile;
         FILE# CHECKPOINT_CHANGE#
             1             758996
             2             758996
             3             758996
             4             758996
             5             758996
    SQL> alter system switch logfile;
    Système modifié.
    SQL> host pause
    Appuyez sur une touche pour continuer...
    SQL> select file#, checkpoint_change# from v$datafile;
         FILE# CHECKPOINT_CHANGE#
             1             758998
             2             758998
             3             758998
             4             758998
             5             758998
    SQL>
    SQL>

  • Archive log switch

    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:00 o1_mf_1_90491_4341nt0b_.arc
    -rw-r-----   1 oracle     oinstall   13420544 May 20 02:01 o1_mf_1_90492_4341oov9_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:02 o1_mf_1_90493_4341q45y_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:02 o1_mf_1_90494_4341qytf_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:03 o1_mf_1_90495_4341s2w8_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:03 o1_mf_1_90496_4341szog_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:04 o1_mf_1_90497_4341v16m_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:05 o1_mf_1_90498_4341wsbl_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:05 o1_mf_1_90499_4341y0ps_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:06 o1_mf_1_90500_4341yyj1_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:06 o1_mf_1_90501_4342044h_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:07 o1_mf_1_90502_434217j9_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 02:10 o1_mf_1_90503_43426g1z_.arc
    -rw-r-----   1 oracle     oinstall   13424640 May 20 05:01 o1_mf_1_90504_434d70c6_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 05:22 o1_mf_1_90505_434fhm1b_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 05:23 o1_mf_1_90506_434fjrgr_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 05:24 o1_mf_1_90507_434fkxkf_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 05:24 o1_mf_1_90508_434flzfp_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 05:25 o1_mf_1_90509_434fnngh_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 05:26 o1_mf_1_90510_434fp67w_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 05:27 o1_mf_1_90511_434fqwks_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 05:28 o1_mf_1_90512_434fslyn_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 05:29 o1_mf_1_90513_434fvr3c_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 05:30 o1_mf_1_90514_434fxrsq_.arc
    -rw-r-----   1 oracle     oinstall   13427712 May 20 05:31 o1_mf_1_90515_434fzr8h_.arc
    -rw-r-----   1 oracle     oinstall   13438976 May 20 10:00 o1_mf_1_90516_434xrhf9_.arcmine is 10.2.0.1 database...my log switch is happening intermittently....log file size is 20 MB
    log_checkpoint_interval              integer     0
    log_checkpoint_timeout               integer     1800
    log_checkpoints_to_alert             boolean     FALSEHow can I set to happen log file switch at every 30 Minutes...

    These are two different issues.
    1. There are frequent log switches so the log file size could [should] be increased.
    2. However, there are, at times, gaps of 3 hours and 5 hours between two
    log switches. I presume that Deepa wants to ensure that a log switch occurs
    "at least every 30minutes". It may occur more frequently than that (twice a
    minutes) but the maximum gap between two log switches is desired as 30minutes.
    That is what ARCHIVE_LAG_TARGET does.
    It is not necessary that only in Standby databases would a DBA want a
    maximum duration between log switches. You might be using this in a database
    (as we have in Deepa's case !) where there are long "idle" stretches of time
    with very little activity as well. Say, you have a background job periodically
    backing up archivelogs using OS based methods (not RMAN) -- to tape
    or to an NFS mount point or an offsite storage facility. ARCHIVE_LAG_TARGET
    will help you ensure that the maximum data loss is 30minutes (even if there
    was only 1 transaction of 1 row in those 30minutes) because that is what
    your SLA might specify. This would be part of your media recovery / DR
    requirements.
    log_checkpoint_timeout is not to do with archiveloging but with checkpoints.
    that is a complete different requirement -- that is for instance recovery not
    media recovery / backup-restore / DR requirements.

  • Dataguard- scheduling manual log switch to have minimal lag

    Hi,
    I need some suggestion..
    Recentry I had configured a physical standby for my 10g production database in maximum performance mode.
    Now , to reduce the lag between the primary and standby , I put one cron job which will do a manual log switch(alter system switch logfile) in every 30 minutes.
    and it is doing the job..!
    Does this have any impact on my databases...?
    Looking forward for your invaluable responce...
    Regards
    Noushad
    DBA

    Maybe you should let Oracle do it's job, configure this parameter which signifies that no buffer will remain dirty (in the cache) for more than 1800 (or whatever you want) seconds:
    LOG_CHECKPOINT_TIMEOUT = 1800:p

  • Redo log switching

    11gR2
    Found out log switched every a few mins (2, 3 mins) at peak periods. I will make the recommendation for larger redo logs such that switches will be every 20 to 30 mins .
    Wanted to know what would be negative side of large redo logs?

    >
    11gR2
    Found out log switched every a few mins (2, 3 mins) at peak periods. I will make the recommendation for larger redo logs such that switches will be every 20 to 30 mins .
    Wanted to know what would be negative side of large redo logs?
    >
    Patience, grasshopper!
    If it ain't broke, don't fix it. So first make sure it is broken, or about to break.
    Unless you have an emergency on your hands you don't want to implement a change like that without careful examination of your current log file usage and history.
    You need to provide more information such as typical size of your log files, number of log groups, number of members in each group, log archive policy, etc.
    1. How often do these 'peak periods' occur? Do they occur fewer than 5 or 6 times a day? Or dozens of times?
    2. How long do they last? A few minutes? Or a few hours?
    3. What is the typical, non-peak rate of switches? This is really your base-line that you need to compare things to.
    4. What has the switch pattern been over the last few weeks or months?
    5. What has the growth in DB activity benn over the last few weeks or months? What do expect over the next few months?
    6. What is your goal in reducing the frequency of log switches?
    Basic negative sides include longer time to archive each log file (the fewer logs in each group the more impact here) and the length of time to recover in the event you need to. With large log files there is more for Oracle to wade through to find the relevant data for restoring the DB to a given point in time.
    Your suggestion of every 20 - 30 minutes means 2 to 3 times per hour. If you currently switch 10 or 12 times per hour you are making a very big change.
    Although you don't want to 'tweak' the logs unnecessarily you also don't want to make such large changes.
    Everything in moderation. If your current switch rate is 10 or 12 times per hour you may want to first cut this to maybe 1/2 to 1/3: that is, to 4 or 5 time per hour. It all depends on the answers to questions like I ask above. If you post the answers to know if will be helpful to anyone trying to advise you.

  • Redo Log Switch 결과...

    환경 : 8.1.7.3.0 (no archive log 모드)
    log_checkpoint_timeout = 0
    log_checkpoint_interval = 999999999
    redo log size = 200M
    현재 check point는 log switch 상태에서만 가능하도록 설정된 것 같습니다.
    거래량이 적어서 그런지 log switch는 30시간 주기입니다.
    제가 실행한 것은 아래 4번째 로그가 current일때
    alter system checkpoint를 하고 조금 있다가..
    alter system switch logfile를 하여 1번째가 current가 된 상황입니다.
    3/16일 14시 까지도 계속 active상태입니다...
    1. 문제가 생긴건지요??? 도움부탁합니다...
    2. no archive log mode에서도 switch 주기를 줄이는 것이 복구에 도움이 되나요...?
    ===========================================
    STATUS , FIRST_CHANGE#,FIRST_TIME
    CURRENT , 8846777646687,2007-03-15 16:57:55
    INACTIVE, 8846777587798,2007-03-14 10:34:40
    INACTIVE, 8846777609448,2007-03-14 17:17:38
    ACTIVE , 8846777643690,2007-03-15 16:01:22

    no archivemode에서 정상복구를 바라는 것인지요?
    잘못된 정책이란 생각이 듭니다.
    no archive mode에서 v$log의 first_change# 중에 가장 작은 것
    이 v$recover_file의 change# 보다 크거나 같다면 복구불능입니다.
    배치작업이라도 있어서 log switch가 한번의 cycle을 돌게 되면 이전
    백업으로는 복구불능입니다. archive mode로 지금 바로 바꾸시지요..
    log_checkpoint_timeout은 checkpoint에 대한 timeout 시간값을
    지정하는 것입니다.
    LOG_CHECKPOINT_INTERVAL specifies the frequency of checkpoints in terms of the number of redo log file blocks that can exist between an incremental checkpoint and the last block written to the redo log. This number refers to physical operating system blocks, not database blocks.
    checkpoint는 아시는 바와 같이 데이터파일과
    리두로그 컨트롤파일의 SCN을 일치시키는 것입니다. 주요한 것은
    DBWR프로세스가 데이터파일에 write를 하겠구요.
    물론 checkpoint와 인스턴스 복구는 관련이 있습니다. checkpoint timeout을
    적당히주면 instance recovery에서 좀 더 빠르게 instance 복구후 DB가
    open되겠습니다. 만약 설정하신대로 하신다면 DB를 abort로
    내리고 open하게 되면
    instance recovery시에 더 많은 시간이 필요하겠습니다.
    게다가 트랜잭션으로 인한 log switch하는 시간이 30시간보다
    작다면 timeout을 준들 영향을 주지 않겠지요. redo log가 꽉
    차게 되면 log switch를 자동으로 하게 되는데 log switch를
    하기전에 checkpoint를 주게 되어 있으니까요.
    그런데 checkpoint와 물리적/논리적 복구와는 다른 개념입니다.
    checkpoint는 위에서 말씀드린 instance recovery와 관련이 있고
    물리적/논리적 복구에서는 archive file이 떨어져 있는가 current redo log가
    존재하는가에 따라서 복구가능여부를 결정되는 것이지요..
    그리고 ACTIVE 상태라는 것은 문서상의 정의에서는 archive mode일 경우
    archiving이 되는 중일 경우, 그리고 이 상태는 complete recovery시에 redo log
    적용시 필요한 정보가 있다는 것입니다.
    no archive mode에서 복구정책을 적용 하겠다는 것은 위험한 발상인 것 같습니다.
    물론 DSS시스템의 경우에는 이미 정책을 no archive mode로
    만들어두고 주말마다 offline backup을 하기도 합니다.
    하지만 DSS에서는 하루에 300번 이상의 log switch가 일어나는
    경우가 있을 정도이니 아무리 백업이 되어 있다 한들 완전복구는
    불능이겠지요. offline backup을 했을 때까지만 복구가 됩니다.
    $LOG
    This view contains log file information from the control files.
    Column Datatype Description
    GROUP#
    NUMBER
    Log group number
    THREAD#
    NUMBER
    Log thread number
    SEQUENCE#
    NUMBER
    Log sequence number
    BYTES
    NUMBER
    Size of the log (in bytes)
    MEMBERS
    NUMBER
    Number of members in the log group
    ARCHIVED
    VARCHAR2(3)
    Archive status (YES |NO)
    STATUS
    VARCHAR2(16)
    Log status:
    UNUSED - Online redo log has never been written to. This is the state of a redo log that was just added, or just after a RESETLOGS, when it is not the current redo log.
    CURRENT - Current redo log. This implies that the redo log is active. The redo log could be open or closed.
    ACTIVE - Log is active but is not the current log. It is needed for crash recovery. It may be in use for block recovery. It might or might not be archived.
    CLEARING - Log is being re-created as an empty log after an ALTER DATABASE CLEAR LOGFILE statement. After the log is cleared, the status changes to UNUSED.
    CLEARING_CURRENT - Current log is being cleared of a closed thread. The log can stay in this status if there is some failure in the switch such as an I/O error writing the new log header.
    INACTIVE - Log is no longer needed for instance recovery. It may be in use for media recovery. It might or might not be archived.
    no archive mode에서도 복구하는 여러가지 방법들이 있기는 합니다.
    예를들어 current redo log가 깨졌을 때에 recovery 방법이라던지
    등등이 문서에 있긴하지요. 하지만 no archivemode에서 백업을 붓고
    복구하는 방법은 찾아보기 힘드실 것입니다. 위에서도 말씀드렸듯이
    no archive mode에서
    v$recover_file의 CHANGE# > v$logl의 minimum FIRST_CHANGE# 이면 데이터파일은 복구가능합니다.
    그러나 CHANGE# <= minimum FIRST_CHANGE# 이면 복구 불가능합니
    다. 그러니 백업을 붓고 복구를 하는 방법에 대한 문서는 거의
    찾기 힘듭니다. advance 방법에 대한 문서에서만 adjust_scn을 쓴다던지 하는 등이 나와있을 뿐입니다.
    글 수정:
    민천사(민연홍)
    아무래도 졸면서 썼나봅니다.;;
    interval과 timeout은 엄연히 다른데요. 왜 timeout과 interval을
    혼동했는지..;;
    LOG_CHECKPOINT_INTERVAL specifies the frequency of checkpoints in terms of the number of redo log file blocks that can exist between an incremental checkpoint and the last block written to the redo log. This number refers to physical operating system blocks, not database blocks.
    LOG_CHECKPOINT_TIMEOUT specifies (in seconds) the amount of time that has passed since the incremental checkpoint at the position where the last write to the redo log (sometimes called the tail of the log) occurred. This parameter also signifies that no buffer will remain dirty (in the cache) for more than integer seconds.

  • Redo logs switches too frequent after migrating the db to different server

    Dear Experts,
    A couple of days back, we migrated our database (belonging to EBusiness Suite) to a different server, to get good performance benefit. The database is 10.2.0.4 and it was migrated from AIX 5.3 to Linux x86 64.
    Users are happy with the performance, but I am getting below errors in the alert logs
    a) Thread 1 cannot allocate new log, sequence 498
    b) Private strand flush not complete
    c) ORACLE Instance PROD - Can not allocate log, archival requiredOracle support is saying the issue is coming because of too frequent log switches. I am wondering how the log switches has become frequent in the new server. In the old server it was about 10 mins for every switch, now it is as frequent as 1 minute?
    Any idea, what could be the reason behind this? Do you agree this issue is coming because frequent log switches?
    Thanks
    ARS

    Kanchana Devasurendra wrote:
    Hi ARS,
    Please check the following item in your new database.
    1. log_archive_max_processes Most properbly value set for this parameter is low ( may be it's set to 1.) Please increase up ( 4)I am curious to know what makes you think 4 is the right magic number for log_archive_max_processes - after all, he's only got one archive destination.
    Regards
    Jonathan Lewis
    http://jonathanlewis.wordpress.com
    http://www.jlcomp.demon.co.uk
    A general reminder about "Forum Etiquette / Reward Points": http://forums.oracle.com/forums/ann.jspa?annID=718
    If you never mark your questions as answered people will eventually decide that it's not worth trying to answer you because they will never know whether or not their answer has been of any use, or whether you even bothered to read it.
    It is also important to mark answers that you thought helpful - again it lets other people know that you appreciate their help, but it also acts as a pointer for other people when they are researching the same question, moreover it means that when you mark a bad or wrong answer as helpful someone may be prompted to tell you (and the rest of the forum) what's so bad or wrong about the answer you found helpful.

Maybe you are looking for

  • PKCS#11 driver dll and Java

    Hello! I'm trying to use a smartcard to do some signing and this needs to be done using Java. I have read about the SUN PKCS#11 provider and thought that this would work. However as it turns out my card vendor refuses to provide me with a pkcs#11 .dl

  • Why do my monitor stay in sleep mold?

     Monitor Status shows: I havea HP 2009 m monitor and Pavilion Slimline s5220f pc, when I turn on my monitor it keeps on say DVI: no signal, VGA:no signal, Auto-switch Sourcen,DefaultSource: DVI-DIGITAL and the  monitors reads, monitor going to sleep.

  • Why do I have to double tap my apps now?

    My iPhone is acting crazy.  Can't slide any screen or touch to open apps.

  • How to restrict permissions for individual business object fields?

    I know that ACE can restrict permissions (read/write/delete) for entire business objects (Business Partner, Opportunity, Activity...). Is it possible to assign security permissions (read/write) to individual attributes of business objects? For exampl

  • Incorrect link for Resources for  DBAs OPEN Source

    current link takes you to http://www.oracle.com/technology/tech/opensource/projects.html should be http://www.oracle.com/technology/community/opensource_projects.html regards DEspina