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
Gbak cannot restore [CORE1144] #1565
Comments
Commented by: @dyemanov It should be reproducible with metadata-only backup. Could you provide it? |
Modified by: @dyemanovassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Commented by: Andrey Lapin (trurl) metadata backup |
Modified by: Andrey Lapin (trurl)Attachment: bankerp_meta.zip [ 10280 ] |
Commented by: @dyemanov 1) This backup cannot be restored using v1.5, it seems that a derived table is used in some view/procedure/trigger (BLR error is thrown). 2) The restore problem is caused by some RDB$RELATION_FIELDS records that have RDB$COLLATION_ID = -1. I don't know how it could happen. But the record referring to a D_TEXT domain stops the restore process because text blobs support collations in v2.0 and there's no such collation with ID = 255 (-1). The issue should go away after updating that column to zero and then backup/restore again. |
Modified by: Sean Leyne (seanleyne)status: Open [ 1 ] => Resolved [ 5 ] resolution: Won't Fix [ 2 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 11641 ] => Firebird [ 15434 ] |
Submitted by: Andrey Lapin (trurl)
Attachments:
bankerp_meta.zip
Gbak shows error, while restoring
gbak:restoring exception EX_NOT_CREATE_DOC
gbak: committing metadata
gbak: ERROR:unsuccessful metadata update
gbak: ERROR: T_JUR_PERSONS
gbak: ERROR: Implementation of text subtype 65332 not located.
gbak:Exiting before completion due to errors
But version 1.5.3 works OK
The text was updated successfully, but these errors were encountered: