security3.fdb and "internal Firebird consistency check"
-------------------------------------------------------
Key: CORE-5949
URL: http://tracker.firebirdsql.org/browse/CORE-5949
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0.4
Environment: Windows 7 x64, Firebird 3.0.4 SuperServer x64
Reporter: Basil A. Sidorov
Change access mode to security3.fdb.
Set read-only is success:
fbsvcmgr xnet://service_mgr action_properties prp_access_mode prp_am_readonly
dbname security.db
Try return to read-write (fbsvcmgr xnet://service_mgr action_properties
prp_access_mode prp_am_readwrite dbname security.db) - bugcheck in firebird.log:
Database: C:\PROGRAM FILES\FB\3.0.4\SECURITY3.FDB
internal Firebird consistency check (next transaction older than oldest active
transaction (266), file: cch.cpp line: 4830)
After bugchek many operation will hang. F.e. connect to Firebir server on stop
Firebird service.
Bug can exploit any user on server console, who knows sysdba password.
If set linger to zero (default is 60 for security3.db):
echo alter database drop linger | isql xnet://security.db
or
echo alter database drop linger | isql security.db
on initial setup for security3.db, then mode changed without bugcheck.
--
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
