nbackup unlock causes internal Firebird consistency check (next transaction
older than oldest active transaction)
-----------------------------------------------------------------------------------------------------------------
Key: CORE-6059
URL: http://tracker.firebirdsql.org/browse/CORE-6059
Project: Firebird Core
Issue Type: Bug
Components: Engine, NBACKUP
Affects Versions: 2.5.8
Environment: Linux 4.1.12-124.25.1.el7uek.x86_64 #2 SMP x86_64 x86_64
x86_64 GNU/Linux
Reporter: Omacht András
Priority: Critical
Hi!
Our backup script uses nbackup.
1. It locks the database with -L
2. Copy it (with scp) to an another box
3. Unlock with -N
We have running and newly starting transactions while the backup process
running.
Backup log:
2019-04-30 23:19:56 /u1/firebird/database.fdb LOCKED [ OK ]
2019-04-30 23:20:00 /u1/firebird/database.fdb SCP[ OK ]
2019-04-30 23:20:00 /u1/firebird/database.fdb UnLOCKED [ OK ]
Firebird log (same time as unlock):
server<--->Tue Apr 30 23:20:00 2019
<------>Database: /u1/firebird/database.fdb
<------>internal Firebird consistency check (next transaction older than oldest
active transaction (266), file: cch.cpp line: 6523)
server<--->Tue Apr 30 23:22:01 2019 (2 mins
later!)
<------>Database: /u1/firebird/database.fdb
<------>deadlock
We have 3 other databases following with the same error (internal Firebird
consistency check (next transaction older than oldest active transaction (266),
file: cch.cpp line: 6523)).
But only 2 of 4 have deadlock entry.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
