IBM Support

PM64740: INCORRECT SQL GENERATED WHEN AN @VERSIONSTRATEGY OF ROWCHANGETIMESTAMPSTRATEGY IS USED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Incorrect SQL is generated when a user's JPA entity uses an
    @VersionStrategy of
    'com.ibm.websphere.persistence.RowChangeTimestampStrategy'.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of the Java Persistence API       *
    *                  (JPA) 2.0 feature of the IBM WebSphere      *
    *                  Application Server V7 Feature Pack for      *
    *                  OSGi Applications and Java Persistence API  *
    *                  2.0 who make use of an @VersionStrategy of  *
    *                  RowChangeTimestampStrategy.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect SQL generated when an         *
    *                      @VersionStrategy of                     *
    *                      RowChangeTimestampStrategy is used.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There exists a potential for incorrect SQL to be generated when
    a user's JPA entity uses an @VersionStrategy of
    'com.ibm.websphere.persistence.RowChangeTimestampStrategy'.
    For
    example, take the following JPA Entity definition:
    @Entity
    @VersionStrategy("com.ibm.websphere.persistence.
    RowChangeTimestampStrategy")
    public class ChildEntity implements Serializable {
    .....
    @Id
    int id;
    @Version
    private Timestamp lupdDatetime;
    .....
    The incorrectly SQL generating is missing the user's
    schema name.  For example, if the user specifies a schema name
    via the "openjpa.jdbc.Schema" property of say 'mySchema'.  In
    this case, SQL generated for CRUD operations on the field
    'lupdDatetime' will not contain the schema name of 'mySchema'.
    

Problem conclusion

  • With this fix, code has been added to ensure that the proper
    SQL is generated when an entity uses
    'com.ibm.websphere.persistence.RowChangeTimestampStrategy' as
    a VersionStrategy.
    
    The fix for this APAR is currently targeted for inclusion
    in Fix Pack 1.0.0.9 for the Feature Pack for OSGi Applications
    and Java Persistence API 2.0.
    
    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

    PM64740

  • Reported component name

    JPA OSGI FEATUR

  • Reported component ID

    5724J0857

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-15

  • Closed date

    2012-06-05

  • Last modified date

    2012-06-05

  • APAR is sysrouted FROM one or more of the following:

    PM59544

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    JPA OSGI FEATUR

  • Fixed component ID

    5724J0857

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 September 2020