Kbase P98319: proutil -C idxfix with options 3 scans the whole database even if the RECID range was specified
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
SYMPTOM(s):
proutil -C idxfix with Options 3 seems to scan the whole database even if the RECID range was specified.
CAUSE:
This is expected behavior.
Option 3 is the combination of Options 1 and Options 2.
Option 1 scans records, ensuring that the records are correctly indexed. For this option, you have the possibility to specify a RECID range, which is the same feature that is activated if you specify a RECID option in Option 3.
Option 2 scans indexes, looking for orphaned index entries. For this option, you cannot specify a RECID range and the whole index will be scanned. The same holds true when you use Option 3: the whole index will be scanned.
Because Option 2 will scan the whole indexes anyway and so will Option 3, it may take some time before Option 3 completes even if you specified a [small] RECID range.
FIX:
Given that this is expected behavior, the only options in case you are already running the command, are to either wait for completion, or to stop idxfix.
Incidentally, stopping idxfix has no adverse consequences with regard to database physical integrity, as the changes made by idxfix are logged in the before image, and normal crash recovery takes place in case idxfix is terminated right in the middle of an index change.