asked on

transaction stuck in limbo

I've got between 3 and 12 computers ( at different locations ) with the same problem.. :

The computers are runnning Interbase 6 and replication.

Some of the computers are slower than the others, about once a week I get an "Transaction Stuck In Limbo" error message while an updating script is running on the 'master' computer, The error message only occurs on the slave computers which are being replicated to... and to fix the problem I perform a backup and restore on the 'master' and 'slave' while the replication service has stopped.

Has anyone got the same problem.. ? Please help guys..

ASKER CERTIFIED SOLUTION

BAlexandrov

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Tomstone

Your question is product (IBReplicator?) related, so you should follow Bojidar's suggestions.

Though, just for your information. A transaction gets in limbo if something unpredictable happens during a two-phase commit (usually used in replication, when a transaction spans over two or more databases). So, there went something wrong in your replication process. Either perform a backup and restore or use gfix.exe to commit/rollback a transaction in limbo.

HTH,
Thomas Steinmaurer
http://www.iblogmanager.com

tonytone1978

ASKER

I have moved to the firebird database http://firebird.sourceforge.net
and had no unexplained transaction stuck in limbo problems..

Thanks guys..