Focal Point
Communication Error (ICMM18822)

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/1381057331/m/2167028006

March 23, 2011, 06:52 PM
Viral
Communication Error (ICMM18822)
Hello,

I have SQL Flow service where executing sql statments and my target is Oracle Package.Procedure (synonym) created.

Oracle Package.Procedure accepts parameters which mapped out to the fields retrieved from the SQL Statement.

Is it possible to call the Oracle Package.Procedure as synonym and passed the parameters from the SQL fetched.
Please advice me on this.

Thanks,


WF 7.6.2/ OS WIN2003.
DM 7.6.2
April 01, 2011, 02:22 PM
Clif
From you signature it appears you are using DataMigrator. Once you have created a synonym for an ORACLE stored procedure you can pass paramaters to it in a Data Flow in a filter (WHERE condition) by specifying a value for each input parameter. Or if you have multiple paramaters in a table you can use a JOIN with an ON condition for each paramater.


N/A
April 04, 2011, 03:58 PM
Viral
Hi Cliff,

What i was trying is not possible in the data flow as per IBI. I have case open with IBI.

What's saying I can not use the synonym created against oracle package.procedure for target.


WF 7.6.2/ OS WIN2003.
DM 7.6.2
April 04, 2011, 04:33 PM
Clif
I looked at the hottrack case, it seems they think you asked if you could use a synonym for an ORACLE stored procedure as a TARGET in a data flow. While the answer is no, that may not be the right question.

If you have an ORACLE stored procedure that updates an ORACLE table, you can still call it in the same way you would call any other ORACLE stored procedure.

It sounds wierd I know. But you would select the synonym as a SOURCE, and then you would pass paramaters with a WHERE condition or JOIN. Except in this case those parms would be the values that you want to update.

The output from the SELECT would be whatever is returned by the stored procedure, possibly a return code.

When you run the flow the stored procedure gets executed, and it does its thing. The DataMigrator server doesn't know what it's doing, it's just calling the stored procedure with the parms you provided and getting the result back.


N/A