Kbase P818: How to stop compiler selecting inactive indexes?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/12/2008 |
|
Status: Unverified
GOAL:
How to stop compiler selecting inactive indexes?
GOAL:
How to prevent error 995 when database contains inactive indexes?
FACT(s) (Environment):
Progress 8.1C
Progress 8.2x
Progress 8.3x
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
Use No Inactive Indexes (-noinactiveidx) to exclude inactive indexes from the compilation of WHERE clauses, as well as LIKE clauses in DEFINE TEMP-TABLE statements.
The client startup parameter -noinactiveidx was added (Progress 8.1C and later) to prevent the compiler from selecting inactive indexes, allowing the developer greater flexibility when deciding which indexes should be used. When a client session is started with this parameter, the compiler is forced to select only active indexes when compiling source code. This does away with the need to delete an index from the database when trying to control which indexes are selected by the Compiler.