Emergency help needed with IBM/Informix support

I have a down 7.31 engine and my var does not have after hours IBM support for Informix. Is there anyway to contact and create a 24x7 support contract on the weekend with IBM? The problem is the engine is stuck with a LONGTX. I had this once before and it won't finish on it's own. It took IBM almost 8 hours the last time to fix it. I cannot afford to wait until Monday to have them do their magic. Thanks Gary Quiring

"Gary Quiring" <gquiring@msn.com> wrote in message news:tkli00dqvrpp1cms30ab7k6fkknp1dagcd@4ax.com... > I have a down 7.31 engine and my var does not have after hours IBM > support for Informix. Is there anyway to contact and create a 24x7 > support contract on the weekend with IBM? > > The problem is the engine is stuck with a LONGTX. I had this once > before and it won't finish on it's own. It took IBM almost 8 hours > the last time to fix it. I cannot afford to wait until Monday to have > them do their magic. It shouldn't take them very long to fix it. I guess you could try to call the support line and offer a pay-per-call case. I've heard that they charge something like US$6,000 for this though, although this may be apocryphal. Where are you? IN EMEA most, but not all, Informix support has been transitioned to Passport Advantage, which includes 24x7 cover, so are you sure you don't have it? There are a number of partners who, like mine, offer out-of-hours support on a T&M basis. However, partners are not contractually allowed to use the tbtools programs. I suppose you might find one that would anyway. Finally, if you're brave and depending upon the volume of data involved, you could restore and roll forward, of course truncating the final log so as not to re-introduce the long transaction.

On Sat, 17 Jan 2004 16:55:45 -0000, "Neil Truby" <neil.truby@ardenta.com> wrote: >"Gary Quiring" <gquiring@msn.com> wrote in message >news:tkli00dqvrpp1cms30ab7k6fkknp1dagcd@4ax.com... >> I have a down 7.31 engine and my var does not have after hours IBM >> support for Informix. Is there anyway to contact and create a 24x7 >> support contract on the weekend with IBM? >> >> The problem is the engine is stuck with a LONGTX. I had this once >> before and it won't finish on it's own. It took IBM almost 8 hours >> the last time to fix it. I cannot afford to wait until Monday to have >> them do their magic. > >It shouldn't take them very long to fix it. > >I guess you could try to call the support line and offer a pay-per-call >case. I've heard that they charge something like US$6,000 for this though, >although this may be apocryphal. > >Where are you? IN EMEA most, but not all, Informix support has been >transitioned to Passport Advantage, which includes 24x7 cover, so are you >sure you don't have it? > >There are a number of partners who, like mine, offer out-of-hours support on >a T&M basis. However, partners are not contractually allowed to use the >tbtools programs. I suppose you might find one that would anyway. > >Finally, if you're brave and depending upon the volume of data involved, you >could restore and roll forward, of course truncating the final log so as not >to re-introduce the long transaction. > We are in NJ. Our var is useless. They have an answering service on the weekends. My support goes through them. The answering service is telling me no is calling them back. As for IBM where or what number would I call for support. The direct hot line won't help me without a contract #. Gary

