Alert log ---Thread 1 cannot allocate new log, sequence 1697

数据库环境为：AIX 6.1，Oracle 10.2.0.1 64位，今天在查看oracle alert log时发现如下信息
Sun Apr 29 16:03:43 2012
Thread 1 cannot allocate new log, sequence 8
Checkpoint not complete
Current log# 3 seq# 7 mem# 0: /oradata/hb/redo03.log
Thread 1 advanced to log sequence 8
Current log# 1 seq# 8 mem# 0: /oradata/hb/redo01.log
Sun Apr 29 17:28:02 2012
Thread 1 advanced to log sequence 9
Current log# 2 seq# 9 mem# 0: /oradata/hbbredo02.log
Sun Apr 29 19:10:39 2012
Thread 1 advanced to log sequence 10
Current log# 3 seq# 10 mem# 0: /oradata/hb/redo03.log
Sun Apr 29 21:23:34 2012
Thread 1 advanced to log sequence 11
Current log# 1 seq# 11 mem# 0: /oradata/hb/redo01.log
Sun Apr 29 22:09:31 2012
Thread 1 cannot allocate new log, sequence 12
Private strand flush not complete
Current log# 1 seq# 11 mem# 0: /oradata/hb/redo01.log
Thread 1 advanced to log sequence 12
Current log# 2 seq# 12 mem# 0: /oradata/hb/redo02.log
Thread 1 advanced to log sequence 13
Current log# 3 seq# 13 mem# 0: /oradata/hb/redo03.log
Mon Apr 30 06:15:20 2012
Thread 1 advanced to log sequence 14
Current log# 1 seq# 14 mem# 0: /oradata/hb/redo01.log
Mon Apr 30 10:04:39 2012
Memory Notification: Library Cache Object loaded into SGA
Heap size 2919K exceeds notification threshold (2048K)
SQL> select * from v$logfile;
GROUP# STATUS TYPE
MEMBER
IS_
1 ONLINE
/oradata/hb/redo01.log
NO
2 ONLINE
/oradata/hb/redo02.log
NO
GROUP# STATUS TYPE
MEMBER
IS_
3 ONLINE
/oradata/hb/redo03.log
NO
数据库当前运行正常，请教一下，
1. 频繁出现的类似
Thread 1 cannot allocate new log, sequence 12
Private strand flush not complete
Current log# 1 seq# 11 mem# 0: /oradata/hb/redo01.log 是怎么造成的？是否需要处理，如果处理，该怎么做？
2。 Memory Notification: Library Cache Object loaded into SGA
Heap size 2919K exceeds notification threshold (2048K)显示heap 值超过设定的阀值，heap起什么作用，是否需要修改阀值，以消除这一"Memory Notification"?

Thread 1 cannot allocate new log, sequence 12
Private strand flush not complete
由"Private strand flush not complete"引起的 cannot allocate new log一般可以忽略， Private strand是10g引入的新特性
Heap size 2919K exceeds notification threshold (2048K)
该信息是由于 10.2.0.1 这个版本的默认 "_kgl_large_heap_warning_threshold" 参数过小， 一般可以忽略。
调整个 "_kgl_large_heap_warning_threshold" 参数和 升级到10.2.0.1 版本均可以 让该"Heap size 2919K exceeds notification threshold (2048K)"信息不再出现， 当然一般也可以忽略该问题

