fatal error

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
hargun
Participant
Posts: 188
Joined: Mon May 16, 2011 7:41 pm
Location: United States

fatal error

Post by hargun »

Hi,

i am getting the following fatal error

Job design
lookup seq file with Db2 database 1 and put ino target table


Db2 database1
.
.
seq file......................lkup......................xfm..............>db2 database


The follwing error coming from reference Db2 database 1
db2_Job_Def_Group,0: DB2 reported: SQLSTATE = 42S22: Native Error Code = -206: Msg = [IBM][CLI Driver][DB2/LINUXX8664] SQL0206N "DEFN_NUM" is not valid in the context where it is used. SQLSTATE=42703 [:0]


i have used the following query
select 1 as batchdummy,max(job_batch_gk) AS JOB_BATCH_GK_REF from AUDIT#psdaDB2_LUW_EDW.pvDBEnvironment#.JOB_BATCH where job_defn_num=#defn_num# and job_group_num=#group_num#
#def_num # and group_num# and #psdaDB2_LUW_EDW.pvDBEnvironment# and #psdafilelocation# are job parameters

I just copy the same job with all same parameters just seq file is different
i don't know why its showing where as already existing job runs fine .
SURA
Premium Member
Premium Member
Posts: 1229
Joined: Sat Jul 14, 2007 5:16 am
Location: Sydney

Re: fatal error

Post by SURA »

Did you changed the target table name?
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
hargun
Participant
Posts: 188
Joined: Mon May 16, 2011 7:41 pm
Location: United States

Post by hargun »

hi sura,

No i didn't change the target table.
sreewin7
Participant
Posts: 41
Joined: Tue Sep 14, 2010 8:48 pm

Post by sreewin7 »

Hey,

Are you testing this job in dev or prod?

1)Dev:- Can you please double check all parameters are same as old job, some times in the administration, admin will change few parameters, due to that job may be aborted with fatal errors.

2) try to load the same data in to peek , if you are using parellel job and let me know the results.

Thanks
Sree
rameshrr3
Premium Member
Premium Member
Posts: 609
Joined: Mon May 10, 2004 3:32 am
Location: BRENTWOOD, TN

Post by rameshrr3 »

Any issue with runtime column propogation being turned on or ( Off ) in the job?

I dont think its a databse table permissions change since your copy job works fine.

Can you compile & run the job in trace mode and see spurious column names or structures that dont belong in your job
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The error message is complaining about "DEFN_NUM". Maybe you left an underscore out of "JOB_DEFN_NUM".
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
SURA
Premium Member
Premium Member
Posts: 1229
Joined: Sat Jul 14, 2007 5:16 am
Location: Sydney

Re: fatal error

Post by SURA »

hargun wrote:
#def_num # and group_num# and #psdaDB2_LUW_EDW.pvDBEnvironment# and #psdafilelocation# are job parameters
If you check the above from your comments

Code: Select all

#def_num #  is good whereas #def_num # and group_num# and  is not

missing # in the group_num.

It is typo or is it how you have it in the query?
Thanks
Ram
----------------------------------
Revealing your ignorance is fine, because you get a chance to learn.
Post Reply