Subject | Re: [firebird-support] unavailable database |
---|---|
Author | Ann Harrison |
Post date | 2013-01-09T16:28Z |
On Wed, Jan 9, 2013 at 9:19 AM, André Knappstein <
Knappstein@...> wrote:
clarify a misunderstanding. Limbo transactions are the result of an
incomplete two phase commit and have nothing to do with multi-file or even
shadowed databases. The application has to initiate a two phase commit
with a call to PREPARE. Normally that's done to coordinate updates in
different databases, but it can also be done to coordinate a database
commit with some other activity that does not have the ability to rollback.
Good luck,
Ann
Knappstein@...> wrote:
>Having nothing to do with your problem - which I'm thinking about - but to
>
> - database only has 1 file (no limbo problems)
>
clarify a misunderstanding. Limbo transactions are the result of an
incomplete two phase commit and have nothing to do with multi-file or even
shadowed databases. The application has to initiate a two phase commit
with a call to PREPARE. Normally that's done to coordinate updates in
different databases, but it can also be done to coordinate a database
commit with some other activity that does not have the ability to rollback.
Good luck,
Ann
>[Non-text portions of this message have been removed]
>