MQSeries.net :: View topic - Error while invoking Stored Procedure call from Compute Node

pdC · Posted: Sun Mar 17, 2013 10:16 pm Post subject:

Hi All,
I am trying to invoke a stored procedure call from the compute node in my messageflow (WMB V8 ) and am seeing some errors that are not very meaningful (to me). I have done a fair bit of online searches to see if I can find any information on the error I am seeing but not had too much luck.
I thought I would see if a post into this forum yields any information before raising a PMR with IBM.

Here are some details of my issue.

Software Level: Message Broker 8.0.0.1

Issue:
An Oracle Store Procedure is being invoked from the messageflow. The invocation fails with errors and the odbctrace.out shows errors such as:

***************
Entry:
Statement = 1178fde30
Data Type = SQL_TIMESTAMP
[ODBC][8847362][7200][2013-03-15 15:30:56.060][SQLGetTypeInfo.c][314]
Exit:[SQL_ERROR]
DIAG [HY004] [IBM][ODBC Oracle Wire Protocol driver]Invalid SQL data type."

***************

Compute Node ESQL Code has:

CREATE PROCEDURE getData (
OUT O_status CHAR,
OUT O_error_message CHAR,
INOUT IO_request_response CHAR
)
LANGUAGE DATABASE
EXTERNAL NAME "myschema.myproc.getData"

Store Procedure has:

PROCEDURE getData (
O_status OUT VARCHAR2,
O_error_message OUT VARCHAR2,
IO_request_response IN OUT CLOB
);

Entry in ODBC.INI file for this datasource:
Driver=/proj/mqsi/8.0.0.1/ODBC/V6.0/lib/UKora24.so
Description=DataDirect ODBC 6.0 Oracle Wire Protocol

I have seen a few internet search hits that indicate that there may be an issue with "CLOB" usage, but it also seems to indicate that using "CHAR" as we have in the ESQL should allow the call to work.
The errors in the odbctrace seem to be around "Timestamp" but I do not have any in my Stored Proc call.

Also, although this may be the only option, our preference would be to not alter the Store Procedure call in any way.

Any advise would be greatly appreciated.