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.
