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
Migrating Firebird 2.5.2 to 3.0.1 gbak restore crashes at the end always [CORE5456] #5727
Comments
Modified by: erkankurtaga (erkankurtaga)Version: 3.0.1 [ 10730 ] Version: 2.5.2 [ 10450 ] => |
Commented by: @dyemanov Did you try restoring with any recent v3.0.2 snapshot build? |
Commented by: erkankurtaga (erkankurtaga) No, I didn't try. I setup the recent v3.0.2 snapshot build, but user adding to firebird very difficult . I use "gsec -add SYSDBA -pass masterkey" command but gsec gives error like that : use gsec -? to get help Because of this ı didn't try. Sorry |
Commented by: erkankurtaga (erkankurtaga) I could create SYSDBA and tried restore with 3.0.2 snapshot. Result is the same. We couldn't restore database ! |
Commented by: erkankurtaga (erkankurtaga) Here is the gbak restore with command at the end Windows 7 Pro error: Problem Event Name: APPCRASH |
Commented by: erkankurtaga (erkankurtaga) Anyone else who answer me, please... |
Commented by: @dyemanov Please also try metadata only restore (-m switch) - whether it crashes or not. And main question: can you provide your backup to FB developers in order to fix the issue? |
Commented by: erkankurtaga (erkankurtaga) Metadata Restore has the same error. FBK is at the attachment. |
Modified by: erkankurtaga (erkankurtaga)Attachment: 29122016_171826.zip [ 13058 ] |
Commented by: @dyemanov Confirmed. |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0.2 [ 10785 ] Fix Version: 4.0 Alpha 1 [ 10731 ] |
Commented by: erkankurtaga (erkankurtaga) I tried new snapshot but the problem is continue: Problem Event Name: APPCRASH |
Commented by: @dyemanov Snapshot containing the bugfix will be available tomorrow. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Deferred Test Details: Waiting for reply on letter to dimitr, 09-feb-2017 22:13 |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] Test Details: Waiting for reply on letter to dimitr, 09-feb-2017 22:13 => Waiting for reply on letter to dimitr, 09-feb-2017 23:13 |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] Test Details: Waiting for reply on letter to dimitr, 09-feb-2017 23:13 => Restoring process takes about 1 minute (too long). |
Hello, I'm having a similar error and I'm not finding any clue what it could be. gbak:fixing views dbkey length |
Provide reproducibl test case, please. |
Windows - Firebird x64 - 3.0.8.33535 Backup - gbak -backup -ignore -v F:\Dados\SOBEBE_15022022.GDB F:\Dados\SOBEBE_15022022.fbk Restore - gbak -create -v F:\Dados\SOBEBE_15022022.fbk F:\Dados\SOBEBE_15022022.fb Thanks. |
At the very end of restore process gbak adjusted values of generators on system tables. In your case the problem query is
Note, it assumes 32-bit integer values - and it is reasonable assumption, as it is hard to imagine more than 2^31 system objects in database (relation constraints in this case). So, expression See below:
I'm pretty sure, it is impossible to reach such values in natural way. The same issue found with two more generators:
gbak could be changed to use BIGINT when adjusting system generators. Resume:
|
After more investigations I think it is could be related with #6054 |
Thanks for the clarification, it was very helpful. |
Now it should be possible to backup and restore database and restore will adjust system generators to actual used max values. |
But this instruction won't let you redo the value of the generator |
IIRC, values of system generators at that moment are zero's. Just try it. |
I had already tried without success, but I found the problem, it had not removed the RDB$FIELDS.RDB$FIELD_NAME objects related to RDB$PROCEDURE_PARAMETERS.RDB$FIELD_SOURCE. |
Submitted by: erkankurtaga (erkankurtaga)
Attachments:
29122016_171826.zip
When Migrating Firebird 2.5.2 to 3.0.1 gbak restore crashes at the end always. We use Delphi XE4 and over and our database components IBSQL and Firedac, I tried restore with command prompt, components restore api and IBExpert restore at its editor manually. Always the same error :
gbak:creating indexes
gbak:committing metadata
gbak:fixing views dbkey length
gbak:updating ownership of packages, procedures and tables
gbak:adding missing privileges
gbak:fixing system generators
IBE: Unsuccessful execution caused by a system error that precludes successful execution of subsequent statements.
Error reading data from the connection.
Commits: 5dd8daf 214921b 3e15291 cebbbf5 2cb8c9c 37e2aa3 7539585 e8dd0b1
====== Test Details ======
Restoring process takes about 1 minute (too long).
After discuss with dimitr it was decided to try another method, without using supplied .fbk
Waiting for sketch / suggestion from dimitr, letter: 10-feb-2016 11:16
The text was updated successfully, but these errors were encountered: