Kbase P83797: Is an index rebuild required after changing the database code page ?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/06/2004 |
|
Status: Unverified
GOAL:
Is an index rebuild required after changing the database code page ?
FIX:
An index rebuild for all indexes (though it only affects character indexes, doing all won't hurt) is needed only if the database collation is changed or required to be changed. So when doing database code page conversion through "proutil -C convchar convert", the following cases will require a collation change:
1. An error of "The current collation table is not compatible with the database
code page. (2899)" is displayed after "proutil -C convchar convert". This
normally happens when converting between non-compatible code pages through
"UNDEFINED" as a bridge (e.g. ISO8859-1 and ISO8859-8(Hebrew), GB2312 and
SHIFT-JIS).
2. The target code page is UTF-8.
3. You want to switch the current collation with either a different named
one if there is any or a self-defined one.