You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gbak in service mode now fails to overwrite a database. The problem is specific to current FB2.5.3 snapshot builds, previous release version (2.5.2) is ok:
gbak: ERROR:could not drop database C:\test.fdb (database might be in use)
gbak: ERROR: Exiting before completion due to errors
Nevertheless, the replaced database file is removed by previous gbak call, so the next call of the same gbak command is successfull (since the file to overwrite is now missing). Once the database file exists, however, gbak fails again.
To be sure that the file is really not in use, I even tried to stop the server before the gbak call, but it didn't help.
Submitted by: michalk1 (michalk1)
Gbak in service mode now fails to overwrite a database. The problem is specific to current FB2.5.3 snapshot builds, previous release version (2.5.2) is ok:
gbak -REP -USER sysdba -PASSWORD masterkey -SERVICE localhost:service_mgr C:\test.gbk C:\test.fdb
gbak: ERROR:could not drop database C:\test.fdb (database might be in use)
gbak: ERROR: Exiting before completion due to errors
Nevertheless, the replaced database file is removed by previous gbak call, so the next call of the same gbak command is successfull (since the file to overwrite is now missing). Once the database file exists, however, gbak fails again.
To be sure that the file is really not in use, I even tried to stop the server before the gbak call, but it didn't help.
The same problem can be demonstrated by fbsvcmgr:
fbsvcmgr localhost:service_mgr -user sysdba -password masterkey action_restore verbose res_replace -dbname C:\test.fdb -bkp_file C:\test.gbk
gbak:opened file C:\test.gbk
could not drop database C:\test.fdb (database might be in use)
-Exiting before completion due to errors
Commits: fa00f70 FirebirdSQL/fbt-repository@219f587
The text was updated successfully, but these errors were encountered: