Comments on: Tip: WebSphere Process Server - Do not delete the ‘tranlog’ on a production server

By: dan

dan — Mon, 23 Jun 2008 17:44:12 +0000

Strangely enough, I have a production server with 0 in-doubt transactions that keeps trying to contact an external transaction agent (Oracle) every 5 minutes and fails.

By: David Currie

David Currie — Mon, 23 Jun 2008 17:34:56 +0000

Phani - typically the transaction manager is retrying periodically because it can’t contact the resource manager in question. If you know it is never going to succeed (the database no longer exists for example) then you can review and complete the indoubt transactions on the runtime tab of the transaction service in the administrative console.

Regards,
David

By: Phani

Phani — Thu, 19 Jun 2008 19:42:04 +0000

Thanks for the reply. I will make note of the server -recovery.

By: dan

dan — Thu, 19 Jun 2008 18:42:47 +0000

Thats a great point.

I am actually working with IBM resources to bring a server back that crashed and has the standard tranlog issues.

Basically, it boils down to start the server with -recovery which I described in a later post. This gives the admin the chance to manually roll-back or commit transactions.

As an aside, we are experiencing issues with Oracle and recovery that I’m waiting for the issue on in order to blog it, but I would say doing the step above resulted in 98% of the transactions being cleared out of the log.

By: Phani

Phani — Thu, 19 Jun 2008 15:53:06 +0000

Dan - Though it is not a good practice to remove transaction logs in Prod, I see it becomes unavoidable sometimes. This happens in cases where by some times the server spews out XA transction recovery exceptions periodically. Can you please give some insight or a link on how to recover these transactions without taking the hard route.
Thanks
Phani