Hi all,
I am leaving this info here, as googling "ORA-04043 ojdbc 12.2 returning
clause" leads pretty quickly to this thread (and accidentally, the issue(?)
persist via jOOQ).
Apparently there is an inconsistency in the new driver. Namely, I observe
the following behaviour:
// schema *with *quotes, *with *returning clause -> does not work with
driver 12.2 'ORA-04043: object "TESTER" does not exist', but works with
driver 12.1
connection.prepareStatement("insert into *\"*TESTER*\"*.\"JDBC_TEST\"
(\"ID\", \"BLUBB\") values (?, ?)"*, new String[]{"ID"}*);
// schema *with *quotes, *without *returning clause -> OK with both drivers
connection.prepareStatement("insert into *\"*TESTER*\"*.\"JDBC_TEST\"
(\"ID\", \"BLUBB\") values (?, ?)");
// schema *without *quotes, *with *returning clause -> OK with both drivers
connection.prepareStatement("insert into TESTER.\"JDBC_TEST\" (\"ID\",
\"BLUBB\") values (?, ?)"*, new String[]{"ID"}*);
// schema *without *quotes, *without *returning clause -> OK with both
drivers
connection.prepareStatement("insert into TESTER.\"JDBC_TEST\" (\"ID\",
\"BLUBB\") values (?, ?)");
Investigation with Oracle ongoing.
Cheers,
Daniel
On Friday, 22 June 2018 08:43:35 UTC+2, Paul Hamer wrote:
>
> Hi Lukas,
>
> Thank you for coming back to this. I have indeed heard/read elsewhere that
> the Oracle OJDBC drivers are not fully backward compatible to their own
> Oracle databases. But, as you suggested back when I posted my issue,
> specifying Settings.renderSchema = false solved the problem. We haven't had
> any issues since then (still using ojdbc8 + 11g). Since we plan to upgrade
> to Oracle 12.2 before releasing our software, we intend to stick to ojdbc8.
>
> Cheers,
> Paul
>
>
> On Friday, June 15, 2018 at 3:21:13 PM UTC+2, Lukas Eder wrote:
>>
>> Hi Paul,
>>
>> Finally an update from my side on this issue - in case you're still
>> encountering it. Another client has investigated this further and found
>> that the problem seems to relate to a driver / server version mismatch.
>> According to the Oracle documentation, these are the correct server
>> versions / driver versions / JDK versions combinations:
>>
>>
>> *Oracle Database version* *JDBC Jar files specific to the release*
>> 12.2 or 12cR2 *ojdbc8.jar* with JDK 8
>> 12.1 or 12cR1 *ojdbc7.jar* with JDK 7 and JDK 8
>> *ojdbc6.jar* with JDK 6
>> 11.2 or 11gR2 *ojdbc6.jar* with JDK 6, JDK 7, and JDK 8
>> (Note: JDK7 and JDK8 are supported in 11.2.0.3 and 11.2.0.4 only)
>> *ojdbc5.jar* with JDK 5
>> See:
>>
>> http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-faq-090281.html#01_03_1
>>
>> Since you're using 11g, you should probably also use ojdbc6, not ojdbc8.
>> The other client reported that on 12.1 using ojdbc8, this fully qualified
>> sequence in INSERT statement issue was the only issue they have
>> encountered, and they cannot backport the JDBC driver because of the
>> requirements imposed by their Weblogic versions.
>>
>> I hope this helps,
>> Lukas
>>
>
--
You received this message because you are subscribed to the Google Groups "jOOQ
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
