REMAKETABLE and indexing afterwards? (AREV Specific)
At 31 MAR 1998 12:09:53PM Michael Slack wrote:
Does a table need to have its indexes rebuilt after a REMAKETABLE has been run against it to change its Frame Size?
My limited understanding of the AREV 3.12 indexing is that the index for a row key points to a particular frame within the table. Since I used REMAKETABLE to change the frame size of a table, I assume the frame numbers that the rows reside in are also changed, that the previous index may be invalid after the process. Unless the REMAKETABLE process also updates the index as it goes.
Do I need to reuild the indexes on a table that I've changed the frame sizes on by using REMAKETABLE? Do I need to flush the indexes only? Or can I reliably leave the indexing alone because the process has already taken care of that part of it for me?
Thank You,
Michael Slack
At 31 MAR 1998 01:58PM Victor Engel wrote:
Actually, index records contain pointers to record keys, not frames, so you should be OK without reindexing.
At 02 APR 1998 11:20AM Aaron Kaplan wrote:
Indexing information, while stored in Linear Hash files, is not a part of the Linear Hash. When remaketable remakes the data file (and the dict file) it does not remake the indexing.
apk@sprezzatura.com