On Sat, 17 Jan 2004 10:41:21 -0500, Gary Quiring <gquiring@msn.com> wrote: >I have a down 7.31 engine and my var does not have after hours IBM >support for Informix. Is there anyway to contact and create a 24x7 >support contract on the weekend with IBM? > >The problem is the engine is stuck with a LONGTX. I had this once >before and it won't finish on it's own. It took IBM almost 8 hours >the last time to fix it. I cannot afford to wait until Monday to have >them do their magic. > >Thanks >Gary Quiring # onstat -x Informix Dynamic Server Version 7.31.UC6 -- On-Line (LONGTX) -- Up 10:34:37 - - -2015216 Kbytes Blocked:LONGTX Transactions address flags userthread locks log begin isolation retrys coordinator 77074018 A---- 7704c018 0 0 COMMIT 0 77074168 A---- 7704c504 0 0 COMMIT 0 770742b8 A---- 7704c9f0 0 0 COMMIT 0 77074408 A---- 7704cedc 0 0 COMMIT 0 77074558 A---- 7704d3c8 0 0 COMMIT 0 770746a8 A---- 7704d8b4 0 0 COMMIT 0 770747f8 A---- 7704dda0 0 0 COMMIT 0 77074948 A---- 7704e28c 0 0 COMMIT 0 77074a98 A---- 7704e778 0 0 COMMIT 0 77074be8 A---- 7704ec64 0 0 COMMIT 0 77074d38 A---- 7704f150 0 0 COMMIT 0 77074e88 A---- 7704f63c 0 0 COMMIT 0 77074fd8 A---- 7704fb28 0 0 COMMIT 0 77075128 A---- 77050014 0 0 COMMIT 0 77075278 A---- 77050500 0 0 COMMIT 0 770753c8 A---- 770509ec 0 0 COMMIT 0 77075518 A---- 77050ed8 0 0 COMMIT 0 77075668 A---- 770513c4 0 0 COMMIT 0 770757b8 A---- 770518b0 0 0 COMMIT 0 77075908 A---- 77051d9c 0 0 COMMIT 0 77075a58 A---- 77052288 0 0 COMMIT 0 77075ba8 A---- 77052774 0 0 COMMIT 0 77075cf8 A---- 77052c60 0 0 COMMIT 0 77075e48 A---- 7705314c 0 0 COMMIT 0 77075f98 A---- 77053638 0 0 COMMIT 0 770760e8 A---- 77053b24 0 0 COMMIT 0 77076238 A---- 77054010 0 0 COMMIT 0 77076388 A---- 770544fc 0 0 COMMIT 0 770764d8 A---- 770549e8 0 0 COMMIT 0 77076628 A---- 77054ed4 0 0 COMMIT 0 77076778 A---- 770553c0 0 0 COMMIT 0 770768c8 A---- 770558ac 0 0 COMMIT 0 77076a18 A---- 77055d98 0 0 COMMIT 0 77076b68 A---- 77056284 1 0 DIRTY 0 77076cb8 A---- 77056770 0 0 COMMIT 0 77076e08 A---S 7705bb1c 2 0 COMMIT 0 action1_shm 77076f58 A---- 770584f8 0 0 NOTRANS 0 770770a8 A---- 77057148 1 0 DIRTY 0 770771f8 A---- 77057b20 1 0 DIRTY 0 77077348 A---- 7705800c 1 0 DIRTY 0 77077498 A---- 770584f8 1 0 DIRTY 0 770775e8 A---- 77057b20 0 0 NOTRANS 0 77077738 A---- 77057634 1 0 DIRTY 0 77077888 A---- 77057634 0 0 NOTRANS 0 770779d8 A---- 770589e4 3 0 COMMIT 0 77077b28 A---- 77058ed0 4 0 COMMIT 0 77077c78 A---- 770593bc 2 0 DIRTY 0 77077dc8 A---- 770598a8 1 0 DIRTY 0 77077f18 A---- 770598a8 0 0 NOTRANS 0 77078068 A---- 770593bc 0 0 NOTRANS 0 770781b8 A---- 77059d94 1 0 DIRTY 0 77078308 A---- 7705a280 1 0 DIRTY 0 77078458 A---- 77059d94 0 0 NOTRANS 0 770785a8 A---- 7705a76c 1 0 DIRTY 0 770786f8 A---- 7705ac58 1 0 DIRTY 0 77078848 A---S 7705b144 2 0 COMMIT 0 action1_shm 77078998 A---- 7705ac58 0 0 NOTRANS 0 77078ae8 A---S 7705b630 1 0 COMMIT 0 action1_shm 77078c38 A---- 77056c5c 1 0 COMMIT 0 77078d88 A---- 7705c008 1 0 COMMIT 0 77078ed8 A---- 7705c008 0 0 NOTRANS 0 77079028 A---- 77056c5c 0 0 NOTRANS 0 77079178 A---- 7705c4f4 1 0 DIRTY 0 770792c8 A---- 7705c9e0 1 0 DIRTY 0 77079418 A---- 7705e27c 1 0 DIRTY 0 77079568 A---- 7705d3b8 3 0 DIRTY 0 770796b8 A---- 7705d8a4 3 0 DIRTY 0 77079808 A---- 7705dd90 3 0 DIRTY 0 77079958 A---- 7705800c 0 0 NOTRANS 0 77079aa8 A---- 7705cecc 1 0 DIRTY 0 77079bf8 A---- 7705a76c 0 0 NOTRANS 0 77079d48 A---- 7705a280 0 0 NOTRANS 0 77079e98 A---- 7705ec54 1 0 DIRTY 0 77079fe8 A---- 7705e768 1 0 DIRTY 0 7707a138 A---- 7705f140 1 0 DIRTY 0 7707a288 A---- 7705f62c 1 0 DIRTY 0 7707a3d8 A---- 770604f0 0 0 NOTRANS 0 7707a528 A---- 77060004 1 0 DIRTY 0 7707a678 A---- 770604f0 1 0 DIRTY 0 7707a7c8 A---- 770609dc 1 0 DIRTY 0 7707a918 A---- 77060ec8 1 0 DIRTY 0 7707aa68 A---- 7705f140 0 0 NOTRANS 0 7707abb8 A---- 770613b4 1 0 DIRTY 0 7707ad08 A---- 77060ec8 0 0 NOTRANS 0 7707ae58 A---- 770618a0 3 0 DIRTY 0 7707afa8 A---- 7705fb18 1 0 DIRTY 0 7707b0f8 A---- 77061d8c 1 0 DIRTY 0 7707b248 A---- 7705fb18 0 0 NOTRANS 0 7707b398 A---- 77061d8c 0 0 NOTRANS 0 89 active, 128 total, 90 maximum concurrent #

Gary Quiring wrote: > On Sat, 17 Jan 2004 10:41:21 -0500, Gary Quiring <gquiring@msn.com> > wrote: > > >>I have a down 7.31 engine and my var does not have after hours IBM >>support for Informix. Is there anyway to contact and create a 24x7 >>support contract on the weekend with IBM? >> >>The problem is the engine is stuck with a LONGTX. I had this once >>before and it won't finish on it's own. It took IBM almost 8 hours >>the last time to fix it. I cannot afford to wait until Monday to have >>them do their magic. >> >>Thanks >>Gary Quiring > > # onstat -x> > Informix Dynamic Server Version 7.31.UC6 -- On-Line (LONGTX) -- Up > 10:34:37 - > - -2015216 Kbytes > Blocked:LONGTX > > Transactions > address flags userthread locks log begin isolation retrys coordinator > 77074018 A---- 7704c018 0 0 COMMIT 0 > 77074168 A---- 7704c504 0 0 COMMIT 0 > 770742b8 A---- 7704c9f0 0 0 COMMIT 0 > 77074408 A---- 7704cedc 0 0 COMMIT 0 > 77074558 A---- 7704d3c8 0 0 COMMIT 0 > 770746a8 A---- 7704d8b4 0 0 COMMIT 0 > 770747f8 A---- 7704dda0 0 0 COMMIT 0 > 77074948 A---- 7704e28c 0 0 COMMIT 0 > 77074a98 A---- 7704e778 0 0 COMMIT 0 > 77074be8 A---- 7704ec64 0 0 COMMIT 0 > 77074d38 A---- 7704f150 0 0 COMMIT 0 > 77074e88 A---- 7704f63c 0 0 COMMIT 0 > 77074fd8 A---- 7704fb28 0 0 COMMIT 0 > 77075128 A---- 77050014 0 0 COMMIT 0 > 77075278 A---- 77050500 0 0 COMMIT 0 > 770753c8 A---- 770509ec 0 0 COMMIT 0 > 77075518 A---- 77050ed8 0 0 COMMIT 0 > 77075668 A---- 770513c4 0 0 COMMIT 0 > 770757b8 A---- 770518b0 0 0 COMMIT 0 > 77075908 A---- 77051d9c 0 0 COMMIT 0 > 77075a58 A---- 77052288 0 0 COMMIT 0 > 77075ba8 A---- 77052774 0 0 COMMIT 0 > 77075cf8 A---- 77052c60 0 0 COMMIT 0 > 77075e48 A---- 7705314c 0 0 COMMIT 0 > 77075f98 A---- 77053638 0 0 COMMIT 0 > 770760e8 A---- 77053b24 0 0 COMMIT 0 > 77076238 A---- 77054010 0 0 COMMIT 0 > 77076388 A---- 770544fc 0 0 COMMIT 0 > 770764d8 A---- 770549e8 0 0 COMMIT 0 > 77076628 A---- 77054ed4 0 0 COMMIT 0 > 77076778 A---- 770553c0 0 0 COMMIT 0 > 770768c8 A---- 770558ac 0 0 COMMIT 0 > 77076a18 A---- 77055d98 0 0 COMMIT 0 > 77076b68 A---- 77056284 1 0 DIRTY 0 > 77076cb8 A---- 77056770 0 0 COMMIT 0 > 77076e08 A---S 7705bb1c 2 0 COMMIT 0 action1_shm > 77076f58 A---- 770584f8 0 0 NOTRANS 0 > 770770a8 A---- 77057148 1 0 DIRTY 0 > 770771f8 A---- 77057b20 1 0 DIRTY 0 > 77077348 A---- 7705800c 1 0 DIRTY 0 > 77077498 A---- 770584f8 1 0 DIRTY 0 > 770775e8 A---- 77057b20 0 0 NOTRANS 0 > 77077738 A---- 77057634 1 0 DIRTY 0 > 77077888 A---- 77057634 0 0 NOTRANS 0 > 770779d8 A---- 770589e4 3 0 COMMIT 0 > 77077b28 A---- 77058ed0 4 0 COMMIT 0 > 77077c78 A---- 770593bc 2 0 DIRTY 0 > 77077dc8 A---- 770598a8 1 0 DIRTY 0 > 77077f18 A---- 770598a8 0 0 NOTRANS 0 > 77078068 A---- 770593bc 0 0 NOTRANS 0 > 770781b8 A---- 77059d94 1 0 DIRTY 0 > 77078308 A---- 7705a280 1 0 DIRTY 0 > 77078458 A---- 77059d94 0 0 NOTRANS 0 > 770785a8 A---- 7705a76c 1 0 DIRTY 0 > 770786f8 A---- 7705ac58 1 0 DIRTY 0 > 77078848 A---S 7705b144 2 0 COMMIT 0 action1_shm > 77078998 A---- 7705ac58 0 0 NOTRANS 0 > 77078ae8 A---S 7705b630 1 0 COMMIT 0 action1_shm > 77078c38 A---- 77056c5c 1 0 COMMIT 0 > 77078d88 A---- 7705c008 1 0 COMMIT 0 > 77078ed8 A---- 7705c008 0 0 NOTRANS 0 > 77079028 A---- 77056c5c 0 0 NOTRANS 0 > 77079178 A---- 7705c4f4 1 0 DIRTY 0 > 770792c8 A---- 7705c9e0 1 0 DIRTY 0 > 77079418 A---- 7705e27c 1 0 DIRTY 0 > 77079568 A---- 7705d3b8 3 0 DIRTY 0 > 770796b8 A---- 7705d8a4 3 0 DIRTY 0 > 77079808 A---- 7705dd90 3 0 DIRTY 0 > 77079958 A---- 7705800c 0 0 NOTRANS 0 > 77079aa8 A---- 7705cecc 1 0 DIRTY 0 > 77079bf8 A---- 7705a76c 0 0 NOTRANS 0 > 77079d48 A---- 7705a280 0 0 NOTRANS 0 > 77079e98 A---- 7705ec54 1 0 DIRTY 0 > 77079fe8 A---- 7705e768 1 0 DIRTY 0 > 7707a138 A---- 7705f140 1 0 DIRTY 0 > 7707a288 A---- 7705f62c 1 0 DIRTY 0 > 7707a3d8 A---- 770604f0 0 0 NOTRANS 0 > 7707a528 A---- 77060004 1 0 DIRTY 0 > 7707a678 A---- 770604f0 1 0 DIRTY 0 > 7707a7c8 A---- 770609dc 1 0 DIRTY 0 > 7707a918 A---- 77060ec8 1 0 DIRTY 0 > 7707aa68 A---- 7705f140 0 0 NOTRANS 0 > 7707abb8 A---- 770613b4 1 0 DIRTY 0 > 7707ad08 A---- 77060ec8 0 0 NOTRANS 0 > 7707ae58 A---- 770618a0 3 0 DIRTY 0 > 7707afa8 A---- 7705fb18 1 0 DIRTY 0 > 7707b0f8 A---- 77061d8c 1 0 DIRTY 0 > 7707b248 A---- 7705fb18 0 0 NOTRANS 0 > 7707b398 A---- 77061d8c 0 0 NOTRANS 0 > 89 active, 128 total, 90 maximum concurrent > > # > > > Humm, An onstat -l along with the onstat -x would give more clue. However, having a "action1_shm" presumably as a distributed transaction co-ordinator using the shared memory protocol is not a good idea. Where is the other engine?? What is it doing?? So perhaps an onstat -x and an onstat -l from that system would help. TBP

