Concering Data audit

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
bhargav_dd
Premium Member
Premium Member
Posts: 57
Joined: Tue Jun 30, 2009 9:38 am

Concering Data audit

Post by bhargav_dd »

Dear All,
-
Recently, there is a requirement that performing data audit throught datastage job. Its functionality includes store error data in a separate file along with error message, row number and source name when detect a violation in terms of data type, length of character string, etc.
-
So, if we wanna perform that within datastage job, what is the best practice for it and what kind of stage would be referred?
If there are other good solution besides datastage, such as unix shell level, pls advise me that as well.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

That really depends on what is meant by "reject" but, in most cases, explicit reject-handling output links from stages combined with post-job row count reconciliation ought to do most of what you require.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kduke
Charter Member
Charter Member
Posts: 5227
Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:

Post by kduke »

Be careful storing this information. If someone runs a job with no warning limit then every row can get an error. You could put millions of errors in an audit table.
Mamu Kim
Post Reply