We have a parallel job which does an update in a DB2 database table, on an iSeries. This is done in an ODBC Enterprise Stage.
The problem is that the job keeps running, and is only stopped by aborting the job manually.
The SQL is as follows:
UPDATE MITBAL
SET MBPOOT = CASE WHEN Trim(CAST(ORCHESTRATE.POOT as varchar(512))) = '' THEN MBPOOT ELSE ORCHESTRATE.POOT END
WHERE MBCONO = 200
AND MBITNO = ORCHESTRATE.ITNO
This SQL works if we execute it in an SQL tool (such as WinSQL), with ORCHESTRATE.... replaced by values.
Parallel job hangs on Database Update
Moderators: chulett, rschirm, roy
-
alexander.kuijl
- Participant
- Posts: 2
- Joined: Thu Oct 22, 2009 5:03 am
-
alexander.kuijl
- Participant
- Posts: 2
- Joined: Thu Oct 22, 2009 5:03 am
Solved by disabling Diagnostics in ODBC Datasource
It turns out that the job finishes nicely if "Enable Job Trace" is unticked in the Diagnostic tab of the ODBC Configuration of the used ODBC Datasource.