Hello People;
I would like to call the Oracle Store Procedure in DataStage thru OCI(NOT
ODBC), what are the step for it? Any documentation or ref?
Thanks in advance
Regards
Rahim _________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
Call Store Procedure in DataStage Thru Oracle OCI in unix
This is useful to know, Ray.
However, is it able to return any sort of success or failure information to DataStage, so that we can log an error if it fails, or perhaps stop other subsequent dependent jobs?
-----Original Message-----
From: Ray Wurlod [mailto:ray.wurlod@Informix.Com]
Sent: Saturday, 30 June 2001 8:46 AM
To: informix-datastage@oliver.com
Subject: RE: Call Store Procedure in DataStage Thru Oracle OCI in unix
User-defined SQL can use {CALL procedure(arg1, arg2)}
Not explicitly documented because its a common thing to want to do.
However, is it able to return any sort of success or failure information to DataStage, so that we can log an error if it fails, or perhaps stop other subsequent dependent jobs?
-----Original Message-----
From: Ray Wurlod [mailto:ray.wurlod@Informix.Com]
Sent: Saturday, 30 June 2001 8:46 AM
To: informix-datastage@oliver.com
Subject: RE: Call Store Procedure in DataStage Thru Oracle OCI in unix
User-defined SQL can use {CALL procedure(arg1, arg2)}
Not explicitly documented because its a common thing to want to do.
Database errors should be logged automatically by DataStage, which is a client to the database server.
If youre using DataStage 4.0 or later, output links have "link variables" associated with them. Thus, for example, on a link that was handling rejected rows you could output the value of variables such as MainOutputLink.DBMSCODE, MainOutputLink.LASTERR and so on, where MainOutputLink is the main output link.
If youre using DataStage 4.0 or later, output links have "link variables" associated with them. Thus, for example, on a link that was handling rejected rows you could output the value of variables such as MainOutputLink.DBMSCODE, MainOutputLink.LASTERR and so on, where MainOutputLink is the main output link.