My datastage job will delete the records which are older than 60 months in the table.
The job is running fine if there is some data older than 60 months.
But when there is no data older than 60 months it is giving me a fatal error :
Error in row #1
Primary Error:
sqlcode=100, state=HY000, message=[IBM][CLI Driver][DB2/AIX64] SQL0100W No row was found for FETCH, UPDATE or DELETE; or the result of a query is an empty table. SQLSTATE=02000
In the UDB DB2 stage i am writing an sql query like :
Delete from table where recorddate < orchestrate.date
here orchestrate.date is the date 60 months old than todays date.
Plz specify how to overcome this error.
No row was found for FETCH, UPDATE or DELETE; or the result
Moderators: chulett, rschirm, roy
Always add a dummy record where the date is >60 months old so that the DELETE always has at least one row to process.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 5
- Joined: Sun Jun 25, 2006 12:31 am
- Location: Melbourne, Australia
The table contains very much real production data.
So, i cant insert any dummy records
The job is as well scheduled in CTRL-M and i am running the job through scripts in unix.
I have coded the script like,if it encounters one fatal error the job will be abended.
Is compressing the message in the log is a permanent solution,if that so then how to do it..?
So, i cant insert any dummy records
The job is as well scheduled in CTRL-M and i am running the job through scripts in unix.
I have coded the script like,if it encounters one fatal error the job will be abended.
Is compressing the message in the log is a permanent solution,if that so then how to do it..?
-
- Participant
- Posts: 5
- Joined: Sun Jun 25, 2006 12:31 am
- Location: Melbourne, Australia
Select the fatal message in Log in DS director and then from the menu click job>Add Rule to Message Handler. Follow the on screen instructions.
Note: make sure you have selected the appropriate log message. Also consult the administrator as most of the log suppression are not applied in Production environment.
Note: make sure you have selected the appropriate log message. Also consult the administrator as most of the log suppression are not applied in Production environment.
Shankar Iyer
Business Analyst
Hewett Packard
Business Analyst
Hewett Packard