Attention Requested: Important Hotfix Notification
The Progress OpenEdge team would like to bring your attention to a potential issue that you may encounter within the OpenEdge database. The issue will only manifest in certain scenarios and will likely impact a very small subset of our customers. However, if left undetected, it may eventually result in a production database fail. To ensure this does not happen for any customer, we have documented the issue and have provided recommended next steps. Please carefully review the following information. If you believe that you may be at risk, please take the appropriate corrective actions provided below.
Note: If you are not directly responsible for your production OpenEdge database, please forward the following information to your Database Administrator or someone with similar responsibility.What is the issue?For very large OpenEdge databases, it is possible that there can be undetected index corruption if the index grows larger than can be referenced by a 32-bit variable.
What symptoms will I experience if this issue occurs in my database?The index corruption will likely lead to one of the following errors:
- SYSTEM ERROR: Attempt to read block 0 which does not exist in area, database (210) (14648)
- SYSTEM ERROR: Index x (table-name,index-name): couldn't find key recid nnnnnnnnn (8783)
In addition, the Index Fix (idxfix) utility is not able to locate the index corruption An Index Rebuild (idxbuild) may temporarily correct the issue, but the index corruption is very likely to occur again.
Finally, After Image (AI) files and OpenEdge Replication can propagate any index corruption.
Will my production database experience this issue?You are vulnerable if the High-Water Mark (HWM) of the area containing the index is above 2 Gb. To determine your HWM, use prostrct statistics (prostrct statistics <dbname> on areas containing indexes. If the number of active blocks listed by the prostrct statistics for an index area is greater than (2^31 / [area records per block]), the area is susceptible to this issue.
If you are on OpenEdge 11.7, the Index Check (idxcheck) utility has been enhanced with a new option: 5 (Validate Tree) which can be used to validate the tree to quickly detect if this issue is present in your 11.7 database. Note: This option is not selected by default.
Once you upgrade to 11.7 you will not experience the issue again, however an idxbuild will need to be run in 11.7 or later for those indexes reported as having the problem.
For additional information on determining if you are vulnerable to this issue, please consult the information available 000075306, Defect: Database crashes with 8783 or 210 error due to index corruption. 