Similar Messages

  • In Noarchivelog mode "Thread 1 cannot allocate new log, sequence 3298"

    Hi,My database mode is noarchivelog but i see my alert.log "Thread 1 cannot allocate new log, sequence 3298"
    what it`s mean?
    I have enough disk space.

    This is very similar to the your still open thread cannot allocate new log, sequence
    Better protocol would surely be to acknowledge the references given then, and why you think they do or do not apply.
    Please get one of these threads marked as answered and continue on the other.
    Please also indicate:
    1) is your database hung.
    2) Output form this query:
    select log_mode from v$database;
    3) Database Version:
    4) Are there any other messages in alert log.
    5) In sqlplus connected as SYSDBA show output from
    archive log list
    Rgds - bigdelboy.

  • Thread 1 cannot allocate new log -- from alert log

    in my alert log file, I have noticed occasionally that this message was showing out during the business hour (8 am ~ 8 pm). Not often , maybe 3 or 4 times, but there are more during the midnight when system run some administration process such as KGL object name :SELECT /*+rule*/ SYS_XMLGEN(VALUE(KU$), XMLFORMAT.createFormat2('VIEW_T', '7')), KU$.OBJ_NUM ,K
    U$.SCHEMA_OBJ.NAME ,KU$.SCHEMA_OBJ.NAME ,'VIEW' ,KU$.SCHEMA_OBJ.OWNER_NAME FROM SYS.KU$_VIEW_VIEW KU$ WHERE KU$
    .OBJ_NUM IN (SELECT * FROM TABLE(DBMS_METADATA.FETCH_OBJNUMS(200001)))
    . My question is : Do I have to add another redo log file to system? and how much is proper?
    I also noticed there where message of "Memory Notification: Library Cache Object loaded into SGA
    Heap size 2829K exceeds notification threshold (2048K)" during that hours. Appreciate any advice. my system is 10g r2 on AIX 5.3 L.

    The "Thread cannot allocate new log" occurs more often off the regular hours due to system run process. It seems more regular occurring at evry 20 minutes. By OEM, I noticed thate there some system processes run at 2 am, 8 am, 2 pm, 8pm. for examples
    1) EMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS();
    2) MGMT_ADMIN_DATA.EVALUATE_MGMT_METRICS;
    3) SELECT /*+ USE_HASH(f a) */ SUM(NVL(F.BYTES - NVL(A.BYTES, 0), 0)/1024/1024), SUM(NVL(F.BYTES, 0)/1024/1024) FROM (SELECT DISTINCT TABLESPACE_NAME FROM USER_TABLES) U, (SELECT TABLESPACE_NAME, SUM(BYTES) BYTES FROM DBA_DATA_FILES GROUP BY TABLESPACE_NAME) F, (SELECT TABLESPACE_NAME, SUM(BYTES) BYTES FROM DBA_FREE_SPACE GROUP BY TABLESPACE_NAME) A WHERE A.TABLESPACE_NAME = U.TABLESPACE_NAME AND F.T...
    I wonder why they are necessary? or I have to ad one more redo log.

  • Thread 1 cannot allocate new log, sequence in Alert log

    Could someone help, I am getting the below message in my alert log
    System: AIX6.1 - Oracle 11r2
    GROUP#     THREAD#     MEMBER                                  ARCHIVED     STATUS             MB
    1     1     +DATA01/mydb/redolog_group1_member1     NO         INACTIVE             1536
    1     1     +DATA01/mydb/redolog_group1_member2     NO         INACTIVE             1536
    2     1     +DATA01/mydb/redolog_group2_member2     NO         CURRENT          1536
    2     1     +DATA01/mydb/redolog_group2_member1     NO         CURRENT          1536
    3     1     +DATA01/mydb/redolog_group3_member2     NO         INACTIVE             1536
    3     1     +DATA01/mydb/redolog_group3_member1     NO         INACTIVE             1536
    Tue Jul 10 18:37:48 2012
    Thread 1 advanced to log sequence 28831 (LGWR switch)
      Current log# 1 seq# 28831 mem# 0: +DATA01/mydb/redolog_group1_member1
      Current log# 1 seq# 28831 mem# 1: +DATA01/mydb/redolog_group1_member2
    Tue Jul 10 19:12:01 2012
    Thread 1 advanced to log sequence 28832 (LGWR switch)
      Current log# 2 seq# 28832 mem# 0: +DATA01/mydb/redolog_group2_member1
      Current log# 2 seq# 28832 mem# 1: +DATA01/mydb/redolog_group2_member2
    Tue Jul 10 19:39:00 2012
    Thread 1 cannot allocate new log, sequence 28833
    Private strand flush not complete
    Tue Jul 10 19:39:18 2012
      Current log# 2 seq# 28832 mem# 0: +DATA01/mydb/redolog_group2_member1
      Current log# 2 seq# 28832 mem# 1: +DATA01/mydb/redolog_group2_member2
    Tue Jul 10 19:41:21 2012
    Thread 1 advanced to log sequence 28833 (LGWR switch)
      Current log# 3 seq# 28833 mem# 0: +DATA01/mydb/redolog_group3_member1
      Current log# 3 seq# 28833 mem# 1: +DATA01/mydb/redolog_group3_member2
    Tue Jul 10 20:15:28 2012
    Thread 1 cannot allocate new log, sequence 28834
    Private strand flush not complete
      Current log# 3 seq# 28833 mem# 0: +DATA01/mydb/redolog_group3_member1
      Current log# 3 seq# 28833 mem# 1: +DATA01/mydb/redolog_group3_member2
    Tue Jul 10 20:16:21 2012Could an increase on the redo log file sizes solve this problem? Unfortunately I do not have a test platform, where I could have tested this.

    mseberg wrote:
    It just a warning. I would read these two notes:
    I suspect the OP is more worried about the apparent two minute gap between the "cannot switch" and the "advanced" at     19:39:18 and 19:41:12 respectively. Did the switch really have to wait for that two minutes, or is this a spurious threat caused by an anomaly in the writing of the alert log.
    As a cross check, I would examine v$event_histogram (or an AWR/Statspack for the interval) for time spent in the event "log file switch (private strand flush incomplete)". In prinicple I wouldn't expect to see waits longer than a few (less than 10) milliseconds; if the histogram shows long waits consistent with the alert log reports than I'd contact Oracle because something odd is happening.
    (Footnote - it's possible that the event times out after a limited interval, log file sync used to time out after 1 second and has recently changed to something shorter and adjustable, so 2 seconds may (for example) appear as 20 x 0.1 seconds.)
    Regards
    Jonathan Lewis

  • Thread ... cannot allocate new log, sequence ...

    I have an error in alert.log:
    Thread 1 cannot allocate new log, sequence ...
    Private strand flush not completeIs it dangerous?
    What does it mean?
    What can I do this mistake will disappear?

    select * from v$log;
    GROUP#,THREAD#,SEQUENCE#,BYTES,MEMBERS,ARCHIVED,STATUS,FIRST_CHANGE#,FIRST_TIME
    1,1,25921,1073741824,1,YES,INACTIVE,4582390708,16.05.2013 13:00:02
    2,1,25922,1073741824,1,YES,INACTIVE,4582566850,16.05.2013 13:27:17
    5,1,25923,1073741824,1,YES,INACTIVE,4582748298,16.05.2013 14:00:02
    4,1,25925,1073741824,1,NO,CURRENT,4582990596,16.05.2013 15:00:03
    3,1,25924,1073741824,1,NO,ACTIVE,4582954136,16.05.2013 14:54:42
    GROUP#,STATUS,TYPE,MEMBER,IS_RECOVERY_DEST_FILE
    1,,ONLINE,/opt/oracle/oradata/prod/redo01.log,NO
    2,,ONLINE,/opt/oracle/oradata/prod/redo02.log,NO
    3,,ONLINE,/opt/oracle/oradata/prod/redo03.log,NO
    4,,ONLINE,/opt/oracle/oradata/prod/redo04.log,NO
    5,,ONLINE,/opt/oracle/oradata/prod/redo05.log,NO
    SELECT optimal_logfile_size FROM   v$instance_recovery
    empty
    The last query result is:
    DAY,00,01,02,03,04,05,06,07,08,09,10,11,12,13,14,15,16,17,18,19,20,21,22,23,Total Switch
    05/01,   0,   0,   0,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   0,   0,   0,   0,17
    05/02,   0,   0,   0,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   0,   0,   0,   0,17
    05/03,   0,   1,   1,   1,   1,   1,   0,   0,   0,   0,   5,   3,   2,   0,   0,   1,   0,   0,   0,   0,   0,   0,   0,   2,18
    05/04,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,26
    05/05,   1,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,25
    05/06,   0,   1,   1,   1,   1,   1,   1,   1,   1,   2,   5,   2,   1,   1,   2,   6,   1,   1,   1,   1,   1,   1,   1,   2,36
    05/07,   0,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   3,   1,   1,   3,   2,   1,   1,   2,   1,   1,   1,   2,30
    05/08,   1,   2,   1,   1,   1,   1,   1,   1,   3,   5,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,   1,   1,   1,   2,33
    05/09,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,26
    05/10,   1,   1,   1,   1,   1,   1,   2,   1,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,   1,   1,   1,   2,28
    05/11,   1,   1,   1,   1,   2,   1,   1,   1,   1,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,27
    05/12,   1,   1,   1,   1,   1,   2,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   2,   1,   1,   1,   1,   0,25
    05/13,   0,   0,   0,   0,   0,   0,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,   1,18
    05/14,   0,   0,   0,   0,   0,   0,   1,   1,   2,   1,   4,   4,   2,   4,   1,   4,   1,   4,   1,   2,   1,   1,   1,   1,36
    05/15,   1,   0,   0,   0,   0,   0,   1,   1,   1,   1,   1,   3,   2,   1,   1,   1,   1,   1,   1,   6,   1,   1,   1,   1,27
    05/16,   0,   0,   0,   0,   0,   0,   1,   1,   3,   3,   2,   2,   1,   2,   2,   0,   0,   0,   0,   0,   0,   0,   0,   0,17

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

    Hi,
    from few days we have sometimes this message into alert. I've just try to increase the size of redo log file but without success, have you got any idea?
    Thank you.
    Wed Jul 30 00:08:05 2014
    Beginning log switch checkpoint up to RBA [0x138bd.2.10], SCN: 4473445936
    Thread 1 advanced to log sequence 80061 (LGWR switch)
      Current log# 1 seq# 80061 mem# 0: F:\ORACLE\PRD\ORIGLOGA\LOG_G11M1.DBF
      Current log# 1 seq# 80061 mem# 1: F:\ORACLE\PRD\MIRRLOGA\LOG_G11M2.DBF
    Beginning log switch checkpoint up to RBA [0x138be.2.10], SCN: 4473445939
    Thread 1 advanced to log sequence 80062 (LGWR switch)
      Current log# 2 seq# 80062 mem# 0: F:\ORACLE\PRD\ORIGLOGB\LOG_G12M1.DBF
      Current log# 2 seq# 80062 mem# 1: F:\ORACLE\PRD\MIRRLOGB\LOG_G12M2.DBF
    Beginning log switch checkpoint up to RBA [0x138bf.2.10], SCN: 4473445942
    Thread 1 advanced to log sequence 80063 (LGWR switch)
      Current log# 3 seq# 80063 mem# 0: F:\ORACLE\PRD\ORIGLOGA\LOG_G13M1.DBF
      Current log# 3 seq# 80063 mem# 1: F:\ORACLE\PRD\MIRRLOGA\LOG_G13M2.DBF
    Wed Jul 30 00:08:06 2014
    Archived Log entry 80064 added for thread 1 sequence 80061 ID 0x70061a1e dest 1:
    Thread 1 cannot allocate new log, sequence 80064
    Checkpoint not complete
    Wed Jul 30 00:08:06 2014
    Archived Log entry 80065 added for thread 1 sequence 80062 ID 0x70061a1e dest 1:
      Current log# 3 seq# 80063 mem# 0: F:\ORACLE\PRD\ORIGLOGA\LOG_G13M1.DBF
      Current log# 3 seq# 80063 mem# 1: F:\ORACLE\PRD\MIRRLOGA\LOG_G13M2.DBF
    Wed Jul 30 00:08:08 2014
    Archived Log entry 80066 added for thread 1 sequence 80060 ID 0x70061a1e dest 1:
    Wed Jul 30 00:08:09 2014
    Completed checkpoint up to RBA [0x138bd.2.10], SCN: 4473445936
    Beginning log switch checkpoint up to RBA [0x138c0.2.10], SCN: 4473445946
    Thread 1 advanced to log sequence 80064 (LGWR switch)
      Current log# 4 seq# 80064 mem# 0: F:\ORACLE\PRD\ORIGLOGB\LOG_G14M1.DBF
    Completed checkpoint up to RBA [0x138c0.2.10], SCN: 4473445946
      Current log# 4 seq# 80064 mem# 1: F:\ORACLE\PRD\MIRRLOGB\LOG_G14M2.DBF
    Archived Log entry 80067 added for thread 1 sequence 80063 ID 0x70061a1e dest 1:
    Completed checkpoint up to RBA [0x138bf.2.10], SCN: 4473445942
    Completed checkpoint up to RBA [0x138be.2.10], SCN: 4473445939

    ========================================================
    GENERIC OPATCH VERSION - FOR USE IN SAP ENVIRONMENT ONLY
    ========================================================
    Oracle Installer di patch provvisorie versione 11.2.0.3.1
    Copyright (c) 2012, Oracle Corporation. Tutti i diritti riservati.
    Oracle Home       : I:\oracle\PRD\11203
    Central Inventory : C:\Program Files\Oracle\Inventory
       from           : n/a
    OPatch version    : 11.2.0.3.1
    OUI version       : 11.2.0.3.0
    Log file location : I:\oracle\PRD\11203\cfgtoollogs\opatch\opatch2014-07-30_00-4
    7-57AM_1.log
    Lsinventory Output file location : I:\oracle\PRD\11203\cfgtoollogs\opatch\lsinv\
    lsinventory2014-07-30_00-47-57AM.txt
    Prodotti di livello superiore installati (1):
    Oracle Database 11g                                                  11.2.0.3.0
    Ci sono 1 prodotti installati in questa Oracle home.
    Patch provvisorie (6) :
    Patch  16167942     : applied on Sat May 18 11:50:42 CEST 2013
    Unique Patch ID:  15646955
    Patch description:  "ORACLE 11G 11.2.0.3 PATCH 15 BUG FOR WINDOWS (64-BIT AMD64
    AND INTEL EM64)"
       Created on 01 Feb 2013, 00:06:51 hrs PST8PDT
       Bugs fixed:
         16167942, 15841373, 14252187, 13877007, 14249514, 13891981, 12637294
         14511876, 14309075, 13736413, 12862170, 13901201, 12819999, 16019955
         15996520, 14775679, 13902963, 15924589, 14525739, 14744263, 12838063
         15910002, 14751895, 14107475, 13262857, 14641969, 15938047, 15982436
         13924173, 14761411, 16042648, 13337530, 14810890, 13605675, 7335665
         12686027, 16011871, 13729351, 13923995, 12813641, 12985237, 14600776
         14565062, 13066936, 14510516, 14192781, 14164191, 14505752, 15834269
         13559463, 14702500, 12345305, 14467027, 14807785, 14590564, 13849733
         13916549, 14755945, 15869211, 13365021, 13972394, 14193629, 14808639
         14189694, 13848402, 14226599, 13621258, 13827380, 14762511, 14064573
         13777449, 15848120, 14546673, 14546638, 14546575, 14469008, 14263073
         14263036, 14258925, 14205448, 14023636, 14035825, 13685544, 14040433
         13593999, 13026410, 12964067, 12873183, 12857027, 12345082, 14589750
         14668670, 13791678, 13769577, 13658087, 14230270, 13890080, 13810393
         13551402, 14644185, 13686047, 12583611, 14488943, 14176879, 13727644
         13517951, 13361350, 14373728, 13602883, 13580513, 10219624, 14645769
         14007968, 14827344, 9153183, 15853081, 14138130, 14168099, 14810093
         13845120, 14277586, 14271305, 13879428, 13938166, 12558569, 10260842
         14569263, 14100232, 13912373, 13653178, 14242977, 14102704, 14001941
         13993634, 13634583, 14828076, 13645875, 14398795, 13879553, 12940620
         14663556, 12327035, 14207902, 12557401, 14653598, 14587310, 14224606
         14577426, 14386985, 13783957, 12656350, 11836374, 14485163, 14624988
         14582487, 14332938, 14166276, 14479390, 14372670, 14038163, 13535104
         13744724, 14245087, 14305767, 14731193, 14313519, 14500723, 12928700
         12571916, 14245825, 13642044, 9706792, 13693929, 13903046, 14581922
         14142884, 14393900, 9778542, 13115786, 13427062, 14164849, 13399711
         11686700, 14175146, 14499293, 13615767, 14625969, 14513934, 14320472
         14613223, 13040943, 12812148, 14360965, 13911821, 14140535, 14204172
         13949042, 14367567, 9949330, 14467202, 14323857, 13834065, 13632653
         14110275, 13549808, 14196818, 13819727, 9751365, 10029609, 11846912
         12646510, 12766337, 12826115, 12860701, 12865360, 12973529, 13031176
         13040909, 13061085, 13066239, 13071375, 13111783, 13114306, 13345188
         13376866, 13393115, 13406688, 13408107, 13433178, 13459147, 13531801
         13553502, 13603792, 13608532, 13622539, 13622968, 13738130, 13961338
         14054189, 13851432, 14063422, 13973307, 14119388, 14282903, 14517263
         13716797, 14465787, 14613900, 14304758, 14251904, 14214257, 14153867
         14009845, 13889047, 13888719, 13820621, 13697828, 12663376, 11675721
         12889329, 13410987, 13965075, 13869978, 13843080, 13825231, 13582411
         13550689, 13023609, 13000491, 10418841, 10317921, 13523527, 13498267
         14096743, 14010695, 13947200, 14259185, 14280458, 14276345, 14543814
         13804294, 13718279, 13612575, 13430938, 13384182, 13377816, 13250244
         12794305, 12693626, 12352406, 12879628, 13534412, 13524698, 13743987
         14207317, 13918644, 14198511, 14088346, 12791981, 13011409, 13038684
         12865902, 12768840, 14076523, 13632809, 14458246, 13359289, 12794025
         9952132, 13780816, 12950694, 14162791, 13093358, 14255600, 13936424
         14301592, 14050233, 13528725, 14500052, 10146616, 14409183, 14324057
         14313389, 5918695, 12430142, 13399435, 13913630, 13732226, 10084752
         13591624, 14237793, 14013094, 10229475, 13078786, 14052474, 13637058
         12646746, 13000553, 14254795, 14215010, 13922729, 13942694, 12898637
         14309390, 13958038, 10214323, 13710236, 14115858, 14240544, 14158332
         13073613, 11074304, 13868705, 12723295, 13853654, 14074606, 13784384
         14386810, 14223718, 14018752, 13258936, 13723052, 12898020, 10625145
         14052871, 13076238, 13992002, 13242070, 12955701, 12693573, 14026888
         13984965, 13366199, 13843286, 13616375, 12839247, 8547978, 13714926
         13023854, 13910420, 11837095, 12842909, 12959852, 13632140, 13780035
         13860201, 13711083, 13628002, 13397104, 12358083, 13743357, 13945708
         10384051, 13591484, 13051250, 13727853, 12959627, 14095820, 5144934
         13657605, 13582702, 12966665, 13463131, 13773133, 12918738, 13099577
         13690409, 13645917, 11708510, 14042380, 13627489, 13652437, 12733042
         13907462, 13608299, 13624984, 9095696, 12794090, 9706532, 13469158
         13947480, 13555112, 13399236, 12910565, 13790109, 12552578, 13896848
         13737746, 13080778, 13458016, 13873885, 12312133, 12731940, 12672969
         13355095, 13981051, 13467683, 13457582, 13370330, 13340388, 12976376
         12797420, 12658411, 10133521, 9761357, 13827394, 13729832, 13851978
         13559770, 13592937, 13592919, 13478856, 13559540, 13641696, 13729808
         13632530, 14100237, 11071989, 13786142, 13839641, 13041324, 13857364
         13853089, 13806545, 13726162, 13657366, 13617861, 13604057, 13483672
         12959140, 12914722, 12910033, 12771830, 13776758, 13339443, 12680491
         10114953, 12966774, 13965211, 12424121, 13478060, 13786778, 13579992
         13705338, 13603613, 13476583, 12745662, 9190186, 13530646, 13520452
         9019231, 13610777, 12905053, 10263668, 13550185, 13385346, 13448206
         12772404, 13911711, 11072246, 13104881, 13863326, 12889054, 13775960
         13777823, 13464002, 11824898, 13535622, 13916709, 12880299, 12918338
         12529945, 13811209, 14058362, 13724808, 13885389, 13649031, 13350245
         13553883, 13388104, 13635347, 13404129, 13031118, 12530140, 13023541
         13767921, 13787482, 13641076, 13807411, 13724992, 12965899, 13791443
         12879027, 13584130, 13495307, 12594032, 13709220, 13247965, 13243072
         13683125, 13652493, 12957127, 10215977, 13014128, 13040331, 12857222
         12977501, 12664456, 12405931, 13525554, 13492863, 13573521, 13873471
         13366268, 13352423, 13460353, 12709476, 13652088, 13886023, 13942723
         12919564, 12894807, 12829021, 12612118, 11063191, 13503598, 13482688
         13354082, 13484963, 13395403, 13542159, 12983611, 13718476, 12846562
         9659614, 13326736, 11846902, 11665727, 13257247, 13588248, 13544396
         13566938, 13615517, 13425727, 13037709, 12730342, 12349553, 13502441
         13258062, 13251796, 13247273, 12659561, 12639013, 12594616, 11772838
         13570057, 12403721, 12585543, 12784549, 12834800, 12975771, 13040171
         13058950, 13063120, 13077335, 13365700, 13382280, 13384397, 13440516
         13454210, 13457537, 13477790, 13496250, 13501787, 13505390, 13506110
         13524899, 13572659, 13594712, 13617627, 13326289, 13555974, 13035360
         13420224, 13419660, 13036331, 13332439, 13420174, 12583826, 13358781
         11883969, 13524237, 12867713, 13328193, 13516727, 11865420, 13502183
         13259364, 13371153, 12998795, 13413168, 12897902, 13044108, 12971242
         12834027, 12620823, 13420516, 12849377, 12975811, 12646784, 12829429
         12538907, 12950823, 12848480, 12823838, 13366202, 13002015, 12834777
         13001901, 13017428, 13082238, 12965049, 11840910, 12656535, 12617123
         13073340, 12925041, 12938841, 13023632, 13066371, 12942119, 11877623
         12810890, 12995950, 12765467, 12934171, 13070939, 12535346, 12985184
         13103913, 12765868, 12622441, 12876314, 12820045, 13038806, 13090686
         12923168, 13362079, 12591252, 12718090, 12873909, 10350832, 12795861
         13039908, 12976590, 13017584, 12627504, 13263435, 12847466, 12797765
         12758736, 12878750, 12861463, 13024624, 12764337, 12662040, 13068077
         12914824, 13074261, 12668341, 12597906, 12932852, 13045518, 12897651
         12960925, 12728585, 13019958, 12902661, 12886827, 12913474, 3522216
         12678920, 12885323, 13334158, 12947871, 12896850, 13001955, 12784559
         12827166, 9703627, 12772345, 12905058, 13345868, 10357727, 12827493
         13004894, 12780983, 12842804, 13146719, 12655301, 12960302, 13085732
         12979199, 12638117, 13357509, 12401111, 12857064, 8631856, 13035804
         13355963, 12845115, 12695029, 12990582, 12971775, 12867511, 12917230
         12582664, 12849688, 12950644, 12588744, 13011520, 12899169, 12823042
    Patch  14658090     : applied on Sat May 18 11:40:34 CEST 2013
    Unique Patch ID:  15859799.1
       Created on 27 Jan 2013, 08:31:45 hrs PST8PDT
       Bugs fixed:
         14658090
    Patch  13575265     : applied on Sat May 18 11:40:14 CEST 2013
    Unique Patch ID:  14606745
       Created on 27 Feb 2012, 02:10:47 hrs PST8PDT
       Bugs fixed:
         13575265
    Patch  13508485     : applied on Sat May 18 11:39:34 CEST 2013
    Unique Patch ID:  14395138
       Created on 21 Dec 2011, 13:23:38 hrs PST8PDT
       Bugs fixed:
         13508485
    Patch  12325243     : applied on Sat May 18 11:38:51 CEST 2013
    Unique Patch ID:  14243031
       Created on 7 Nov 2011, 11:57:40 hrs PST8PDT
       Bugs fixed:
         12325243
    Patch  9584028      : applied on Sat May 18 11:38:31 CEST 2013
       Created on 22 Jun 2012, 11:39:40 hrs CEST
       Bugs fixed:
         9584028
    OPatch succeeded.

  • 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?

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

    We were receiving the following messages in alert log. We have Oracle 10g R2 database having four redo log groups with two members each (50 MB). To overcome this error yesterday we added two more groups with same config. Again we received the same message in the alert log.
    Alert Log contents:
    Fri Dec 22 11:21:39 2006
    Thread 1 cannot allocate new log, sequence 1193
    Checkpoint not complete
    Current log# 1 seq# 1192 mem# 0: /u02A/oradata/admin/origlogA/redo01.log
    Thread 1 advanced to log sequence 1193
    Current log# 5 seq# 1193 mem# 0: /u02A/oradata/admin/origlogA/redo05.log
    Thread 1 cannot allocate new log, sequence 1194
    Checkpoint not complete
    Current log# 5 seq# 1193 mem# 0: /u02A/oradata/admin/origlogA/redo05.log
    Current log# 5 seq# 1193 mem# 1: /u02B/oradaFri Dec 22 11:21:50 2006
    Thread 1 advanced to log sequence 1194
    Current log# 6 seq# 1194 mem# 0: /u02A/oradata/admin/origlogA/redo06.log
    Current log# 6 seq# 1194 mem# 1: /u02B/oradata/admin/origlogB/redo06_2.log
    Thread 1 advanced to log sequence 1195
    Current log# 2 seq# 1195 mem# 0: /u02A/oradata/admin/origlogA/redo02.log
    Current log# 2 seq# 1195 mem# 1: /u02B/oradata/admin/origlogB/redo02_2.log
    Fri Dec 22 11:22:05 2006
    Thread 1 cannot allocate new log, sequence 1196
    Checkpoint not complete
    Current log# 2 seq# 1195 mem# 0: /u02A/oradata/admin/origlogA/redo02.log
    Current log# 2 seq# 1195 mem# 1: /u02B/oradata/admin/origlogB/redo02_2.log
    Thread 1 advanced to log sequence 1196
    Current log# 3 seq# 1196 mem# 0: /u02A/oradata/admin/origlogA/redo03.log
    Current log# 3 seq# 1196 mem# 1: /u02B/oradata/admin/origlogB/redo03_2.log
    Thread 1 cannot allocate new log, sequence 1197
    Checkpoint not complete

    You might not want to revivify threads from 2006. Create a new thread, including all the information to make it a [url  http://catb.org/esr/faqs/smart-questions.html]smart question. Which version and patch level of Oracle are you on, which platform, how often are your logs switching, a relevant clip from your alert log surrounded by {noformat}{noformat} tags, etc.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • 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.

  • Very Urgent: Thread 1 cannot allocate new log, sequence 6 : Script stuck

    I am running one script, it is stuck with log file showing:
    Thread 1 cannot allocate new log, sequence 6
    All online logs needed archiving
    Current log# 7 seq# 5 mem# 0: /u13/sjmarte/oradata/redo7a.log
    I have checked the database: it is in archivelog mode
    Checked the archvie dest: we have space in TB's
    And almost 24GB's occupied by log files each of 6GB's.
    ====================================
    Can any one please help us how to get rid of this issue

    Sorry I m new to this forum.
    We dont have a seperate FRA in this case.
    This is the log file information:
    Wed May 18 13:28:23 2011
    Thread 1 advanced to log sequence 5 (LGWR switch)
    Current log# 7 seq# 5 mem# 0: /u13/sjmarte/oradata/redo7a.log
    Current log# 7 seq# 5 mem# 1: /u14/sjmarte/oradata/redo7b.log
    Wed May 18 13:31:58 2011
    ORACLE Instance sjmarte - Can not allocate log, archival required
    Wed May 18 13:31:58 2011
    Thread 1 cannot allocate new log, sequence 6
    All online logs needed archiving
    Current log# 7 seq# 5 mem# 0: /u13/sjmarte/oradata/redo7a.log
    Current log# 7 seq# 5 mem# 1: /u14/sjmarte/oradata/redo7b.log
    Here is archive log list
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /backup/oracle/sjmarte/archive
    Oldest online log sequence 2
    Next log sequence to archive 2
    Current log sequence 5
    Edited by: 784786 on May 18, 2011 11:35 AM

  • Thread 1 cannot allocate new log, sequence 1258

    Hello buddies,
    I am receiving this message and not sure on how to fix it.
    Please guide me.
    Fri Jul 30 22:00:17 2010
    Thread 1 advanced to log sequence 1256 (LGWR switch)
    Current log# 2 seq# 1256 mem# 0: F:\maindb\LOG_02.DBF
    Fri Jul 30 22:00:36 2010
    Thread 1 advanced to log sequence 1257 (LGWR switch)
    Current log# 3 seq# 1257 mem# 0: F:\maindb\LOG_03.DBF
    Fri Jul 30 22:00:51 2010
    Thread 1 cannot allocate new log, sequence 1258
    Checkpoint not complete
    Current log# 3 seq# 1257 mem# 0: F:\maindb\LOG_03.DBF
    Fri Jul 30 22:00:53 2010
    Thread 1 advanced to log sequence 1258 (LGWR switch)
    Current log# 1 seq# 1258 mem# 0: F:\maindb\LOG_01.DBF
    Fri Jul 30 22:01:09 2010
    Thread 1 cannot allocate new log, sequence 1259
    Checkpoint not complete
    Current log# 1 seq# 1258 mem# 0: F:\maindb\LOG_01.DBF
    Fri Jul 30 22:01:11 2010
    Thread 1 advanced to log sequence 1259 (LGWR switch)
    Current log# 2 seq# 1259 mem# 0: F:\maindb\LOG_02.DBF
    Fri Jul 30 22:01:23 2010
    Thread 1 cannot allocate new log, sequence 1260
    Checkpoint not complete
    Current log# 2 seq# 1259 mem# 0: F:\maindb\LOG_02.DBF
    Fri Jul 30 22:01:26 2010
    Thread 1 advanced to log sequence 1260 (LGWR switch)
    Current log# 3 seq# 1260 mem# 0: F:\maindb\LOG_03.DBF
    Sat Jul 31 00:06:03 2010
    Thread 1 cannot allocate new log, sequence 1261
    Checkpoint not complete
    Current log# 3 seq# 1260 mem# 0: F:\maindb\LOG_03.DBF
    Sat Jul 31 00:06:05 2010
    Thread 1 advanced to log sequence 1261 (LGWR switch)
    Current log# 1 seq# 1261 mem# 0: F:\maindb\LOG_01.DBF
    Sat Jul 31 01:00:00 2010
    Thread 1 cannot allocate new log, sequence 1262
    Checkpoint not complete
    Current log# 1 seq# 1261 mem# 0: F:\maindb\LOG_01.DBF
    Sat Jul 31 01:00:02 2010
    Thread 1 advanced to log sequence 1262 (LGWR switch)
    Current log# 2 seq# 1262 mem# 0: F:\maindb\LOG_02.DBF
    Sat Jul 31 01:00:02 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 01:00:02 2010
    Thread 1 cannot allocate new log, sequence 1263
    Checkpoint not complete
    Current log# 2 seq# 1262 mem# 0: F:\maindb\LOG_02.DBF
    Sat Jul 31 01:00:08 2010
    Thread 1 advanced to log sequence 1263 (LGWR switch)
    Current log# 3 seq# 1263 mem# 0: F:\maindb\LOG_03.DBF
    Sat Jul 31 01:00:11 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 01:00:11 2010
    Thread 1 cannot allocate new log, sequence 1264
    Checkpoint not complete
    Current log# 3 seq# 1263 mem# 0: F:\maindb\LOG_03.DBF
    Sat Jul 31 01:00:14 2010
    Thread 1 advanced to log sequence 1264 (LGWR switch)
    Current log# 1 seq# 1264 mem# 0: F:\maindb\LOG_01.DBF
    Sat Jul 31 01:02:22 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 01:02:22 2010
    Thread 1 advanced to log sequence 1265 (LGWR switch)
    Current log# 2 seq# 1265 mem# 0: F:\maindb\LOG_02.DBF
    Sat Jul 31 06:00:12 2010
    Thread 1 advanced to log sequence 1266 (LGWR switch)
    Current log# 3 seq# 1266 mem# 0: F:\maindb\LOG_03.DBF
    Sat Jul 31 06:00:24 2010
    Thread 1 advanced to log sequence 1267 (LGWR switch)
    Current log# 1 seq# 1267 mem# 0: F:\maindb\LOG_01.DBF
    Sat Jul 31 06:00:43 2010
    Thread 1 cannot allocate new log, sequence 1268
    Checkpoint not complete
    Current log# 1 seq# 1267 mem# 0: F:\maindb\LOG_01.DBF
    Sat Jul 31 06:00:44 2010
    Thread 1 advanced to log sequence 1268 (LGWR switch)
    Current log# 2 seq# 1268 mem# 0: F:\maindb\LOG_02.DBF
    I checked the size of the redo log: and its 10mb:
    spool F:\admin\maindb/create/create.log
    startup nomount
    create database maindb
        maxinstances 1
        datafile 'F:/data/maindb/system_01.dbf' size 250m
        sysaux datafile 'F:/data/maindb/sysaux_01.dbf' size 100m
        extent management local
        undo tablespace undo
                datafile 'F:/data/maindb/undo_01.dbf' size 40m
        default temporary tablespace temp
                tempfile 'F:/data/maindb/temp_01.dbf' size 40m
                extent management local uniform size 1m
        logfile 'F:/data/maindb/log_01.dbf' size 10m,
                'F:/data/maindb/log_02.dbf' size 10m,
                'F:/data/maindb/log_03.dbf' size 10m
        user sys identified by "abc"
        user system identified by "abc";
    whenever sqlerror continue
    @F:\10g/rdbms/admin/catalog
    @F:\10g/rdbms/admin/catproc
    @F:\10g/rdbms/admin/catblock
    @F:\10g/rdbms/admin/caths
    @F:\10g/rdbms/admin/dbmspool
    @F:\10g/rdbms/admin/dbmsrand
    @F:\10g/rdbms/admin/otrcsvr
    connect system/abc
    @F:\10g/sqlplus/admin/pupbld
    spool offSome parameters from my init file: log_archive_max_processes=15
    processes = 200
    log_checkpoint_timeout = 0
    log_checkpoint_interval = 0
    fast_start_mttr_target = 0
    Please help me.
    Thanking in advance.
    Nith

    Dear sb92075,
    I have increased the size of the redo log files to 15M to see how things work.
    select * from v$logfile;
    select group#, sequence#, bytes, archived, members, status
    from v$log;
    alter database drop logfile group 1;
    alter database
    add logfile group 1 ('F:\MAINDB\LOG_01.log') SIZE 15M;
    alter system switch logfile;
    alter database drop logfile group 2;
    alter database
    add logfile group 2 ('F:\MAINDB\LOG_02.LOG') SIZE 15M;
    ALTER SYSTEM CHECKPOINT GLOBAL;
    alter database drop logfile group 3;
    alter database
    add logfile group 3 ('F:\MAINDB\LOG_03.LOG') SIZE 15M;So, all I have to do now is just wait and see how things go after this, right?
    When these statements were being executed, I noticed some errors also but I think I should ignore them for now.
    Some sample messages are:
    Completed: alter database drop logfile group 3
    Sat Jul 31 11:06:40 2010
    alter database
    add logfile group 3 ('F:\MAINDB\LOG_03.LOG') SIZE 15M
    Sat Jul 31 11:06:40 2010
    Completed: alter database
    add logfile group 3 ('F:\MAINDB\LOG_03.LOG') SIZE 15M
    Sat Jul 31 11:08:54 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 11:08:55 2010
    Thread 1 advanced to log sequence 1274 (LGWR switch)
    Sat Jul 31 11:08:55 2010
      Current log# 2 seq# 1274 mem# 0:F:\MAINDB\LOG_02.LOG
    Sat Jul 31 11:08:55 2010
    Thread 1 advanced to log sequence 1275 (LGWR switch)
      Current log# 3 seq# 1275 mem# 0: F:\MAINDB\LOG_03.LOG
    Sat Jul 31 11:09:03 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 11:09:03 2010
    Thread 1 cannot allocate new log, sequence 1276
    Checkpoint not complete
      Current log# 3 seq# 1275 mem# 0: F:\MAINDB\LOG_03.LOG
    Sat Jul 31 11:09:06 2010
    Thread 1 advanced to log sequence 1276 (LGWR switch)
      Current log# 1 seq# 1276 mem# 0: F:\MAINDB\LOG_01.LOG
    Sat Jul 31 11:11:13 2010
    ALTER SYSTEM ARCHIVE LOG
    Sat Jul 31 11:11:13 2010
    Thread 1 advanced to log sequence 1277 (LGWR switch)
      Current log# 2 seq# 1277 mem# 0: F:\MAINDB\LOG_02.LOGPlease comment.

  • Thread 1 cannot allocate new log, sequence 28703

    Hello,
    I have a problem in my production database. I have an Oracle database 10.2.0.2 64 bits, and Checking the alertlog I see this message some days ago:
    Thread 1 cannot allocate new log, sequence 19943
    Private strand flush not complete
    Current log# 1 seq# 19942 mem# 0: E:\ORADATA\INCARLOP\REDO01A.LOG
    Current log# 1 seq# 19942 mem# 1: F:\ORADATA\INCARLOP\REDO01B.LOG
    My archivelogs size is 90 MB and I have enough free space in my filesystem
    what can be the problem?
    Thanks!!!

    fjfranken wrote:
    The problem is caused by the fact that Oracle wants to start using a redo-log file which is still in use by a running checkpoint.
    Most of the time this problem is solved by adding more redo-log-groups.No, what you are describing would be more the "+Check point not complete+" error, which could be solved by adding more logfile group or increase the current size.
    The message of the OP is similar, but not the same. It would rather means that log switch cannot occur because the redo has not been written, this could be a disk contention to write down the redo. If this is eratic behaviour it could safely be ignore.
    Nicolas.

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

    hi,
    i m working on oracle 10g rac database on aix machine . i m getting this error on peck time
    Thread 1 cannot allocate new log, sequence 1558 Checkpoint not complete
    i read lots of documents and they asked to increase size of redo file or add more redo files.
    can u plz describe me y m i getting this error ? & how adding redo file can help in this error.
    thxs

    when yours current redo log filled and then started to switch another log then checkpoint occurs ,this checkpoint started to write dirty buffer from buffer cache to datafile , you cannot reuse this logfile unless checkpoint process writes alls dirty buffer from buffer cache to disk which contained this redo log file.If you attempt to reuse the same log file which cause to checkpoint upon log switch then you will get this error.
    Typically this error comes where yours number of redo log switches occuring too frequently or you have less number of redo logs.
    lets say if you have 2 redolog file A and B,yours A redolog filled and then oracle switch from redo log A to B,checkpoint occurs,DBWRn started to write dirty buffer to disk meanwhile yours redo log B also get filled antoher log switch occurs to be attempt to reuse redo log file A ,but redo log A will not be entertain unless the previous checpoint completed to write alls dirty block from buffer cache to hard disk which is contained thats redo log A.
    Adding redo log will be helpful in this case that redo log will switch to another new added redo log say C and A log file will get more time to be completed checkpoint which he/she contains contents.
    Khurram

  • Cannot allocate new log, sequence Checkpoint not complete

    Hi,
    Im having very frequent log switches and Im getting error as
    " cannot allocate new log, sequence Checkpoint not complete"
    I was having 3 redo log groups with 50 MB each. After I found this error in the alert log; I increased teh number of redo log groups to 6 with 50MB each. Still the issue is not getting resolved.
    Please suggest what will be the best solution for this.
    Following is a snippet from alertlog.
    ==================================================
    Sun Apr 19 09:14:08 2009
    Thread 1 advanced to log sequence 5811
    Current log# 2 seq# 5811 mem# 0: /u01/app/oracle/oradata/mview/redo02.log
    Thread 1 cannot allocate new log, sequence 5812
    Checkpoint not complete
    Current log# 2 seq# 5811 mem# 0: /u01/app/oracle/oradata/mview/redo02.log
    Sun Apr 19 09:14:18 2009
    Thread 1 advanced to log sequence 5812
    Current log# 3 seq# 5812 mem# 0: /u01/app/oracle/oradata/mview/redo03.log
    Thread 1 cannot allocate new log, sequence 5813
    Checkpoint not complete
    Current log# 3 seq# 5812 mem# 0: /u01/app/oracle/oradata/mview/redo03.log
    Thread 1 advanced to log sequence 5813
    Current log# 1 seq# 5813 mem# 0: /u01/app/oracle/oradata/mview/redo01.log
    Thread 1 cannot allocate new log, sequence 5814
    Checkpoint not complete
    Current log# 1 seq# 5813 mem# 0: /u01/app/oracle/oradata/mview/redo01.log
    Sun Apr 19 09:14:32 2009
    Thread 1 advanced to log sequence 5814
    Current log# 2 seq# 5814 mem# 0: /u01/app/oracle/oradata/mview/redo02.log
    Thread 1 cannot allocate new log, sequence 5815
    Checkpoint not complete
    Current log# 2 seq# 5814 mem# 0: /u01/app/oracle/oradata/mview/redo02.log
    Thread 1 advanced to log sequence 5815
    Current log# 3 seq# 5815 mem# 0: /u01/app/oracle/oradata/mview/redo03.log
    Thread 1 cannot allocate new log, sequence 5816
    Checkpoint not complete
    Current log# 3 seq# 5815 mem# 0: /u01/app/oracle/oradata/mview/redo03.log
    Sun Apr 19 09:14:44 2009
    =========================================================
    Regards
    Pratheej

    Anand... wrote:
    Hi Sir,
    Although i too had suggested increasing the redo logfile size, but after going through [http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:69012348056] i was little confused as Tom has mentioned
    Another way is to make the log files smaller, hence increasing the frequency with which we checkpoint ---- Can you explain why so.
    I was a little surprised when I read that posting - but noticed it was dated May 2000 - when databases were still quite small and less busy. (And Tom suggested 25MB as being "modest" rather than "tiny" - which is probably what many people would call 25MB these days). And May 2000 probably means 8.0 or 8.1 - and the whole log buffer, redo generation, checkpointing technology has changed a lot since then.
    Basically, if you hit "checkpoint not complete", you need more online log space so that it's possible during the busiest times to keep generating redo log information while the checkpoint queues are being cleared far enough to allow older log files to be recycled.
    You can do this by adding more log files, or by increasing the sizes of the log files you use. Tom's point, I think, was that if you chose the option to add more files and kept them small (or even made them smaller) then the volume of dirty data blocks that you could create while filling a log file would be small, so the database writer wouldn't have to do much work to make each log file available for re-use. (I'm not sure I'd agree with the approach, though - even for 8i - because it could easily lead to an increase in the volume of datablocks written, even if it did bypass the checkpoint issue).
    Regards
    Jonathan Lewis
    http://jonathanlewis.wordpress.com
    http://www.jlcomp.demon.co.uk
    "For every expert there is an equal and opposite expert."
    Arthur C. Clarke

  • Cannot allocate new log, sequence

    Hi ,I see my alert.log which writed 'Thread 1 cannot allocate new log, sequence '
    what is Thread 1 cannot allocate new log, sequence ?

    Please see the following for a similar discussion:
    Thread 1 cannot allocate new log, sequence 1196,Checkpoint not complete

Maybe you are looking for