Transaction Isolation Level Settings
Specify transaction isolation level settings to set the transaction isolation level for a database. This setting prevents dirty read, repeatable read, and phantom read of the database. For more information about the transaction isolation level settings in
Adapter for JDBC, see
Transaction Isolation Level Settings.
Note:
Use a ; (semi-colon) to delimit table filter, transaction isolation level, and driver-dependent property settings. Do not enter spaces after the semi-colon. For example: TableFilter=‘<current catalog>'.‘Accounting';driverType=oci
Use the following format to specify the transaction isolation levels of the database:
transactionIsolation=value
where value is the integer value of the transaction isolation level.
For example, transactionIsolation=2, where 2 sets the TRANSACTION_READ_COMMITTED isolation level.
You can specify only one transaction isolation level for a connection. The commonly used transaction isolation levels and their values are:
Transaction Isolation Settings | Value |
TRANSACTION_READ_UNCOMMITTED | 1 |
TRANSACTION_READ_COMMITTED | 2 |
TRANSACTION_REPEATABLE_READ | 4 |
TRANSACTION_SERIALIZABLE | 8 |
For information about the transaction isolation levels supported by your database, refer to your database documentation.
If you do not specify the isolation level in the Other Properties field, the default isolation level of the database is considered. If you specify an isolation level that is not supported by the database, an error is thrown while enabling the connection.