Hi,
we've got a job that updates a bunch of rows in an oracle table. The monitor says that the correct number of rows were read and written to the output link, however a few of the rows aren't getting updated.
doesn't make sense to me ...
Pete.
Oracle Updates Gone Missing
Moderators: chulett, rschirm, roy
-
TheButterflyE
- Participant
- Posts: 1
- Joined: Wed Oct 04, 2006 10:42 pm
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard. :D
The link row count tells you how many rows DataStage sent to Oracle.
It does not tell you how many were accepted by Oracle.
Look in the job log (Director client, Log view) to see whether any warnings were generated by Oracle. Chances are that there is one (or two maybe) for each row that failed to be updated.
The link row count tells you how many rows DataStage sent to Oracle.
It does not tell you how many were accepted by Oracle.
Look in the job log (Director client, Log view) to see whether any warnings were generated by Oracle. Chances are that there is one (or two maybe) for each row that failed to be updated.
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.
Common 'problem'. As noted, the monitor shows update requests - it's up to your job to ensure they are valid updates. 
Keep in mind the fact that Oracle updates that update zero records are not considered to have failed - they successfully update nothing. Same with deletes. So DataStage has nothing bad to report back to you when that happens. You'll need to drill into the ones that didn't happen and attempt to figure out why.
Note: I'm assuming you've checked the job's log to see if any warnings were logged (not finding any) and are not relying on the stats shown by the 'monitor' in the Designer.
Keep in mind the fact that Oracle updates that update zero records are not considered to have failed - they successfully update nothing. Same with deletes. So DataStage has nothing bad to report back to you when that happens. You'll need to drill into the ones that didn't happen and attempt to figure out why.
Note: I'm assuming you've checked the job's log to see if any warnings were logged (not finding any) and are not relying on the stats shown by the 'monitor' in the Designer.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers