My Oracle Support Banner

Using Non-Default Constructor with SQL Object Type Fails With "Inconsistent java and sql object types" (Doc ID 2360186.1)

Last updated on MARCH 15, 2019

Applies to:

JDBC - Version 11.2.0.1.0 to 12.2.0.0.0 [Release 11.2 to 12c]
Information in this document applies to any platform.

Symptoms

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 11.2.0.4, 12.1.0.2, and 12.2.0.1 JDBC driver.

Changes

 

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
Symptoms
Changes
Cause
Solution
References


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