• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1826
  • Last Modified:

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..
1 Solution
Better ask at borland.public.interbase.replication newsgroup at news://newsgroups.borland.com

Bojidar Alexandrov
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.

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

Thanks guys..

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now