Index becomes active after interrupting an IDXACTIVATE session

IDXACTIVATE session is interrupted during the key build phase of index activate leaves the index marked as active.
After an IDXACTIVATE session is interrupted, the _storageobject._object-attrb is changed to active even though the process was aborted before completion.
The _StorageObject._Object-attrib is changed from 17 to 1 (in case of a new unique index) or from 16 to 0 (in case of a new non-unique index).

The log file contains messages confirming that the index has been activated when the keys have not finished being built.

Example after interrupting activating the CustNum inactive index against a sports2000 sample database:

IDXACTIV5: (14636) Enabling table locks.
IDXACTIV5: (-----) upIndexBuildTarget index 8 (CustNum) find next returned -1218
Index Activate: Index Name  No. 15  - 1217 keys added. (13244)
Index Activate: Index Name  No. 15  - 1217 keys processed. (13245)
Index Activate: Index Name has been activated.
IDXACTIV5: (453)  Logout by Index Activate on CON:.

Upgrade to OpenEdge 10.2B08, 11.2.1.0 , 11.3.0 or later where the status(s) for CTL+C and Quit, when issued during key build portion of index activate, are handled properly leaving the index inactive.
 

ONLINE: De-activate the index again through the Data Dictionary then re-run IDXACTIVATE to completion.

OFFLINE: De-activate the index again through the Data Dictionary the run IDXBUILD.
 

Progress Article: 

IDXACTIVATE / IDXFIX leave index admin locks after being interupted