A table.fetch CAS action that includes a WHERE clause might fail. This issue occurs when the action is run on an indexed table that contains missing values, which are also known as "not a number" (NaN) values.

In this scenario, the following symptoms occur:

• The CAS session in which the fetch action runs stops responding.
• No results or errors are returned to the client.
• The CAS server log prints exception and traceback messages similar to the following:

 

INFO  [00000007] 43912 example_user 18 [tkcasaimp.c:4504] - ++ action table.fetch / table={name='example_table', caslib='example_caslib', where='example_column >= 2061656517.341'},
from=1, to=1000, maxRows=1000, sasTypes=false, index=false;
FATAL [00000007] 43912 example_user 18 [cas.c:160] - Exception in action.
FATAL [00000007] 43912 example_user 18 [cas.c:162] - Domain exception
FATAL [00000007] 43912 example_user 18 [cas.c:191] - ENCRYPTED TRACEBACK BEGIN
<Encrypted traceback contents>
ENCRYPTED TRACEBACK END