Job hanging at CDC stage

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
jweir
Participant
Posts: 134
Joined: Wed Aug 04, 2010 12:31 pm

Job hanging at CDC stage

Post by jweir »

Hi all,

I have a job that uses the CDC stage to check if the source records are insert, update or copy records. I am looking up to the target table that has about 6.8 million records. In the current run of the job, only one record is looking up to the 6.8 million. For some reason, it has been taking almost 2 hours and the job is hung at the CDC stage. How can I speed this job up?

I have sorted and partitioned on the change keys on both inputs but still no luck. Any tips?

Thanks in advance.
Jweir

--- If strength were all, tiger would not fear scorpion.
jweir
Participant
Posts: 134
Joined: Wed Aug 04, 2010 12:31 pm

Post by jweir »

I found the solution. Instead of sorting and partitioning on the inputs, I did an ORDER BY on the reference table select query on the CDC keys. After I did this, the job completed within a minute.

I will mark this as resolved.
Jweir

--- If strength were all, tiger would not fear scorpion.
elsont
Participant
Posts: 16
Joined: Wed Oct 08, 2008 1:20 am
Location: Chicago

Post by elsont »

Hi jweir, I saw your solution but it doesn't looks good to me. Your solution will work correctly only if all of your stages are running sequentially (then it is not a good design as you are not using parallell capability).
Post Reply