Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.9K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.5K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.2K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 154 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 402 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
Jdev 12c - setting db proxy user
FYI
OracleConnection.openProxySession() behaviour has changed between ojdbc6 and ojdbc7 drivers(and I didn't found this is documented somewhere).
So if you are using db proxy users in 12c ADF application, then you must invoke conn.autoCommit(false) after setting proxy user(because in ojdbc7, returned proxy connection will have this value set to true).
Dario
Comments
-
It is documented.
"The
Oracle.connect()method defaults to afalsesetting of the auto-commit flag. However, it also has signatures to set it explicitly. In the Oracle JDBC implementation, the auto-commit flag defaults totrue." -
Well, this is documentation for sqlj and first sentence just confirms what I said(that auto-commit by default should be false)
Just to clarify my original post:
When you retrieve jdbc connection in adf application(for example, in app module impl class), that connection already has autocommit=false (because framework will set this property)
Difference between adf 11.x and 12.x is in setting db proxy user (by using conn.openProxySession() ) :
In 11.x (which uses ojdbc6 driver) invocation of openProxySession() method will preserve autocommit=false
In 12.x (which uses ojdbc7 driver) invocation of openProxySession() method will reset autocommit to true (and adf app will not work correctly with this setting)
Dario
-
ojdbc7.jar is based on JDBC 4.1 and JDBC 4.1 still sets auto-commit to true by default.
"The default is for auto-commit mode to be enabled when the Connection object is
created."
Could auto commit be false for the PROXYTYPE_USER_NAME specified?
-
CONNECTION_PROPERTY_AUTOCOMMIT_DEFAULT is true in both 11g and 12c.
Is setting of false documented?