DSXchange

I have developed one job
Its having Table_1 as target table.For target stage i am using Db2 partition(Db2/UDB Enterprise stage).
Its showing me error like
"main_program: Fatal Error: Table `Table_1' must exist before querying the node group"

This table is having partition as follows:

CREATE TABLE "CN "."Table_1" (
"Column_1" BIGINT NOT NULL ,
"Column_2" CHAR(3) NOT NULL ,
....
)
COMPRESS YES
DISTRIBUTE BY HASH("Column_1")
INDEX IN "CNX002_ALL" PARTITION BY RANGE("YEAR", "MONTH")
(PART "PART0" STARTING(+2000.,+01.) IN "CNS002_ALL",
PART "PART1" STARTING(+2000.,+02.) IN "CNS002_ALL",
PART "PART2" STARTING(+2000.,+03.) IN "CNS002_ALL",
PART "PART3" STARTING(+2000.,+04.) IN "CNS002_ALL",
PART "PART4" STARTING(+2000.,+05.) IN "CNS002_ALL",
PART "PART5" STARTING(+2000.,+06.) IN "CNS002_ALL",
PART "PART6" STARTING(+2000.,+07.) IN "CNS002_ALL",
PART "PART7" STARTING(+2000.,+08.) IN "CNS002_ALL",
PART "PART8" STARTING(+2000.,+09.) IN "CNS002_ALL",
PART "PART9" STARTING(+2000.,+10.) IN "CNS002_ALL",
PART "PART10" STARTING(+2000.,+11.) IN "CNS002_ALL",
PART "PART11" STARTING(+2000.,+12.) IN "CNS002_ALL",
PART "PART12" STARTING(+2001.,+01.) IN "CNS002_ALL",
PART "PART13" STARTING(+2001.,+02.) IN "CNS002_ALL",
PART "PART14" STARTING(+2001.,+03.) IN "CNS002_ALL",
PART "PART15" STARTING(+2001.,+04.) IN "CNS002_ALL",
PART "PART16" STARTING(+2001.,+05.) IN "CNS002_ALL",
PART "PART17" STARTING(+2001.,+06.) IN "CNS002_ALL",
PART "PART18" STARTING(+2001.,+07.) IN "CNS002_ALL",
PART "PART19" STARTING(+2001.,+08.) IN "CNS002_ALL",
PART "PART20" STARTING(+2001.,+09.) IN "CNS002_ALL",
PART "PART21" STARTING(+2001.,+10.) IN "CNS002_ALL",
PART "PART22" STARTING(+2001.,+11.) IN "CNS002_ALL",
PART "PART23" STARTING(+2001.,+12.) IN "CNS002_ALL",
PART "PART24" STARTING(+2002.,+01.) IN "CNS002_ALL",
PART "PART25" STARTING(+2002.,+02.) IN "CNS002_ALL",
PART "PART26" STARTING(+2002.,+03.) IN "CNS002_ALL",
PART "PART27" STARTING(+2002.,+04.) IN "CNS002_ALL",
PART "PART28" STARTING(+2002.,+05.) IN "CNS002_ALL",
PART "PART29" STARTING(+2002.,+06.) IN "CNS002_ALL",
PART "PART30" STARTING(+2002.,+07.) IN "CNS002_ALL",
PART "PART31" STARTING(+2002.,+08.) IN "CNS002_ALL",
PART "PART32" STARTING(+2002.,+09.) IN "CNS002_ALL",
PART "PART33" STARTING(+2002.,+10.) IN "CNS002_ALL",
PART "PART34" STARTING(+2002.,+11.) IN "CNS002_ALL",
PART "PART35" STARTING(+2002.,+12.) IN "CNS002_ALL",
PART "PART36" STARTING(+2003.,+01.) IN "CNS002_ALL",
PART "PART37" STARTING(+2003.,+02.) IN "CNS002_ALL",
PART "PART38" STARTING(+2003.,+03.) IN "CNS002_ALL",
PART "PART39" STARTING(+2003.,+04.) IN "CNS002_ALL",
PART "PART40" STARTING(+2003.,+05.) IN "CNS002_ALL",
PART "PART41" STARTING(+2003.,+06.) IN "CNS002_ALL",
PART "PART42" STARTING(+2003.,+07.) IN "CNS002_ALL",
PART "PART43" STARTING(+2003.,+08.) IN "CNS002_ALL",
PART "PART44" STARTING(+2003.,+09.) IN "CNS002_ALL",
PART "PART45" STARTING(+2003.,+10.) IN "CNS002_ALL",
PART "PART46" STARTING(+2003.,+11.) IN "CNS002_ALL",
PART "PART47" STARTING(+2003.,+12.) IN "CNS002_ALL",
PART "PART48" STARTING(+2004.,+01.) IN "CNS002_ALL",
PART "PART49" STARTING(+2004.,+02.) IN "CNS002_ALL",
PART "PART50" STARTING(+2004.,+03.) IN "CNS002_ALL",
PART "PART51" STARTING(+2004.,+04.) IN "CNS002_ALL",
PART "PART52" STARTING(+2004.,+05.) IN "CNS002_ALL",
PART "PART53" STARTING(+2004.,+06.) IN "CNS002_ALL",
PART "PART54" STARTING(+2004.,+07.) IN "CNS002_ALL",
PART "PART55" STARTING(+2004.,+08.) IN "CNS002_ALL",
PART "PART56" STARTING(+2004.,+09.) IN "CNS002_ALL",
PART "PART57" STARTING(+2004.,+10.) IN "CNS002_ALL",
PART "PART58" STARTING(+2004.,+11.) IN "CNS002_ALL",
PART "PART59" STARTING(+2004.,+12.) IN "CNS002_ALL",
PART "PART60" STARTING(+2005.,+01.) IN "CNS002_ALL",
PART "PART61" STARTING(+2005.,+02.) IN "CNS002_ALL",
PART "PART62" STARTING(+2005.,+03.) IN "CNS002_ALL",
PART "PART63" STARTING(+2005.,+04.) IN "CNS002_ALL",
PART "PART64" STARTING(+2005.,+05.) IN "CNS002_ALL",
PART "PART65" STARTING(+2005.,+06.) IN "CNS002_ALL",
PART "PART66" STARTING(+2005.,+07.) IN "CNS002_ALL",
PART "PART67" STARTING(+2005.,+08.) IN "CNS002_ALL",
PART "PART68" STARTING(+2005.,+09.) IN "CNS002_ALL",
PART "PART69" STARTING(+2005.,+10.) IN "CNS002_ALL",
PART "PART70" STARTING(+2005.,+11.) IN "CNS002_ALL",
PART "PART71" STARTING(+2005.,+12.) IN "CNS002_ALL",
PART "PART72" STARTING(+2006.,+01.) IN "CNS002_ALL",
PART "PART73" STARTING(+2006.,+02.) IN "CNS002_ALL",
PART "PART74" STARTING(+2006.,+03.) IN "CNS002_ALL",
PART "PART75" STARTING(+2006.,+04.) IN "CNS002_ALL",
PART "PART76" STARTING(+2006.,+05.) IN "CNS002_ALL",
PART "PART77" STARTING(+2006.,+06.) IN "CNS002_ALL",
PART "PART78" STARTING(+2006.,+07.) IN "CNS002_ALL",
PART "PART79" STARTING(+2006.,+08.) IN "CNS002_ALL",
PART "PART80" STARTING(+2006.,+09.) IN "CNS002_ALL",
PART "PART81" STARTING(+2006.,+10.) IN "CNS002_ALL",
PART "PART82" STARTING(+2006.,+11.) IN "CNS002_ALL",
PART "PART83" STARTING(+2006.,+12.) IN "CNS002_ALL",
PART "PART84" STARTING(+2007.,+01.) IN "CNS002_ALL",
PART "PART85" STARTING(+2007.,+02.) IN "CNS002_ALL",
PART "PART86" STARTING(+2007.,+03.) IN "CNS002_ALL",
PART "PART87" STARTING(+2007.,+04.) IN "CNS002_ALL",
PART "PART88" STARTING(+2007.,+05.) IN "CNS002_ALL",
PART "PART89" STARTING(+2007.,+06.) IN "CNS002_ALL",
PART "PART90" STARTING(+2007.,+07.) IN "CNS002_ALL",
PART "PART91" STARTING(+2007.,+08.) IN "CNS002_ALL",
PART "PART92" STARTING(+2007.,+09.) IN "CNS002_ALL",
PART "PART93" STARTING(+2007.,+10.) IN "CNS002_ALL",
PART "PART94" STARTING(+2007.,+11.) IN "CNS002_ALL",
PART "PART95" STARTING(+2007.,+12.) IN "CNS002_ALL",
PART "PART96" STARTING(+2008.,+01.) IN "CNS002_ALL",
PART "PART97" STARTING(+2008.,+02.) IN "CNS002_ALL",
PART "PART98" STARTING(+2008.,+03.) IN "CNS002_ALL",
PART "PART99" STARTING(+2008.,+04.) IN "CNS002_ALL",
PART "PART100" STARTING(+2008.,+05.) ENDING(+2008.,+05.) IN "CNS002_ALL")
ORGANIZE BY (( "Column_name" ) ,);

Can any one suggest me
is it require to do some change in Datastage job so that job can conside partition of table? & if so then what change we need to do?
Please suggest me.

What mode are you using in the Enterprise stage? The Write, Truncate and Append mode all require the table to exist prior to running the job. The Create and Replace will create the table at runtime, but I am not sure how you would specify the range partitioning.

Brad

you can use db2 load stage or db2 api stage