Stored procedure - Wierd behavior

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
vinothkumar
Participant
Posts: 342
Joined: Tue Nov 04, 2008 10:38 am
Location: Chennai, India

Stored procedure - Wierd behavior

Post by vinothkumar »

I am expecting a strange behavior in Stored procedure stage. I am trying to call a DB2 procdure having 3 input parameters and 4 output parameters. When I run with a single row, for some cases the procedure runs fine. But when I run with multiple rows the DataStage job is aborting with the reason 'Stored_Procedure_15,0: Fatal Error: Fatal: Wrong number or types of arguments in call to'. I checked the input parameter values and types and they are looking good.

Case1 : Input parameters are 3685889,19991231,20101231 -> This is working fine.

Case2 : Input parameters are 7409763,19991231,20101231 -> This is throwing the error in DataStage. But when I run the same through Outside of DataStage it is running fine.
Top
Post Reply

Return to “IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)”