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
Transaction rollback after every OracleTransaction block
Good morning,
We are using traditional ado.net SQL via 32 bit odp.net in a .NET 4 solution. We are noticing what appears to be a rollback statement issued after block of SQL statements within an OracleTransaction. Switching over to TransactionScope from OracleTransaction appears to fix the problem as well as going back to the .NET 2 Microsoft Oracle driver. At this point going back to the Microsoft driver is not an option as it is no longer supported by Microsoft going forward. Is anyone aware of a way to configure odp.net to not issue a rollback statement after every SQL statement(s) without having to switch everything over to using TransactionScope? Thank you.
We are using traditional ado.net SQL via 32 bit odp.net in a .NET 4 solution. We are noticing what appears to be a rollback statement issued after block of SQL statements within an OracleTransaction. Switching over to TransactionScope from OracleTransaction appears to fix the problem as well as going back to the .NET 2 Microsoft Oracle driver. At this point going back to the Microsoft driver is not an option as it is no longer supported by Microsoft going forward. Is anyone aware of a way to configure odp.net to not issue a rollback statement after every SQL statement(s) without having to switch everything over to using TransactionScope? Thank you.
Tagged:
This discussion has been closed.