Troubleshooting
Problem
If you define a variable on a timestamp column in an Access Definition, and give it a default value, you may receive the error message 'Wrong lexical token at position nn' when trying to save the Access Definition.
Symptom
An example of the symptom would be an error message in the SQL tab of Table Specifications, after setting a timestamp column equal to a variable in the WHERE clause: An invalid SQL Select statement has been specified for SOR112U.FREDD.OPTIM_ORDERS. Wrong lexical token at position 24.
Log InLog in to view more of this document
Was this topic helpful?
Document Information
More support for:
IBM InfoSphere Optim Test Data Management Solution
Software version:
9.1, 8.1, 11.3.0
Operating system(s):
AIX, HP-UX, Linux, Solaris, Windows
Document number:
523119
Modified date:
08 July 2021
UID
swg21693718