Query 11g DB from Stored Procedure Call through Oracle Database Provider for DRDA returns Sqlcode -440 (Doc ID 2005181.1)

Last updated on APRIL 14, 2022

Applies to:

Oracle Database Provider for DRDA - Version 12.1.0.2 and later
Linux x86-64

Symptoms

While trying to query Oracle 11.2.0.3 Database from stored procedure CALL,
with connection "from" DB2 v10 (and COBOL) on z/OS through ODP4DRDA 12.1.0.2 on Linux x86-64
"to" Oracle 11.2.0.3 Database on Linux x86-64, results in sqlcode -440;

The code currently only supports CALL with bind variables and should support
literals, NULL, and expressions, as well as bind variables for CALL.

The -440 trace file (pp_22020_drdaas.trc) shows the following messages:

Entering dpsadrexCSqlstt_proc_desc, Cursor= 0x49bc708 at 2015-02-25 16:35:56.553882000 my_schnm="MKT", ln=3 my_prcnm="ICIS_WRITE_TO_TRANSACTION_LOG", ln=29 MyMemoryAlloc(4200) => 0x49ce040 OCIHandleAlloc(@h0x49cee48,OCI_HTYPE_DESCRIBE) -> RC=0 Looking for standalone procedure MKT.ICIS_WRITE_TO_TRANSACTION_LOG with 5 args is_synonym: schema=MKT, prcnm=ICIS_WRITE_TO_TRANSACTION_LOG === There are 0 seemingly acceptable procedure(s) with name ICIS_WRITE_TO_TRANSACTION_LOG OCIHandleFree(h0x49cee48,OCI_HTYPE_DESCRIBE) -> RC=0 Exiting dpsadrexCSqlstt_proc_desc, RC= 1 at 2015-02-25 16:35:56.635160000 === SQLCASet: sqlcode=-440

Cause

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Query 11g DB from Stored Procedure Call through Oracle Database Provider for DRDA returns Sqlcode -440 (Doc ID 2005181.1)

Applies to:

Symptoms

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!