Job failing

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
dspxguy
Participant
Posts: 156
Joined: Thu May 24, 2007 4:09 pm
Location: Simi Valley, CA

Job failing

Post by dspxguy »

one of the job is failing due to these error messages

Stg3,0: Failure during execution of operator logic.

APT_CombinedOperatorController(0),0: Fatal Error: Fatal: [IBM][CLI Driver] SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032
Unable to connect to DB2 server 'etlprod'.

node_etlnode3: Player 5 terminated unexpectedly.


the job design is one db2 enterprise stage extracting data and then a lookup is performed using 8 db2 API stages.

Code: Select all

                 4 api stages
                   | | | |
DB2 enterprise -->lookup--> tx-->sort-->funnel-->sf
                   | | | |
                  4 api stages 
is there a limitation of DB2 stages used in a job?

Thanks
Last edited by dspxguy on Tue Oct 02, 2007 2:44 pm, edited 2 times in total.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Please wrap your job design in Code tags.

There is no limit on the number of DB2 stages in a DataStage job, from a technical perspective. From a maintainability perspective, there ought to be. It is apparent, however, that there is a limit on the number of simultaneous connections to your DB2 instance. Enlist the help of your DBA to determine whether this limit has been encountered.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply