IDS not writing to online.log
Answered: red (solid confidence) — Thread trails off mid-diagnosis of a stalled checkpoint/hung onmode after an apparent crash-recovery long-transaction rollback; no confirmation the server ever fully recovered.
Advisory only.
Posted in 2017
A 12.10.FC7 server stopped writing to online.log; nearly all 106 logical logs were full, the last checkpoint was far behind, and onmode -l/-c hung. Suggestions included looking for a long/open transaction (onstat -x, -u for 'R'), checking LTXHWM/LTXEHWM (70/80) and DYNAMIC_LOGS, and adding many more logical logs so a huge rollback could finish. onstat -g stk revealed an sqlexec thread parked in hang_thread/afhandler (an assertion caught by the hang-thread feature), so Andreas advised a restart with fast recovery, keeping backups, ONDBSPACEDOWN 2 and opening a PMR. A log-truncation script was dismissed as a red herring. No confirmed resolution is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Andreas Legner warns that in a checkpoint-blocked-for-down-space situation during fast recovery you must use 'onmode -yk' and specifically avoid 'onmode -yuk'; the asker also tried force-killing a session with 'onmode -z' while the engine was mid-rollback from an unstable crash/restart. Both are risky if misapplied during an in-flight long-transaction rollback.
onmode -yuk onmode -z
Advisory only — not a substitute for testing in a non-production environment first.
Topics: Server Administration
Hi again,
Wanted to ask for some opinions. Had an issue with the log file being empty.
Noticed something not right wiht my logical files:
49945778 52 U-B---- 278553 54:4200003 150000 150000 100.00
499457e0 53 U---C-- 278554 54:4350003 150000 104298 69.53
49945848 54 U-B---- 278455 54:4500003 150000 150000 100.00
.....
498de028 73 U-B---- 278474 54:7350003 150000 150000 100.00
498de090 74 U-B---- 278475 54:7500003 150000 150000 100.00
498de0f8 75 U-B---L 278476 54:7650003 150000 150000 100.00
498de160 76 U-B---- 278477 54:7800003 150000 150000 100.00
tried onmode -l and onmode -c but they are hanging and doing nothing...
Look for an open transaction that spans all the logs in onstat -x
Dan
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of STEVEN AB
Sent: Thursday, January 05, 2017 7:45 AM
To: ids@iiug.org
Subject: IDS not writing to online.log [38439]
Hi again,
Wanted to ask for some opinions. Had an issue with the log file being empty.
Noticed something not right wiht my logical files:
49945778 52 U-B---- 278553 54:4200003 150000 150000 100.00
499457e0 53 U---C-- 278554 54:4350003 150000 104298 69.53
49945848 54 U-B---- 278455 54:4500003 150000 150000 100.00 ......
498de028 73 U-B---- 278474 54:7350003 150000 150000 100.00
498de090 74 U-B---- 278475 54:7500003 150000 150000 100.00
498de0f8 75 U-B---L 278476 54:7650003 150000 150000 100.00
498de160 76 U-B---- 278477 54:7800003 150000 150000 100.00
tried onmode -l and onmode -c but they are hanging and doing nothing...
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Logs 75 through 52 are full. Log 53 is currently in use. Sounds like
you may be running into a long transaction. Check the two
LTXHWM/LTXEHWM settings in $ONCONFIG. I've seen some ridiculously low
settings like 50/60. You can see if you are in the middle of a rollback
with onstat -u, look for a session with an 'R' flag. There is also a
setting to tell the engine to automatically add a log (and how many)
when it runs out of logs - DYNAMIC_LOGS.
Are you trying something like "load from file insert into table" with a
billion row file? That is guaranteed to cause a long transaction.
As for logfile, grep MSG out of $ONCONFIG, that would be where messages
are being written.
j.
On 1/5/17 7:45 AM, STEVEN AB wrote:
> Hi again,
>
> Wanted to ask for some opinions. Had an issue with the log file being empty.
>
> Noticed something not right wiht my logical files:
>
> 49945778 52 U-B---- 278553 54:4200003 150000 150000 100.00
> 499457e0 53 U---C-- 278554 54:4350003 150000 104298 69.53
> 49945848 54 U-B---- 278455 54:4500003 150000 150000 100.00
> ......
> 498de028 73 U-B---- 278474 54:7350003 150000 150000 100.00
> 498de090 74 U-B---- 278475 54:7500003 150000 150000 100.00
> 498de0f8 75 U-B---L 278476 54:7650003 150000 150000 100.00
> 498de160 76 U-B---- 278477 54:7800003 150000 150000 100.00
>
> tried onmode -l and onmode -c but they are hanging and doing nothing...
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
By online.log you mean logical logs, right?
So what exactly do you think is not right here? Where's there anything=20
empty?
Looks like last checkpoint happened a good while ago ('L' flag). And if=20
onmode commands hang, this would mean something's blocked within the=20
server?
Find main=5Floop in onstat -g ath and look at its state and stack (onstat -=
g=20
stk <tid>). Same for onmode=5Fmon thread.
Andreas
From: "STEVEN AB" <alexsuru1457@gmail.com>
To: ids@iiug.org
Date: 05.01.2017 13:45
Subject: IDS not writing to online.log [38439]
Sent by: ids-bounces@iiug.org
Hi again,=20
Wanted to ask for some opinions. Had an issue with the log file being=20
empty.=20
Noticed something not right wiht my logical files:=20
49945778 52 U-B---- 278553 54:4200003 150000 150000 100.00=20
499457e0 53 U---C-- 278554 54:4350003 150000 104298 69.53=20
49945848 54 U-B---- 278455 54:4500003 150000 150000 100.00=20
......=20
498de028 73 U-B---- 278474 54:7350003 150000 150000 100.00=20
498de090 74 U-B---- 278475 54:7500003 150000 150000 100.00=20
498de0f8 75 U-B---L 278476 54:7650003 150000 150000 100.00=20
498de160 76 U-B---- 278477 54:7800003 150000 150000 100.00=20
tried onmode -l and onmode -c but they are hanging and doing nothing...=20
***************************************************************************=
****=20
Forum Note: Use "Reply" to post a response in the discussion forum.=20
Hi Jack, yes, it could be, but no long transaction would take weeks :
yes, I can't see logical logs and checkpoints in online.log.
What should I look for in onstat -g ath and stk ?
What should I lood I look for ? ......... 48755f58 A---- 48720ce0 3 - - DIRTY - 0 487562c8 A---- 4870bf30 3 - - DIRTY - 0 48756638 A---- 4871ac48 3 - - DIRTY - 0 487569a8 A---- 48722738 3 - - DIRTY - 0 48756d18 A---- 4872f9f8 2 - - DIRTY - 0 48757088 A---- 48721e70 3 - - DIRTY - 0 487573f8 A---- 48718928 0 - - COMMIT - 0 48757768 A---- 487215a8 3 - - DIRTY - 0 48757ad8 A---- 48710e38 0 - - COMMIT - 0 48757e48 A---- 4871bdd8 0 - - COMMIT - 0 487581b8 A---- 48711fc8 3 - - DIRTY - 0 48758528 A---- 4871cf68 0 - - NOTRANS - 0 48758898 A---- 4873a998 2 - - DIRTY - 0 48758c08 A---- 48725320 3 - - DIRTY - 0 48758f78 A---- 4871e0f8 3 - - DIRTY - 0 487592e8 A---- 48723000 3 - - DIRTY - 0 48759658 A---- 4871e9c0 0 - - COMMIT - 0 487599c8 A---- 4870d988 3 - - DIRTY - 0 48759d38 A---- 48713158 0 - - COMMIT - 0 4875a0a8 A---- 48727f08 0 - - COMMIT - 0 4875a418 A---- 48716608 3 - - DIRTY - 0 4875a788 A---- 487264b0 1 - - DIRTY - 0 4875aaf8 A---- 48726d78 1 - - DIRTY - 0 4875ae68 A---- 48727640 2 - - DIRTY - 0 4875b1d8 A---- 487264b0 0 - - NOTRANS - 0 4875b548 A---- 48726d78 0 - - NOTRANS - 0 4875b8b8 A---- 48712890 3 - - DIRTY - 0 4875bc28 A---- 487287d0 0 - - DIRTY - 0 4875bf98 A---- 48729098 3 - - DIRTY - 0 4875c308 A---- 48729960 3 - - DIRTY - 0 4875c678 A---- 4872a228 3 - - DIRTY - 0 4875c9e8 A---- 4872aaf0 3 - - DIRTY - 0 4875cd58 A---- 4872b3b8 3 - - DIRTY - 0 4875d0c8 A---- 4872bc80 3 - - DIRTY - 0 4875d438 A---- 4872c548 3 - - DIRTY - 0 4875d7a8 A---- 4872ce10 3 - - DIRTY - 0 4875db18 A---- 4872f130 3 - - DIRTY - 0 4875de88 A---- 4872dfa0 2 - - DIRTY - 0 4875e1f8 A---- 4872e868 3 - - DIRTY - ...............
7237 4a10d028 4870d0c0 1 cond wait defunct 1cpu* sqlexec
Stack for thread: 7237 sqlexecbase: 0x0000000049cee000
len: 69632
pc: 0x00000000013e79ef
tos: 0x0000000047f94f40
state: cond wait
vp: 1
0x00000000013e79ef (oninit) yield_processor_mvp
0x0000000001400b51 (oninit) mt_wait
0x00000000013d0421 (oninit) hang_thread
0x00000000013d148c (oninit) afhandler
0x00000000013d2ce2 (oninit) afcrash_interface
0x00000000013dd011 (oninit) vp_child_handler
0x000000361a80f7e0 (/lib64/libpthread-2.12.so) (null)
for tid in $(onstat -g ath | egrep "main=5Floop|onmode=5Fmon" | awk '{print=
=20
$1}'); do
onstat -g stk $tiddone
Just in case 'crit' should be in any of these outputs, e.g. wait4critex,=20
check onstat -u for any X flags and proceed from there.
'Weeks' you're saying?? No checkpoint in weeks ?? And no other issues?=20
Server running and serving fine?
I'd say time for a PMR, if this is a recent version.
onstat -a, onstat -g ses 0 and onstat -g stk all to get an overview.
onstat -g out | gzip > shmem.gz to secure a shared memory dump which=20might serve for deeper analysis.
... might be related ... could be holding some resources that now are=20
blocking other activity like checkpoints ...
The idea of the hang-thread feature is, where possible, to avoid an=20
immediate engine abort in case of an otherwise crashing assertion, and=20
allow for a restart at a more convenient time - but the restart should=20
be performed.
Now this restart and fast recovery had to go through quite a few logical=20
logs .... fingers crossed!
In case any errors should occur during fast recovery:
- be sure to have ONDBSPACEDOWN 2
- don't override a checkpoint block at end of fast rec in case of any=20
chunk/space going down
- don't use 'onmode -yuk' either, but only 'onmode -yk' in such=20
checkpoint-blocked-for-down-space situation
- open a PMR early
Also be sure not to throw away any backups taken before that last=20
checkpoint (I reckon you weren't able to take any afterwards).
Andreas
From: "STEVEN AB" <alexsuru1457@gmail.com>
To: ids@iiug.org
Date: 05.01.2017 15:00
Subject: Re: IDS not writing to online.log [38446]
Sent by: ids-bounces@iiug.org
7237 4a10d028 4870d0c0 1 cond wait defunct 1cpu* sqlexec=20
Stack for thread: 7237 sqlexec=20base: 0x0000000049cee000=20
len: 69632=20
pc: 0x00000000013e79ef=20
tos: 0x0000000047f94f40=20
state: cond wait=20
vp: 1=20
0x00000000013e79ef (oninit) yield=5Fprocessor=5Fmvp=20
0x0000000001400b51 (oninit) mt=5Fwait=20
0x00000000013d0421 (oninit) hang=5Fthread=20
0x00000000013d148c (oninit) afhandler=20
0x00000000013d2ce2 (oninit) afcrash=5Finterface=20
0x00000000013dd011 (oninit) vp=5Fchild=5Fhandler=20
0x000000361a80f7e0 (/lib64/libpthread-2.12.so) (null)=20
***************************************************************************=
****=20
Forum Note: Use "Reply" to post a response in the discussion forum.=20
Your script lines weren't so readable but I got this:
-bash-4.1$ for tid in $(onstat -g ath | egrep "main loop|onmode mon" | awk
'{print $1}');do
> onstat -g stk $tid> done
with no output.
I did not say that there were not checkpoint, just I that it doesn't show in
online.log, onlog -l shows lots of transactions.
I got this weird line from onstat -g ses
21327 sysapi - -1 56.a7.7e 1 172032 108872 off
tried to onmode -z session but no success
btw, this is not prod environement
Also, onstat - always has the same output
That 'main loop' should be main=5Floop, and equally 'onmode mon' ->=20
onmode=5Fmon.
In that log. logs overview your last checkpoint was about 80 logs behind,=20
not sure how much time this would mean. Did you see a new checkpoint in=20
the meantime? Did the 'L' flag move, from log 278476 ?
-> onstat -g ckp (if on a recent version)
You'd also see no more online.log entries if the file system holding this=20
file is full. Beyond this we'd have to assume some sort of blockage.
That 'onstat -g ses' line isn't particularly weird:
session #RSAM total used =20
dynamic
id user tty pid hostname threads memory memory =20
explain
21327 sysapi - -1 56.a7.7e 1 172032 108872 =20
off=20
Looking like some JDBC session (pid -1) from host IP 56.a7.7e...=20
(truncated), for user sysapi.
Andreas
From: "STEVEN AB" <alexsuru1457@gmail.com>
To: ids@iiug.org
Date: 05.01.2017 16:09
Subject: Re: IDS not writing to online.log [38450]
Sent by: ids-bounces@iiug.org
Your script lines weren't so readable but I got this:=20
-bash-4.1$ for tid in $(onstat -g ath | egrep "main loop|onmode mon" | awk =
'{print $1}');do=20
> onstat -g stk $tid=20
> done=20
with no output.=20I did not say that there were not checkpoint, just I that it doesn't show=20
in=20
online.log, onlog -l shows lots of transactions.=20
I got this weird line from onstat -g ses=20
21327 sysapi - -1 56.a7.7e 1 172032 108872 off=20
***************************************************************************=
****=20
Forum Note: Use "Reply" to post a response in the discussion forum.=20
-bash-4.1$ for tid in $(onstat -g ath | egrep "main=5Floop|onmode=5Fmon" | awk
'{print $1}');
> do
> onstat -g stk $tid> done
-bash-4.1$
AUTO_CKPTS=On RTO_SERVER_RESTART=Off
Critical Sections Physical Log Logical Log
Clock Total Flush Block # Ckpt Wait Long # Dirty Dskflu Total Avg Total Avg
Interval Time Trigger LSN Time Time Time Waits Time Time Time Buffers /Sec
Pages /Sec Pages /Sec
166374 23:35:53 CKPTINTVL 278411:0x231b6018 0.7 0.6 0.0 7 0.0 0.0 0.0 10582
10582 3105 10 86574 288
166375 23:40:53 CKPTINTVL 278412:0x10139018 0.7 0.6 0.0 5 0.0 0.0 0.0 9014
9014 2929 9 72123 240
166376 23:45:53 CKPTINTVL 278412:0x1fde7388 0.7 0.7 0.0 14 0.0 0.0 0.0 8388
8388 3079 10 64749 215
166377 23:50:53 CKPTINTVL 278413:0xaccb17c 0.6 0.6 0.0 2 0.0 0.0 0.0 8129 8129
2827 9 63746 212
166378 23:55:53 CKPTINTVL 278413:0x1b27715c 0.8 0.8 0.0 6 0.0 0.0 0.0 8422
8422 2945 9 67066 223
166379 00:00:53 CKPTINTVL 278414:0x6e6015c 0.7 0.7 0.0 11 0.0 0.0 0.0 8649
8649 2956 9 67112 223
166380 00:05:53 CKPTINTVL 278414:0x165c81cc 0.7 0.7 0.0 8 0.0 0.0 0.0 8252
8252 2892 9 63406 211
166381 00:10:53 CKPTINTVL 278415:0xc1b15c 0.5 0.5 0.0 5 0.0 0.0 0.0 8048 8048
2836 9 61547 205
166382 00:15:53 CKPTINTVL 278415:0x10073018 0.7 0.6 0.0 1 0.0 0.0 0.0 8098
8098 2904 9 62602 208
166383 00:20:54 CKPTINTVL 278415:0x1f201018 0.6 0.5 0.0 1 0.0 0.0 0.0 8016
8016 2839 9 61892 205
166384 00:25:54 CKPTINTVL 278416:0xa191320 0.8 0.8 0.0 7 0.0 0.0 0.0 8801 8801
3524 11 63940 213
166385 00:30:54 CKPTINTVL 278416:0x194af018 1.0 1.0 0.0 2 0.0 0.0 0.0 7956
7956 2775 9 62320 207
166386 00:35:55 CKPTINTVL 278417:0x3abf500 1.8 1.7 0.0 13 0.0 0.0 0.0 7980
4577 2875 9 61551 205
166387 00:41:56 CKPTINTVL 278417:0xc1b3018 60.2 57.7 0.0 20 0.6 1.7 3.3 5878
101 2563 8 34634 113
166388 00:41:59 *Admin 278444:0xf46018 4.2 0.1 0.0 17 0.0 3.7 4.2 893 893 4997
81 4004323 65644
166389 00:41:59 *Admin 278445:0x1a02215c 0.2 0.1 0.0 16 0.0 0.1 0.2 114 114
2875 2875 252620 252620
166390 00:41:59 *Admin 278445:0x2301d264 0.1 0.0 0.0 8 0.0 0.1 0.1 55 55 1979
1979 36859 36859
166391 00:41:59 *Admin 278448:0xb6413b4 0.1 0.0 0.0 13 0.0 0.1 0.1 103 103
2972 2972 353268 353268
166392 00:41:59 *Admin 278476:0x8cff018 1.1 0.1 0.0 1 0.0 1.1 1.1 135 135 7820
7820 4189438 4189438
166393 00:41:59 *Admin 278476:0xa7de018 0.1 0.0 0.0 2 0.0 0.1 0.1 14 14 529
529 6879 6879
Max Plog Max Llog Max Dskflush Avg Dskflush Avg Dirty Blocked
pages/sec pages/sec Time pages/sec pages/sec Time
10240 1597 58 7117 15 0
You probably have add enough new logical logs to allow the rollback to
complete.
Art
On Jan 5, 2017 10:25, "STEVEN AB" <alexsuru1457@gmail.com> wrote:
> tried to onmode -z session but no success
>
> btw, this is not prod environement
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a114b71b813dc4805455af46c
Hi Art,
tried that already. When I add a logical log I will see the corresponding
entry in online.log and a checkpoint, and nothing happens after that. And I
can't switch the logical logs because onmode -l is not working
What happens to your logs when you are done with them? Are they backing
up? I have many times seen an engine freeze if waiting for logical logs
to back off.
j.
On 1/5/17 11:15 AM, STEVEN AB wrote:
> Hi Art,
> tried that already. When I add a logical log I will see the corresponding
> entry in online.log and a checkpoint, and nothing happens after that. And I
> can't switch the logical logs because onmode -l is not working
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
Hi Jack, it happened to me lots of times too, but not this time, this is different.
How many logs did you have to begin with and how many did you add? What are
LTXHWM & LTXEHWM set to?
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on 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 5, 2017 at 11:15 AM, STEVEN AB <alexsuru1457@gmail.com> wrote:
> Hi Art,
> tried that already. When I add a logical log I will see the corresponding
> entry in online.log and a checkpoint, and nothing happens after that. And I
> can't switch the logical logs because onmode -l is not working
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a11423f32263aac05455d3d46
Your last checkpoint still is the one in log 278476 ... not good, and not=20
looking like you're getting regular checkpoints.
Unfortunately these LotusNotes emails get mangled, so you still didn't get =
my command right: It should be
- main loop with an underscore instead of the blanc between main and=20
loop
- same for onmode mon
HTH
Andreas
From: "STEVEN AB" <alexsuru1457@gmail.com>
To: ids@iiug.org
Date: 05.01.2017 16:52
Subject: Re: IDS not writing to online.log [38454]
Sent by: ids-bounces@iiug.org
-bash-4.1$ for tid in $(onstat -g ath | egrep "main=3D5Floop|onmode=3D5Fmon=
" |=20
awk=20
'{print $1}');=20
> do=20
> onstat -g stk $tid=20
> done=20
-bash-4.1$=20
AUTO=5FCKPTS=3DOn RTO=5FSERVER=5FRESTART=3DOff=20
Critical Sections Physical Log Logical Log=20
Clock Total Flush Block # Ckpt Wait Long # Dirty Dskflu Total Avg Total=20
Avg=20
Interval Time Trigger LSN Time Time Time Waits Time Time Time Buffers /Sec =
Pages /Sec Pages /Sec=20
166374 23:35:53 CKPTINTVL 278411:0x231b6018 0.7 0.6 0.0 7 0.0 0.0 0.0=20
10582=20
10582 3105 10 86574 288=20
166375 23:40:53 CKPTINTVL 278412:0x10139018 0.7 0.6 0.0 5 0.0 0.0 0.0 9014 =
9014 2929 9 72123 240=20
166376 23:45:53 CKPTINTVL 278412:0x1fde7388 0.7 0.7 0.0 14 0.0 0.0 0.0=20
8388=20
8388 3079 10 64749 215=20
166377 23:50:53 CKPTINTVL 278413:0xaccb17c 0.6 0.6 0.0 2 0.0 0.0 0.0 8129=20
8129=20
2827 9 63746 212=20
166378 23:55:53 CKPTINTVL 278413:0x1b27715c 0.8 0.8 0.0 6 0.0 0.0 0.0 8422 =
8422 2945 9 67066 223=20
166379 00:00:53 CKPTINTVL 278414:0x6e6015c 0.7 0.7 0.0 11 0.0 0.0 0.0 8649 =
8649 2956 9 67112 223=20
166380 00:05:53 CKPTINTVL 278414:0x165c81cc 0.7 0.7 0.0 8 0.0 0.0 0.0 8252 =
8252 2892 9 63406 211=20
166381 00:10:53 CKPTINTVL 278415:0xc1b15c 0.5 0.5 0.0 5 0.0 0.0 0.0 8048=20
8048=20
2836 9 61547 205=20
166382 00:15:53 CKPTINTVL 278415:0x10073018 0.7 0.6 0.0 1 0.0 0.0 0.0 8098 =
8098 2904 9 62602 208=20
166383 00:20:54 CKPTINTVL 278415:0x1f201018 0.6 0.5 0.0 1 0.0 0.0 0.0 8016 =
8016 2839 9 61892 205=20
166384 00:25:54 CKPTINTVL 278416:0xa191320 0.8 0.8 0.0 7 0.0 0.0 0.0 8801=20
8801=20
3524 11 63940 213=20
166385 00:30:54 CKPTINTVL 278416:0x194af018 1.0 1.0 0.0 2 0.0 0.0 0.0 7956 =
7956 2775 9 62320 207=20
166386 00:35:55 CKPTINTVL 278417:0x3abf500 1.8 1.7 0.0 13 0.0 0.0 0.0 7980 =
4577 2875 9 61551 205=20
166387 00:41:56 CKPTINTVL 278417:0xc1b3018 60.2 57.7 0.0 20 0.6 1.7 3.3=20
5878=20
101 2563 8 34634 113=20
166388 00:41:59 *Admin 278444:0xf46018 4.2 0.1 0.0 17 0.0 3.7 4.2 893 893=20
4997=20
81 4004323 65644=20
166389 00:41:59 *Admin 278445:0x1a02215c 0.2 0.1 0.0 16 0.0 0.1 0.2 114=20
114=20
2875 2875 252620 252620=20
166390 00:41:59 *Admin 278445:0x2301d264 0.1 0.0 0.0 8 0.0 0.1 0.1 55 55=20
1979=20
1979 36859 36859=20
166391 00:41:59 *Admin 278448:0xb6413b4 0.1 0.0 0.0 13 0.0 0.1 0.1 103 103 =
2972 2972 353268 353268=20
166392 00:41:59 *Admin 278476:0x8cff018 1.1 0.1 0.0 1 0.0 1.1 1.1 135 135=20
7820=20
7820 4189438 4189438=20
166393 00:41:59 *Admin 278476:0xa7de018 0.1 0.0 0.0 2 0.0 0.1 0.1 14 14=20
529=20
529 6879 6879=20
Max Plog Max Llog Max Dskflush Avg Dskflush Avg Dirty Blocked=20
pages/sec pages/sec Time pages/sec pages/sec Time=20
10240 1597 58 7117 15 0=20
***************************************************************************=
****=20
Forum Note: Use "Reply" to post a response in the discussion forum.=20
IBM Informix Dynamic Server Version 12.10.FC7X9 -- On-Line -- Up 21:12:30 --10623252 Kbytes
Stack for thread: 7 main_loop()base: 0x00000000494fc000
len: 69632
pc: 0x00000000013e79ef
tos: 0x0000000049509380
state: sleeping
vp: 8
0x00000000013e79ef (oninit) yield_processor_mvp
0x00000000013eb1d7 (oninit) mt_yield
0x0000000000572bd0 (oninit) main_loop
0x00000000013c1790 (oninit) th_init_initgls
0x0000000001428327 (oninit) startup
IBM Informix Dynamic Server Version 12.10.FC7X9 -- On-Line -- Up 21:12:30 --10623252 Kbytes
Stack for thread: 7117 onmode_monbase: 0x0000000049871000
len: 69632
pc: 0x00000000013e79ef
tos: 0x0000000049880d00
state: sleeping
vp: 1
0x00000000013e79ef (oninit) yield_processor_mvp
0x00000000013eb1d7 (oninit) mt_yield
0x0000000000564353 (oninit) onmode_monitor
0x00000000013c1790 (oninit) th_init_initgls
0x0000000001428327 (oninit) startup
By the way, this happened after someone ran a log cleaning script that looks like this: /bin/cat /opt/informix/tmp/online.log | gzip -c9 > /opt/informix/tmp/online.log.`date +%d%m%y`.gz ; > /opt/informix/tmp/online.log
You're probably going to need at least another 50 logs to complete the
rollback.
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on 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 Fri, Jan 6, 2017 at 4:05 AM, STEVEN AB <alexsuru1457@gmail.com> wrote:
> Had 100 and added 4
>
> LTXHWM 70
> LTXEHWM 80>
> Thank you,
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a114e21263c393005456b041b
That is a red herring. You can clean the online.log anytime. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on 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 Fri, Jan 6, 2017 at 4:44 AM, STEVEN AB <alexsuru1457@gmail.com> wrote: > By the way, this happened after someone ran a log cleaning script that > looks > like this: > > /bin/cat /opt/informix/tmp/online.log | gzip -c9 > > /opt/informix/tmp/online.log.`date +%d%m%y`.gz ; > > /opt/informix/tmp/online.log > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --94eb2c12cad0dabd9605456b09f1
There are 106 Llogs , 300MB each, what kind of rollback could that be ?
The word huge comes to mind. The session that owned the transaction should still have been in memory to see what it was doing. Art On Jan 6, 2017 17:59, "STEVEN AB" <alexsuru1457@gmail.com> wrote: > There are 106 Llogs , 300MB each, what kind of rollback could that be ? > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --047d7bf0d004ef9ab3054589bb8c
At this point the server had been restarted less than a day ago (21 hours, =
12 mins).
Do you still not see new online.log entries or checkpoints?
From: "STEVEN AB" <alexsuru1457@gmail.com>
To: ids@iiug.org
Date: 06.01.2017 10:31
Subject: Re: IDS not writing to online.log [38463]
Sent by: ids-bounces@iiug.org
IBM Informix Dynamic Server Version 12.10.FC7X9 -- On-Line -- Up 21:12:30=20
--=2010623252 Kbytes=20
Stack for thread: 7 main=5Floop()=20base: 0x00000000494fc000=20
len: 69632=20
pc: 0x00000000013e79ef=20
tos: 0x0000000049509380=20
state: sleeping=20
vp: 8=20
0x00000000013e79ef (oninit) yield=5Fprocessor=5Fmvp=20
0x00000000013eb1d7 (oninit) mt=5Fyield=20
0x0000000000572bd0 (oninit) main=5Floop=20
0x00000000013c1790 (oninit) th=5Finit=5Finitgls=20
0x0000000001428327 (oninit) startup=20
IBM Informix Dynamic Server Version 12.10.FC7X9 -- On-Line -- Up 21:12:30=20
--=2010623252 Kbytes=20
Stack for thread: 7117 onmode=5Fmon=20base: 0x0000000049871000=20
len: 69632=20
pc: 0x00000000013e79ef=20
tos: 0x0000000049880d00=20
state: sleeping=20
vp: 1=20
0x00000000013e79ef (oninit) yield=5Fprocessor=5Fmvp=20
0x00000000013eb1d7 (oninit) mt=5Fyield=20
0x0000000000564353 (oninit) onmode=5Fmonitor=20
0x00000000013c1790 (oninit) th=5Finit=5Finitgls=20
0x0000000001428327 (oninit) startup=20
***************************************************************************=
****=20
Forum Note: Use "Reply" to post a response in the discussion forum.=20