Problem about "Checkpoint not complete"

Dear Friends ,
I got the following error in my database 2 or 3 times a day . The error is :
Current log# 1 seq# 4127 mem# 0: /dbfs/oradata/ababil/redo01.log
Thread 1 cannot allocate new log, sequence 4128
Checkpoint not complete
I am using Oracle 10g database server where each redo log file size is 512 MB , and each of the file contains ONE member .
Our production server is used in a Private BANK .
In this moment How can I resolve this problem ?

Hi,
Girish, I will try to figure out and you tell me the which is best.
Adding the Space or Size to the Existing Redo Log File Size, it will be effect the some time slack for performing the
Checkpoint as the Case concern with OP.
While comparing with scenario where we are adding the Extra Redo Log File, where the one extra Check point will increase in Cycle and as with respective need size/ space is increased (in terms), but the size of existence file is not changed.
I think better to add an Extra Redo Log File, Instead of increasing the Size of present Redo log file.
Let me know what you think... and please post your concerns and Suggestions.
- Pavan Kumar N

Similar Messages

  • Checkpoint not complete error in alert log

    version : 10.2.0.5 , 11.2.0.2
    This is what I found about "Checkpoint not complete" from google
    "+This message indicates that Oracle wants to reuse a redo log file, but the current checkpoint position is still in that log. In this case, Oracle must+
    +wait until the checkpoint position passes that log. Because the incremental checkpoint target never lags the current log tail by more than 90%+
    +of the smallest log file size, this situation may be encountered if DBWR writes too slowly, or if a log switch happens before the log is completely full,+
    +or if log file sizes are too small.+ "
    Question1.
    What do they mean by Oracle reusing a redo log file ? When one ORL is full , oracle will switch to the next one ; it won't reuse it. Right ?
    Question2.
    "the current checkpoint position is still in that log" . What is checkpoint position ?
    Question3. How often does a checkpoint occur ? (frequency as per time)

    Question1.
    What do they mean by Oracle reusing a redo log file ? When one ORL is full , oracle will switch to the next one ; it won't reuse it. Right ?You have some groups of redo log, each redo log has members with same information. Redo log run in a circular way, when a group is full, changes to the next group of redo log and when the last group is written continue overwritten the first group.
    http://docs.oracle.com/cd/B28359_01/server.111/b28310/onlineredo001.htm
    Question2.
    "the current checkpoint position is still in that log" . What is checkpoint position ?copy and paste from:
    http://docs.oracle.com/cd/E14072_01/server.112/e10713/startup.htm#BABGDACG
    "A data structure that indicates the checkpoint position, which is the SCN in the redo stream where instance recovery must begin"
    Question3. How often does a checkpoint occur ? (frequency as per time)Checkpoints occur in diferents situations, not per time, please check:
    http://docs.oracle.com/cd/E11882_01/server.112/e16508/startup.htm#CNCPT89045

  • Oracle 10G Checkpoint not complete Cannot allocate new log

    We have an oracle 10G database that has 4 groups of 200M redo logs. We are constantly seeing Checkpoint not complete followed by Cannot allocate new log.. messages in the alert log. When I look at the v$instance_recovery table I see this:
    SQL> select WRITES_MTTR, WRITES_LOGFILE_SIZE, WRITES_LOG_CHECKPOINT_SETTINGS, WRITES_OTHER_SETTINGS,
    2 WRITES_AUTOTUNE, WRITES_FULL_THREAD_CKPT from v$instance_recovery;
    WRITES_MTTR WRITES_LOGFILE_SIZE WRITES_LOG_CHECKPOINT_SETTINGS
    WRITES_OTHER_SETTINGS WRITES_AUTOTUNE WRITES_FULL_THREAD_CKPT
    0 0 66329842
    0 309461 41004
    It seems most of our checkpointing is being caused by the log_checkpoint_interval being set to 10000, which means we are doing 20 checkpoints during one redo log since our OS blocksize is 1024. What I'm thinking about doing is first adding two more redo log groups, and then either increasing the log_checkpoint_interval to 40000 (5 checkpoints for one redo log) or unsetting log_checkpoint_interval and setting fast_start_mttr_target to 600. Which would be the recommended parameter change? I think Oracle recommends using the fast_start_mttr_target. Are there any other suggestions?

    Hi
    >>unsetting log_checkpoint_interval and setting fast_start_mttr_target to 600.
    its a better idea,look on it
    http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams068.htm#REFRN10058
    Just set fast_start_mttr_target parameter.it will resolve ur problem.
    Thanks
    Kuljeet

  • Thread 1 cannot allocate new log, sequence 5720 Checkpoint not completed

    Hi,
    I can see a lot of messages like that:
    Thread 1 cannot allocate new log, sequence 5720
    Checkpoint not complete
    What is the problem?? I think is about permissions.
    What permissions do i need to give to log_archive_dest directory and redo log file directory??
    Is the only thing that i can see that coulb be the problem because my HP-UX change the permissions of some directories sometimes and the SYS ADMIN don´t know how and why.
    I can do:
    SQL> alter system switch logfile;
    System altered.
    SQL> alter system checkpoint;
    System altered.
    Tks,
    Paulo.

    Thread 1 cannot allocate new log, sequence 5720
    Checkpoint not complete
    What is the problem?Lgwr wants to switch to and reuse the "tail" redo group, but since checkpointing for that group is not yet completed, lgwr has to wait until all data, that the redo protects, has been written down to datafiles. This stops (temporarily) writing of redo from buffer to log files and you get that message in the alert.log.
    How many redo log groups and what is their size?

  • Warning - Checkpoint not complete

    Hi,
    We have been getting Checkpoint not complete warning in development every day when we run update chk. in DB13. It is completed succesffully with the above warning. To resolve this warning message, we tried by setting the parameters LOG_CHECKPOINT_INTERVAL = 0, LOG_BUFFER = 1048576. But still we are facing this problem. We have refered one note (79341) which talks about increasing the log file size. In production, the log file size is same development and there is no other difference, but it is getting completed succesffully in prd. But in development it is giving this warning.
    Can any one suggest on this?
    Regards.....Iyy

    Hello,
    A Checkpoint is a database event which synchronizes the modified data blocks in memory with the datafiles on disk.Depending on the number of datafiles in a database, a checkpoint can be a highly resource intensive operation.
    If FAST_START_MTTR_TARGET is specified, LOG_CHECKPOINT_INTERVAL should not be set or set to 0.
    To your concern between Prod and Dev you need to look in to redo logs switch how frequently it is.Then you can look in to actions.
    Checkpoint not complete  in Dev might be becoz DBWR writes too slowly, or log switch happens before the log is completely full.
    So it depends on database activity.So ou can consider option of resizing logfile.
    Regards
    Vinod

  • Checkpoint not complete + db_writer_processes/dbwr_io_slaves

    Hi,
    Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option.
    After I noticed this error into the alert log:
    Thread 2 cannot allocate new log, sequence 152831
    Checkpoint not complete
    Current log# 17 seq# 152830 mem# 0: +ONLINELOG/evodb/onlinelog/group_17.272.729333887
    Thread 2 advanced to log sequence 152831
    Current log# 14 seq# 152831 mem# 0: +ONLINELOG/evodb/onlinelog/group_14.269.729333871
    And read a lot to understand the real cause (for the moment I increased the the redolog file from 5 to 7 (250mb each)).
    As it seems I've no problem with the ARCH processes, I read that the cause can be the DBWR0 process that is not "fast" enough to write block I've into redos, and free them for archiving.
    I read then something about the asynchronous I/O, and how db_writer_processes/dbwr_io_slaves can simulate the async write to disk.
    I think I understood the difference between db_writer_processes and dbwr_io_slaves.
    My question is how I can understand if my database needs more DBWR process.
    At the moment my configuration is:
    db_writer_processes 1
    dbwr_io_slaves 0
    Thanks in advance,
    Samuel

    Hi Samuel,
    There is still a major confusion on your side concerning the DBWR. It will NOT write data from your redo buffers to the redo logs, since it is the job of the LGWR.
    When a log switch occurs (so, you will use a different redo group), then it is the job of the ARCn process(es) to backup the 'used' redo log to a archive log.
    When your ARCn process(es) are not fast enough, and a log swicth occurs, it may happen that you have no inactive (read archived) redo group.... then Oracle 'hangs' till it can find such a redo group available.
    So, you may want to add 1 (or more) redo group, or increase the size of the redo log files, or have more archiver processes.
    DBWr job is to write dirty database blocks back to datafiles.
    CKPT also works independently of the LGWR and DBWR.
    Check this:
    http://www.dbasupport.com/forums/archive/index.php/t-5351.html
    And another couple of links:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/process.htm
    Concepts of checkpoint, dbwr, lgwr processes
    HTH,
    Thierry
    Edited by: Urgent-IT on Feb 10, 2011 5:33 PM
    Added mote about CKPT + link
    Edited by: Urgent-IT on Feb 10, 2011 5:37 PM
    Added another 2 links

  • "checkpoint not complete" in alert log file.

    Hi, all.
    I have got a message of "Checkpoint not complete" in alert log file.
    Thread 2 advanced to log sequence 531
    Current log# 7 seq# 531 mem# 0: \\.\REDO231
    Current log# 7 seq# 531 mem# 1: \\.\REDO232
    Thread 2 cannot allocate new log, sequence 532
    Checkpoint not complete
    Current log# 7 seq# 531 mem# 0: \\.\REDO231
    Current log# 7 seq# 531 mem# 1: \\.\REDO232
    I searched "Checkpoint not complete" issue in this forum.
    As solutions,
    1. add more redo log groups
    2. increase the size of redo log
    3. check I/O contention
    4. set LOG_CHECKPOINT_INTERVAL, LOG_CHECKPOINT_TIMEOUT or
    FAST_START_MTTR_TARGET
    I think No.4 is the possible first approach in our environment.
    I think No.1 and No2 are not the ploblems in our environment.
    I ask the above issue oracle support center, but
    I was told that "if you are not getting this message frequently, you do not need to worry about it" from an oracle engineer.
    Is this true?? If I am not getting this message frequently, there is no problem
    in terms of database integrity, consistency, and performance?
    I will be waiting for your advice and experience in real life.
    Thanks and Regards.

    Redo Log Tuning Advisory and Automatic Checkpoint Tuning are new features introduced in Oracle 10G, if you are on 10g you may benefit from these features.
    The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance, however it must balanced out with the expected recovery time. Undersized log files increase checkpoint activity and increase CPU usage. As rule of thumb switching logs at most once every fifteen minutes.
    Checkpoint frequency is affected by several factors, including log file size and the setting of the FAST_START_MTTR_TARGET initialization parameter. 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 redo logfile sizing advisory is specified by column optimal_logfile_size of v$instance_recovery. This feature require setting the parameter "fast_start_mttr_target" for the advisory to take effect and populate the column optimal_logfile_size.
    Also you can obtain redo sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control.
    To enable automatic checkpoint tuning, unset FAST_START_MTTR_TARGET or set it to a nonzero value(This is measured in seconds and by default, this feature is not enabled, because FAST_START_MTTR_TARGET has a default value of 0). If you set this parameter to zero this feature will be disabled. When you enable fast-start checkpointing, remove or disable(set to 0) the following initialization parameters:
    - LOG_CHECKPOINT_INTERVAL
    - LOG_CHECKPOINT_TIMEOUT
    - FAST_START_IO_TARGET
    Enabling fast-start checkpointing can be done statically using the initialization files or dynamically using -
    SQL> alter system set FAST_START_MTTR_TARGET=10;
    Best regards.

  • Thread 1 cannot allocate new log, sequence 714 - Checkpoint not complete

    I'm working in a Oracle 10g database, running on RHEL. The alert_*.log file is putting out this type of text for the past few months:
    Thread 1 advanced to log sequence 713 (LGWR Switch)
    Current log#2 seq# 713 mem# 0: /dbfiles/..../onlinelog/filename.log
    Current log #2 ..........
    Thread 1 cannot allocate new log, sequence 714
    Checkpoint not complete
    Any ideas to get me pointed in the right direction is appreciated,
    Thank you in advance,
    Wes

    The immediate fixes Vishal suggests are the standard answer, but there is more to it, as the MOS doc he references shows. Additional questions I would ask:
    How long is the delay between the inability to switch and when it actually switches? How many datafiles do you have? What is waiting in the db?
    In general, I find making log files sized for the rare massive updates, then using the built-in timeouts to switch every 20 or 30 minutes (depending on management recoverability expectations), helps avoid some of these problems. More specifically, run a statspack or awr (if licensed) report for maybe an hour during heavy times, and see what it thinks the waits are. Tuning is an iterative process, and sometimes different things can cause similar symptoms. Sometimes fixing the biggest problem (which is often poor SQL) can radically change the symptoms observed. Other times you find you have dying hardware, or someone messed up a switch configuration.

  • Checkpoint not complete;;cannot allocate new log ;;; PLZ HELP ME

    Hi all,
    We are working on Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 on a Redhat Linux Server platform.
    We are facing the following problem in the alert.log file :
    Wed Aug 22 02:58:57 2007
    Thread 1 cannot allocate new log, sequence 43542
    Checkpoint not complete
    Current log# 1 seq# 43541 mem# 0: /u01/oradata/DB01/redo01.log
    Thread 1 advanced to log sequence 43542
    Current log# 4 seq# 43542 mem# 0: /u01/oradata/DB01/redo04.log
    Current log# 4 seq# 43542 mem# 1: /u01/oraindx/DB01/redo04.log
    Wed Aug 22 03:00:00 2007
    Thread 1 advanced to log sequence 43543
    Current log# 5 seq# 43543 mem# 0: /u01/oradata/DB01/redo05.log
    Current log# 5 seq# 43543 mem# 1: /u01/oraindx/DB01/redo05.log
    Wed Aug 22 03:01:00 2007
    Thread 1 cannot allocate new log, sequence 43544
    Checkpoint not complete
    Current log# 5 seq# 43543 mem# 0: /u01/oradata/DB01/redo05.log
    Current log# 5 seq# 43543 mem# 1: /u01/oraindx/DB01/redo05.log
    Thread 1 advanced to log sequence 43544
    Current log# 6 seq# 43544 mem# 0: /u01/oradata/DB01/redo06.log
    Current log# 6 seq# 43544 mem# 1: /u01/oraindx/DB01/redo06.log
    Wed Aug 22 03:01:26 2007
    Thread 1 advanced to log sequence 43545
    Current log# 2 seq# 43545 mem# 0: /u01/oradata/DB01/redo02.log
    Thread 1 advanced to log sequence 43546
    Current log# 3 seq# 43546 mem# 0: /u01/oradata/DB01/redo03.log
    Thread 1 advanced to log sequence 43547
    Current log# 1 seq# 43547 mem# 0: /u01/oradata/DB01/redo01.log
    Wed Aug 22 03:01:38 2007
    Thread 1 cannot allocate new log, sequence 43548
    Checkpoint not complete
    Current log# 1 seq# 43547 mem# 0: /u01/oradata/DB01/redo01.log
    I know that this message indicates that Oracle wants to reuse a redo log file, but
    the current checkpoint position is still in that log. In this case, Oracle must
    wait until the checkpoint position passes that log. Because the
    incremental checkpoint target never lags the current log tail by more than 90%
    of the smallest log file size, this situation may be encountered :
    1-if DBWR writes too slowly,
    or
    2-if a log switch happens before the log is completely full,
    or
    3-if log file sizes are too small.
    I read some posts in this forum regarding this error but sincerly i don't know how to find the exact cause of this error? Maybe Should I add new redo files or one new redo group? I don't know how to resolve it :( ;;;
    such as I have 6 redo files 3 of them 5MB size and the others 3 files 10MB size ;
    Thank you,
    Regards,
    Message was edited by:
    HAGGAR

    Make DBWR write more aggressively - as you are on 9i the parameter I would use is FAST_START_MTTR_TARGET=(how long you want recovery to take in seconds), the lower that number, the more aggressively DBWR has to write to keep up with the target, the advantage of this is that by the time LGWR comes to overwrite the redo log file, the chances are that DBWR has already written the "high scn#" (and beyond) from the checkpoint q.
    -- This disadvantage is that you will get more I/O to your disks.
    2. Create more redo log file groups - this will give DBWR more time to write before LGWR tries to overwrite a particular redolog file, again the chances are that the extra (6th) or (7th) group will give CKPT enough time to completely checkpoint beyond the "highest scn#" before that group is again required..
    Which one to go for.. well that's up to you and your setup, if you have an I/O bound system then 2. would be better for you, as 1. will just increase your I/O problem, however if physical space is an issue and I/O isn't then 1. might be better (with the added advantage that instance recovery will also be faster).
    Sorry for the training session, but as with everything to do with Oracle, there is rarely one solution that apply to everyone...
    Gopu

  • CHECKDB-Checkpoint not complete

    Hello,
    After upgrade to oracle 10.2.0.4 from 9.2.0.8 when i run the CHECKDB i get a warning message as follows.
    BR0974I Checking database messages in G:\ORACLE\PRD\SAPTRACE\BACKGROUND\alert_prd.log ...         
    BR0976W Database message alert - level: WARNING, line: 6335083, time: 2008-09-17 21.46.09, message:
    Checkpoint not complete                                                                           
    BR0976W Database message alert - level: WARNING, line: 6335095, time: 2008-09-17 21.46.10, message:
    Checkpoint not complete                                                                           
    BR0976W Database message alert - level: WARNING, line: 6335108, time: 2008-09-17 21.46.32, message:
    Checkpoint not complete                                                                           
    BR0976W Database message alert - level: WARNING, line: 6335190, time: 2008-09-17 23.10.25, message:
    Checkpoint not complete                                                                           
    BR0976W Database message alert - level: WARNING, line: 6335203, time: 2008-09-17 23.10.40, message:
    Checkpoint not complete                                                                           
    BR0976W Database message alert - level: WARNING, line: 6335216, time: 2008-09-17 23.10.58, message:
    Checkpoint not complete                                                                           
    BR0976W Database message alert - level: WARNING, line: 6335229, time: 2008-09-17 23.12.17, message:
    Checkpoint not complete                                                                               
    Why is this occuring?
    When i run it again immediately this warning message goes off?
    Please give some idea why it is so?
    Regards,
    Siddhartha RV.

    Hi,
    this problem is related to redolog file size ,Increass the size of redolog files.
    For more information .please followup the snote 79341.
    click on below link
    [https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=79341]
    karan

  • Error CheckPoint not complete .

    Hi Guru's
    Could some one advice how to solve this problem which is found in the trace file ..
    psvdbsp01 (oracle)[gisp]/db/gisp/dba/bdump$: tail -300 alert_gisp.log
    Thread 1 cannot allocate new log, sequence 262393
    Checkpoint not complete
    Current log# 3 seq# 262392 mem# 0: /db/gisp/redolog/gisp_redo_3a.dbf
    Current log# 3 seq# 262392 mem# 1: /db/gisp/mirrlog/gisp_redo_3b.dbf
    Tue Mar 12 12:31:19 2013
    Thread 1 advanced to log sequence 262393 (LGWR switch)
    Current log# 4 seq# 262393 mem# 0: /db/gisp/redolog/gisp_redo_4a.dbf
    Current log# 4 seq# 262393 mem# 1: /db/gisp/mirrlog/gisp_redo_4b.dbf
    Tue Mar 12 12:42:51 2013
    Starting control autobackup
    Control autobackup written to SBT_TAPE device
    comment 'API Version 2.0,MMS Version 5.4.1.0',
    media '5950'
    handle 'GISP_auto_cf_bkup_20130312_c-1206537362-20130312-02'
    Tue Mar 12 12:44:29 2013
    Thread 1 cannot allocate new log, sequence 262394
    Checkpoint not complete
    Current log# 4 seq# 262393 mem# 0: /db/gisp/redolog/gisp_redo_4a.dbf
    Current log# 4 seq# 262393 mem# 1: /db/gisp/mirrlog/gisp_redo_4b.dbf
    Tue Mar 12 12:44:29 2013
    Thread 1 advanced to log sequence 262394 (LGWR switch)
    Current log# 1 seq# 262394 mem# 0: /db/gisp/redolog/gisp_redo_1a.dbf
    Current log# 1 seq# 262394 mem# 1: /db/gisp/mirrlog/gisp_redo_1b.dbf
    Tue Mar 12 12:44:29 2013
    Thread 1 advanced to log sequence 262395 (LGWR switch)
    Current log# 2 seq# 262395 mem# 0: /db/gisp/redolog/gisp_redo_2a.dbf
    Current log# 2 seq# 262395 mem# 1: /db/gisp/mirrlog/gisp_redo_2b.dbf
    Tue Mar 12 12:44:30 2013
    Thread 1 advanced to log sequence 262396 (LGWR switch)
    Current log# 3 seq# 262396 mem# 0: /db/gisp/redolog/gisp_redo_3a.dbf
    Current log# 3 seq# 262396 mem# 1: /db/gisp/mirrlog/gisp_redo_3b.dbf
    Thread 1 cannot allocate new log, sequence 262397
    Checkpoint not complete
    Current log# 3 seq# 262396 mem# 0: /db/gisp/redolog/gisp_redo_3a.dbf
    Current log# 3 seq# 262396 mem# 1: /db/gisp/mirrlog/gisp_redo_3b.dbf
    Tue Mar 12 12:44:30 2013
    Thread 1 advanced to log sequence 262397 (LGWR switch)
    Current log# 4 seq# 262397 mem# 0: /db/gisp/redolog/gisp_redo_4a.dbf
    Current log# 4 seq# 262397 mem# 1: /db/gisp/mirrlog/gisp_redo_4b.dbf
    Thread 1 cannot allocate new log, sequence 262398
    Checkpoint not complete
    Current log# 4 seq# 262397 mem# 0: /db/gisp/redolog/gisp_redo_4a.dbf
    Current log# 4 seq# 262397 mem# 1: /db/gisp/mirrlog/gisp_redo_4b.dbf
    Tue Mar 12 12:44:32 2013
    Thread 1 advanced to log sequence 262398 (LGWR switch)
    Current log# 1 seq# 262398 mem# 0: /db/gisp/redolog/gisp_redo_1a.dbf
    Current log# 1 seq# 262398 mem# 1: /db/gisp/mirrlog/gisp_redo_1b.dbf
    Thread 1 cannot allocate new log, sequence 262399
    Checkpoint not complete
    Current log# 1 seq# 262398 mem# 0: /db/gisp/redolog/gisp_redo_1a.dbf
    Current log# 1 seq# 262398 mem# 1: /db/gisp/mirrlog/gisp_redo_1b.dbf
    Tue Mar 12 12:44:32 2013
    Thread 1 advanced to log sequence 262399 (LGWR switch)
    Current log# 2 seq# 262399 mem# 0: /db/gisp/redolog/gisp_redo_2a.dbf
    Current log# 2 seq# 262399 mem# 1: /db/gisp/mirrlog/gisp_redo_2b.dbf
    Thread 1 cannot allocate new log, sequence 262400
    Checkpoint not complete
    Current log# 2 seq# 262399 mem# 0: /db/gisp/redolog/gisp_redo_2a.dbf
    Current log# 2 seq# 262399 mem# 1: /db/gisp/mirrlog/gisp_redo_2b.dbf
    And the archive log list show's there is a lag in the sequence number ..
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /db/gisp/archive_logs_rman/
    Oldest online log sequence 262432
    Next log sequence to archive 262435
    Current log sequence 262435
    SQL>
    Any expert suggestion is highly apprciated .
    Thanks
    Edited by: 790072 on 13/03/2013 15:18

    Hi,
    10Mb for logfile is very low.
    You can check logswitch using this query:
    SELECT SUM (DECODE (TO_CHAR (first_time, 'hh24'), '00', 1, 0)) "h0",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '01', 1, 0)) "h1",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '02', 1, 0)) "h2",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '03', 1, 0)) "h3",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '04', 1, 0)) "h4",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '05', 1, 0)) "h5",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '06', 1, 0)) "h6",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '07', 1, 0)) "h7",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '08', 1, 0)) "h8",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '09', 1, 0)) "h9",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '10', 1, 0)) "h10",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '11', 1, 0)) "h11",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '12', 1, 0)) "h12",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '13', 1, 0)) "h13",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '14', 1, 0)) "h14",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '15', 1, 0)) "h15",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '16', 1, 0)) "h16",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '17', 1, 0)) "h17",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '18', 1, 0)) "h18",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '19', 1, 0)) "h19",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '20', 1, 0)) "h20",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '21', 1, 0)) "h21",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '22', 1, 0)) "h22",
             SUM (DECODE (TO_CHAR (first_time, 'hh24'), '23', 1, 0)) "h23"
        FROM V$log_history
    GROUP BY TRUNC (first_time), TO_CHAR (first_time, 'Dy')
    ORDER BY 1;Oracle suggest 1 logswitch every 20 minutes, 3 per hour.
    Please post the output of my query.
    Regards

  • Another 'Checkpoint not complete' case ....

    Hi;
    I getting some 'Checkpoint not complete' in log alert. This is not frecuently, however I understand this is not good.
    my DB is Oracle 10G, RAC, two nodes.
    I executed the next query, but I'm not clear how to determine the redo logs files size.
    Can anybody explain me, if these values are OK?
    SQL> set linesize 200
    SQL> select * from v$log;
    GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARC STATUS FIRST_CHANGE# FIRST_TIM
    1 1 8630 52428800 1 NO CURRENT 1320381521 16-MAR-10
    2 1 8629 52428800 1 YES INACTIVE 1320220450 16-MAR-10
    3 2 11341 52428800 1 NO CURRENT 1320386723 16-MAR-10
    4 2 11340 52428800 1 YES INACTIVE 1320242239 16-MAR-10
    Also, I executed the next query that somebody sent me, but the optimal size is empty.
    SQL> SELECT TARGET_MTTR,ESTIMATED_MTTR,WRITES_MTTR,WRITES_LOGFILE_SIZE, OPTIMAL_LOGFILE_SIZE FROM V$INSTANCE_RECOVERY;
    TARGET_MTTR ESTIMATED_MTTR WRITES_MTTR WRITES_LOGFILE_SIZE OPTIMAL_LOGFILE_SIZE
    0 16 0 13413
    As I explained previuosly, this problem is not frecuently, occurs two times in month, but my DB is not used at full capacity, but sometimes is experiencing some slowness, I don't know if fixing this, can help to solve this problem.
    I was reading this thread, Checkpoint not complete but still I'm confused.
    These are my doubts;
    How can I determine the exact redo log files, I got now? I think is 2, but I'm not sure.
    If I want to change that, to increase the redo size, how can I do that?
    Does the DB needs to be shutdown to change this?
    Thanks for your help.
    Regards;
    ANG

    How can I determine the exact redo log files, I got now? I think is 2, but I'm not sure. You have 4 redo log groups, with 1 redologfile per group.
    select member from v$logfile;
    If I want to change that, to increase the redo size, how can I do that? You can resize the redolog file size by, Checking here
    http://www.idevelopment.info/data/Oracle/DBA_tips/Database_Administration/DBA_34.shtml
    Does the DB needs to be shutdown to change this?Nope. The database can be online.
    HTH
    -Anantha

  • Checkpoint not complete 10g

    Hi guys,
    I have problem with big number of archived logs in 10.2.0.3 64bit database, so i have investigate a bit and found out that redolgs members size are 16 mb each, and when i looked in alert log i have found this:
    Thu Sep 15 07:49:49 2011
    Thread 1 cannot allocate new log, sequence 10611
    Checkpoint not complete Current log# 1 seq# 10610 mem# 0: /db/rd01/redo01.log
    Current log# 1 seq# 10610 mem# 1: /db/rd02/redo11.rdo
    Thread 1 advanced to log sequence 10611
    Current log# 2 seq# 10611 mem# 0: /db/rd01/redo02.log
    Current log# 2 seq# 10611 mem# 1: /db/rd02/redo22.rdo
    Thu Sep 15 07:50:01 2011
    Thread 1 advanced to log sequence 10612
    Current log# 3 seq# 10612 mem# 0: /db/rd01/redo03.log
    Current log# 3 seq# 10612 mem# 1: /db/rdo33/redo33.rdo
    Thread 1 cannot allocate new log, sequence 10613
    Checkpoint not complete Current log# 3 seq# 10612 mem# 0: /db/rd01/redo03.log
    Current log# 3 seq# 10612 mem# 1: /db/rd02/redo33.rdo
    Thu Sep 15 07:50:15 2011
    Thread 1 advanced to log sequence 10613
    Current log# 1 seq# 10613 mem# 0: /db/rd01/redo01.log
    Current log# 1 seq# 10613 mem# 1: /db/rd02/redo11.rdo
    Thread 1 advanced to log sequence 10614
    Current log# 2 seq# 10614 mem# 0: /db/rd01/redo02.log
    Current log# 2 seq# 10614 mem# 1: /db/rd02/redo22.rdo
    Then i have resized logfiles to 50mb and now i have this in my alert log:
    Thread 1 advanced to log sequence 14377
    Current log# 3 seq# 14377 mem# 0: /db/rd01/redo03.log
    Current log# 3 seq# 14377 mem# 1: /db/rd02/redo33.rdo
    Fri Sep 16 13:26:08 2011
    Thread 1 cannot allocate new log, sequence 14378
    Checkpoint not complete
    Current log# 3 seq# 14377 mem# 0: /db/rd01/redo03.log
    Current log# 3 seq# 14377 mem# 1: /db/rd02/redo33.rdo
    Thread 1 advanced to log sequence 14378
    Current log# 1 seq# 14378 mem# 0: /db/rd01/redo01.log
    Current log# 1 seq# 14378 mem# 1: /db/rd02/redo11.rdo
    Fri Sep 16 13:27:00 2011
    Thread 1 cannot allocate new log, sequence 14379
    Checkpoint not complete
    Current log# 1 seq# 14378 mem# 0: /db/rd01/redo01.log
    Current log# 1 seq# 14378 mem# 1: /db/rd02/redo11.rdo
    Thread 1 advanced to log sequence 14379
    Current log# 2 seq# 14379 mem# 0: /db/rd01/redo02.log
    Current log# 2 seq# 14379 mem# 1: /db/rd02/redo22.rdo
    Im aware that my redologs are too small, but how to determine best size? I have try this query:
    select ACTUAL_REDO_BLKS,TARGET_REDO_BLKS,TARGET_MTTR,ESTIMATED_MTTR,
    OPTIMAL_LOGFILE_SIZE,CKPT_BLOCK_WRITES  from v$instance_recovery;
    ACTUAL_REDO_BLKS TARGET_REDO_BLKS TARGET_MTTR ESTIMATED_MTTR OPTIMAL_LOGFILE_SIZE CKPT_BLOCK_WRITES
    184,003     184,320     0     15          1,187,991
    but it didnt gave me anything for OPTIMAL_LOGFILE_SIZE!
    Any ideas?

    rootsman wrote:
    Hi guys,
    I have problem with big number of archived logs in 10.2.0.3 64bit database, so i have investigate a bit and found out that redolgs members size are 16 mb each, and when i looked in alert log i have found this:
    Thu Sep 15 07:49:49 2011
    Thread 1 cannot allocate new log, sequence 10611
    Checkpoint not complete Current log# 1 seq# 10610 mem# 0: /db/rd01/redo01.log
    Current log# 1 seq# 10610 mem# 1: /db/rd02/redo11.rdo
    Thread 1 advanced to log sequence 10611
    Current log# 2 seq# 10611 mem# 0: /db/rd01/redo02.log
    Current log# 2 seq# 10611 mem# 1: /db/rd02/redo22.rdo
    Thu Sep 15 07:50:01 2011
    Thread 1 advanced to log sequence 10612
    Current log# 3 seq# 10612 mem# 0: /db/rd01/redo03.log
    Current log# 3 seq# 10612 mem# 1: /db/rdo33/redo33.rdo
    Thread 1 cannot allocate new log, sequence 10613
    Checkpoint not complete Current log# 3 seq# 10612 mem# 0: /db/rd01/redo03.log
    Current log# 3 seq# 10612 mem# 1: /db/rd02/redo33.rdo
    Thu Sep 15 07:50:15 2011
    Thread 1 advanced to log sequence 10613
    Current log# 1 seq# 10613 mem# 0: /db/rd01/redo01.log
    Current log# 1 seq# 10613 mem# 1: /db/rd02/redo11.rdo
    Thread 1 advanced to log sequence 10614
    Current log# 2 seq# 10614 mem# 0: /db/rd01/redo02.log
    Current log# 2 seq# 10614 mem# 1: /db/rd02/redo22.rdo
    Then i have resized logfiles to 50mb and now i have this in my alert log:
    Thread 1 advanced to log sequence 14377
    Current log# 3 seq# 14377 mem# 0: /db/rd01/redo03.log
    Current log# 3 seq# 14377 mem# 1: /db/rd02/redo33.rdo
    Fri Sep 16 13:26:08 2011
    Thread 1 cannot allocate new log, sequence 14378
    Checkpoint not complete
    Current log# 3 seq# 14377 mem# 0: /db/rd01/redo03.log
    Current log# 3 seq# 14377 mem# 1: /db/rd02/redo33.rdo
    Thread 1 advanced to log sequence 14378
    Current log# 1 seq# 14378 mem# 0: /db/rd01/redo01.log
    Current log# 1 seq# 14378 mem# 1: /db/rd02/redo11.rdo
    Fri Sep 16 13:27:00 2011
    Thread 1 cannot allocate new log, sequence 14379
    Checkpoint not complete
    Current log# 1 seq# 14378 mem# 0: /db/rd01/redo01.log
    Current log# 1 seq# 14378 mem# 1: /db/rd02/redo11.rdo
    Thread 1 advanced to log sequence 14379
    Current log# 2 seq# 14379 mem# 0: /db/rd01/redo02.log
    Current log# 2 seq# 14379 mem# 1: /db/rd02/redo22.rdo
    Im aware that my redologs are too small, but how to determine best size? I have try this query:
    select ACTUAL_REDO_BLKS,TARGET_REDO_BLKS,TARGET_MTTR,ESTIMATED_MTTR,
    OPTIMAL_LOGFILE_SIZE,CKPT_BLOCK_WRITES  from v$instance_recovery;
    ACTUAL_REDO_BLKS TARGET_REDO_BLKS TARGET_MTTR ESTIMATED_MTTR OPTIMAL_LOGFILE_SIZE CKPT_BLOCK_WRITES
    184,003     184,320     0     15          1,187,991
    but it didnt gave me anything for OPTIMAL_LOGFILE_SIZE!
    Any ideas?Add redo log members to avoid the "eckpoint not complete" issue.
    --neeraj                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Checkpoint not complete.. Please help

    Hi I am getting the following notification in my alert log..
    Oracle Version : 10.2.0.1.0
    Do I need to worry about this??
    Checkpoint not complete
    Current log# 6 seq# 18987 mem# 0: I:\ORACLE\ORADATA\AUTOPLNT\REDO06.LOG
    Current log# 6 seq# 18987 mem# 1: I:\ORACLE\ORADATA\AUTOPLNT\REDO_LOGS\REDO06A.LOG
    Thread 1 advanced to log sequence 18988
    Current log# 5 seq# 18988 mem# 0: I:\ORACLE\ORADATA\AUTOPLNT\REDO05.LOG
    Current log# 5 seq# 18988 mem# 1: I:\ORACLE\ORADATA\AUTOPLNT\REDO_LOGS\REDO05A.LOG
    Regards,
    Arun Kumar

    Usually its there after the hot backup.. along with the checkpoint message i am getting below notification also..
    Private strand flush not complete
    I think after hot backup the redologs are written as tablespaces were in backup mode.. Am i right?
    just now i found that it happens before hot backup also...
    as we do swicth log file before the backup also it might be occuring right?
    Rest of the day its smooth... no notification.. redo log files hardly switched for an hour..
    Please advice...
    Regards,
    Arun

  • Checkpoint not complete - BR0976W

    Recently, my SAP always got this error when I enter t-code DB14 and double click a "Database check" item :
    BR0976W Database message alert - level: WARNING, line: 1281, time: 2011-06-12 01.13.45, message : Checkpoint not complete
    I am using Oracle 9i, SAP Kernel release 640, archive log mode.
    What should I do now ?
    Add more log files ? Decrease the log switch frequency ?
    Any ideal ?

    Hello Ming,
    as Markus wrote check SAP note 79341, maybe you are affected by the problem described in section 5: "Selftune Checkpointing". This is quite common.
    The best way to prevent "checkpoint not complete" messages would be to speed up IO for the online redologs. Make sure that writing to disk is as fast as possible for your online redo logs. Most of the time slow IO causes these messages.
    Regards,
    Mark

Maybe you are looking for