Which parameter to change to avoid "cannot allocate new log"

Hello Everyone.
I'm running 9i r2 on windows 2003 SD edition server with ISCSI attached. on the ISCSI drive i have 1 group of redo logs together with DBF's in the data directory. The other 2 redo groups are on the 2 separate local disks together with archive logs (in another folder).
I'm getting a few "cannot allocate new log" errors every couple of days and in the event viewer "Archive process error: ORACLE Instance prdps - Can not allocate log, archival required"
I'm not sure which parameter i should change.
Current setup:
db_writer_processes     1
dbwr_io_slaves          0
Here is the output from v$sysstat:
49     DBWR checkpoint buffers written     8     7410575
50     DBWR transaction table writes     8     7748
51     DBWR undo block writes     8     4600265
52     DBWR revisited being-written buffer     8     5313
53     DBWR make free requests     8     26383
54     DBWR free buffers found     8     19838373
55     DBWR lru scans     8     21831
56     DBWR summed scan depth     8     21265425
57     DBWR buffers scanned     8     21265425
58     DBWR checkpoints     8     1719
59     DBWR cross instance writes     40     0
60     DBWR fusion writes     40     0
This is from alert.log:
Fri Mar 06 00:25:52 2009
ARC0: Completed archiving log 1 thread 1 sequence 7004
Fri Mar 06 00:25:54 2009
Thread 1 advanced to log sequence 7006
Current log# 3 seq# 7006 mem# 0: E:\ORACLE\ORADATA\PRDPS\REDO03A.LOG
Current log# 3 seq# 7006 mem# 1: F:\ORACLE\ORADATA\PRDPS\REDO03B.LOG
Current log# 3 seq# 7006 mem# 2: G:\ORACLE\ORADATA\PRDPS\REDO03C.LOG
Fri Mar 06 00:25:54 2009
ARC1: Evaluating archive log 2 thread 1 sequence 7005
ARC1: Beginning to archive log 2 thread 1 sequence 7005
Creating archive destination LOG_ARCHIVE_DEST_1: 'F:\ORACLE\ORADATA\PRDPS\ARCHIVE\PRDPS_001_07005.ARC'
Fri Mar 06 00:26:03 2009
Thread 1 advanced to log sequence 7007
Current log# 1 seq# 7007 mem# 0: E:\ORACLE\ORADATA\PRDPS\REDO01A.LOG
Current log# 1 seq# 7007 mem# 1: F:\ORACLE\ORADATA\PRDPS\REDO01B.LOG
Current log# 1 seq# 7007 mem# 2: G:\ORACLE\ORADATA\PRDPS\REDO01C.LOG
Fri Mar 06 00:26:03 2009
ARC0: Evaluating archive log 2 thread 1 sequence 7005
ARC0: Unable to archive log 2 thread 1 sequence 7005
Log actively being archived by another process
ARC0: Evaluating archive log 3 thread 1 sequence 7006
ARC0: Beginning to archive log 3 thread 1 sequence 7006
Creating archive destination LOG_ARCHIVE_DEST_1: 'F:\ORACLE\ORADATA\PRDPS\ARCHIVE\PRDPS_001_07006.ARC'
Fri Mar 06 00:26:15 2009
ARC1: Completed archiving log 2 thread 1 sequence 7005
ARC1: Evaluating archive log 3 thread 1 sequence 7006
ARC1: Unable to archive log 3 thread 1 sequence 7006
Log actively being archived by another process
Fri Mar 06 00:26:16 2009
Thread 1 cannot allocate new log, sequence 7008
All online logs needed archiving
Current log# 1 seq# 7007 mem# 0: E:\ORACLE\ORADATA\PRDPS\REDO01A.LOG
Current log# 1 seq# 7007 mem# 1: F:\ORACLE\ORADATA\PRDPS\REDO01B.LOG
Current log# 1 seq# 7007 mem# 2: G:\ORACLE\ORADATA\PRDPS\REDO01C.LOG
Thread 1 advanced to log sequence 7008
Current log# 2 seq# 7008 mem# 0: E:\ORACLE\ORADATA\PRDPS\REDO02A.LOG
Current log# 2 seq# 7008 mem# 1: F:\ORACLE\ORADATA\PRDPS\REDO02B.LOG
Current log# 2 seq# 7008 mem# 2: G:\ORACLE\ORADATA\PRDPS\REDO02C.LOG
Fri Mar 06 00:26:16 2009
ARC1: Evaluating archive log 3 thread 1 sequence 7006
ARC1: Unable to archive log 3 thread 1 sequence 7006
Log actively being archived by another process
ARC1: Evaluating archive log 1 thread 1 sequence 7007
ARC1: Beginning to archive log 1 thread 1 sequence 7007
Should i just change
db_writer_processes     1
dbwr_io_slaves          2
Thank you
Any help appreciated.

This message indicates that Oracle wants to reuse a redo log file, but
the
corresponding checkpoint associated is not terminated. In this case,
Oracle
must wait until the checkpoint is completely realized. This situation
may be encountered particularly when the transactional activity is
important.
check for:
- Background checkpoint started.
- Background checkpoint completed.
These two statistics must not be different more than once. If this is
not true, your database hangs on checkpoints. LGWR is unable to
continue
writing the next transactions until the checkpoints complete.
Three reasons may explain this difference:
- A frequency of checkpoints which is too high.
- A checkpoints are starting but not completing
- A DBWR which writes too slowly.
The way to resolve incomplete checkpoints is through tuning
checkpoints and
logs:
1) Give the checkpoint process more time to cycle through the logs
- add more redo log groups
- increase the size of the redo logs
2) Reduce the frequency of checkpoints
- increase LOG_CHECKPOINT_INTERVAL
- increase size of online redo logs
3) Improve the efficiency of checkpoints enabling the CKPT process
with CHECKPOINT_PROCESS=TRUE
4) Set LOG_CHECKPOINT_TIMEOUT = 0. This disables the checkpointing
based on
time interval.
5) Another means of solving this error is for DBWR to quickly write
the dirty
buffers on disk. The parameter linked to this task is:
DB_BLOCK_CHECKPOINT_BATCH.
DB_BLOCK_CHECKPOINT_BATCH specifies the number of blocks which are
dedicated
inside the batch size for writing checkpoints. When you want to
accelerate
the checkpoints, it is necessary to increase this value.

Similar Messages

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

  • Increased logfile size and now get cannot allocate new log

    Because we were archiving up to 6 and 7 times per minute, I increased our logfiles from size from 13M to 150M. I also increased the number of groups from 3 to 5.
    Because we want to ensure recoverability within a certain timeframe, I also have a script that runs every 15 minutes and issues 2 commands: ALTER SYSTEM SWITCH LOGFILE; and ALTER SYSTEM CHECKPOINT;
    I am now seeing in my alert.log file the following, almost every time we do a log switch.
    Thread 1 cannot allocate new log, sequence 12380
    Private strand flush not complete
    No other changes have been made to the database.
    Why would this now be doing this?
    Should I not be doing both the ALTER SYSTEM SWITCH LOGFILE and the ALTER SYSTEM CHECKPOINT?
    Is there something else I should be looking at?
    Any suggestions/answers would be greatly appreciated.
    Db version: 11.1.0.7
    OS: OEL 5.5

    Set the FAST_START_MTTR_TARGET parameter to the instance recovery time in seconds that you want...
    ALTER SYSTEM SET LOG_ARCHIVE_MAX_PROCESSES=upto 10; this will make sure that the redo logs are copied faster....
    The sizing redo log files can influence performance because DBWR, LGWR and ARCH are all working during high DML periods.
    A too small online redo log file size can cause slowdowns from excessive DBWR and checkpointing behavior. A high checkpointing frequency and the "log file switch (checkpoint incomplete) can also cause slowdowns.
    Add additional log writer processes (LGWR).
    Ensure that the archived redo log filesystem resides on a separate physical disk spindle.
    Put the archived redo log filesystem on super-fast solid-state disks.

  • 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

  • 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

  • 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

  • Cannot allocate new log&Private strand flush not complete

    There are two Oracle10g(10.2.0.5) Database running on SUN M5000(SPARC64 VII 2.53 GHz Quad-Core Processors*4/32GB Memory).
    The first Oracle10g DB is running with 8GB SGA and 1GB PGA, the second Oracle10g DB is runing with 7GB SGA and 2GB PGA.
    We encountered a issue on the second Oracle DB. When we manually switch the online redo logs with an alter system command as below.
    SQL> alter system switch logfile;
    The Alert log will display the following messages:
    Thread 1 cannot allocate new log, sequence xxx
    Private strand flush not complete .
    All other Oracle10g DB will not occur "Private strand flush not complete" messages except for the second Oracle10g DB. I want to know the detail reason.
    I also saw two Doc ID:[ID 372557.1] and [ID 435887.1] from Oracle Metalink. But I am not satisfacted with what they wrote.
    My last target to resolve the issue.
    Anyone help me ?
    I am kylix.
    [email protected]

    hi
    Hemant
    iam very new to this field,since 20 days i am having one big problem in my databases,i have 2 database in my windows server environment ,recently i have upgrade my both the database from 10g to 11g.Why i upgrade means in 10g iam getting error ora-07445 access violation,in my alertlog file (when iam going to take full database backup through export getting this error in logfile and export stops with error) so i thought to apply the patch,but with discussion with my manager and team, we all thought this is the time to upgrade so we changed to 11g
    then 11g upgrade is 100% successfully completed, to verify the export on 11g ,i thought to take logical backup of my 2 database's
    C:\Users\Administrator>exp system/password@tnsname file=full_05_1_2013.dmp log=05_1_2013.log full=y
    Export: Release 11.2.0.1.0 - Production on Sat Jan 19 09:18:06 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Export done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set
    server uses AR8MSWIN1256 character set (possible charset conversion)
    About to export the entire database ...
    . exporting tablespace definitions
    . exporting profiles
    . exporting user definitions
    . exporting roles
    . exporting resource costs
    . exporting rollback segment definitions
    . exporting database links
    . exporting sequence numbers
    . exporting directory aliases
    . exporting context namespaces
    . exporting foreign function library names
    . exporting PUBLIC type synonyms
    . exporting private type synonyms
    . exporting object type definitions
    . exporting system procedural objects and actions,
    what happening here is it just coming to this point and stopping here for hours............more than 10 hours (I have to kiill this session manually).I tried with single user its working but when i take full backup of database export , then it not working,,, i have cross check every possibilities by giving full privilages,space check,and many other but no solution, i was unable to take full backup ,(but i can take single user backup)
    i have even applied bundle patch (Oracle® Database Server Version 11.2.0.1 Patch 16) 100% sucessfully but the error continious)))))))))))))))))))))))))))))))))))
    NOTE:___one more twist here is , when i bounce the database then i can take full database backup with out error and warnings for 6 to 7 times then again at 8th time its again stopping at above point.......................................................(when i need full logical backup again i need to bounce the db)
    what for its stopping here, why it is not going forward,,, its issue with both the database's same,
    NOTE:ERROR IN MY ALERTLOG FILE AND TRACEFILE IS
    trace file d:\app\admin\diag\rdbms\memfa\memfa\trace\memfa_j000_7844.trc
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Windows NT Version V6.0 Service Pack 2
    CPU : 16 - type 8664, 16 Physical Cores
    Process Affinity : 0x0x0000000000000000
    Memory (Avail/Total): Ph:1148M/16379M, Ph+PgF:17118M/32914M
    Instance name: abha210
    Redo thread mounted by this instance: 1
    Oracle process number: 22
    Windows thread id: 7844, image: ORACLE.EXE (J000)
    *** 2013-01-17 12:00:00.124
    *** SESSION ID:(196.16104) 2013-01-17 12:00:00.124
    *** CLIENT ID:() 2013-01-17 12:00:00.124
    *** SERVICE NAME:(SYS$USERS) 2013-01-17 12:00:00.124
    *** MODULE NAME:(DBMS_SCHEDULER) 2013-01-17 12:00:00.124
    *** ACTION NAME:(PURGE_LOG) 2013-01-17 12:00:00.124
    purge queue_table SYS.SCHEDULER_FILEWATCHER_QT
    purge queue_table SYS.SCHEDULER$_EVENT_QTAB
    alertlogfile___________________________
    Thread 1 cannot allocate new log, sequence 123
    Private strand flush not complete
    Current log# 4 seq# 122 mem# 0: D:\APP\ADMIN\ORADATA\memfa\REDO04.LOG
    Thread 1 advanced to log sequence 123 (LGWR switch)
    Current log# 5 seq# 123 mem# 0: D:\APP\ADMIN\ORADATA\memfa\REDO05.LOG
    already i have change my redo log to 50 to 500 each(3) and increase retention time too
    i have tried for more than 50 time by running full database export command ,but its not working ,sometimes 24 hours till at that point only(if i bounce the both the database's then,full database export completes in 9 min(successfully without error and without warnings
    these are veru new databases size nearly 8gb each
    please assist/help me in solving this issue,

  • Cannot allocate new log

    Hello,
    I use Oracle 10.2. I have 3 redo groups, two members in each. I lost member of redo2 group, added it (alter system drop logfile member/alter system add logfile member). NOw I am getting alerts:
    Thread 1 advanced to log sequence xx
    Current log# 2 seq# (...) /redo02.log
    Current log# 2 seq# (...) /redo02b.log <- this is the one that was lost
    Thread 1 cannot allocate new log, sequence xxx
    Checkpoint not complete
    Current log# 2 seq# (...) /redo02.log
    Current log# 2 seq# (...) /redo02b.log
    Tue Mar 04 (..)
    Thread 1 advanced to log sequence xxx
    Current log# 3 seq# (...) /redo03.log
    Current log# 3 seq# (...) /redo03b.log
    I've read previous posts about it, but my problems seems to me to be different, because before losing that redo member I didn't have any alerts. Only after adding it again I have. I neither change anything in number of redo groups nor in redo member sizes.
    Greets
    A.

    The message has nothing to do with your dropping and adding a member.
    The "checkpoint not complete" indicates that the Checkpoint that Oracle
    implicitly issued when switching out of a log group hadn't completed by the
    time the logwriter came around back to the same log group.
    The checkpoint is taking approximately the same time as it takes the logwriter
    to cycle through your 3 groups. Group 2 just happens to be the boundary case.
    You should either
    a Add more groups
    b Add new groups of larger sizes and drop the existing groups (of smaller sizes).

  • Cannot allocate new log importing hanging

    Hai All,
    When I imort a 1.59 Gb data into a database after some time
    a mesaage in alertlog file and import hanging
    message
    ======
    Thread 1 cannot allocate new log, sequence 7
    Checkpoint not complete
    ======
    I have 3 redo log groups with 2 members with the size of 300MB
    How to resolve this? pleas help its an urgent.. please..
    Shiju

    Firstly the database in archive mode but I changed to noarchive mode before imorting the data
    my sql screen
    ==========
    SQL> archive log list
    Database log mode No Archive Mode
    Automatic archival Enabled
    Archive destination /archive
    Oldest online log sequence 7
    Current log sequence 11
    SQL>
    Please help
    Shiju

  • 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

  • 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

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

Maybe you are looking for