logical log problem
Posted in 2010
Topics: Logging & Checkpoints
Dear all, Currently face one problem, one of the instance logical log keep full even i try to backup everyday. But based on my understanding this instance suppose not much activities. Anywhere i can check what caused the logical log keep getting full? Thanks in advance.
Hi,
Please post the platform and version of your issue. It is very difficult
to diagnose something with out this detail.
The logical logs are not designed to hold a whole days activity with no
backup. Each log must be backed up individually, so maybe you need to
make the individual logs bigger?
That being said, try "onstat -l " to list the logical logs, then run
"onlog -n xxx" where xxx is the uniqid of the current log
This will show you the transactions running through the logs, who the
user was, what the session id was (691033 below for example) and what
was happening.
In my example there are a number of insert statements and index
additions happening.
E.g.
onstat -l
=========address number flags uniqid begin size used
%used
504abfb8 11 U-B---- 32381 6:53 1500 1500
100.00
506d5fb8 12 U-B---- 32382 6:1553 1500 1500
100.00
508fffb8 13 U-B---- 32383 6:3053 1500 1500
100.00
50b31ab8 14 U---C-L 32384 6:4553 1500 1098
73.20
50b31b00 15 U-B---- 32375 6:6053 1500 1500
100.00
50b31b48 16 U-B---- 32376 6:7553 1500 1500
100.00
onlog -n 32384
==============
IBM Informix Dynamic Server Logical Log display
Software Serial Number AAA#B000000
Copyright IBM Corporation 1996, 2004 All rights reserved.
log uniqid: 32384.
addr len type xid id link
18 52 BEGIN 142 32384 0 01/22/2010 16:37:24
691033 sdev
4c 396 HINSERT 142 0 18 5000a0 31f00c03 332
1d8 72 ADDITEM 142 0 4c 5000a1 31f00c03 344363 1
12
220 72 ADDITEM 142 0 1d8 5000a2 31f00c03 402690 1
12
268 48 COMMIT 142 0 220 01/22/2010 16:37:24
1018 52 BEGIN 165 32384 0 01/22/2010 16:37:24
691036 sdev
104c 396 HINSERT 165 0 1018 5000a0 31f00c04 332
11d8 72 ADDITEM 165 0 104c 5000a1 31f00c04 344363 1
12
1220 72 ADDITEM 165 0 11d8 5000a2 31f00c04 402695 1
12
1268 48 COMMIT 165 0 1220 01/22/2010 16:37:24
2018 52 BEGIN 137 32384 0 01/22/2010 16:37:24
691034 sdev
204c 396 HINSERT 137 0 2018 5000a0 31f00c05 332
21d8 72 ADDITEM 137 0 204c 5000a1 31f00c05 344363 1
12
2220 72 ADDITEM 137 0 21d8 5000a2 31f00c05 402694 1
12
2268 48 COMMIT 137 0 2220 01/22/2010 16:37:24
3018 52 BEGIN 143 32384 0 01/22/2010 16:37:24
691035 sdev
304c 396 HINSERT 143 0 3018 5000a0 31f00c06 332
31d8 72 ADDITEM 143 0 304c 5000a1 31f00c06 344363 1
12
addr len type xid id link
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
YAN CHING TAN
Sent: Friday, 22 January 2010 4:43 p.m.
To: ids@iiug.org
Subject: logical log problem [18738]
Dear all,
Currently face one problem, one of the instance logical log keep full
even i try to backup everyday. But based on my understanding this
instance suppose not much activities.
Anywhere i can check what caused the logical log keep getting full?
Thanks in advance.
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
DISCLAIMER:
This email contains confidential information and may be legally privileged. If
you are not the intended recipient or have received this email in error,
please notify the sender immediately and destroy this email.
You may not use, disclose or copy this email or its attachments in any way.
Any opinions expressed in this email are those of the author and are not
necessarily those of the Fonterra Co-operative Group.
http://www.fonterra.com/
Hi,
backup of logical logs once a day is not very often. I think most of us backup
immediately ONE log becomes full (or at least in short intervals).
Please post the logical log configuration/usage ( the output of onstat -l)
And the online.log (message log) of one day (log switches give an entry there).
Regards,
Andreas
>
-------------------------------------------
SPAR Österreichische Warenhandels-AG
Hauptzentrale
A - 5015 Salzburg, Europastrasse 3
FN 34170 a
Tel: +43 662 4470 84923
Mobile: +43 664 6259575
E-Mail: Andreas.KUTSCHE@spar.at
Internet: http://www.spar.at
Wichtiger Hinweis: Der Inhalt dieser E-Mail kann vertrauliche und rechtlich
geschützte Informationen, insbesondere Betriebs- oder Geschäftsgeheimnisse,
enthalten, zu deren Geheimhaltung der Empfänger verpflichtet ist. Die
Informationen in dieser E-Mail sind ausschließlich für den Adressaten
bestimmt. Sollten Sie die E-Mail irrtümlich erhalten haben so ersuchen wir
Sie, die Nachricht von Ihrem System zu löschen und sich mit uns in Verbindung
zu setzen.
Über das Internet versandte E-Mails können leicht manipuliert oder unter
fremdem Namen erstellt werden. Daher schließen wir die rechtliche
Verbindlichkeit der in dieser Nachricht enthaltenen Informationen aus. Der
Inhalt der E-Mail ist nur rechtsverbindlich, wenn er von uns schriftlich
bestätigt und gezeichnet wird.
Sollte trotz der von uns verwendeten Virus-Schutzprogramme durch die Zusendung
von E-Mails ein Virus in Ihre Systeme gelangen, haften wir nicht für evtl.
hieraus entstehende Schäden.
Wir danken für Ihr Verständnis.
Important notice: The contents of this e-mail may contain confidential and
legally protected information that is in particular related to operational and
trade secrets, which the recipient is obliged to treat as confidential. The
information in this e-mail is made available exclusively for use by the
addressee. In the event that the e-mail may have been sent to you in error, we
would ask you to kindly delete this communication from your system and to
contact us.
E-mails sent via the Internet can be easily manipulated or sent out under
someone else's name. We therefore do not accept legal liability for the
information contained in this communication. The contents of the e-mail are
only legally binding if they have been confirmed and signed by us in writing.
If, in spite of our using Antivirus protection software, a virus may have
penetrated your system through the sending of this e-mail, we do not accept
liability for any damage that may possibly arise as a result of this.
We trust that you appreciate our position.
-------------------------------------------
-----Ursprüngliche Nachricht-----
> Von: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] Im Auftrag von YAN
> CHING TAN
> Gesendet: Freitag, 22. Januar 2010 04:43
> An: ids@iiug.org
> Betreff: logical log problem [18738]
>
> Dear all,
>
> Currently face one problem, one of the instance logical log keep full even
> i
> try to backup everyday. But based on my understanding this instance
> suppose
> not much activities.
>
> Anywhere i can check what caused the logical log keep getting full?
>
> Thanks in advance.
>
>
> **************************************************************************
> *****
> Forum Note: Use "Reply" to post a response in the discussion forum.
You can use the onlog utility to see what activity is in the logs. The
partnums of affected tables are in the onlog output and you can map that to
a table or index partition in the sysmaster:systabnames table. See the post
yesterday about rootdbs filling up, you may be experiencing a similar
problem. A workaround for that was posted in the thread.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
See you at the 2010 IIUG Informix Conference
April 25-28, 2010
Overland Park (Kansas City), KS
www.iiug.org/conf
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Thu, Jan 21, 2010 at 10:42 PM, YAN CHING TAN <yc_tan@hotmail.com> wrote:
> Dear all,
>
> Currently face one problem, one of the instance logical log keep full even
> i
> try to backup everyday. But based on my understanding this instance suppose
> not much activities.
>
> Anywhere i can check what caused the logical log keep getting full?
>
> Thanks in advance.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--00151747373ab1b546047dc06933
hi YC, You can migrate to separate dbspace from rootdbs.If you feel rootdbs full. rgds schillache