ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Oracle Stored Procedure call with 9.2.0.3

Post new topic  Reply to topic
 Oracle Stored Procedure call with 9.2.0.3 « View previous topic :: View next topic » 
Author Message
rcrippen
PostPosted: Wed Jun 02, 2004 9:07 am    Post subject: Oracle Stored Procedure call with 9.2.0.3 Reply with quote

Apprentice

Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY

Using WBIMB v5.0 CSD03, I am trying to call a stored procedure in a PASSTHRU function inside a Compute node. The oracle client is 9.2.0.3 connecting to an Oracle db on a Sun Solaris.

The syntax is as follows:
SET OutputLocalEnvironment.DatabaseResults[] =
PASSTHRU('{call e_auth.cteumer.einv_mq_reply(?,?)}',
InputRoot.XML.ssoResponse.transactionID, InputRoot.XML.ssoResponse.status);

The ODBC data source has been created and I can execute the stored procedure through the SQLPlus tool using the same user id and password that I set in the mqsisetdbparms utility.

The error message that is returning via the SQL return codes:
<SQLState>HY000</SQLState>
<SQLErrorText>[Oracle][ODBC][Ora]ORA-06550: line 1, column 7: PLS-00201: identifier &apos;EAUTH.E_AUTH_CTEUMER&apos; must be declared ORA-06550: line 1, column 7: PL/SQL: Statement ignored </SQLErrorText>
<SQLCode>-1</SQLCode>
<SQLNativeError>6550</SQLNativeError>

I've searched the archives and don't seem to find a solution that matches this issue.

Has anyone encountered this or have any suggestions?

Thanks,

Rob Crippen
Back to top
View user's profile Send private message Visit poster's website
kirani
PostPosted: Wed Jun 02, 2004 10:24 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Have you tried calling a procedure using CREATE ...PROCEDURE?
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
JT
PostPosted: Thu Jun 03, 2004 6:03 am    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.

Not sure how much difference there is between calling a Oracle stored procedure and an Oracle function, but this is how we invoke our stored functions:
Quote:
SET OutputLocalEnvironment.Variables.XML.TlaMessage.Response[] =
passthru('select PRODUCTSA.psa_productcentralxml_pkg.getDCProducts_XML(?,?) DATA FROM DUAL',distChannel,sellArrangement);

Where PRODUCTSA is the name of the schema, psa_productcentralxml_pkg is the name of the package and getDCProducts_XML(?,?) is the name of the function. We also call Oracle functions that are not packaged.
Back to top
View user's profile Send private message
rcrippen
PostPosted: Fri Jun 04, 2004 12:11 pm    Post subject: Reply with quote

Apprentice

Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY

kirani,
I tried to use an ESQL Create procedure in the following way:
CREATE PROCEDURE processStatusEXT(IN parm1 CHARACTER,
IN parm2 CHARACTER)
EXTERNAL NAME eauther_user.e_auth_cteumer.einv_mq_reply;

When I deploy, I get a syntax error:
BIP2402E: (,26.24) Syntax Error : '.'.

What could be wrong?

Rob
Back to top
View user's profile Send private message Visit poster's website
rcrippen
PostPosted: Fri Jun 04, 2004 12:45 pm    Post subject: Reply with quote

Apprentice

Joined: 01 Aug 2002
Posts: 45
Location: Rochester, NY

Persistence pays off!!!

I wrapped the external stored procedure name in double quotes and low and behold the stored procedure was invoked....

Here is the ESQL syntax I used:

DECLARE inputParm1 CHARACTER;
DECLARE inputParm2 CHARACTER;
SET inputParm1 = InputRoot.XML.ssoResponse.transactionID;
SET inputParm2 = InputRoot.XML.ssoResponse.status;
CALL processStatusEXT(inputParm1,inputParm2);

CREATE PROCEDURE processStatusEXT(IN parm1 CHARACTER,
IN parm2 CHARACTER)
EXTERNAL NAME "eauth_user.e_auth_cteumer.einv_mq_reply";


Thanks for everyone's help.

Rob Crippen
Back to top
View user's profile Send private message Visit poster's website
kirani
PostPosted: Fri Jun 04, 2004 4:17 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Sorry for the late repy. I am glad the problem is now resolved.
The reason it was failing is because of . in your stored procedure names.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Oracle Stored Procedure call with 9.2.0.3
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.