Kbase P146042: When truncating an area with indexes in it, indexes are NOT marked as inactive when the associated t
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/06/2009 |
|
Status: Unverified
SYMPTOM(s):
When truncating an area with indexes in it, indexes are NOT marked as inactive when the associated table is not in the same area
When the associated table is dropped, database corruption results
Record <recid> in block <number> has table <number> which doesn't exist. (5433)
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
OpenEdge Category: Database
CAUSE:
Active indexes point to data that doesn't exist
CAUSE:
Bug# OE00183289
FIX:
Apply OpenEdge 10.1C04, 10.2A02 Service Packs or Upgrade to OpenEdge 10.2B where this issue has been fixed.
WORKAROUND#1:
Truncate the Storage Area of the deleted table.
WORKAROUND#2:
Revert to backup.
The following documents the correct behaviour:
If an index is truncated as part of an area truncate
1) If its associated table data resides in the same area the index can remain active, since there are no invalid data the active indexes are pointing to (similar to when a table is first created with active indexes).
2) if its associated table resides in a different area than the one being truncated, the index must be marked inactive
If a table is truncated as part of an area truncation
1) All indexes in the same area (which are also truncated) can remain active
2) All indexes in other areas associated with tables in the truncated area must be marked inactive