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

Restore from gbak backup using service doesn't report an error [CORE3942] #4275

Closed
firebird-automations opened this issue Oct 2, 2012 · 10 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @pcisar

When database exists and isc_spb_res_create instead isc_spb_res_replace is specified, restore using service doesn't report any error, just silently does nothing.

Although not confirmed, could it be a general issue with error reporting from gbak service?

(Also see CORE3942?focusedCommentId=26802&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#⁠action_26802 for related errors)

Commits: fb08ee8 1ef34fd FirebirdSQL/fbt-repository@0475a59 FirebirdSQL/fbt-repository@6542d03

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

There are may be issues with error reporting

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Can you check 2.5.2 ?

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

The same for 2.5.2 (supercalssic).

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Pavel, in current B2_5_Release I get:
#⁠ ./fbsvcmgr localhost:service_mgr user sysdba password masterkey action_restore dbname /tmp/e.fdb bkp_file emp.fbk
database /tmp/e.fdb already exists. To replace it, use the -REP switch

(though there are other issues with gbak's error reporting as service)

Can you recheck please this particular problem?

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Original test case is not reproduced in both B2_5_Release and trunk. On the other hand 2 related issues are found:
- message 'Error closing database, but backup file is OK' is lost
- message 'Invalid metadata detected. Use -FIX_FSS_METADATA option.' is lost

I close this issue with fix for this 2 errors.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

Version: 2.5.2 Update 1 [ 10521 ]

Version: 2.5.2 [ 10450 ]

Version: 3.0 Initial [ 10301 ]

description: When database exists and isc_spb_res_create instead isc_spb_res_replace is specified, restore using service doesn't report any error, just silently does nothing.

Although not confirmed, could it be a general issue with error reporting from gbak service?

=>

When database exists and isc_spb_res_create instead isc_spb_res_replace is specified, restore using service doesn't report any error, just silently does nothing.

Although not confirmed, could it be a general issue with error reporting from gbak service?

(Also see CORE3942?focusedCommentId=26802&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#⁠action_26802 for related errors)

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

Fix Version: 2.5.3 [ 10461 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: Done successfully

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

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