Siebel Does Not COMMIT On SELECTs, Keeping Locks On Database
Last updated on MARCH 01, 2018
Applies to:Siebel Financial Services CRM - Version 16.15 [IP2016] and later
Information in this document applies to any platform.
Based on IBM DB2 LUW documentation a unit of work (UOW) is initiated when an application process starts, or when the previous UOW ends because of something other than the termination of the application process.
A unit of work ends with a commit operation, a rollback operation, or the end of an application process. Because the SIEBEL does not issue COMMIT many application handles have transactions keeping increasing in time from SIEBEL application.
This behavior of keeping transactions active for a very long time causes:
- DB2 Workload Management cannot be used with SIEBEL on certains areas, because transactions keep increasing in time (so not alert possible with WLM);
- Incapability to BIND or REBIND access plans (locks due to SIEBEL keeps causing contention on DB2 system catalog).
For this reason is not possible to do maintenance on DB2 server while the Siebel Application is online (without stop / start SIEBEL application).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms