As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
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
Posts: 397 | Location: New York City | Registered: May 03, 2007
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
Posts: 397 | Location: New York City | Registered: May 03, 2007