Re: Thread 1 cannot allocate new log, sequence
Date: Fri, 03 Oct 2008 14:02:58 +0200
Message-ID: <gc51li$atn$1@news.onet.pl>
ddf pisze:
> On Oct 2, 8:52 am, "odbio..._at_spamu.pl" <odbio..._at_spamu.pl> wrote:
>> Hi, >> >> I have 2 "Thread 1 cannot allocate new log, sequence" messages in my oracle's alert log. This messeges were few days ago and didn't come back. Is it >> problem. Should I do something with it? >> >> Thanks in advance
>
> It might be, it might NOT be.
>
> Check your redo log size
>
> SELECT group# "GROUP",
> bytes "SIZE",
> status "STATUS"
> FROM v$log;
Result:
GROUP SIZE STATUS
---------- ---------- ----------------
1 104857600 INACTIVE
2 104857600 CURRENT
3 104857600 INACTIVE
4 104857600 INACTIVE
5 104857600 INACTIVE
>
> and your redo log switch time
>
> SELECT ROUND(AVG(1440 * (b.first_time - a.first_time)), 0) "Log switch
> time - minutes"
> FROM v$loghist a, v$log b
> WHERE b.sequence# = a.sequence# + 1
> AND a.sequence# = (SELECT MAX(sequence#) FROM v$loghist)
> ORDER BY a.sequence#;
Result:
Log switch
time - minutes
8
>
> You're probably running that database in archivelog mode and the
> error was generated because of an archiving issue. It could also be
> generated by a 'checkpoint not complete' problem.
Yes.
It was "Checkpoint not complete"
Transactional
> activity in your database may have hit a new 'high' at the point those
> error messages appeared, causing Oracle to fall behind on it's
> archiving of the older redo logs prior to re-use because the log
> switch time decreased dramatically.
>
> Of course without actually seeing your system and its activity level
> all of this is simply guesswork.
>
>
> David Fitzjarrell
Received on Fri Oct 03 2008 - 07:02:58 CDT