Client crashes when doing FOR EACH query with I/O in readfrmb 290 error

ABL Client running a FOR EACH query fails with error 290 in readfrmb.
ABL client crashes with 290 error which is always on a srt client-temp sort file

The error is related to the volume of data being processed at the time:

• If there are very few records returned by the query then the client does not crash.
• With more data returned by the query, the client crashes.

Stack trace from _progres on AIX reads:

Same Query works fine in OpenEdge version 10.

If client is connecting via TCP, the 290 error appears in database logfile for a SRV process instead.
The remote server may crash as a consequence

There are no index corruption reported by IDXCHECK or IDXFIX scans

This is a product defect that results in an incorrect entry size of a b-tree note.

Upgrade to OpenEdge 11.5.1, 11.6.0 or later.   Where intermediate nodes are split like a root block rather than the leaf block.

When connecting to the database over a network, the fixed version needs to be installed on both client and server machines.

 

Setting -TB to 16 (or 32) in the client-connection parameters has been shown to alleviate the issue.

Identify the query and if possible optimize the result set to only return the necessary information using the most efficient index bracketing.

Due to the nature of this defect, it can manifest with different sets of symptoms.
In other confirmed cases, it triggers an error: (2733)  SYSTEM ERROR: Bad query request 

Progress Article:

 Client fails with error 2733 when running a FOR EACH query with an OR operator