SQL0206N & SQLSTATE=42703

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
MURALI123
Participant
Posts: 46
Joined: Sun Jun 21, 2009 1:37 am
Location: CHENNAI

SQL0206N & SQLSTATE=42703

Post by MURALI123 »

Hi All,

I have got the below warning can anybody suggest me.

SQL0206N "BEPERSTAT" is not valid in the context where it is used. SQLSTATE=42703

Regards,
Malli
Top
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Suggest you provide more information. We have no idea what database you are using or what action there is causing this. Details, man, details!
-craig

"You can never have too many knives" -- Logan Nine Fingers
Top
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:
Contact ray.wurlod

Post by ray.wurlod »

My guess is that you have used this as a table name and no such-named table exists in the schema that you are using (possibly a default schema).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Top
Post Reply

Return to “IBM<sup>®</sup> Infosphere DataStage Server Edition”