Using Non-Default Constructor with SQL Object Type Fails With "Inconsistent java and sql object types"
(Doc ID 2360186.1)
Last updated on OCTOBER 17, 2022
Applies to:JDBC - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 11.2 to 12c]
Information in this document applies to any platform.
Given the following scenario:
* Using a SQL object type
* Using an associated array of that type
* After the fact, a new attribute is added to that object type
* A non-default constructor is created to give the option of filling in a default value for that new attribute.
Working with that non-default constructor is successful when it is called directly from PL/SQL using SQL*Plus.
However, that non-default constructor fails with the following error when called from JDBC:
The problem reproduces with the 184.108.40.206, 220.127.116.11, and 18.104.22.168 JDBC driver.
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