Last updated on FEBRUARY 27, 2017
Applies to:Oracle TopLink - Version 18.104.22.168 to 22.214.171.124.0 [Release 12c]
Information in this document applies to any platform.
This issue can occur when migrating from TopLink 10.1.3.x to EclipseLink 2.4.2/EclipseLink 2.5.2. An application has Named Queries of SQL type, all of them work fine in TopLink, but throw an exception with EclipseLink.
Example Query in the workbench, where Customer is a simple object with 5 attributes and no relationships:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms