Fixes are available
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
APAR status
Closed as program error.
Error description
OpenJPA Criteria API and canonical metamodel result in SQL Exceptions when using WebSphere version 8.0: ORA-00918 column ambiguously defined ORA-00936 missing expression - WHERE clause for the primary key attribute is not included in the statement The generated source code for canonical metamodel classes mirrored the same inheritance hierarchy of the domain classes. The problem is also reported in OPENJPA-2305 Canonical MetaModel class generation should not use inhertence https://issues.apache.org/jira/browse/OPENJPA-2305
Local fix
na
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile who make use of * * JPA generated MetaModel. * **************************************************************** * PROBLEM DESCRIPTION: JPA Canonical MetaModel class * * generation should not use inheritance. * **************************************************************** * RECOMMENDATION: * **************************************************************** The generated source code for canonical metamodel classes mirrored the same inheritance hierarchy of the domain classes. This strategy exposed an error that resulted in wrong target SQL query under the following domain model: a) A @MappedSuperClass M defined a primary key field x b) The primary key field x is an @EmbeddedId E c) An @Entity class D derived from M and navigated to the fields of E via x
Problem conclusion
With this fix, code has been added to OpenJPA to make certain the correct MetaModel is generated when inheritance is used in a domain model. The fix for this APAR is currently targeted for inclusion in Service Levels (Fix Packs) 8.5.5.1. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM93337
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-07-18
Closed date
2013-09-12
Last modified date
2013-09-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
LIBERTY PROFILE
Fixed component ID
5724J0814
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
11 January 2022