ODBC Stage -- job running almost 4 hrs.

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
sreddy
Participant
Posts: 144
Joined: Sun Oct 21, 2007 9:13 am

ODBC Stage -- job running almost 4 hrs.

Post by sreddy »

Hi

I have job like this

Source1: ODBC stage extracting data .
Reference: ODBC Stage feching some data.

LookuStage: Condition Not met: Fail
Lookup Failure: Drop
Target: ODBC Stage ( Deleting records out put from source after lookup )


Job is running almost 4 hrs. I run the job first on 4 node system. It is taking somuch time but output after lookup 1456 records.

The same job when i run on single node
Lookup_Active_PO,0: Ignoring duplicate entry at table record 46; no further warnings will be issued for this table

APT_CombinedOperatorController(1),0: [IBM(DataDirect OEM)][ODBC DB2 Wire Protocol driver]Socket closed.
[IBM(DataDirect OEM)][ODBC DB2 Wire Protocol driver]Socket closed.
[IBM(DataDirect OEM)][ODBC DB2 Wire Protocol driver]Socket closed.


Now i am planning to use DB2API stage instead of ODBC.

Thanks
SReddy
Sreenivasulu
Premium Member
Premium Member
Posts: 892
Joined: Thu Oct 16, 2003 5:18 am

Post by Sreenivasulu »

Switch on the odbc tracing in the odbc.ini file and check which part is causing the bottleneck

Regards
Sreeni
Post Reply