Subject Stuck Transaction caused by gbak
Author cyndi_lewis55
We have a production database that has an active, but stuck, transaction, which we can see using Sinatica. The transaction was started by a gbak backup that was started 3 weeks ago and has not completed. We see the gbak command in Task Manager; it is not taking any CPU time. We backup this database nightly and subsequent backups have completed. We're on Firebird 2.1.

What's your advise for resolving this? We're considering killing gbak. But, is it safe? Will it rollback the stuck transaction? Will any data that users have entered since gbak got stuck be lost? And, this is a large database, around 35GB. Will it take forever for garbage collection to occur?

Thanks for your advise.