Path: text.usenetserver.com!out04a.usenetserver.com!news.usenetserver.com!in02.usenetserver.com!news.usenetserver.com!postnews.google.com!m36g2000hse.googlegroups.com!not-for-mail From: Mark D Powell Newsgroups: comp.databases.oracle.server Subject: Re: Thread 1 cannot allocate new log, sequence Date: Fri, 3 Oct 2008 05:38:33 -0700 (PDT) Organization: http://groups.google.com Lines: 54 Message-ID: References: <1a412016-3325-426b-a3a8-28f5c91100fe@a1g2000hsb.googlegroups.com> NNTP-Posting-Host: 192.85.50.2 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1223037513 28218 127.0.0.1 (3 Oct 2008 12:38:33 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Fri, 3 Oct 2008 12:38:33 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: m36g2000hse.googlegroups.com; posting-host=192.85.50.2; posting-account=qJFqbQkAAACYQSLN0-cvP6ydkRfuOu6u User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe) Xref: usenetserver.com comp.databases.oracle.server:448389 X-Received-Date: Fri, 03 Oct 2008 08:38:33 EDT (text.usenetserver.com) On Oct 2, 11:29=A0am, ddf wrote: > On Oct 2, 8:52=A0am, "odbio...@spamu.pl" wrote: > > > Hi, > > > I have 2 "Thread 1 cannot allocate new log, sequence" messages in my or= acle'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 =A0 =A0 group# "GROUP", > =A0 =A0 =A0 =A0 bytes "SIZE", > =A0 =A0 =A0 =A0 status "STATUS" > FROM =A0 =A0 =A0 v$log; > > 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# =3D a.sequence# + 1 > AND a.sequence# =3D (SELECT MAX(sequence#) FROM v$loghist) > ORDER BY a.sequence#; > > You're probably running =A0that database in archivelog mode and the > error was generated because of an archiving issue. =A0It could also be > generated by a 'checkpoint not complete' =A0problem. =A0Transactional > 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 I agree with David and Hans. Look at how often you switch redo logs then perform some combination of adding more online redo logs or make them bigger if you regularly see places where the online redo logs are switching within only a couple of minutes. It is generally fine if you have one short switch time every day as long as the other times are more reasonable. But it you have an extended period where you are constantly switching you need bigger logs. HTH -- Mark D Powell --