Row leakage

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
ahmedwaseem2000
Premium Member
Premium Member
Posts: 145
Joined: Fri Sep 15, 2006 12:23 pm

Row leakage

Post by ahmedwaseem2000 »

Hi,

I was looking for an existing script or a job that would back track and find out which job has dropped the record. it gets bit too laborious as there are far too many jobs to be verified manually. what we have to check is the number of rows read, and the number of rows written to the output should match. not sure how to handle when the data is restructured. can you please suggest if there is a script or how to automate this re-conciliation ?

Thanks!!
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Nothing exists. You have to design it in yourself. Some sites have developed row count reconciliation routines, but they don't report at the individual row level. You'd need to design something into the actual job flow itself.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ahmedwaseem2000
Premium Member
Premium Member
Posts: 145
Joined: Fri Sep 15, 2006 12:23 pm

Post by ahmedwaseem2000 »

Thanks Ray!!

Any advice to handle the data restructuring points like rows spreading out of transformer, aggreation's or pivots?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

What we (Zenith Solutions) do is adopt a special link naming convention for those times when total rows out <> total rows in, and the routines have the capacity built-in to recognise such a link name and not react to a link row count mismatch.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply