Subject | Re: [firebird-support] Re: Anyone know what this error means, isc_req_sync? |
---|---|
Author | Helen Borrie |
Post date | 2004-07-27T15:46:14Z |
At 02:12 PM 27/07/2004 +0000, you wrote:
transactions don't arise in a transaction involving only one database, and
limbo transactions have no capability to "unlimbo" themselves. A limbo
transaction is a two-phase, multi-database transaction that gets left in an
indeterminate state when the connection is lost to one or other databases
before the two-phase commit completes.
If you are getting messages about limbo transactions, you'll need to fix
them. This requires use of the gfix utility and Chapter 39 of The Firebird
Book (coming real soon! :-) ) Absent The Firebird Book, study the
relevant section in the IB6 OpGuide.pdf.
/heLen
>This is very helpful, Thanks. Now an addition tidbit. I amUh-oh, this could be a different sort of sync error altogether. Limbo
>encountering this error when retrying an a select statement after
>encountering a limbo transaction error. So does this mean the
>transaction is out of limbo state and the query has proceeded before
>I retry? What is the best way to handle limbo transactions errors
>encountered during a query?
transactions don't arise in a transaction involving only one database, and
limbo transactions have no capability to "unlimbo" themselves. A limbo
transaction is a two-phase, multi-database transaction that gets left in an
indeterminate state when the connection is lost to one or other databases
before the two-phase commit completes.
If you are getting messages about limbo transactions, you'll need to fix
them. This requires use of the gfix utility and Chapter 39 of The Firebird
Book (coming real soon! :-) ) Absent The Firebird Book, study the
relevant section in the IB6 OpGuide.pdf.
/heLen