You could try user-defined SQL using CALL - I do not know whether this will work.
As a general rule, definitions of stored procedures to be invoked by DataStage have to be imported (or created) first (so that the number of arguments can be verified) and must have at least a return result set. In my experience, at least one input parameter is required, even if the stored procedure ignores it. I have only ever invoked stored procedures through an ODBC stage. DataStage Designer's Help suggests that stored procedures can only be used from ODBC or BCP stages.
Ray Wurlod
Education and Consulting Services
ABN 57 092 448 518
Problem with calling Oracle Stored Procedure
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 39
- Joined: Tue May 20, 2003 3:36 am
- Location: Singapore
You can use CALL in the OCI Stage as User Defined SQL. You can pass in parameters. It is unsupported. To make sure the parameters are bound correctly make all the columns KEY = YES. You cannot get any values back.
If you are hoping for some error checking be aware that not all errors returned from Oracle are trappable.
Online Help? You're reading it! I'm guessing he meant "F1" help or help from the pdfs. All are pretty weak.
If you are hoping for some error checking be aware that not all errors returned from Oracle are trappable.
Online Help? You're reading it! I'm guessing he meant "F1" help or help from the pdfs. All are pretty weak.