StoredProcedureQuery with OUT param fails with Oracle when using more then 2 named parameters

Description

Similar procedure with 2 IN params and 1 OUT works.
Exception occurs in procedures with more then 2 IN params;
But procedure works if use positional params.

Procedure with 3 IN params and 1 OUT

Usage :

Procededure :

Exceprion :

Environment

Oracle 11g

Activity

Show:
Gail Badner
July 14, 2016, 7:08 PM

This may have been fixed by HHH-10756. Please try using 5.2.0.Final or 5.1.1-SNAPSHOT and let us know if either of those versions worked for you.

Olegs Sedacs
August 3, 2016, 11:30 AM
5.2.0 version :

Procedure signature in DB

Named procedure

Invocation

Result

Aparna Parikh
September 7, 2016, 2:56 PM

I have the exact same setup as above, and see the same exception listed above. Has this been fixed yet/is there a workaround for it?

Assignee

Unassigned

Reporter

Olegs Sedacs

Fix versions

None

Labels

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure