Kbase P117035: How to perform an IDXFIX which requires no locks within a database.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/16/2009 |
|
Status: Verified
GOAL:
How to perform an IDXFIX which requires no locks within a database.
GOAL:
What is the -NL option of IDXFIX
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
FIX:
A new feature was added to IDXFIX in 10.1A01 and 10.0B05 to prevent IDXFIX from impacting a production environment (potentially issuing certain types of locks against records or indices as it checks the record or index consistency).
The expectation is that by utilizing the -NL startup option the IDXFIX operation can proceed with less impact to the production performance of the database.
Since changes are occurring while the IDXFIX is running and IDXFIX with the -NL option is effectively using the equivalent to "read uncommited" it may perceive false positives during its scanning of the records/indices.
The outputs of option 1 for IDXFIX has been improved to facilitate scripted parsing of the output so that checking of any potential index problems can be made easier.
For that reason it is recommended that only option 1 be used at this time with the -NL startup option.
Syntax of command with new parameter:
proutil <dbname> -C idxfix -NL
Syntax of command with new parameter using tee to capture output:
proutil <dbname> -C idxfix -NL | tee idxfix.out
Any option of IDXFIX which would require a lock (any fix operation) will be rejected typically with the following message:
This option not allowed when running with -NL.