UD - Moose
UD Employe posted June 25, 2002 02:42
Well some good news.
It appears that IBM in its infinite wisdom changed the way DB2 on AIX commits data within stored procedures. Sometime between Fixpack 4 and Fixpack 6 IBM decided that a close cursor no longer performed a commit. As some history you couldn\'t even perform a commit in a stored procedure until Fixpack3 so we had stored procedures that only closed a cursor and not perform a commit. This change caused locks to be held for an entire lock timeout period. This reduced our ability to serve as many clients as we typically can. Again this was the way IBM recommended this action was performed.
You might as why this hit us now. Well when we upgraded to v3.0 of the MetaProcessor platform we also took the chance to upgrade our db2 instance. We have performed all testing with db2 at FixPack6 for v3.0. Our development environments are db2 running on Linux. Only our beta environment runs on db2 for AIX. That environment does not produce enough load to notice the problem. Our development environment and loadtest environment which run on db2 for Linux would not have shown this problem as the commit issue appears to be only a change on the AIX platform.
Things may still from time to time be busy due to upgrades happening still but for the most part you should be able to connect to the servers without a problem at this time.
We thank you for your patience through this whole process.
Thank You
Paul
---------------------------------------------------------------------
Ja ist es denn wahr, erst veroeffentlichen und dann selbst testen.
Ich wuerde sagen UD hat ganz einfach gepennt !!
Sollten sich weitere Aenderungen ergeben, dann stehen die hier.
Happy LRM-crunching without Restart-losts (mal abwarten ob Kahn heute einen guten Tag hat).
