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.
[{"Product":{"code":"SSMLQ4","label":"IBM InfoSphere Optim Test Data Management Solution"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.1;8.1;11.3.0","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
08 July 2021
UID
swg21693718