DB2 error when I run the job

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
suresh.narasimha
Premium Member
Premium Member
Posts: 81
Joined: Mon Nov 21, 2005 4:17 am
Location: Sydney, Australia
Contact:

DB2 error when I run the job

Post by suresh.narasimha »

Hello

My job aborted with a DB2 message " [IBM][CLI Driver][DB2] SQL0471N Invocation of routine "SYSIBM.SQLTABLES" failed due to reason "00E7900C". SQLSTATE=55023 "

I have searched forum, but could not find appropriate post.

Regarding my job, I'm using a db2 stage and writing into a file, I was able to view data through DataStage data browser. The query is a straight select statement.

And when I ran the job it aborted with the message above. To troubleshoot, I logged into DB2 database and the user has execute privilege to SYSIBM.SQLTABLES (execute privilege has been given to PUBLIC)

I'm not sure where exactly it is going wrong.

Could you please advise me on this ?

Thanks
Suresh
SURESH NARASIMHA
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Search a DB2 forum or Google. What do these particular DB2 error codes mean?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Yup, Google brings what seems to be the error and solution right up if you are feeling lucky.
-craig

"You can never have too many knives" -- Logan Nine Fingers
suresh.narasimha
Premium Member
Premium Member
Posts: 81
Joined: Mon Nov 21, 2005 4:17 am
Location: Sydney, Australia
Contact:

DB2 error when I run the job

Post by suresh.narasimha »

Hi,

I have searched google and found the link that you have posted, but I wanted to make sure before I go to the DBA and ask him to enable the stored proc.

the issue has been resolved, stored procedure was not enabled due to some upgrade in db2 database.

Thanks for yor help.
SURESH NARASIMHA
Post Reply