IBM Support

PM80016: 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 IBM WebSphere Application      *
    *                  Server V6.1.0 Feature Pack for Enterprise   *
    *                  JavaBeans 3.0 who make use of an            *
    *                  @VersionStrategy of                         *
    *                  RowChangeTimestampStrategy.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect SQL is generated when an      *
    *                      @VersionStrategy of                     *
    *                      RowChangeTimestampStrategy is used.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There exists the potential for incorrect SQL to be generated
    when your 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 your schema name.
    For example, if you specify 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 Enterprise JavaBeans 3.0 Feature Pack Fix Pack 47
    (6.1.0.47) of WebSphere Application Server version
    6.1.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

    PM80016

  • Reported component name

    WAS EJB3 FEATUR

  • Reported component ID

    5724J0851

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-04

  • Closed date

    2013-01-08

  • Last modified date

    2013-01-08

  • 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

    WAS EJB3 FEATUR

  • Fixed component ID

    5724J0851

Applicable component levels

  • R610 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022