Private strand flush not complete message

Hi,
I am running Oracle10gR2 on Windows and I occationally receive the following error message on alert file. I could not find any documentation why I'm geting this.
Thread 1 cannot allocate new log, sequence 2112
"Private strand flush not complete"
I added a new log group with 2 members but I am still recieving the error.
Do you think increasing the logfile size would help? If so, is it possible to have different logfile size in oracle? and can I do this dynamically?
Thanks,
Amir

I also get this error:
Thread 1 cannot allocate new log, sequence 2122
Checkpoint not complete
How can I increase the log file?

Similar Messages

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

  • Alert log: Private strand flush not complete

    We are runnig Oracle 10.2
    I noticed we are getting "Private strand flush not complete" line in alert log file.
    Here is the snippet from the actual alert log file.
    Thu Aug 31 06:27:23 2006
    Thread 1 advanced to log sequence 17998
    Current log# 3 seq# 17998 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
    Current log# 3 seq# 17998 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
    Thu Aug 31 06:31:12 2006
    Thread 1 advanced to log sequence 17999
    Current log# 4 seq# 17999 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
    Current log# 4 seq# 17999 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
    Thu Aug 31 06:35:49 2006
    Thread 1 advanced to log sequence 18000
    Current log# 5 seq# 18000 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
    Current log# 5 seq# 18000 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
    Thu Aug 31 06:40:59 2006
    Thread 1 advanced to log sequence 18001
    Current log# 6 seq# 18001 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
    Current log# 6 seq# 18001 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
    Thu Aug 31 06:45:03 2006
    Thread 1 advanced to log sequence 18002
    Current log# 1 seq# 18002 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
    Current log# 1 seq# 18002 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
    Thu Aug 31 06:49:21 2006
    Thread 1 advanced to log sequence 18003
    Current log# 2 seq# 18003 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
    Current log# 2 seq# 18003 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
    Thu Aug 31 06:52:04 2006
    Thread 1 cannot allocate new log, sequence 18004
    Private strand flush not complete
    Current log# 2 seq# 18003 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
    Current log# 2 seq# 18003 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
    Thread 1 advanced to log sequence 18004
    Current log# 3 seq# 18004 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
    Current log# 3 seq# 18004 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.logThu Aug 31 06:55:40 2006
    Thread 1 advanced to log sequence 18005
    Current log# 4 seq# 18005 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
    Current log# 4 seq# 18005 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
    Thu Aug 31 06:59:21 2006
    Thread 1 advanced to log sequence 18006
    Current log# 5 seq# 18006 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
    Current log# 5 seq# 18006 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
    Thu Aug 31 07:03:35 2006
    Thread 1 advanced to log sequence 18007
    Current log# 6 seq# 18007 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
    Current log# 6 seq# 18007 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
    Thu Aug 31 07:08:28 2006
    Thread 1 advanced to log sequence 18008
    Current log# 1 seq# 18008 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
    Current log# 1 seq# 18008 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
    Thu Aug 31 07:11:31 2006
    Thread 1 advanced to log sequence 18009
    Current log# 2 seq# 18009 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
    Current log# 2 seq# 18009 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
    Thu Aug 31 07:15:32 2006
    Thread 1 advanced to log sequence 18010
    Current log# 3 seq# 18010 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
    Current log# 3 seq# 18010 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
    Thu Aug 31 07:23:10 2006
    Thread 1 advanced to log sequence 18011
    Current log# 4 seq# 18011 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
    Current log# 4 seq# 18011 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
    Thu Aug 31 07:28:41 2006
    Thread 1 advanced to log sequence 18012
    Current log# 5 seq# 18012 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
    Current log# 5 seq# 18012 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
    Thu Aug 31 07:32:35 2006
    Thread 1 advanced to log sequence 18013
    Current log# 6 seq# 18013 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
    Current log# 6 seq# 18013 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
    Thu Aug 31 07:36:00 2006
    Thread 1 advanced to log sequence 18014
    Current log# 1 seq# 18014 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
    Current log# 1 seq# 18014 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
    Thu Aug 31 07:39:42 2006
    Thread 1 advanced to log sequence 18015
    Current log# 2 seq# 18015 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
    Current log# 2 seq# 18015 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
    Thu Aug 31 07:44:36 2006
    Thread 1 advanced to log sequence 18016
    Current log# 3 seq# 18016 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
    Current log# 3 seq# 18016 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
    Thu Aug 31 07:49:13 2006
    Thread 1 advanced to log sequence 18017
    Current log# 4 seq# 18017 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
    Current log# 4 seq# 18017 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
    Thu Aug 31 07:57:52 2006
    Thread 1 advanced to log sequence 18018
    Current log# 5 seq# 18018 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
    Current log# 5 seq# 18018 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
    Thu Aug 31 08:02:52 2006
    Thread 1 advanced to log sequence 18019
    Current log# 6 seq# 18019 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
    Current log# 6 seq# 18019 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
    Thu Aug 31 08:05:50 2006
    Thread 1 advanced to log sequence 18020
    Current log# 1 seq# 18020 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
    Current log# 1 seq# 18020 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
    Thu Aug 31 08:08:24 2006
    Thread 1 cannot allocate new log, sequence 18021
    Private strand flush not complete
    Current log# 1 seq# 18020 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
    Current log# 1 seq# 18020 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
    Thread 1 advanced to log sequence 18021
    Current log# 2 seq# 18021 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
    Current log# 2 seq# 18021 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
    Thu Aug 31 08:09:53 2006
    Thread 1 advanced to log sequence 18022
    Current log# 3 seq# 18022 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
    Current log# 3 seq# 18022 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
    Thu Aug 31 08:12:02 2006
    Thread 1 advanced to log sequence 18023
    Current log# 4 seq# 18023 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
    Current log# 4 seq# 18023 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
    Thu Aug 31 08:14:09 2006
    Thread 1 advanced to log sequence 18024
    Current log# 5 seq# 18024 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
    Current log# 5 seq# 18024 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
    Thu Aug 31 08:14:22 2006
    Thread 1 advanced to log sequence 18025
    Current log# 6 seq# 18025 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
    Current log# 6 seq# 18025 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
    Thu Aug 31 08:21:13 2006
    Thread 1 advanced to log sequence 18026
    Current log# 1 seq# 18026 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
    Current log# 1 seq# 18026 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
    Thu Aug 31 08:23:42 2006
    Thread 1 advanced to log sequence 18027
    Current log# 2 seq# 18027 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
    Current log# 2 seq# 18027 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
    Thu Aug 31 08:25:12 2006
    Thread 1 advanced to log sequence 18028
    Current log# 3 seq# 18028 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
    Current log# 3 seq# 18028 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
    Thu Aug 31 08:32:06 2006
    Thread 1 advanced to log sequence 18029
    Current log# 4 seq# 18029 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
    Current log# 4 seq# 18029 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
    Thu Aug 31 08:40:34 2006
    Thread 1 advanced to log sequence 18030
    Current log# 5 seq# 18030 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
    Current log# 5 seq# 18030 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
    Thu Aug 31 08:41:25 2006
    Thread 1 advanced to log sequence 18031
    Current log# 6 seq# 18031 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
    Current log# 6 seq# 18031 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
    Thu Aug 31 08:43:10 2006
    Thread 1 advanced to log sequence 18032
    Current log# 1 seq# 18032 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
    Current log# 1 seq# 18032 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
    Thu Aug 31 08:44:22 2006
    Thread 1 advanced to log sequence 18033
    Current log# 2 seq# 18033 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
    Current log# 2 seq# 18033 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
    Thu Aug 31 08:45:40 2006
    Thread 1 advanced to log sequence 18034
    Current log# 3 seq# 18034 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
    Current log# 3 seq# 18034 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
    Thu Aug 31 08:46:20 2006
    Thread 1 advanced to log sequence 18035
    Current log# 4 seq# 18035 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
    Current log# 4 seq# 18035 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
    Thu Aug 31 08:49:32 2006
    Thread 1 advanced to log sequence 18036
    Current log# 5 seq# 18036 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
    Current log# 5 seq# 18036 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
    Thu Aug 31 08:50:51 2006
    Thread 1 advanced to log sequence 18037
    Current log# 6 seq# 18037 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
    Current log# 6 seq# 18037 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
    Thu Aug 31 08:52:24 2006
    Thread 1 advanced to log sequence 18038
    Current log# 1 seq# 18038 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
    Current log# 1 seq# 18038 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
    Thu Aug 31 08:53:47 2006
    Thread 1 advanced to log sequence 18039
    Current log# 2 seq# 18039 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
    Current log# 2 seq# 18039 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
    Thu Aug 31 08:54:55 2006
    Thread 1 advanced to log sequence 18040
    Current log# 3 seq# 18040 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
    Current log# 3 seq# 18040 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
    Thu Aug 31 08:56:51 2006
    Thread 1 advanced to log sequence 18041
    Current log# 4 seq# 18041 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
    Current log# 4 seq# 18041 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
    Thu Aug 31 08:58:12 2006
    Thread 1 advanced to log sequence 18042
    Current log# 5 seq# 18042 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
    Current log# 5 seq# 18042 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
    Thu Aug 31 08:59:14 2006
    Thread 1 advanced to log sequence 18043
    Current log# 6 seq# 18043 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
    Current log# 6 seq# 18043 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
    Thu Aug 31 09:00:17 2006
    Thread 1 advanced to log sequence 18044
    Current log# 1 seq# 18044 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
    Current log# 1 seq# 18044 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
    Can some one help me to understand what does it mean? Do we need to take any action?
    TIA.
    Regards,
    Dharmesh Patel

    There's a metalink note about this
    (Alert Log Messages: Private Strand Flush Not Complete
    Note:372557.1), but the most importannt message is :
    These messages are not a cause for concern unless there is a significant gap between the "cannot allocate new log" message and the "advanced to log sequence" message.
    This issue is infact not a bug and is expected behaviour.
    Werner

  • Private strand flush not complete in 11gR2 Database

    Hi All
    We have upgraded our EBS11i instacne 10.2.0.3 to 11.2.0.1 and we have found the issue in alert like "Private strand flush not complete"
    Alert log content:
    Private strand flush not complete
    Current log# 4 seq# 12241 mem# 0: /ebiz/oracle/proddata/log4b.dbf
    Current log# 4 seq# 12241 mem# 1: /ebiz/oracle/proddata/log4a.dbf
    Current log# 4 seq# 12241 mem# 2: /ebiz/oracle/proddata/log4c.dbf
    Beginning log switch checkpoint up to RBA [0x2fd2.2.10], SCN: 5965767130292
    Thread 1 advanced to log sequence 12242 (LGWR switch)
    Current log# 1 seq# 12242 mem# 0: /ebiz/oracle/proddata/log1b.dbf
    Current log# 1 seq# 12242 mem# 1: /ebiz/oracle/proddata/log1a.dbf
    Current log# 1 seq# 12242 mem# 2: /ebiz/oracle/proddata/log1c.dbf
    Thu Dec 01 08:31:07 2011
    Archived Log entry 11610 added for thread 1 sequence 12241 ID 0x3c710a4 dest 1:
    Thu Dec 01 08:36:16 2011
    Completed checkpoint up to RBA [0x2fd2.2.10], SCN: 5965767130292
    Thu Dec 01 08:42:43 2011
    Incremental checkpoint up to RBA [0x2fd2.489.0], current log tail at RBA [0x2fd2.7bc.0]
    Thu Dec 01 09:00:25 2011
    kewastUnPackStats(): bad magic 1 (0xb72d1fa0, 0)
    kewastUnPackStats(): bad magic 1 (0xb72d1fa0, 0)
    Thu Dec 01 09:02:48 2011
    We have check MOS documnet "Alert Log Messages: Private Strand Flush Not Complete [ID 372557.1]" which is for 11gR1.
    We have any solutione for this issue in 11gR2.
    Regards
    Shaik

    Please see these docs.
    Init.ora Parameter "DB_WRITER_PROCESSES" Reference Note [ID 67422.1]
    Understanding and Tuning Buffer Cache and DBWR [ID 62172.1]
    Thanks,
    Hussein

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

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

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

  • Private strand flush not complete

    hi,
    I have installed oracle 10.2.0 installed and i have configured rman daily backup on it.
    But i got some entries in my alert log like.
    Mon Sep 15 03:55:18 2008
    Thread 1 cannot allocate new log, sequence 416
    Private strand flush not complete
      Current log# 3 seq# 415 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\NEO\REDO03.LOG
    Thread 1 advanced to log sequence 416
      Current log# 1 seq# 416 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\NEO\REDO01.LOG
    Mon Sep 15 03:55:27 2008
    Starting control autobackup
    Mon Sep 15 03:55:28 2008
    Errors in file d:\oracle\product\10.2.0\admin\neo\udump\neo_ora_4384.trc:
    Mon Sep 15 03:55:28 2008
    Errors in file d:\oracle\product\10.2.0\admin\neo\udump\neo_ora_4384.trc:
    Mon Sep 15 03:55:28 2008
    Errors in file d:\oracle\product\10.2.0\admin\neo\udump\neo_ora_4384.trc:
    Control autobackup written to DISK device
         handle 'C:\ORACLE BACKUP SET\C-1742413464-20080915-00'In this code
    Private strand flush not complete
    is creating some problem due to this issue i got my daily backup job status as failed.
    i try to find the reason for this problem which is like
    [ http://www.dba-oracle.com/t_cannot_allocate_log_private_strand_flush.htm]
    which shows it is not an issue.
    even i try backup my archive log files by command.
    RMAN> backup archivelog all;
    Starting backup at 15-SEP-08
    current log archived
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=110 devtype=DISK
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=417 recid=45 stamp=665480457
    channel ORA_DISK_1: starting piece 1 at 15-SEP-08
    channel ORA_DISK_1: finished piece 1 at 15-SEP-08
    piece handle=C:\ORACLE BACKUP SET\1SJQKR8B_1_1 tag=TAG20080915T074059 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 15-SEP-08
    Starting Control File and SPFILE Autobackup at 15-SEP-08
    piece handle=C:\ORACLE BACKUP SET\C-1742413464-20080915-02 comment=NONE
    Finished Control File and SPFILE Autobackup at 15-SEP-08which also gives the same alert in my alert.log file.
    Thanks
    Umesh

    Hi,
    RMAN> show all
    2> ;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'C:\Oracle Backup Set\%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   'C:\Oracle Backup Set\%U';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFNEO.ORA'; # defaultand my disk has 12 gb of space left and total bakckup of my database is of 4 gb for last 5 days so i think space is not a problem.
    Hament is there any way to find out why the job failed exactly if you know.
    Thanks

  • Chronic checkpoint not complete message in alertlog file

    Hi,
    We have oracle 10g hosted on linux.i could see the following message in the alert log file.
    Thread 1 cannot allocate new log, sequence 184070 Checkpoint not complete.
    we have 3 redo log groups with 50MB size.
    In the initparameter file:The following values were set.
    log_checkpoint_interval = 0
    log_checkpoint_timeout =1800
    fast_start_mttr_target=0
    Can some one guide me what needs to be done to avoid the chronic checkpoint not complete message in the alertlog file.
    Thanks

    Thank you. Even i listed the history of log switches per hour over the last week:
    DAY 00:00 01:00 02:00 03:00 04:00 05:00 06:00 07:00 08:00 09:00 10:00 11:00 12:00 13:00 14:00 15:0
    18/08 280 279 283 280 281 283 281 275 279 275 230 0 0 0 0 0 0 0
    17/08 279 279 284 281 287 282 282 285 279 279 276 275 278 273 276 277 280
    16/08 277 283 283 277 278 279 277 284 279 278 280 280 279 277 280 281 278
    15/08 281 281 284 279 279 283 283 284 284 285 282 280 281 282 278 287 276
    14/08 272 277 281 278 282 279 279 283 280 281 283 284 283 279 278 278 278
    13/08 279 278 281 281 284 285 281 282 270 277 274 275 281 279 280 279 279
    12/08 396 403 362 431 430 295 280 281 285 285 280 289 289 284 281 284 279
    7 rows selected.

  • Error in local message system; message 008899000001 not complete, Message n

    Hello All,
    While configuring Solman Service Desk, after configuring basis configuration. I am getting following error while creating ticket from satellite system.
    Error in local message system; message 008899000001 not complete
    Message no. BCOS030
    Thanks,
    Piyush

    Hi,
    There were few threads in the past with the same issue, check [this one|ERROR when Trying to Create Support Message in Satillite system;.
    Also [this thread|create support message;.
    Regards
    Naveen

  • 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 in NOARCHIVELOG mode

    Hi,
    This is first time I am seeing this. In my 11.1.0.7 development database on SOLARIS, I see checkpoint not complete message in alert log file and my database is running in NOARCHIVELOG mode. Can any expert throw light on this that why this warning is there even in NOARCHIVELOG mode?
    Salman

    871174 wrote:
    Hi,
    This is first time I am seeing this. In my 11.1.0.7 development database on SOLARIS, I see checkpoint not complete message in alert log file and my database is running in NOARCHIVELOG mode. Can any expert throw light on this that why this warning is there even in NOARCHIVELOG mode?
    Salman,
    The error doesn't have any relation to the archive log or no archive log mode of the database but to the size of the redo log files of yours and some other factors. The error basically means that you are not able to checkpoint your last current redo quickly enough before it can be reused. What's the size of the redo log files of yours?
    Aman....

  • Checkpoint not complete in alert log file Oracle 11gR2 RAC

    Hi,
    I found checkpoint not complete in alert log file, almost every 3 seconds .
    In metalink i saw for this error, archive_lag_target=0, already this value was set to 0 in my database.
    We have 7 redo log groups for each instance, each group is of two redo log files, each file size is 50m.
    To avoid this error what i need to do..........
    please help me..................

    When you "checkpoint not complete" messages in your alert log this normally means your online redo logs are defined too small to handle the load and you have filled and need to switch to a new online redo log before the checkpoint triggered by the previous log switch has been completed.
    Increasing your online redo log size is normally the fix for this.
    HTH -- Mark D Powell --
    PS - The following Oracle support document may also apply:
    Checkpoint Not Complete In Alert.log Due To Setting Of Archive_lag_target [ID 435780.1]
    Edited by: Mark D Powell on Nov 7, 2011 8:29 AM

  • Check pont not complete

    hi
    is it true that Increasing the size of redo log will avoid
    'Check point not complete' message in alert log.
    One more thing, Is there any redo generate while taking export.
    Version 10g Rel 2
    Thanks in advance

    not on itself... I'd rather check the physical configuration of your redologs and the point in time when this happens. See, there is a lot of things going out on disk once a checkpoint occurs. With a bit of misconfiguration you'll have one (lets call it) thread write out the information on the same spindle that tries to switch the logfile. That's the point where your "Checkpoint not complete" happens.

  • Delivery group 001 is not complete

    Hi Gurus
    I created an order with multiple items having different shipping points and transportation groups.
    When I am creating delivery, I am able to do split the delivery and process it manually because of different shipping points and transportation groups.
    I created another order with the same items, If I am trying to run delivery in background with TCode VL10G or VL10BATCH, it is not allowing me to do so and it is showing an error:
    "Delivery group 001 is not complete
        Message no. VL089
    Diagnosis
        Delivery group 001 copied from the sales order on which the delivery is
        based, is not complete. Not all items of the delivery group exist in
        this delivery."
    Can anyone provide some info on how to run deliveries background with help of a batch?
    Points will be awarded. Please guide me.

    Yes. You are absolutely correct. It is about sales BOM.
    As this turned into another problem, I started new thread, but I will post the content here as well, coz this is my show stopper. Please help me.
    I have sales BOMs.
    BOM 1- Header -ABC, with components 1212, & 2323.
    BOM 2 - Header DEF, with components 4545, 5656
    Transportation group (from Material Master)
    Z01 - Restricted
    Z02 - Unrestricted
    Loading Group (from Material Master)
    Z01 - Restricted
    Z02 - Unrestricted
    I have few BOMs where the transportation group of header item and components BOTH do not differ and ALSO differ to one another.
    eg:
    ABC  Z02         DEF   Z01
    1212  Z01        4545   Z01
    2323  Z02        5656   Z01
    Ship.cond ;            Trans.Grp ;          Route
    A1                       Z01                     OVNT
    A1                       Z02                     4DAY
    Ship.Cond ;        Loading Grp            Plant             Ship.Point
    A1                    Z01                        1000              ZS1
    A1                    Z02                        1000              ZNS1   
    I created an order with a Sales BOM that has both restricted and unrestricted transportation group components.
    But for the whole BOM (including components), it is pulling up the data of Header item (route & shipping point) and it is not bringing in appropriate info (route & shipping point)  of components.
    EG: IDEALLY IT SHOULD BE LIKE THIS:
                        ROUTE            SHIP.POINT
    10  ABC        4DAY              ZNS1
    11  1212       OVNT              ZS1
    12  2323       4DAY              ZNS1
    BUT IT IS SHOWING UP IN ORDER LIKE BELOW:
                        ROUTE            SHIP.POINT
    10  ABC        4DAY              ZNS1
    11  1212       4DAY               ZNS1
    12  2323       4DAY               ZNS1
    Hope I am clear. I want to see the route and shipping point of components as they are determined from route determination and shipping point determination, unlike what I see now.
    2) Where I can find the configuration of Delivery group and other than in Item Category? Can you please suggest me the path? I would like to see separate delivery groups if the route and shipping points differ to the items in order for the appropriate delivery split.
    Please guide me how to fix this.
    Edited by: Vamsi  Sai Srinivas on Dec 8, 2008 5:21 AM

  • Commit not complete

    Hi,
    My program is written in ProC,which consists of several insert statement followed by commit.
    But when i exit the application i am getting an error " COMMIT NOT COMPLETE ".
    Need your suggestion very urgently.
    Thanks,
    Chitrasen

    Judging from the lack of response, I think you need to post a little more information.
    Are you sure all the inserts are successful? are you checking Oracle status after each one?
    Are you sure that the commit is called? Is successful? Are the rows you inserted visible in the database (eg from SQL*Plus)?
    How do you "exit the application"? Is there a chance that after your commit, something in the application initiates a new transaction?
    Where does this "COMMIT NOT COMPLETE" message come from?
    PS probably better to continue this post in the Call Interface forum which covers PRO* as well as OCI - see Oracle Call Interface (OCI)
    HTH
    Regards Nigel

  • 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