LONGTX message during engine startup

Here's the message: Informix Dynamic Server Version 7.30.UC2 -- On-Line (LONGTX) -- Up 00:06:56 -- 323584 Kbytes Blocked:LONGTX From online.log: 15:33:11 Continuing Long Transaction (for COMMIT): tx 0x8fc70cb4 nouser info due to XA or distributed (2-phase commit) transaction" Is there anyway to tell how long the transactions is? Also what causes this? Thanks Gary Quiring

You crashed you engine or shutdown crashed the machine while in the middle of a distributed transaction affecting tables on multiple instances. You will have to wait for it to complete. Try looking at onstat -x. Art S. Kagel Gary Quiring wrote: > > Here's the message: > > Informix Dynamic Server Version 7.30.UC2 -- On-Line (LONGTX) -- Up > 00:06:56 -- > 323584 Kbytes > Blocked:LONGTX > > From online.log: > 15:33:11 Continuing Long Transaction (for COMMIT): tx 0x8fc70cb4 no> user info > due to XA or distributed (2-phase commit) transaction" > > Is there anyway to tell how long the transactions is? Also what > causes this? > > Thanks > Gary Quiring

Not necessarily says the grim faced mja. Informix is a client of a TPM ie something else is co-ordinating the transaction. Now informix's behaviour is defined very explicitly by the Open groups XA transaction standard. Poor old informix does not know how far this thing goes so... a) It cannot kill and rollback an XA transaction unless it receives direction from the co-ordinator to that effect or the transaction crosses log HWM or (shudder) it crosses Exclusive High water mark) b) It gets worse. If the co-ordinator issues the XAPRECOMMIT, ie boyz we're all ready to do our thing. But no commit ever comes along. Under these circumstances Informix will do an heuristic rollback (err eventually). This is very bad situation (we're talking distributed corruption here), the standard says informix must inform the co- ordinator about what it has and has not done, it will hang in Longtx until it can. If it cannot contact the co-ordinator... that means forever. Informix have to dial in and do their magic oncheck stuff to close the open transaction ( or you can restore your instance). I have recently been aquiring this particular tee-shirt. regrds mja In article <39A2DCEC.43200658@bloomberg.net>, kagel@bloomberg.net wrote: > You crashed you engine or shutdown crashed the machine while in the middle > of a distributed transaction affecting tables on multiple instances. You will > have to wait for it to complete. Try looking at onstat -x. > > Art S. Kagel > > Gary Quiring wrote: > > > > Here's the message: > > > > Informix Dynamic Server Version 7.30.UC2 -- On-Line (LONGTX) -- Up > > 00:06:56 -- > > 323584 Kbytes > > Blocked:LONGTX > > > > From online.log: > > 15:33:11 Continuing Long Transaction (for COMMIT): tx 0x8fc70cb4no > > user info > > due to XA or distributed (2-phase commit) transaction" > > > > Is there anyway to tell how long the transactions is? Also what > > causes this? > > > > Thanks > > Gary Quiring > Sent via Deja.com http://www.deja.com/ Before you buy.