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 fails to fix system generators while restoring [CORE3733] #4079

Closed
firebird-issue-importer opened this issue Jan 16, 2012 · 11 comments
Closed

Comments

@firebird-issue-importer

Submitted by: Ramsees Rastafa (ramsees79)

Attachments:
rastrometa.fbk

I have a .fbk file that cannot be restored using fb 2.5.1, I have no problems with fb 2.5.0, the error I get is:

gbak: committing metadata
Database restore canceled 14:17:15 due to IBPP exception:

*** IBPP::SQLException ***
Context: ServiceImpl::Wait
Message: isc_service_query failed

SQL Message : -413
Overflow occurred during data type conversion.

Engine Code : 335544334
Engine Message :
conversion error from string "1O1 "

This is the FlameRobin error, but I get the same error if I use gbak in the console.

I can send you the .fbk if you ask me, since I don't see a way to attach it here.

Commits: a230e65 f5cc73a fb91147

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 16, 2012

Commented by: Ramsees Rastafa (ramsees79)

Here is the fbk.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 16, 2012

Modified by: Ramsees Rastafa (ramsees79)

Attachment: rastrometa.fbk [ 12087 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 16, 2012

Modified by: Ramsees Rastafa (ramsees79)

security: Developers [ 10012 ] =>

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 17, 2012

Commented by: @dyemanov

Recreate the primary key on the table DRASCLIENTES before backing up and the restore will succeed. I don't know how you managed to create it as it looks like being named by the engine itself but in fact it was named manually using the reserved prefix (INTEG_). This situation confuses some part of the restore code.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 17, 2012

Commented by: @dyemanov

Alex, this is a regression caused by the fix for CORE3461. I would suggest to ignore (all or conversion only) errors while fixing the generators.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 17, 2012

Modified by: @dyemanov

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 18, 2012

Modified by: @AlexPeshkoff

summary: GBAK can't commit metadata while restoring... => GBAK fails to fix system generators while restoring

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 18, 2012

Commented by: @AlexPeshkoff

Use correct way to detect digital strings. In 2.1 with missing SIMILAR TO had to ignore errors when fixing generators.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 18, 2012

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

Fix Version: 2.1.5 [ 10420 ]

Fix Version: 2.5.2 [ 10450 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 23, 2013

Modified by: @pcisar

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 29, 2015

Modified by: @pavel-zotov

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

QA Status: Done successfully

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

Successfully merging a pull request may close this issue.

None yet
2 participants