No question at this time
DBA Top 10
1 M. Cadot 6500
2 B. Vroman 2700
3 J. Péran 1600
4 P. Tsongayinwe 1500
5 P. Wisse 1200
6 A. Kavsek 1100
7 D. Walgude 400
7 J. Schnackenberg 400
9 J. Alcroft 200
10 A. Hudspith 100
10 D. Johnson 100
10 B. B 100
About
DBA-Village
The DBA-Village forum
Forum as RSS
as RSS feed
Site Statistics
Ever registered users48695
Total active users1320
Act. users last 24h0
Act. users last hour0
Registered user hits last week12
Registered user hits last month347
Go up

Thread 1 cannot allocate new log, sequence
Next thread: While adding disk to diskgroup we don't wont rebalnce how can we do that
Prev thread: ORA-01130 while performing Oracle Database Cloning

Message Score Author Date
In alert log of my oracle databases, I can read : ...... Purnelle Stéphane Sep 09, 2011, 15:27
Hi, this is not a error. It means that a manual l...... Score: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 Pts Peter Häusler Sep 09, 2011, 15:31
Hello Stéphane, here is a link that will help y...... Score: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 Pts Bruno Vroman Sep 09, 2011, 15:33
Sorry Peter but what you say is wrong. This e...... Score: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 Pts Michel Cadot Sep 09, 2011, 15:47
OK Thank you ... Purnelle Stéphane Sep 09, 2011, 15:54
Ok its the point of view... these messages are ...... Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts Peter Häusler Sep 09, 2011, 15:55
I have : 2011-09-09 13:31:27.208000 +02:00 Th...... Purnelle Stéphane Sep 09, 2011, 16:03
Hi Stéphane, "<i>In my case, there is not a sig...... Score: 500 PtsScore: 500 PtsScore: 500 PtsScore: 500 PtsScore: 500 Pts Bruno Vroman Sep 09, 2011, 16:12
<i> its the point of view </i> No it is a f...... Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts Michel Cadot Sep 09, 2011, 17:16
Have to learn that universal solving key for other...... Bye Bye Michel Cadot Sep 14, 2011, 13:51

Follow up by mail Click here


Subject: Thread 1 cannot allocate new log, sequence
Author: Purnelle Stéphane, Belgium
Date: Sep 09, 2011, 15:27, 4043 days ago
Os info: Oracle Enterprise Linux
Oracle info: Oracle 11.2.0
Message: In alert log of my oracle databases, I can read :

Thread 1 cannot allocate new log, sequence 248
Checkpoint not complete

I would like to know why I have this message and
some way to resolve it

Thank you
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Thread 1 cannot allocate new log, sequence
Author: Peter Häusler, Austria
Date: Sep 09, 2011, 15:31, 4043 days ago
Score:   Score: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 Pts
Message: Hi,
this is not a error. It means that a manual log switch has been take place in you database. This message is a harmless output in your database. You can read Metalink Note: 435887.1 for more information.

regards
Peter
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Thread 1 cannot allocate new log, sequence
Author: Bruno Vroman, Belgium
Date: Sep 09, 2011, 15:33, 4043 days ago
Score:   Score: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 Pts
Message: Hello Stéphane,

here is a link that will help you.
  http://www.lmgtfy.com/?q=%22cannot+allocate+new+log%22+%22checkpoint+not+complete%22

;-)

Bruno Vroman.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Thread 1 cannot allocate new log, sequence
Author: Michel Cadot, France
Date: Sep 09, 2011, 15:47, 4043 days ago
Score:   Score: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 Pts
Message:

Sorry Peter but what you say is wrong.
This error means the database (and everyone accessing it) has to wait dbwr ends the current checkpoint before it can allocate a new log and then allows transactions to go on.
So it is a performances harmful message.

Solutions are:
- You are not io bound, allocate new dbwr processes (db_writer_processes parameter)
- Allocate new log groups and increase their size
- Spread data of more disks
- Buy faster disks

Regards
Michel
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Thread 1 cannot allocate new log, sequence
Author: Purnelle Stéphane, Belgium
Date: Sep 09, 2011, 15:54, 4043 days ago
Message: OK

Thank you
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Thread 1 cannot allocate new log, sequence
Author: Peter Häusler, Austria
Date: Sep 09, 2011, 15:55, 4043 days ago
Score:   Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts
Message: Ok
its the point of view...
these messages are not a cause for concern unless there is a significant gap in seq# between the "cannot allocate new log" message and the "advanced to log sequence" message.

regards
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Thread 1 cannot allocate new log, sequence
Author: Purnelle Stéphane, Belgium
Date: Sep 09, 2011, 16:03, 4043 days ago
Message: I have :

2011-09-09 13:31:27.208000 +02:00
Thread 1 cannot allocate new log, sequence 246
Checkpoint not complete
Current log# 2 seq# 245 mem# 0: /.../redo02.log
2011-09-09 13:32:00.252000 +02:00
Thread 1 advanced to log sequence 246 (LGWR switch)
Current log# 3 seq# 246 mem# 0: /.../redo03.log

In my case, there is not a significant gap.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Thread 1 cannot allocate new log, sequence
Author: Bruno Vroman, Belgium
Date: Sep 09, 2011, 16:12, 4043 days ago
Score:   Score: 500 PtsScore: 500 PtsScore: 500 PtsScore: 500 PtsScore: 500 Pts
Message: Hi Stéphane,

"In my case, there is not a significant gap. "
Well,
   2011-09-09 13:31:27.208000 +02:00
   2011-09-09 13:32:00.252000 +02:00
This is more than 30 seconds with a DB "frozen"...

If it happens once in a while, I would say that this is a problem. If it happens 1 / 3 months, no worry.

Too be more kind than simply pointing to Google:
 Metalink note 147468.1 "Checkpoint Tuning and Troubleshooting Guide"

Best regards,

Bruno.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Thread 1 cannot allocate new log, sequence
Author: Michel Cadot, France
Date: Sep 09, 2011, 17:16, 4043 days ago
Score:   Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts
Message:

its the point of view

No it is a fact.

these messages are not a cause for concern unless there is a significant gap in seq# between the "cannot allocate new log" message and the "advanced to log sequence" message

The gap in sequence # is ALWAYS the number of redo log groups.
It cannot be less otherwise a new log can be allocated.
It cannot be more because this the reason of the message: no log is available to be allocated and the number that can be and is currently allocated is the number you have created.

Regards
Michel
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Thread 1 cannot allocate new log, sequence
Author: Bye Bye Michel Cadot, Croatia
Date: Sep 14, 2011, 13:51, 4038 days ago
Message: Have to learn that universal solving key for others!

THX for sharing that!
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here