Re: Alert Log Warnings

Hi Chris,

Anyone seen this before? Yeah, sure!
This means all logs need archiving at the same time. There are two reasons for this happen:
either there is a 'burst' of transaction volume or the archive log disk is full, and Oracle can't archive any log In the latter case you can archive a log manually to a different destination. Usually, the problem is a combination of the two problems together. When I need to create a database I usually start off with groups, with members of 5M, and I make them bigger when Oracle starts generating the messages below. Please note: when this happens the system will hang until the condition is resolved. It is not slowing down, apparently still something happens that resolves the current situation.

Hth,

Sybrand Bakker, Oracle DBA

cmilner wrote in message <373A8300.47399859_at_connect.com.au>...
>Hiya,
>
>Getting the follow warnings in Alert log....
>
>Thu May 13 17:39:31 1999
>Thread 1 advanced to log sequence 14751
> Current log# 3 seq# 14751 mem# 0: /oradb/07/bta4/log2_3_bta4.dbf
> Current log# 3 seq# 14751 mem# 1: /oradb/08/bta4/log3_3_bta4.dbf
> Current log# 3 seq# 14751 mem# 2: /oradb/06/bta4/log1_3_bta4.dbf
>Thu May 13 17:40:11 1999
>Thread 1 cannot allocate new log, sequence 14752
>Checkpoint not complete
> Current log# 3 seq# 14751 mem# 0: /oradb/07/bta4/log2_3_bta4.dbf
> Current log# 3 seq# 14751 mem# 1: /oradb/08/bta4/log3_3_bta4.dbf
> Current log# 3 seq# 14751 mem# 2: /oradb/06/bta4/log1_3_bta4.dbf
>
>I'm pretty sure this is to do with redo logs not being large enough. I have
2 groups, each 8M, I added a third group 8M, but still get the warnings. Couldn't find any literature in the books either on this.
>
>Database seems be slowing as well!
>
>Any seen this before...
>
>Cheers
>
>Chris
Received on Thu May 13 1999 - 03:03:22 CDT