Kbase P96632: Expected records are not available via the primary index
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
18/01/2005 |
|
Status: Unverified
SYMPTOM(s):
Expected records are not available via the primary index
All records were available using the primary index since the deployment of this new application
Those records that are not accessible via the primary index can be accessed using a non-unique index
An inactive primary unique index field was assigned a unique integer value for some records leaving the rest with an initial value of 0
CHANGE:
Ran proutil <dbname> -C idxbuild
CAUSE:
An application was deployed with an incomplete, inactivated, primary unique index that was activated unintentionally via the idxbuild. On activation, each time a record was encountered with an initial value of 0 for the unique field, after the first encounter; the record was treated as a duplicate and not indexed, thus not returned on a query using the primary index.
FIX:
This is expected behavior.
When reactivating the unique index by running idxbuild, the following error message displays each time it encounters a duplicate key:
Fix RECID <recid>, <file-name> already exists with <field value>. (1127)
When running idxfix and selecting #3, the following error message displays each time it encounters a duplicate key:
<file-name> already exists with <field/value...>. (132)
Complete the assignment of unique values to the unique index field and rebuild the index.