Fixes are available
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
In order to correctly determine whether a table name is too long for a given dictionary the OpenJPA schema tools rely on a configuration attribute on their DBDictionary class. This attribute is typically set in the user's persistence.xml file. The Rational Application Developer tooling uses OpenJPA's schema tools to generate DDLin two ways. If a database connection is available, all is good - the user's persistence.xml file will be used. If no database connection is available, Rational Application Developer uses the DBDictionary command line arg to indicate the database type. This overrides the user's setting from persistence.xml and the table length is not calculated correctly.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of Java Persistence API (JPA) * * schema generation tools included with IBM * * WebSphere Application Server V8.0 * **************************************************************** * PROBLEM DESCRIPTION: The JPA schema generation tools * * calculates the length of a table name * * incorrectly. * **************************************************************** * RECOMMENDATION: * **************************************************************** The OpenJPA schema tool may be used to create or modify tables for a set of entities. When it processes an entity which has specified a schema name it, incorrectly, includes the schema name when calculating the table name length. If this length exceeds the limit for a given database, an exception will be thrown by the tool.
Problem conclusion
The OpenJPA schema tool has been updated and will no longer include the schema name when calculating the length of a table name. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.2. 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
PM45439
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-08-10
Closed date
2011-09-29
Last modified date
2011-09-29
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
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
27 October 2021