Код: Выделить всё
gbak: ERROR: unsuccessful metadata update
gbak: ERROR: key size exceeds implementation restriction for index "REESTRS_
IDX2"
gbak: Exiting before completion due to errorsAbstract: This error indicates that the key size for the specified index is larger than the maximum (255) value allowed.
Problem:
When restoring a database gbak reports the error:
gbak: creating indexes
gbak: ERROR: unsuccessful metadata update
gbak: ERROR: key size exceeds implementation restriction for index "TABLE1_INDEX"
gbak: Exiting before completion due to errors
Solution:
The information in this article applies to:
* InterBase all versions
InterBase indexes have a limitation that the maximum key size be 255 bytes.
This error indicates that the key size for the specified index is larger than the
maximum value allowed.
One way to get into this situation is with updates to the system tables. If the column
length is expanded due to directly updating the system tables, this error could arise
on restore.
When the index was created the key size was under the maximum allowed
size. When the system tables were updated and the column length expanded
the new key size was larger than the maximum size allowed.
The workaround is to identify the problem index and:
1) delete the index if updated column length(s) are required
2) reduce column length(s) so that the key size is under the maximum
************
Example
************
This is an example of how to get into this situation.
1) create a table with a varchar(40) column
2) create an index on the varchar column
3) Update the system tables and change the length of the varchar
field to 300.
4) Backup the database
5) Restore the database
Gbak will report the error "key size exceeds implementation restriction ..." on the restore.
This error can be resolved in one of two ways:
1) delete the index on the varchar column
2) reduce the size of the varchar column so that the key size is below the
maximum size allowed.