Manoj Chaurasia Posted November 8, 2011 Share Posted November 8, 2011 Hi, I have a BW process which should invoke a JDBC stored procedure. This procedure is having 3 input parameters and i am successfully able to run it in DB where as when i am calling this JDBC procedure in BW, it is not displaying the input parameters. I have refreshed the activity many times, reopened the project but still it is not showing the input parameters in it. Any ideas how to resolve this issue. Thanks ashwini Link to comment Share on other sites More sharing options...
Rajasegaran P Posted October 23, 2015 Share Posted October 23, 2015 Ashwini, Can you provide details about the stored procedure like what is the input type. I think tibco does not support certain datatypes of stored procs. Regards, Raja... Link to comment Share on other sites More sharing options...
Manoj Chaurasia Posted October 23, 2015 Author Share Posted October 23, 2015 I have definitely seen this issue with incompatible datatypes as Raja mentions. I am assuming you have already tested the connection and BW is able to connect to the Oracle instance successfully. Did you test the stored proc from the DB using the same user as BW is using. The BW user may not be able to see the proc. Link to comment Share on other sites More sharing options...
Manoj Chaurasia Posted October 23, 2015 Author Share Posted October 23, 2015 Hi Ashwini, More often than not, this is an issue with the database driver that you are using. Try changing the database driver. If nothing works, you can use the SQL Direct Activity for writing the whole commmand like "EXECUTE SP_TEST(PARAM1,PARAM2,PARAM3);" Please make sure that you are adding the commas and semicolons while you are concatenating the command. Let me know if that helps. Best Regards, Suvratanu --------------------------------------------------------------------------------------------- Suvratanu Baidya | mailto:sbaidya@infocepts.com| www.infocepts.com --------------------------------------------------------------------------------------------- Link to comment Share on other sites More sharing options...
Manoj Chaurasia Posted October 23, 2015 Author Share Posted October 23, 2015 Have you made sure that the database SP code is complied before you attempt to connect to it. Also, are you able to connect to the database in the first place. Link to comment Share on other sites More sharing options...
Divya T Posted January 14, 2020 Share Posted January 14, 2020 The work around for this: Duplicate the SP outside the Package with a different name. Ones the structure is consumed changing the name to actual SP and Procedure works. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now