Error while invoking database stored procedure while mapping to varchar,int

Question

Hi I am using Oracle SOA 11g 11.1.1.4
In that i am calling db procedure.The procedure is taking input parameters int and varchar and nillable is true for both cases.Its a sybase data base.
I am calling this db proc through db adater.Here I am mapping integer and string values to input parametres of db procedure.
While testing i am getting following exception.Here in the error 9000 is the value i am passing for integer input.
Exception occured when binding was invoked. Exception occured during invocation
failed due to: Unimplemented object conversion. Conversion of type
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Procedure1' failed due to: Unimplemented object conversion. Conversion of type 9000 whose JDBC type is OTHER to a Java object is not supported. An attempt was made to convert type 9000 to a Java object using an unsupported JDBC type: OTHER. Use a data type with a supported JDBC type. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>
</part>
<part name="detail">
<detail>Unimplemented object conversion. Conversion of type 9000 whose JDBC type is OTHER to a Java object is not supported. An attempt was made to convert type 9000 to a Java object using an unsupported JDBC type: OTHER. Use a data type with a supported JDBC type. </detail>
</part>
<part name="code">
<code>null</code>
</part>
</bindingFault>
</bpelFault>
</fault>
<faultType>
Please help on this.
Thanks
<message>0</message>
</faultType>
</messages>

Answer 1

I'm having a similar issue, while trying to invoke a SP from MS SQL Server.
where the following is the DB adapter
<schema targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/db/RetailDelivery/dbo/BPEL_Proc/" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:db="http://xmlns.oracle.com/pcbpel/adapter/db/RetailDelivery/dbo/BPEL_Proc/" elementFormDefault="qualified">
<element name="InputParameters">
<complexType>
<sequence>
<element name="WorkFlowId" type="int" db:index="1" db:type="INT" minOccurs="0" nillable="true"/>
<element name="Err" type="int" db:index="2" db:type="INT" minOccurs="0" nillable="true"/>
<element name="StateID" type="int" db:index="3" db:type="INT" minOccurs="0" nillable="true"/>
</sequence>
</complexType>
</element>
<element name="OutputParameters">
<complexType>
<sequence>
<element name="WorkFlowId" type="int" db:index="1" db:type="INT" minOccurs="0" nillable="true"/>
<element name="Err" type="int" db:index="2" db:type="INT" minOccurs="0" nillable="true"/>
<element name="StateID" type="int" db:index="3" db:type="INT" minOccurs="0" nillable="true"/>
</sequence>
</complexType>
</element>
</schema>
and this is .xsl for data transformations
<xsl:template match="/">
<db:InputParameters>
<db:WorkFlowId>
<xsl:if test="/ns0:Customer_Object/ns0:input_number/@xsi:nil">
<xsl:attribute name="xsi:nil">
<xsl:value-of select="/ns0:Customer_Object/ns0:input_number/@xsi:nil"/>
</xsl:attribute>
</xsl:if>
<xsl:value-of select="/ns0:Customer_Object/ns0:input_number"/>
</db:WorkFlowId>
</db:InputParameters>
</xsl:template>
</xsl:stylesheet>
where input_number is defined as Int.
The problem is
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PD_Tables_Populate' failed due to: Unimplemented object conversion.
Conversion of type 6014 whose JDBC type is OTHER to a Java object is not supported.
An attempt was made to convert type 6014 to a Java object using an unsupported JDBC type: OTHER.
Use a data type with a supported JDBC type.
where 6014 is actually the value i am filling in input_number field. The issue is that if i create new application and using the same db adapter it is working, but for some reason it is giving me this error for the current application.
I'm using the same DB connection for calling other procedures and they are working with the same application.
Any help will be appreciated! Thanks in advance!
The problem was in the DB Adapter. After re-deploying it and delete/create data source it is working correctly now.
Edited by: Huku on Aug 29, 2011 1:04 PM