Folder stage -> XML stage -> Hash File stage(with input and output on the same file) -> OCI
The reason I use Hash file stage is to remove duplicate data. Most of times it works fine and I have used a lot in my jobs with a hash file stage having input and output link for the same file. But I experienced problem today that I had 10000 records write to the hash file and only 100 records were inserted into the table in OCI stage. When I viewed the file, it definitely had more than 100 records in the hash file. The job was completed successfully without any error or warning. Does anyone experienced the same problem?Thanks
How many rows went "into" the OCI stage - perhaps you are getting insert errors due to constraints. Add a reject link in the job to ensure that this isn't causing your dropped records.
No eror. only 100 rows went into OCI stage but has 10000 rows in the hash file
ArndW wrote:How many rows went "into" the OCI stage - perhaps you are getting insert errors due to constraints. Add a reject link in the job to ensure that this isn't causing your dropped records. ...
Also, do you re-create the hashed file each run or append to it? Is the error visible on each run or just occasionally? Do other jobs use the same hashed file? If you turn off buffering on the write does the error remain?
The file is used only in one job. File is recreated every job run. No write cache is used.
ArndW wrote:Also, do you re-create the hashed file each run or append to it? Is the error visible on each run or just occasionally? Do other jobs use the same hashed file? If you turn off buffering on the write d ...
Just occasionally. But It happened today and last week.
ArndW wrote:Also, do you re-create the hashed file each run or append to it? Is the error visible on each run or just occasionally? Do other jobs use the same hashed file? If you turn off buffering on the write d ...
Could you check like you have given the same path in the Input & output tab of Hash file. If you have given a path in input & some other path in output, it may take from the old hash file.
Run stopped after 100 rows can only be caused by one thing; when the job run request is issued, a limit of 100 rows is imposed. Check the Limits tab on your Job Run Options dialog.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ray.wurlod wrote:Run stopped after 100 rows can only be caused by one thing; when the job run request is issued, a limit of 100 rows is imposed. Check the Limits tab on your Job Run Options dialog. ...
I will check the Run Options when I get back office tomorrow morning. But I run the sequence job from the director. There are many other jobs in this sequence and only this job got stopped after 100 rows. Very werid.
</a>