How to capture errors while running Oracle BulkLoad

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
chuarkai
Participant
Posts: 10
Joined: Mon Apr 28, 2003 6:43 am

How to capture errors while running Oracle BulkLoad

Post by chuarkai »

Hi,

How can I know that there are error while populating data using ORAOCIBL stage.

Normally, when there is warning in a job, the status in Director will be shown as 'Finished (see log)' but in this case it is just 'Finish'. So that I will not know that there is error.


Thank you.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

We don't let DS actually do the bulk load, only generate the data and control files for us. We then do the actual loading using korn shell scripts to parallelize the loading. That being said...

When loaded via DataStage, does it generate the 'normal' discard or bad files if there are errors? You may need to do something akin to what we are doing. In an after-job ExecSH call to a sql script, check for the presence of these files, or perhaps their existance with a non-zero size depending on exactly how the errors show up. You could also grep the load's log file for errors. Any of these cases could generate a non-zero return code which DataStage will pick up as a Warning in the job's log.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply