My Oracle Support Banner

E-DB2: Change Assistant and AutoCommit (Doc ID 2532932.1)

Last updated on APRIL 19, 2019

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.53 and later
Information in this document applies to any platform.

Goal

 During an Upgrade, a customer site using Db2 sees that when using Peoplesoft Change Assistant to run upgrade scripts, it appears to be auto-commiting after each sql statement even though there is not a commit in the script.

The Db2cmd.exe (command line processor) runs in auto-commit mode,  by default. This means that a commit is executed for every statement in the script. If the script itself contains commits, we then commit every statement twice.This generates excessive overhead in the DB2 subsystem when executing large alter scripts such as during an Application upgrade.

Questions:

1. If auto commit is the default behaviour of Change Assistant in executing upgrade scripts on all database platforms or

2. Auto commit behaviour of Change Assistant is due to the fact that db2cmd.exe (command line processor) runs in auto-commit mode by default because customer is using Db2.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.