Re: [firebird-support] Transaction in limbo

2016-07-19 Thread 'Mark Rotteveel' m...@lawinegevaar.nl [firebird-support]
Of course there is: just call isc_prepare and never commit or rollback. Mark - Bericht beantwoorden - Van: "Dimitry Sibiryakov s...@ibphoenix.com [firebird-support]" <firebird-support@yahoogroups.com> Aan: <firebird-support@yahoogroups.com> Onderwerp: [firebir

Re: [firebird-support] Transaction in limbo

2016-07-19 Thread Dimitry Sibiryakov s...@ibphoenix.com [firebird-support]
19.07.2016 12:14, michael.vilhelm...@microcom.dk [firebird-support] wrote: > As I read about 2 phase commits, its about 2 databases. We do not use more > than one There is no other way to get transaction in limbo. -- WBR, SD.

Re: [firebird-support] Transaction in limbo

2016-07-19 Thread michael.vilhelm...@microcom.dk [firebird-support]
No - here I cannot since we have one external access to this database. And sinse this database is the only one doing this, I have a suspecion that this external access is doing something wrong. But I will check my own programs first to be sure I do not do it wrong

Re: [firebird-support] Transaction in limbo

2016-07-19 Thread Dimitry Sibiryakov s...@ibphoenix.com [firebird-support]
19.07.2016 13:33, michael.vilhelm...@microcom.dk [firebird-support] wrote: > I have total access to the code :) > I wrote all of it. But you cannot be sure that they use only your software. -- WBR, SD.

Re: [firebird-support] Transaction in limbo

2016-07-19 Thread michael.vilhelm...@microcom.dk [firebird-support]
I have total access to the code :) I wrote all of it. I only have one routine, where I do two connects to the database. Those do not interact in any way. Or at least they shouldn't - i'll do a check.

Re: [firebird-support] Transaction in limbo

2016-07-19 Thread Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
On 19-7-2016 12:14, michael.vilhelm...@microcom.dk [firebird-support] wrote: > As I read about 2 phase commits, its about 2 databases. We do not use > more than one Not really, two-phase commits can also be applied to a single database, single connection. It just means that instead of doing an

Re: [firebird-support] Transaction in limbo

2016-07-19 Thread Lester Caine les...@lsces.co.uk [firebird-support]
On 19/07/16 11:14, michael.vilhelm...@microcom.dk [firebird-support] wrote: > As I read about 2 phase commits, its about 2 databases. We do not use > more than one Application with two connections to the same database? That may not be so easy to spot if you don't have full access to the code. --

Re: [firebird-support] Transaction in limbo

2016-07-19 Thread michael.vilhelm...@microcom.dk [firebird-support]
As I read about 2 phase commits, its about 2 databases. We do not use more than one

Re: [firebird-support] Transaction in limbo

2016-07-19 Thread michael.vilhelm...@microcom.dk [firebird-support]
We do not use either replication or more than one database.

Re: [firebird-support] Transaction in limbo

2016-07-19 Thread Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
On 19-7-2016 09:32, michael.vilhelm...@microcom.dk [firebird-support] wrote: > I have a database, which have had to instances where there have been > Transactions in limbo. > I know how to fix this. > > I am on the other hand unsure why they appear. > What can cause this? > What should/could I

Re: [firebird-support] Transaction in limbo

2016-07-19 Thread 'Thomas Steinmaurer' t...@iblogmanager.com [firebird-support]
> Hi > > I have a database, which have had to instances where there have been > Transactions in limbo. > I know how to fix this. > > I am on the other hand unsure why they appear. > What can cause this? > What should/could I check, so I can eliminate this from occuring. Something went wrong

[firebird-support] Transaction in limbo

2016-07-19 Thread michael.vilhelm...@microcom.dk [firebird-support]
Hi I have a database, which have had to instances where there have been Transactions in limbo. I know how to fix this. I am on the other hand unsure why they appear. What can cause this? What should/could I check, so I can eliminate this from occuring. The database is a Firebird 2.5 running