On Sat, 17 Jan 2004 20:23:40 +0000, TBP <TBP@Nospam.Nothere.Co.Uk> wrote: I finally got past the IBM auto attendent and got some help. The tech was a super nice person. They had to truncate the log. I did not notice that Action1 was also down to a LONGTX until after I posted. Luckily they had no problem fixing that one either. Gary

"Gary Quiring" <gquiring@msn.com> wrote in message news:ohsi00d4u19lj0juk1n9fv6l7ivuis983r@4ax.com... > On Sat, 17 Jan 2004 16:55:45 -0000, "Neil Truby" > <neil.truby@ardenta.com> wrote: > > >"Gary Quiring" <gquiring@msn.com> wrote in message > >news:tkli00dqvrpp1cms30ab7k6fkknp1dagcd@4ax.com... > >Where are you? IN EMEA most, but not all, Informix support has been > >transitioned to Passport Advantage, which includes 24x7 cover, so are you > >sure you don't have it? > We are in NJ. This is somewhere in America then?

"Gary Quiring" <gquiring@msn.com> wrote in message news:keaj00t4ig396ti43s1q5knpul5sjtr3lh@4ax.com... > On Sat, 17 Jan 2004 20:23:40 +0000, TBP <TBP@Nospam.Nothere.Co.Uk> > wrote: > > I finally got past the IBM auto attendent and got some help. The tech > was a super nice person. They had to truncate the log. Well, it's good to hear that you received excellent service from IBM. It's this sort of thing that will encourage end-users to stay with Informix.