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

Jump to bottom

Unable to restore a database with inactive indices if any SP/trigger contains an explicit plan [CORE1725] #2149

Open
firebird-automations opened this issue Feb 4, 2008 · 4 comments
Open

Unable to restore a database with inactive indices if any SP/trigger contains an explicit plan [CORE1725] #2149

firebird-automations opened this issue Feb 4, 2008 · 4 comments
Labels
affect-version: 2.0.0 affect-version: 2.0.1 affect-version: 2.0.2 affect-version: 2.0.3 affect-version: 2.1 RC1 component: engine priority: major qa: done successfully type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @dyemanov

Is duplicated by CORE6350

Votes: 2

gbak -r -i <backup path> <database path>. Note the -i switch which is expected to deactivate the indices (e.g. backup contains duplicates in PK). Now, if any PSQL code contains an explicit plan referencing any indices, then the restore fails:

gbak:creating indexes
gbak: committing metadata
gbak: ERROR:<index name> cannot be used in the specified plan
gbak:Exiting before completion due to errors

At this point, tables with data are restored fine but all the PSQL objects are lost.

====== Test Details ======

::: NB ::: This bug was fixed between 17-dec-2018 and 23-jan-2019.
Builds 4.0.0.1346 and 3.0.5.33084 (both of 17.12.2018) still have bug: no program units will be in restored DB.
Builds 4.0.0.1391 (23.01.2019) and 3.0.5.33097 (01.02.2019) work fine.

Ticket state can be changed to resolved / fixed.
@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: Done successfully

Test Details: ::: NB ::: This bug was fixed between 17-dec-2018 and 23-jan-2019.
Builds 4.0.0.1346 and 3.0.5.33084 (both of 17.12.2018) still have bug: no program units will be in restored DB.
Builds 4.0.0.1391 (23.01.2019) and 3.0.5.33097 (01.02.2019) work fine.

Ticket state can be changed to resolved / fixed.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue is duplicated by CORE6350 [ CORE6350 ]

@dyemanov dyemanov mentioned this issue Mar 9, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affect-version: 2.0.0 affect-version: 2.0.1 affect-version: 2.0.2 affect-version: 2.0.3 affect-version: 2.1 RC1 component: engine priority: major qa: done successfully type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@firebird-automations