Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 584 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 45 Data Integration
- 45 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 666 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Does oracle support TRANSACTION_READ_UNCOMMITTED level?

426225
Member Posts: 3
I am using oc4j drivers with jdbc for oracle 9i
I could not set the transaction isolation level to TRANSACTION_READ_UNCOMMITTED.
Does oracle support this transaction level ?
(SQL Server support it)
Here is the stack trace of the error:
java.sql.SQLException: READ_COMMITTED et SERIALIZABLE sont les seuls niveaux de transaction valides
java.sql.SQLException: READ_COMMITTED et SERIALIZABLE sont les seuls niveaux de transaction valides
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.driver.OracleConnection.setTransactionIsolation(OracleConnection.java:1681)
Thanks for any help...
I could not set the transaction isolation level to TRANSACTION_READ_UNCOMMITTED.
Does oracle support this transaction level ?
(SQL Server support it)
Here is the stack trace of the error:
java.sql.SQLException: READ_COMMITTED et SERIALIZABLE sont les seuls niveaux de transaction valides
java.sql.SQLException: READ_COMMITTED et SERIALIZABLE sont les seuls niveaux de transaction valides
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.driver.OracleConnection.setTransactionIsolation(OracleConnection.java:1681)
Thanks for any help...
Comments
-
Mahmoud,
The error message, you have posted, seems very clear -- the only valid values are READ_COMMITTED and SERIALIZABLE. This is also documented in the "Oracle9i JDBC Developers Guide and Reference", chapter 19 [Coding Tips and Troubleshooting], in the section entitled "Transaction Isolation Levels and Access Modes". Here is an excerpt:
the Oracle server supports only the TRANSACTION_READ_
COMMITTED and TRANSACTION_SERIALIZABLE transaction isolation levels
As someone who moved from Oracle to Informix, I can tell you from my experience, that different RDBMS's have the same functions, but each works differently. So while you probably needed to use the TRANSACTION_READ_UNCOMMITTED isolation level with "SQL Server", you don't need it for Oracle.
What you need to do is forget how you do things with "SQL Server", and learn how to do things the Oracle way. As you have seen, trying to transfer "SQL Server" code to Oracle doesn't always work.
The Oracle documentation is available from
http://tahiti.oracle.com
Good Luck,
Avi.
This discussion has been closed.