gbak

Not registered There were issues with restoring if indexes used in explicit plans inside PSQL code had been dropped.

fixed by A. dos Santos Fernandes

~ ~ ~

Not registered gbak could not restore a database containing broken foreign keys. Now, the restore continues to run, the user gets a diagnostic indicating which FK caused the problem. The affected index becomes inactive and, after restore, the database is left in shutdown state.

fixed by A. Peshkov

~ ~ ~

Not registered gbak would stall when used via the Services Manager and an invalid command line was passed.

fixed by V. Horsun

~ ~ ~

Not registered A computed column of a blob or array type would zero values in the first column of the table being restored.

fixed by D. Yemanov

~ ~ ~

Not registered Fixed some backup issues with stream BLOBs that caused them to be truncated under some conditions.

fixed by N. Samofatov

~ ~ ~

Not registered Interdependent views caused problems during the restore process.

fixed by A. Brinkman

~ ~ ~

SF #750659 If you want to start a fresh db, you should be able to restore a backup done with the metadata-only option. Generator values were resisting metadata-only backup and retaining latest values from the live database, instead of resetting the generators to zero.

fixed by C. Valderrama, D. Yemanov

~ ~ ~

SF #908319 In v.1.5, wrong error messages would appear when using gbak with service_mgr.

fixed by V. Horsun

~ ~ ~

SF #1122344 gbak -kill option would drop an existing shadow.

fixed by D. Yemanov

~ ~ ~

Not registered gbak was adding garbage bytes to the SPB when called in the -se[rvice_mgr] mode.

fixed by A. dos Santos Fernandes, C. Valderrama, V. Horsun

~ ~ ~