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
Restore of encrypted backup of database with SQL dialect 1 fails [CORE6071] #6321
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffsummary: Restore of dialect==1 database encrypted backup fails => Restore of encrypted backup of database with SQL dialect 1 fails |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 2 [ 10888 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Deferred Test Details: Have question about implementation, sent it to Alex, 04.06.2019 16:48. Waiting for reply. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Deferred => Done successfully Test Details: Have question about implementation, sent it to Alex, 04.06.2019 16:48. Waiting for reply. => NB: bug was reproduced only when "gbak -keyholder <keyholder_name>" was used. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Ticket must be RE-opened.
If we comment out line "$FBHOME/bin/gfix -sql_dialect 1 $DBNAME" then this script works fine.
Checked on 4.0.2.2799, 5.0.0.590. PS. Steps to reproduce:
|
What exact command raises error ? |
Both cases of 'gbak -rep ...' raise the same errors:
|
Yes, exactly: first we encrypt DB and after this we change its dialect:
Of course, I could understand wrongly ticket subject, but - whats wrong here ? |
Submitted by: @AlexPeshkoff
gbak: ERROR:Dynamic SQL Error
gbak: ERROR: SQL error code = -817
gbak: ERROR: Metadata update statement is not allowed by the current database SQL dialect 1
gbak:Exiting before completion due to errors
Commits: f81ae05
====== Test Details ======
NB: bug was reproduced only when "gbak -keyholder <keyholder_name>" was used.
The text was updated successfully, but these errors were encountered: