read data from DB2 API Stage (iSeries) job hanging

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
mjakubo
Premium Member
Premium Member
Posts: 10
Joined: Thu Apr 26, 2007 4:49 am

read data from DB2 API Stage (iSeries) job hanging

Post by mjakubo »

Hi,

I have a problem with hanging job reading data from DB2 API Stage from iSeries.
For testing I created a simple job: db2_stage,link1, transformer, link2, ds_file.

The SQL within the db2_stage contains a join of four tables and works fine in Navigator (native ODBC tool for iSeries). The "View data" button in stage gives a result as well.
But when I run the job, the link2 get blue (active) in Designer but link1 get not active and job hang.
When I changed the SQL with join of 3 tables the job run. I tested as well another comibation of 3 tables from my starting script and the job run as well.

Every hint will be helpfull.

mjakubo
Minhajuddin
Participant
Posts: 467
Joined: Tue Mar 20, 2007 6:36 am
Location: Chennai
Contact:

Post by Minhajuddin »

Try replacing the DB2 API stage with a row generator stage. This will filter out other possibilities for this behavior.

Also, how may records do you expect for your query?
Minhajuddin

<a href="http://feeds.feedburner.com/~r/MyExperi ... ~6/2"><img src="http://feeds.feedburner.com/MyExperienc ... lrow.3.gif" alt="My experiences with this DLROW" border="0"></a>
mjakubo
Premium Member
Premium Member
Posts: 10
Joined: Thu Apr 26, 2007 4:49 am

Post by mjakubo »

Minhajuddin wrote:Try replacing the DB2 API stage with a row generator stage. This will filter out other possibilities for this behavior.

Also, how may records do you expect for your query?
Hi Minhajuddin,

- yes row generator stage worked fine (and API with join of 3 tables as well)
- 250k records (when job run, worked within half a minute)
- I made another check and used ODBC_Enterprise stage with same SQL which do not work in API-stage, and the job run as well.

May be somebody can give a hint/idea how to analyse the error. Because the job hung I get no error message or something else.

Thanks,
Mjakubo
mjakubo
Premium Member
Premium Member
Posts: 10
Joined: Thu Apr 26, 2007 4:49 am

Post by mjakubo »

Hi All,

I don't know really why but the job worked fine now. I created new DB2_API stage and used custom SQL and created column by load of saved column list and the error was gone. Strange. :evil:

Thanks
Minhajuddin
Participant
Posts: 467
Joined: Tue Mar 20, 2007 6:36 am
Location: Chennai
Contact:

Post by Minhajuddin »

Cool, Time to mark the post as "Resolved" then :)
Minhajuddin

<a href="http://feeds.feedburner.com/~r/MyExperi ... ~6/2"><img src="http://feeds.feedburner.com/MyExperienc ... lrow.3.gif" alt="My experiences with this DLROW" border="0"></a>
Post Reply