Subject | troubles after restore |
---|---|
Author | Walter Neumann |
Post date | 2003-09-08T19:10:54Z |
Hallo all,
restoring the database I received the error not enough memory for sort. So I
switched off the indices and succeeded. Only one index I can not activate
with the same error. The field of this index is varchar(50) and the table has
about 9.000 rows. It's only a normal index for optimize search time.
PC: P III/600 256 MB RAM, SuSE Linux 8.2, Firebird 1.0 SS
1. Which memory is used for sorting and building the index. Is it the tmp
directory, specified in isc config?
2. The main table in the DB has a PK, which is referenced in many tables.
After the restore I can't delete any row in this table. Error message:
"internal gds software consistency check (partner index description not found
(175))". There don't exist an index with the name 'partner'. It exists a
field with this name, which has a foreigen key to the main table. I deleted
this foreigen key and rebuilded it. But it's always the same error. It
depends not to the key, which I couldn't activate! Is there a system table
corrupt?
Many thanks to your advices.
Walter Neumann
restoring the database I received the error not enough memory for sort. So I
switched off the indices and succeeded. Only one index I can not activate
with the same error. The field of this index is varchar(50) and the table has
about 9.000 rows. It's only a normal index for optimize search time.
PC: P III/600 256 MB RAM, SuSE Linux 8.2, Firebird 1.0 SS
1. Which memory is used for sorting and building the index. Is it the tmp
directory, specified in isc config?
2. The main table in the DB has a PK, which is referenced in many tables.
After the restore I can't delete any row in this table. Error message:
"internal gds software consistency check (partner index description not found
(175))". There don't exist an index with the name 'partner'. It exists a
field with this name, which has a foreigen key to the main table. I deleted
this foreigen key and rebuilded it. But it's always the same error. It
depends not to the key, which I couldn't activate! Is there a system table
corrupt?
Many thanks to your advices.
Walter Neumann