Skip to content
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

Closed
firebird-automations opened this issue Feb 28, 2007 · 8 comments
Closed

Gbak cannot restore [CORE1144] #1565

firebird-automations opened this issue Feb 28, 2007 · 8 comments

Comments

@firebird-automations
Copy link
Collaborator

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

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

It should be reproducible with metadata-only backup. Could you provide it?

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Adriano dos Santos Fernandes [ asfernandes ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Andrey Lapin (trurl)

metadata backup

@firebird-automations
Copy link
Collaborator Author

Modified by: Andrey Lapin (trurl)

Attachment: bankerp_meta.zip [ 10280 ]

@firebird-automations
Copy link
Collaborator Author

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.

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Won't Fix [ 2 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11641 ] => Firebird [ 15434 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants