Thread 1 advanced to log sequence (redo log)

Hi All,
db:oracle 10gR2(10.2.0.4)
os:solaris10
My alert log file shows following information all the time....can you please explain me whats going on??
Mon Jan 30 01:40:30 2012
Thread 1 advanced to log sequence 253305
Current log# 2 seq# 253305 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
Mon Jan 30 01:45:40 2012
Thread 1 advanced to log sequence 253306
Current log# 3 seq# 253306 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
Mon Jan 30 01:51:21 2012
Thread 1 advanced to log sequence 253307
Current log# 1 seq# 253307 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
Mon Jan 30 01:56:53 2012
Thread 1 advanced to log sequence 253308
Current log# 2 seq# 253308 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
Mon Jan 30 02:01:57 2012
Thread 1 advanced to log sequence 253309
Current log# 3 seq# 253309 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
Mon Jan 30 02:06:31 2012
Thread 1 advanced to log sequence 253310
Current log# 1 seq# 253310 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
Mon Jan 30 02:11:37 2012
Thread 1 advanced to log sequence 253311
Current log# 2 seq# 253311 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
Mon Jan 30 02:16:44 2012
Thread 1 advanced to log sequence 253312
Current log# 3 seq# 253312 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
Mon Jan 30 02:21:51 2012
Thread 1 advanced to log sequence 253313
Current log# 1 seq# 253313 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
Mon Jan 30 02:27:11 2012
Thread 1 advanced to log sequence 253314
Current log# 2 seq# 253314 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
Mon Jan 30 02:32:31 2012
Thread 1 advanced to log sequence 253315
Current log# 3 seq# 253315 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
Mon Jan 30 02:37:25 2012
Thread 1 advanced to log sequence 253316
Current log# 1 seq# 253316 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO01.LOG
Mon Jan 30 02:42:15 2012
Thread 1 advanced to log sequence 253317
Current log# 2 seq# 253317 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO02.LOG
Mon Jan 30 02:47:05 2012
Thread 1 advanced to log sequence 253318
Current log# 3 seq# 253318 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\JNPC\REDO03.LOG
I appreciate your response......
thanks.

This information shows that the log switch has occured.
The LGWR writes the redo information from the redo log buffer to the online redo log file. When the current online redo log file fills, LGWR begins writing to the next available online redo log file. In the mean time, the ARC process archives the contents of the filled online redo log file (If the database is in archivelog mode. If its in noarchive mode, then the filled online redo log file would not be archived). These archives are given a unique log sequence number.
In your case 253305, 253306..are the log sequence numbers.
You can refer http://docs.oracle.com/cd/B10501_01/server.920/a96521/onlineredo.htm for a detailed information

Similar Messages

Thread 1 advanced to log sequence 33072???

what is the quick solution to it..

sorry forgot to add this.....
Thread 1 cannot allocate new log, sequence 33073
Checkpoint not complete
Current log# 2 seq# 33072 mem# 0: /home/oracle/oracle/product/10.2.0/oradata/orcl2/redo02.log
Mon Dec 10 09:59:46 2007

Multiple log groups per thread to improve performance with high redo writes

I am reading Pro Oracle 10g RAC on Linux (good book). On p.35 the authors state that they recommend 3-5 redo log groups per thread if there is a "large" amount of redo.
Who does having more redo log groups improve performance? Does oracle paralelize the writes?

redo logs are configured per instance, from experience you need atleast 3 redo log groups per thread to help switch over and sufficient time for archives to complete before reuse of the first redo log group. When you have a large redo log activity there is a potential that redo log groups will switch more often and it is important that archive has completed before an exisiting redo log group can be reused, else the database /instance may hang.
I think that is what the author is referencing here, have sufficient redo log groups (based on the acitivty of your environment) to allow switching and allowing sufficient time for archives to complete.

A More Advanced History Log with Smart Timer

In the way that I use photoshop, I heavily depend on the History Log. I would like to have the option to preserve the data in the History Window instead of having to cut and paste the various 'History States' and then save them as different layers. In addition, I would like the option to be able to see the exact timing of each action performed in the history window.
I would like to know how much time I am spending on each open window in Photoshop, Lightroom or other Adobe Product. A Smart Timer built into the history log would be perfect for this.
A Simple tool that generates an Embedded Log of the date, the exact start and end time, a log entry showing when that photoshop window was on top of the screen with mouse or graphic tablet activity, and an exact minute count of how long that photoshop window was worked on (minus the bathroom breaks or moments of inactivity).
I can't tell you how much I would love to be able to open up a Photoshop Document that I previously worked on and have the History Log in the History Window still preserved.... no matter how large of a file is saved. With the embedded Smart Timer, It would be great to be able to show my clients the exact time that was worked on their projects. It would also be nice to check up on students, employeess or co-workers progress.
Thank You

there is it is called "name"
here is an example of how to find all faces that are not named currently
make a smart albumn
choose "Name" in first field
Then "contains"
The leave it blank
anywhere that it finds a name that is empty it sorts it to the smart folder and you then can go thru them that way
Please note that some photos have more than one face and even if one face is named and the others are not it still finds it and sorts it to the smart album

Any advanced call log tracker for Palm Treo's?

I own a Palm Treo 680, with Rogers as my carrier. I subscribe to a phone plan that allows me to call 200 daytime min/mth (8am-6pm) for free and $x.xx thereafter, and unlimited evenings & weekends. I also subscribe to text messaging; Rogers allows me to send 125 msgs/mth and $0.xx thereafter, & receiving text msgs is free. Now, "Total Hawk 1.01" by Wolflane Software comes close to what I want, but doesn't allow me to enter parameters for the said restrictions. Does anyone know of any palm software that is slightly more advanced than "Total Hawk"? Thx in advance.
Post relates to: Treo 680 (Rogers)

Personally I don't use any software to track this, but I did a lot of looking around and the Total Hawk looks like the best that is out there.
One software you might want to look at is Central for Treo looks like 4.40 is the latest version
http://www.palmloyal.com/addons.php?name=News&file=article&sid=17929
Post relates to: Centro (Sprint)

I am trying to have some LabVIEW code called in a New thread exit when the testStand sequence terminates

I have a Sequence that launches a sequence in a New Thread that happens to launch some LabVIEW code. The problem is when the LabVIEW code finishes, it will not close even when the TestStand sequence terminates. Is there a way to tell this LabVIEW code to Exit, I've tried the Quit LabVIEW function, but that causes a C++ RunTime Error. The LabVIEW code does end though, and it is set in the VI properties to:
Checked - Show Front Panel When Called
Checked - Close Afterwardds if originally closed
The sequence call that the LabVIEW code is launched from has the following options:
- New Thread
Unchecked - Automatically wait for the thread to complete at the end of the current sequence
Unchecked - Initially Suspended
Unchecked - Use single threaded apartment
Any clues on this would be appreciated.

Hi ADL,
Everything should close correctly if you check the checkbox "Automatically wait for the thread to complete at the end of the current sequence" in the thread settings.
With it unchecked, I am seeing the behavior you are.
Gavin Fox
Systems Software
National Instruments

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

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)"信息不再出现，当然一般也可以忽略该问题

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

ARC0: Unable to archive log 1 thread 1 sequence 1292

Hi all,
We are getting error in our alert logfile:
We are using oracle 9.2.0.8 on RHEL5, is there solution to overcome this problem
Thread 1 advanced to log sequence 1293
Current log# 3 seq# 1293 mem# 0: /u01/app/oracle/oradata/icai/redo03.log
Current log# 3 seq# 1293 mem# 1: /oradata/data/redo03a.log
Current log# 3 seq# 1293 mem# 2: /oradata/data/redo03d
Mon Aug 16 11:31:10 2010
ARC0: Evaluating archive   log 2 thread 1 sequence 1291
ARC0: Unable to archive log 2 thread 1 sequence 1291
      Log actively being archived by another process
Mon Aug 16 11:31:28 2010
ARC3: Completed archiving log 2 thread 1 sequence 1291
Mon Aug 16 11:50:44 2010
Thread 1 advanced to log sequence 1293
Current log# 3 seq# 1293 mem# 0: /u01/app/oracle/oradata/icai/redo03.log
Current log# 3 seq# 1293 mem# 1: /oradata/data/redo03a.log
Current log# 3 seq# 1293 mem# 2: /oradata/data/redo03d
Mon Aug 16 11:50:44 2010
ARCH: Evaluating archive   log 1 thread 1 sequence 1292
Mon Aug 16 11:50:44 2010
ARCH: Beginning to archive log 1 thread 1 sequence 1292
Mon Aug 16 11:50:44 2010
ARC3: Evaluating archive   log 1 thread 1 sequence 1292
Mon Aug 16 11:50:44 2010
ARC3: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:50:44 2010
Creating archive destination LOG_ARCHIVE_DEST_3: 'drsite_delhi'
Creating archive destination LOG_ARCHIVE_DEST_2: 'hp'
Mon Aug 16 11:51:21 2010
ARC0: Evaluating archive   log 1 thread 1 sequence 1292
ARC0: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:51:28 2010
ARC3: Evaluating archive   log 1 thread 1 sequence 1292
ARC3: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:52:21 2010
ARC0: Evaluating archive   log 1 thread 1 sequence 1292
ARC0: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:53:21 2010
ARC0: Evaluating archive   log 1 thread 1 sequence 1292
ARC0: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:54:21 2010
ARC0: Evaluating archive   log 1 thread 1 sequence 1292
ARC0: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:54:37 2010
ARC1: Evaluating archive   log 1 thread 1 sequence 1292
ARC1: Unable to archive log 1 thread 1 sequence 1292

rt noe the value os log_archive_maz_process=4
SQL> show parameter log_arch
NAME TYPE VALUE
log_archive_dest string
log_archive_dest_1 string location=/arch/icai/icai_ mand
atory
log_archive_dest_10 string
log_archive_dest_2 string service=hp optional reopen=15
log_archive_dest_3 string service=drsite_delhi optional
reopen=15
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
NAME TYPE VALUE
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
NAME TYPE VALUE
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s.dbf
log_archive_max_processes integer 4
log_archive_min_succeed_dest integer 1
log_archive_start boolean TRUE
log_archive_trace integer 0
SQL>

ORA-00333: redo log read error block

ORA-01033: ORACLE initialization or shutdown in progress ...
/ as sysdba
SQL> shutdown immediate;
SQL> startup nomount;
SQL> alter database mount;
SQL> alter database open;
ORA-00333: redo log read error block 8299 count 8192
SQL> SELECT * FROM V$VERSION;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Product
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL> select group#,members,THREAD, STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE# from v$log;
GROUP# MEMBERS,THREAD,STATUS,ARCHIVED,BYTES,FIRST_TIME,FIRST_CHAGE#,SEQUENCE#
1 1 1 CURRENT NO 52428800 29-FEB-12 1597643 57
2 1 1 INACTIVE NO 52428800 29-FEB-12 1573462 56
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Feb 29 19:46:38 2012
Recovery of Online Redo Log: Thread 1 Group 1 Seq 56 Reading mem 0
Mem# 0 errs 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_7LZYZK8S_.LOG
Wed Feb 29 19:46:40 2012
Completed redo application
Wed Feb 29 19:46:40 2012
Completed crash recovery at
Thread 1: logseq 56, block 6568, scn 1597642
270 data blocks read, 270 data blocks written, 1460 redo blocks read
Wed Feb 29 19:46:43 2012
Thread 1 advanced to log sequence 57
Thread 1 opened at log sequence 57
Current log# 2 seq# 57 mem# 0: C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
Successful open of redo thread 1
Wed Feb 29 19:46:43 2012
SMON: enabling cache recovery
Wed Feb 29 19:46:55 2012
Successfully onlined Undo Tablespace 1.
Wed Feb 29 19:46:55 2012
SMON: enabling tx recovery
Wed Feb 29 19:46:56 2012
Database Characterset is AL32UTF8
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=19, OS id=3024
Wed Feb 29 19:47:09 2012
Completed: alter database open
Wed Feb 29 19:47:14 2012
db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Wed Feb 29 20:33:30 2012
MMNL absent for 1537 secs; Foregrounds taking over
Wed Feb 29 20:33:31 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:31 2012
MMNL absent for 1540 secs; Foregrounds taking over
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:32 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 20:33:33 2012
MMNL absent for 1540 secs; Foregrounds taking over
Wed Feb 29 21:45:24 2012
MMNL absent for 4318 secs; Foregrounds taking over
MMNL absent for 4318 secs; Foregrounds taking over
MMNL absent for 4322 secs; Foregrounds taking over
Dump file c:\oraclexe\app\oracle\admin\xe\bdump\alert_xe.log
Wed Feb 29 22:30:01 2012
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 3, v.3244
CPU : 2 - type 586, 2 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:3097M/3546M, Ph+PgF:5143M/5429M, VA:1943M/2047M
Wed Feb 29 22:30:01 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
__shared_pool_size = 201326592
__large_pool_size = 8388608
__java_pool_size = 4194304
__streams_pool_size = 0
spfile = C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DBS\SPFILEXE.ORA
sga_target = 805306368
control_files = C:\ORACLEXE\ORADATA\XE\CONTROL.DBF
__db_cache_size = 587202560
compatible = 10.2.0.1.0
db_recovery_file_dest = C:\oraclexe\app\oracle\flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 4
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=winsp3ue)(PORT=1522))
job_queue_processes = 4
audit_file_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\ADUMP
background_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\BDUMP
user_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\UDUMP
core_dump_dest = C:\ORACLEXE\APP\ORACLE\ADMIN\XE\CDUMP
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 268435456
PMON started with pid=2, OS id=2176
PSP0 started with pid=3, OS id=2204
MMAN started with pid=4, OS id=2208
DBW0 started with pid=5, OS id=2212
LGWR started with pid=6, OS id=2220
CKPT started with pid=7, OS id=2240
SMON started with pid=8, OS id=2460
RECO started with pid=9, OS id=2464
CJQ0 started with pid=10, OS id=2480
MMON started with pid=11, OS id=2484
Wed Feb 29 22:30:02 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=2492
Wed Feb 29 22:30:02 2012
starting up 4 shared server(s) ...
Oracle Data Guard is not available in this edition of Oracle.
Wed Feb 29 22:30:02 2012
alter database mount exclusive
Wed Feb 29 22:30:06 2012
Setting recovery target incarnation to 2
Wed Feb 29 22:30:06 2012
Successful mount of redo thread 1, with mount id 2657657770
Wed Feb 29 22:30:06 2012
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Wed Feb 29 22:30:07 2012
alter database open
Wed Feb 29 22:30:07 2012
Beginning crash recovery of 1 threads
Wed Feb 29 22:30:07 2012
Started redo scan
Wed Feb 29 22:30:15 2012
Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
ORA-00333: redo log read error block 10347 count 6144
ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
ORA-27070: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).
Waiting for Help
Regards

Errors in file c:\oraclexe\app\oracle\admin\xe\udump\xe_ora_2544.trc:
ORA-00333: redo log read error block 10347 count 6144
ORA-00312: online log 2 thread 1: 'C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG'
ORA-27070: async read/write failed
OSD-04016: Error queuing an asynchronous I/O request.
O/S-Error: (OS 23) Data error (cyclic redundancy check).Might your redo log file is corrupted or not exist, check physically. -> C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_7LZYZL5V_.LOG
is it archivelog mode?
perform fake recovery and open resetlogs.

Thread 1 advanced to log sequence (redo log)

Similar Messages

Maybe you are looking for