IBM Support

PI16847: SCHEMA SETTING IN THE ORM FILE DOESN'T PROPAGATE TO THE GENERATED SEQUENCES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • With openJPA 2.0, if defininig a schema name in
    persistence-unit-defaults attribute in the orm.xml file, the
    generated sequence doesn't have the default schema name as
    specified.
    

Local fix

  • Add the followign property to set a schema:
    
    <property name="openjpa.jdbc.Schema" value="xxxx"/>
    
    Or set it as a JVM property would help workaround the issue.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0.0, V8.5.0 and V8.5.5 who        *
    *                  define a persistence unit default           *
    *                  (<persistence-unit-defaults>) schema        *
    *                  in an orm.xml file.                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: A default Schema defined in a           *
    *                      persistence unit default in an          *
    *                      orm.xml file is not being honored.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Take the following entry in a JPA orm.xml file:
    <persistence-unit-metadata>
    <persistence-unit-defaults>
    <schema>schemaInPUDefaults</schema>
    </persistence-unit-defaults>
    </persistence-unit-metadata>
    Assuming this is the only schema defined in the entire app,
    then this schema should be used by default (the JPA
    specification clearly defines how the defaults in
    <persistence-unit-defaults> should be used by a provider).
    However, this schema is not used by OpenJPA.
    

Problem conclusion

  • With this fix, code has been added to OpenJPA to properly
    handle a default schema defined in the persistence unit
    default settings or an orm.xml.
    
    The fix for this APAR is currently targeted for
    inclusion in Service Levels (Fix Packs) 8.0.0.10 and 8.5.5.5
    of WebSphere Application Server versions 8.0.0 and 8.5.5.
    
    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

    PI16847

  • Reported component name

    WEBS APP SER DE

  • Reported component ID

    5724H8900

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-27

  • Closed date

    2014-09-25

  • Last modified date

    2014-09-25

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

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

Document Information

Modified date:
28 April 2022