Hi,
Got a job Oracle stage -> Hash file
When I compile the job and run, it gives me the no. of rows processed as 256, but sometimes, it shows me no of process as 20 rows only, when run from sequencer.
In the source no. of rows are 256.
No error logs or warning coming.
In the Oracle stage it's a simple SQL query.
Any ideas.
Thanks,
Performance stats and no. of rows in source does not match
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Hashed files (and please note it's not "hash" file) destructively overwrite records if the key (as identified in metadata) is the same.
Do you have duplicate keys coming from source?
Are there any other constraints in your job design that might limit the number of rows to 20?
Do you have duplicate keys coming from source?
Are there any other constraints in your job design that might limit the number of rows to 20?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
However, even with a destructive overwrite down to 20 going on it would still show 256 going in, which is what I'm assuming is meant by 'processed'. The surprise people get is when they pull the records back out.
As to the issue, if I had to guess (and I do) the fact that the problem comes when run 'from a sequencer' usually implies a parameter passing problem which could translate to getting connected to a different instance / database than expected - one that only has 20 records in the source. That or the source simply isn't static and it is changing on you, not like we've never seen that before. Have you verified your connection parameters when you see this issue?
As to the issue, if I had to guess (and I do) the fact that the problem comes when run 'from a sequencer' usually implies a parameter passing problem which could translate to getting connected to a different instance / database than expected - one that only has 20 records in the source. That or the source simply isn't static and it is changing on you, not like we've never seen that before. Have you verified your connection parameters when you see this issue?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: