Subject | Re: [IBO] Re: Object in use when dropping table (255 something limit) |
---|---|
Author | Russell Belding |
Post date | 2001-07-25T10:26:02Z |
I found the following in the IBPhoenix Knowledge base:
KnowledgeBase Id: 98
Question:
Performing too many ALTER statements may generate
error -607 "Unsuccessful metadata update
-TABLE -too many versions".
Answer:
InterBase only allows up to a maximum of 255 versions of each record in the
system tables. Exceeding the limit produces the error shown above. The 255
record version maximum for a record in a system table is not always reached
because system tables experience garbage collection in the same manner as
user
tables. Look up the index topic of "Garbage collection" in the online
InterBase help for the specifics on how garbage collection is done.
The solution:
- Perform a backup and restore of the database.
**********END
I cannot immediately see how this would affect the creation and deletion of
tables.
What would happen for example if one created and dropped tables T1, T2, T3,
...?
Russell Belding
KnowledgeBase Id: 98
Question:
Performing too many ALTER statements may generate
error -607 "Unsuccessful metadata update
-TABLE -too many versions".
Answer:
InterBase only allows up to a maximum of 255 versions of each record in the
system tables. Exceeding the limit produces the error shown above. The 255
record version maximum for a record in a system table is not always reached
because system tables experience garbage collection in the same manner as
user
tables. Look up the index topic of "Garbage collection" in the online
InterBase help for the specifics on how garbage collection is done.
The solution:
- Perform a backup and restore of the database.
**********END
I cannot immediately see how this would affect the creation and deletion of
tables.
What would happen for example if one created and dropped tables T1, T2, T3,
...?
Russell Belding