Kbase P185479: Performance concerns regarding high CPU utilization on an OS400/DB2 machine when specific ODBC jobs
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/04/2011 |
|
Status: Unverified
SYMPTOM(s):
Performance concerns regarding high CPU utilization on an OS400/DB2 machine when specific ODBC jobs are running.
Packages on AS400/DB2 side which are known as a SQL Query Plan from the AS400/DB2 standpoint seem to be causing high CPU utilization.
The packages are created by the Data Direct ODBC when test connect is done to test the DSN connection
The third party upgrade of the database and its application was unsuccessful but the database upgrade included more tables and fields and changes in logicals.
The schema holder was rebuilt to synchronize the changes on the DB2/400 database
FACT(s) (Environment):
Windows
AS/400 iSeries Server
ODBC DataServer
OpenEdge 10.x
CHANGE:
The third party upgrade of the database and its application was unsuccessful but the database upgrade included more tables and fields on the existing table and existing logicals.
CAUSE:
DB2/400 database schema changes caused the existing packages to run using the old query plan, cursor as well as access path which caused the high cpu time
FIX:
The recommendation is to remove the packages and sections associated with the Data Direct driver.
After the deletion of the old packages, you need to use the DSN on the windows to do the test connect to make sure you can connect again as well as click on the "Modify Bindings" on the "Modify Bindings" tab of the ODBC DSN properties. Failing to do the above steps will yield the following error:
s100: [Data Direct][ODBC DB2 Wire Protocol driver] [UDB DB2 for iSeries and AS/400] Program name NULLID.DDOU510B not found in plan. Please bind the required packages through the DB2 driver setup screen.
If you want to learn more about data Direct Driver related DB2/400 packages read the URL link on the References on note section below.