|
|
|
A very rarely encountered problem involving index pruning could lead to a corrupted index following a database automatic recovery:
Error 14 at open. CTSTATUS.FCS has messages:
User# 00002 ERROR: Invalid node links
Tue Oct 30 02:13:55 2018
User# 00002 MyFile.idx [1]: 527
The requirements to see this issue are an index created with the performance optimization LOGIDX (which speeds up automatic recovery and is on by default starting in V10.3 and later) and the index must have at least 3 levels or more in the index tree, and requires deleting all of the key values in an index node, and its parent node. Then if the c-tree Server process is improperly closed, and automatic recovery occurs, this issue might occur.
The logic has been modified to correct this.
