New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gfix reports db ownership error way too late [CORE2271] #2697
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff At the same time backported in 1.5 fix for CORE1972 - it's no sense having only half of solution ported. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 Beta 1 [ 10251 ] Fix Version: 1.5.6 [ 10225 ] Fix Version: 2.1.3 [ 10302 ] Fix Version: 2.0.6 [ 10303 ] |
Commented by: @AlexPeshkoff Decreased security level - has no really critical issues. |
Modified by: @AlexPeshkoffsecurity: Developers [ 10012 ] => |
Commented by: @AlexPeshkoff Fix will go into final 2.1.2 release |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: Saulius Vabalas (svabalas)
on 70GB db gfix reports "Unable to perform operation. You must be either SYSDBA or owner of the database" only after 30 min of CPU/HDD activity. Would be nice to check db ownership first thing without such a huge delay. Most of the time db fixing is an operation performed when customer has outage due to db problems. Every downtime minute counts then.
command line:
/opt/firebird/bin/gfix -mend -full db.fdb
Commits: 2929d70 4a62812 a3ee9e0 7d1e52e
The text was updated successfully, but these errors were encountered: