Kbase P105347: Area with indexes truncated, data of corresponding table(s) remain within another area
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
GOAL:
What happens if area with indexes is truncated while data of corresponding table(s) remain within another area?
GOAL:
A consequence of "truncate area" with indexes deleted
FIX:
When an area with indexes is truncated, using "proutil <db> -C truncate area <area-name>", then the indexes are not de-activated.
This will cause problem if the table for the corresponding indexes was not in the same area, or if the area where the table resides is not truncated.
No data is seen after having "truncated" the index, it is NEEDED to rebuild the indexes.