Subject | Cannot restore |
---|---|
Author | Tomas Krejzek |
Post date | 2011-06-20T08:44:16Z |
Hello, I have problem with one database.
It ODS is 11.1, but we are using it on FB2.5 32bit, everything is on Windows (XP or 7).
It work's well.
But when we tried to backup and restore it we have a problem.
If I do the backup using FB2.1 gbak a then try to restore, it raises an error -
Invalid BLR at offset 350 - BLR syntax error : expected valid BLR code at offset 350,
encountered 190.
And database is looking valid, but there are no triggers, views nor procedures.
But in restore log there are notes that gbak creates them - the error raises as the last
message just before commiting and going home (there is message Commiting Metadata).
If I backup the database using FB2.5 gbak and restore it on the current server it is
restored well.
But when I try to downgrade it back to FB2.1 it failed.
I create backup using FB2.1 gbak. It is ok.
But during restroe it raises an error - action cancelled by trigger (3) to preserve data
integrity table/procedure han non-SQL security class defined.
The database stays shutdown and after brink online it looks similar to previous one.
It doesn't depend on server version (FB2.1 32bit or FB2.1 64bit)
It ODS is 11.1, but we are using it on FB2.5 32bit, everything is on Windows (XP or 7).
It work's well.
But when we tried to backup and restore it we have a problem.
If I do the backup using FB2.1 gbak a then try to restore, it raises an error -
Invalid BLR at offset 350 - BLR syntax error : expected valid BLR code at offset 350,
encountered 190.
And database is looking valid, but there are no triggers, views nor procedures.
But in restore log there are notes that gbak creates them - the error raises as the last
message just before commiting and going home (there is message Commiting Metadata).
If I backup the database using FB2.5 gbak and restore it on the current server it is
restored well.
But when I try to downgrade it back to FB2.1 it failed.
I create backup using FB2.1 gbak. It is ok.
But during restroe it raises an error - action cancelled by trigger (3) to preserve data
integrity table/procedure han non-SQL security class defined.
The database stays shutdown and after brink online it looks similar to previous one.
It doesn't depend on server version (FB2.1 32bit or FB2.1 64bit)