Subject | Re: [firebird-support] Restore Database Errors |
---|---|
Author | Mark Rotteveel |
Post date | 2013-02-17T12:11:10Z |
On 16-2-2013 20:57, Craig Cox wrote:
http://tech.groups.yahoo.com/group/firebird-support/message/85457:
"The problem is caused by some RDB$RELATION_FIELDS records that have
RDB$COLLATION_ID = -1. I have no idea what engine version or GUI tool
could generate it. It wasn't a problem previously, but text blobs
support collations in v2.0 and an attempt to find a collation with ID =
255 (-1) fails in your database. The issue should go away after setting
RDB$COLLATION_ID to zero for all records containing a value of -1 there."
and try again.
Mark
--
Mark Rotteveel
> Firebird 1.5 Database on LinuxSee this message:
>
> I have a database that appears to be running fine; however, when I try to restore a backup from FB 1.5 (Linux) to FB 2.5 (Windows), none of the tables show up in the restored database. I have completed similar restores with other databases. The first error message occurs when it tries to restore the first table. That error is:
>
> gbak:committing metadata for table ORDERS
> gbak:error committing metadata for table ORDERS
> gbak: ERROR:unsuccessful metadata update
> gbak: ERROR: ORDERS
> gbak: ERROR: Implementation of text subtype 65280 not located.
http://tech.groups.yahoo.com/group/firebird-support/message/85457:
"The problem is caused by some RDB$RELATION_FIELDS records that have
RDB$COLLATION_ID = -1. I have no idea what engine version or GUI tool
could generate it. It wasn't a problem previously, but text blobs
support collations in v2.0 and an attempt to find a collation with ID =
255 (-1) fails in your database. The issue should go away after setting
RDB$COLLATION_ID to zero for all records containing a value of -1 there."
> After that the errors associated with remaining tables all look like:Might be a result of the first error. Try the proposed fix (on a copy!)
>
> gbak:committing metadata for table PARTS
> gbak:error committing metadata for table PARTS
> gbak: ERROR:unsuccessful metadata update
> gbak: ERROR: TABLE PARTS
> gbak: ERROR: Can't have relation with only computed fields or constraints
>
> This leads to a cascading set of errors concerning indexes etc.
and try again.
Mark
--
Mark Rotteveel