Hi All
I have two jobs to load a table.The first job loads the data from master to the target.The second job updates the data from child to the target.But when the second job finds no data to be updated it gets aborted with the error .
[DataStage][SQL Client][ODBC][IBM][CLI Driver][DB2/6000] SQL0100W No row was found for FETCH, UPDATE or DELETE; or the result of a query is an empty table. SQLSTATE=02000
Does the datastage job gets aborted if it does not find anything to update?If this is the case, then how should I implement the update strategy?
Regards
Shiva
Shivakumar
Update Problem
Moderators: chulett, rschirm, roy
-
- 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:
Good plan. It's more efficient to identify updateable rows before trying to update them. DB2 does not allow you to update non-existent rows (this is true of most databases).
What is your "update rule" - update existing rows only? A workaround would be to change this to "update existing rows or insert new rows" but this won't run as fast, and may not be what you want.
What is your "update rule" - update existing rows only? A workaround would be to change this to "update existing rows or insert new rows" but this won't run as fast, and may not be what you want.