Kbase P144938: Truncate area not deactivating all indexes
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/02/2010 |
|
Status: Verified
SYMPTOM(s):
Truncate area not deactivating all indexes
Truncated tables where indexes are also in the area, remain active
Truncated tables which only have 'default' indexes in the same area, are deactivated
Truncated tables where indexes are in another area, are deactivated
Indexes in an area that was truncated remained active for a table that wasn't truncated
Table was truncated and its non-truncated indexes remained active
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
CAUSE:
Bug# OE00183289
FIX:
Apply OpenEdge 10.1C04, 10.2A02 Service Packs or Upgrade to OpenEdge 10.2B where this issue has been fixed.
After running a proutil -C truncate area operation, use VST tables to pre-check the active/de-active status of related indexes. For example finding which PRIMARY indexes are active/de-active before (say) deleting the table after truncate area (the primary index needs to be active in order to delete a table).
OUTPUT TO "index_primes.file".
PUT UNFORMATTED "some" SKIP.
FOR EACH _file WHERE _file._file-number > 0 AND NOT _file-name BEGINS "SYS",
FIRST _index WHERE RECID(_index) = _file._prime-index NO-LOCK:
PUT UNFORMATTED _file-name SKIP _index-name SKIP.
END.