About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Troubleshooting
Problem
Oracle SQL DELETE and SQL INSERT Statements do not auto commit (patch issue)
Symptom
Automatic commit on database transactions is disabled for custom pools with a type=remote and transaction=true, causing latency in commit of database transactions (waits on commit) in business processes. Issue introduced in patch 4316 and patch 4217.
Possible symptoms:
(1) Lightweight JDBC adapter LWJDBC when using an Oracle custom pool and pool.type is set to remote may have noticeably longer commit times for insert and delete after applying patch.
(2) Unable to purge a table on Oracle 10GR2 SGBD, when using custom pool and pool.type is set to remote.
When we execute
the request on Oracle directly, no problem. When the request is done on GIS,
the result is OK, but nothing is removed on Oracle (the data are not purged,
but the DB is locked).
After investigation, the request is executed, but
not committed.
No error messages given until the connection between GIS and Oracle is broken where you will then see the rollback begin in Oracle.
[{"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Data management - Purge","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.0;4.3;4.2","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
To view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use the link to actual document below to access the full document. You will be asked to log on if you are not already logged in. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Historical Number
NFX5565
Was this topic helpful?
Document Information
Modified date:
25 February 2019
UID
swg21559525
Manage My Notification Subscriptions