Waiting for next logical log file to be freed
On IDS 7.31UC2 under Solaris 2.7 the engine stalled with "Waiting for Next Logical Log File to be Freed", even though continuous ontape -c backups were running and all 200 logs were marked backed up (B) except the current one. Martin Fuerderer suggested checking onstat -l to find which log was blocking, noting a log can stay pinned by a still-open transaction even after backup. The poster countered that LTXHWM/LTXEHWM (40/50) should have triggered long-transaction rollback; a side debate confirmed those values are percentages of logs used, not of the last log. John Bejarano could only speculate about disk or buffer problems. No resolution is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi all, IDS - 7.31UC2-X6 OS - Solaris 2.7 (x86 platform) Recently my database engine was halted and the online.log shown as below. Has anyone come accross of this warning message? If yes, how does it happen and what is the resolution? 05:58:43 Logical Log 17386 Complete. 05:58:44 Logical Log 17386 - Backup Started 05:58:46 Logical Log 17386 - Backup Completed 05:59:58 Checkpoint Completed: duration was 4 seconds. 05:59:59 Waiting for Next Logical Log File to be Freed Thanks & regards, Miyaki __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
btw, the logical log
backup (ontape -c) is running all
the time and all the logs are being backup
successfully during the incident.
--- miyaki <lcib@yahoo.com> wrote:
> Hi all,
>
> IDS - 7.31UC2-X6
> OS - Solaris 2.7 (x86 platform)
>
> Recently my database engine was halted and the
> online.log shown as below. Has anyone come accross
> of
> this warning message? If yes, how does it happen and
> what is the resolution?
>
> 05:58:43 Logical Log 17386 Complete.
> 05:58:44 Logical Log 17386 - Backup Started
> 05:58:46 Logical Log 17386 - Backup Completed
> 05:59:58 Checkpoint Completed: duration was 4
> seconds.
> 05:59:59 Waiting for Next Logical Log File to be
> Freed
>
> Thanks & regards,
> Miyaki
>
>
>
> __________________________________
> Do you Yahoo!?
> Protect your identity with Yahoo! Mail AddressGuard
> http://antispam.yahoo.com/whatsnewfree
>
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
Hi,
"onstat -l" output would give a better picture of the situation.
Also, try to find out, which logical log unique ID this "next
log file" has (also from "onstat -l" output) and why it was not
yet backed up (search IDS message log for errors/warnings).
Possibly, the log file in question was backed up ("onstat -l"
output shows "B"-flag), but there's an open transaction in it
(i.e. a transaction that's still open has log records in this log
file). This is also a reason why a log file cannot be re-used
(over-written), because in case of rollback of the open
transaction, the log records from this file would be needed
for the rollback processing.
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich
Data Management Solutions
"miyaki " <lcib@yahoo.com>
Sent by: forum.subscriber@iiug.org
11.11.2003 03:58
To: ids@iiug.org
cc:
Subject: Re: Waiting for next logical log file to be freed [2155]
btw, the logical log backup (ontape -c) is running all
the time and all the logs are being backup
successfully during the incident.
--- miyaki <lcib@yahoo.com> wrote:
> Hi all,
>
> IDS - 7.31UC2-X6
> OS - Solaris 2.7 (x86 platform)
>
> Recently my database engine was halted and the
> online.log shown as below. Has anyone come accross
> of
> this warning message? If yes, how does it happen and
> what is the resolution?
>
> 05:58:43 Logical Log 17386 Complete.
> 05:58:44 Logical Log 17386 - Backup Started
> 05:58:46 Logical Log 17386 - Backup Completed
> 05:59:58 Checkpoint Completed: duration was 4
> seconds.
> 05:59:59 Waiting for Next Logical Log File to be
> Freed
>
> Thanks & regards,
> Miyaki
>
>
>
> __________________________________
> Do you Yahoo!?
> Protect your identity with Yahoo! Mail AddressGuard
> http://antispam.yahoo.com/whatsnewfree
>
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
Hi,
The engine has total 200 logical logs and the LONGTX
threshold was configured as below.
LTXHWM 40
LTXEHWM 50
While the engine halted, all the logical logs are
already backup (with "B" flag) by the ontape -c
process, except only one log with "C" and "L" flag. If
the backup is not running, I will get a message saying
"Logical Logs are full - Backup is needed" instead of
this "Waiting for next logical log..."
Regarding the 2nd possibility, if a transaction is
trying to fill up a log that having an open
transaction, which means that there's a open
transaction has not been committed while other
transaction has fill-up all the logical logs until
other transaction trying to reused back the log. In
this case, why that particular open transaction in the
log is not hitting the LONGTX? With my current LONGTX
threshold, any open transaction that do not commit
within 40% of total logs (80 logs), then the said
transaction will be classified as LONGTX and will
start to roll back.
Appreciate that someone can enlighten me on this
issue...
Thanks & regards,
Miyaki
--- Martin Fuerderer <MARTINFU@de.ibm.com> wrote:
> Hi,
>
> "onstat -l" output would give a better picture of
> the situation.
> Also, try to find out, which logical log unique ID
> this "next
> log file" has (also from "onstat -l" output) and why
> it was not
> yet backed up (search IDS message log for
> errors/warnings).
>
> Possibly, the log file in question was backed up
> ("onstat -l"
> output shows "B"-flag), but there's an open
> transaction in it
> (i.e. a transaction that's still open has log
> records in this log
> file). This is also a reason why a log file cannot
> be re-used
> (over-written), because in case of rollback of the
> open
> transaction, the log records from this file would be
> needed
> for the rollback processing.
>
> Regards,
> Martin
> --
> Martin Fuerderer
> IBM Informix Development Munich
> Data Management Solutions
>
>
>
>
>
> "miyaki " <lcib@yahoo.com>
> Sent by: forum.subscriber@iiug.org
> 11.11.2003 03:58
>
>
> To: ids@iiug.org
> cc:
> Subject: Re: Waiting for next logical
> log file to be freed [2155]
>
>
>
> btw, the logical log backup (ontape -c) is running
> all
> the time and all the logs are being backup
> successfully during the incident.
>
> --- miyaki <lcib@yahoo.com> wrote:
> > Hi all,
> >
> > IDS - 7.31UC2-X6
> > OS - Solaris 2.7 (x86 platform)
> >
> > Recently my database engine was halted and the
> > online.log shown as below. Has anyone come accross
> > of
> > this warning message? If yes, how does it happen
> and
> > what is the resolution?
> >
> > 05:58:43 Logical Log 17386 Complete.
> > 05:58:44 Logical Log 17386 - Backup Started
> > 05:58:46 Logical Log 17386 - Backup Completed
> > 05:59:58 Checkpoint Completed: duration was 4
> > seconds.
> > 05:59:59 Waiting for Next Logical Log File to be
> > Freed
> >
> > Thanks & regards,
> > Miyaki
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Protect your identity with Yahoo! Mail
> AddressGuard
> > http://antispam.yahoo.com/whatsnewfree
> >
>
>
> __________________________________
> Do you Yahoo!?
> Protect your identity with Yahoo! Mail AddressGuard
> http://antispam.yahoo.com/whatsnewfree
>
>
>
>
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
Actually, if I remember correctly (and that is very doubtful!) it's actually
40% and 50% of your last log, which is why the logs have to be big enough,
as well.
--
Bye now,
Obnoxio
"C'est pas parce qu'on n'a rien à dire qu'il faut fermer sa gueule"
- Coluche
"Necrophilia means never having to say ... well, anything!"
- Captain Pedantic
"Ogni uomo mi guarda come se fossi una testa di cazzo"
- Marco
>From: "miyaki " <lcib@yahoo.com>
>To: ids@iiug.org
>Subject: Re: Waiting for next logical log file to be freed [2165] Date:
>Tue, 11 Nov 2003 21:21:30 -0500 (EST)
>
>Hi,
>
>The engine has total 200 logical logs and the LONGTX
>threshold was configured as below.
>LTXHWM 40
>LTXEHWM 50>
>While the engine halted, all the logical logs are
>already backup (with "B" flag) by the ontape -c
>process, except only one log with "C" and "L" flag. If
>the backup is not running, I will get a message saying
>"Logical Logs are full - Backup is needed" instead of
>this "Waiting for next logical log..."
>
>Regarding the 2nd possibility, if a transaction is
>trying to fill up a log that having an open
>transaction, which means that there's a open
>transaction has not been committed while other
>transaction has fill-up all the logical logs until
>other transaction trying to reused back the log. In
>this case, why that particular open transaction in the
>log is not hitting the LONGTX? With my current LONGTX
>threshold, any open transaction that do not commit
>within 40% of total logs (80 logs), then the said
>transaction will be classified as LONGTX and will
>start to roll back.
>
>Appreciate that someone can enlighten me on this
>issue...
>
>Thanks & regards,
>Miyaki
>
>--- Martin Fuerderer <MARTINFU@de.ibm.com> wrote:
> > Hi,
> >
> > "onstat -l" output would give a better picture of
> > the situation.
> > Also, try to find out, which logical log unique ID
> > this "next
> > log file" has (also from "onstat -l" output) and why
> > it was not
> > yet backed up (search IDS message log for
> > errors/warnings).
> >
> > Possibly, the log file in question was backed up
> > ("onstat -l"
> > output shows "B"-flag), but there's an open
> > transaction in it
> > (i.e. a transaction that's still open has log
> > records in this log
> > file). This is also a reason why a log file cannot
> > be re-used
> > (over-written), because in case of rollback of the
> > open
> > transaction, the log records from this file would be
> > needed
> > for the rollback processing.
> >
> > Regards,
> > Martin
> > --
> > Martin Fuerderer
> > IBM Informix Development Munich
> > Data Management Solutions
> >
> >
> >
> >
> >
> > "miyaki " <lcib@yahoo.com>
> > Sent by: forum.subscriber@iiug.org
> > 11.11.2003 03:58
> >
> >
> > To: ids@iiug.org
> > cc:
> > Subject: Re: Waiting for next logical
> > log file to be freed [2155]
> >
> >
> >
> > btw, the logical log backup (ontape -c) is running
> > all
> > the time and all the logs are being backup
> > successfully during the incident.
> >
> > --- miyaki <lcib@yahoo.com> wrote:
> > > Hi all,
> > >
> > > IDS - 7.31UC2-X6
> > > OS - Solaris 2.7 (x86 platform)
> > >
> > > Recently my database engine was halted and the
> > > online.log shown as below. Has anyone come accross
> > > of
> > > this warning message? If yes, how does it happen
> > and
> > > what is the resolution?
> > >
> > > 05:58:43 Logical Log 17386 Complete.
> > > 05:58:44 Logical Log 17386 - Backup Started
> > > 05:58:46 Logical Log 17386 - Backup Completed
> > > 05:59:58 Checkpoint Completed: duration was 4
> > > seconds.
> > > 05:59:59 Waiting for Next Logical Log File to be
> > > Freed
> > >
> > > Thanks & regards,
> > > Miyaki
> > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Protect your identity with Yahoo! Mail
> > AddressGuard
> > > http://antispam.yahoo.com/whatsnewfree
> > >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Protect your identity with Yahoo! Mail AddressGuard
> > http://antispam.yahoo.com/whatsnewfree
> >
> >
> >
> >
>
>
>__________________________________
>Do you Yahoo!?
>Protect your identity with Yahoo! Mail AddressGuard
>http://antispam.yahoo.com/whatsnewfree
>
_________________________________________________________________
Express yourself with cool emoticons - download MSN Messenger today!
http://www.msn.co.uk/messenger
Nope. Those
percentages refer to the number of logs
used, not the amount of the last log used. I'm
positive. I've seen it before while watching LONGTX's
rollback.
As for the original poster, sorry, I've never seen
that with logs actually being backed up, and safe and
sane settings for the LTX parameters. <grasping at
straws> Could there be an issue with the disks where
the logical logs are stored? Could some buffer
somewhere be blocked? </grasping>
--John Bejarano
DBA, Shutterfly, Inc.
--- "Obnoxio The...." <obnoxio@hotmail.com> wrote:
> Actually, if I remember correctly (and that is very
> doubtful!) it's actually
> 40% and 50% of your last log, which is why the logs
> have to be big enough,
> as well.
>
> --
> Bye now,
> Obnoxio
>
> "C'est pas parce qu'on n'a rien à dire qu'il faut
> fermer sa gueule"
> - Coluche
>
> "Necrophilia means never having to say ... well,
> anything!"
> - Captain Pedantic
>
> "Ogni uomo mi guarda come se fossi una testa di
> cazzo"
> - Marco
>
>
>
>
> >From: "miyaki " <lcib@yahoo.com>
> >To: ids@iiug.org
> >Subject: Re: Waiting for next logical log file to
> be freed [2165] Date:
> >Tue, 11 Nov 2003 21:21:30 -0500 (EST)
> >
> >Hi,
> >
> >The engine has total 200 logical logs and the
> LONGTX
> >threshold was configured as below.
> >LTXHWM 40
> >LTXEHWM 50> >
> >While the engine halted, all the logical logs are
> >already backup (with "B" flag) by the ontape -c
> >process, except only one log with "C" and "L" flag.
> If
> >the backup is not running, I will get a message
> saying
> >"Logical Logs are full - Backup is needed" instead
> of
> >this "Waiting for next logical log..."
> >
> >Regarding the 2nd possibility, if a transaction is
> >trying to fill up a log that having an open
> >transaction, which means that there's a open
> >transaction has not been committed while other
> >transaction has fill-up all the logical logs until
> >other transaction trying to reused back the log. In
> >this case, why that particular open transaction in
> the
> >log is not hitting the LONGTX? With my current
> LONGTX
> >threshold, any open transaction that do not commit
> >within 40% of total logs (80 logs), then the said
> >transaction will be classified as LONGTX and will
> >start to roll back.
> >
> >Appreciate that someone can enlighten me on this
> >issue...
> >
> >Thanks & regards,
> >Miyaki
> >
> >--- Martin Fuerderer <MARTINFU@de.ibm.com> wrote:
> > > Hi,
> > >
> > > "onstat -l" output would give a better picture
> of
> > > the situation.
> > > Also, try to find out, which logical log unique
> ID
> > > this "next
> > > log file" has (also from "onstat -l" output) and
> why
> > > it was not
> > > yet backed up (search IDS message log for
> > > errors/warnings).
> > >
> > > Possibly, the log file in question was backed up
> > > ("onstat -l"
> > > output shows "B"-flag), but there's an open
> > > transaction in it
> > > (i.e. a transaction that's still open has log
> > > records in this log
> > > file). This is also a reason why a log file
> cannot
> > > be re-used
> > > (over-written), because in case of rollback of
> the
> > > open
> > > transaction, the log records from this file
> would be
> > > needed
> > > for the rollback processing.
> > >
> > > Regards,
> > > Martin
> > > --
> > > Martin Fuerderer
> > > IBM Informix Development Munich
> > > Data Management Solutions
> > >
> > >
> > >
> > >
> > >
> > > "miyaki " <lcib@yahoo.com>
> > > Sent by: forum.subscriber@iiug.org
> > > 11.11.2003 03:58
> > >
> > >
> > > To: ids@iiug.org
> > > cc:
> > > Subject: Re: Waiting for next
> logical
> > > log file to be freed [2155]
> > >
> > >
> > >
> > > btw, the logical log backup (ontape -c) is
> running
> > > all
> > > the time and all the logs are being backup
> > > successfully during the incident.
> > >
> > > --- miyaki <lcib@yahoo.com> wrote:
> > > > Hi all,
> > > >
> > > > IDS - 7.31UC2-X6
> > > > OS - Solaris 2.7 (x86 platform)
> > > >
> > > > Recently my database engine was halted and the
> > > > online.log shown as below. Has anyone come
> accross
> > > > of
> > > > this warning message? If yes, how does it
> happen
> > > and
> > > > what is the resolution?
> > > >
> > > > 05:58:43 Logical Log 17386 Complete.
> > > > 05:58:44 Logical Log 17386 - Backup Started
> > > > 05:58:46 Logical Log 17386 - Backup Completed
> > > > 05:59:58 Checkpoint Completed: duration was
> 4
> > > > seconds.
> > > > 05:59:59 Waiting for Next Logical Log File to
> be
> > > > Freed
> > > >
> > > > Thanks & regards,
> > > > Miyaki
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Protect your identity with Yahoo! Mail
> > > AddressGuard
> > > > http://antispam.yahoo.com/whatsnewfree
> > > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > Protect your identity with Yahoo! Mail
> AddressGuard
> > > http://antispam.yahoo.com/whatsnewfree
> > >
> > >
> > >
> > >
> >
> >
> >__________________________________
> >Do you Yahoo!?
> >Protect your identity with Yahoo! Mail AddressGuard
> >http://antispam.yahoo.com/whatsnewfree
> >
>
>
_________________________________________________________________
> Express yourself with cool emoticons - download MSN
> Messenger today!
> http://www.msn.co.uk/messenger
>
>