We have an app wich I send gbak and gfix with it to do backup's in any workstation. There are some customers who still are using FB 2.0. After we upgraded gbak and gfix files to version 2.5.2.26539, we still can make backup connecting on FB 2.0 servers. But when we try to restore this same backup file, to the same FB 2.0 server the following error is happening at the end of the process:
gbak: committing metadata
gbak: ERROR:Dynamic SQL Error
gbak: ERROR: SQL error code = -104
gbak: ERROR: Token unknown - line 1, column 247
gbak: ERROR: SIMILAR
gbak:Exiting before completion due to errors
This error doesn't happen with gbak 2.5.1.
The text was updated successfully, but these errors were encountered:
I believe Alex intention was to hide this error in 2.0 / 2.1:
"Use correct way to detect digital strings. In 2.1 with missing SIMILAR TO had to ignore errors when fixing generators." -- CORE3733
Submitted by: Honório Morais (honoriojpm)
Votes: 1
We have an app wich I send gbak and gfix with it to do backup's in any workstation. There are some customers who still are using FB 2.0. After we upgraded gbak and gfix files to version 2.5.2.26539, we still can make backup connecting on FB 2.0 servers. But when we try to restore this same backup file, to the same FB 2.0 server the following error is happening at the end of the process:
gbak: committing metadata
gbak: ERROR:Dynamic SQL Error
gbak: ERROR: SQL error code = -104
gbak: ERROR: Token unknown - line 1, column 247
gbak: ERROR: SIMILAR
gbak:Exiting before completion due to errors
This error doesn't happen with gbak 2.5.1.
The text was updated successfully, but these errors were encountered: