Hi,
I would like to know if there is a way of actually checking within a datastage job how many rows actually get updated on an informix table.
For example we are updating a record on a table which does not exist but datastage still shows the job as being run successfully and updated. But I need to know how many rows actually did get updated.
Finding out how many actually updated using Informix CLI
Moderators: chulett, rschirm, roy
Welcome!
Back in the old days when I worked with Informix, I recall it having the same behaviour as the Oracle databases I support now - it is perfectly happy to update or delete a nonexistent record. We'd need to investigate the sqlca area where 'the number of records effected' by the current sql were returned to check for a 0 if we felt that was an error.
I know of no such mechanism available from DataStage, perhaps others do. All I can suggest in its absence is a 'post process' that counts the number of records with the current timestamp, assuming that is, that your updates timestamp the records they touch. Compare that with the expected count based on the input records used in the update link.
Back in the old days when I worked with Informix, I recall it having the same behaviour as the Oracle databases I support now - it is perfectly happy to update or delete a nonexistent record. We'd need to investigate the sqlca area where 'the number of records effected' by the current sql were returned to check for a 0 if we felt that was an error.
I know of no such mechanism available from DataStage, perhaps others do. All I can suggest in its absence is a 'post process' that counts the number of records with the current timestamp, assuming that is, that your updates timestamp the records they touch. Compare that with the expected count based on the input records used in the update link.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers