IBM Support

JR52031: Tools using the WebSphere Commerce dataload utility on Oracle 12 c may encounter SQLException

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Tools using the dataload utility inside the WebSphere Commerce
    EAR application, e.g. Store Publish, on Oracle 12c may encounter
     a SQLException related to auto-commit, with the message: "Could
     not commit with auto-commit set on".
    
    This occurs because the connection object used by the dataload
    utility to manage retrieval of new primary keys does not set the
     auto-commit property to false.
    
    The Oracle 12c JDBC driver throws a SQLException when a commit
    is invoked on a connection with auto-commit enabled, as
    documented in the JDBC specification.
    

Local fix

  • Since the dataload utility is used in both the EAR application
    and as a stand-alone application, the following workarounds are
    available.
    
    1) For the EAR application:
    Add oracle.jdbc.autoCommitSpecCompliant=false as a custom system
     property under:
    "Application servers > server1 > Process definition > Java
    Virtual Machine > Custom properties"
    
    Expand "Java and Process Management" under "Server
    Infrastructure" heading to locate "Process definition"
    
    2) For the stand-alone utility:
    In the file ${WC}/xml/config/alldbconnector.xml, under the
    <oracle> element, add this:
    <property name="oracle.jdbc.autoCommitSpecCompliant"
    value="false" />
    

Problem summary

  • USERS AFFECTED:
    WebSphere Commerce users on v7.0 who use Oracle 12c as the
    backend database may see failures (SQLException) from invocation
     of tools (e.g. Store Publish) that use dataload utility in the
    EAR application.
    
    PROBLEM ABSTRACT:
    Tools using the WebSphere Commerce dataload utility on Oracle
    12c may encounter SQLException
    
    BUSINESS IMPACT:
    Invocation of tools (e.g. Store Publish) that use the dataload
    utility inside the EAR application may lead to failures on
    Oracle 12c databases
    
    RECOMMENDATION:
    

Problem conclusion

  • This iFix resolves the issue by correcting the behavior of the
    dataload utility on the connection used to manage primary key
    retrieval by setting its auto-commit property to false.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR52031

  • Reported component name

    WC BUS EDITION

  • Reported component ID

    5724I3800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-12-11

  • Closed date

    2015-01-26

  • Last modified date

    2015-01-26

  • 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

    WC BUS EDITION

  • Fixed component ID

    5724I3800

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYSYL","label":"WebSphere Commerce Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB31","label":"WCE Watson Marketing and Commerce"}}]

Document Information

Modified date:
12 December 2021