RDBPROD: Unexpected Deadlocks Updating Rdb Tables Using JDBC Thin Server (Doc ID 742146.1)

Last updated on AUGUST 03, 2016

Applies to:

Oracle Rdb Server on OpenVMS - Version 7.2.1.3 and later
Oracle JDBC for Rdb - Version 7.2 and later
Information in this document applies to any platform.

Goal

Using the Oracle JDBC for Rdb Thin server to update an Oracle Rdb database, many deadlocks are reported. The same application connected to an Oracle RDBMS database does not report any deadlocks.

Since the default isolation level is READ COMMITTED on Oracle RDBMS and READ SERIALIZABLE on Oracle Rdb, the following information has been added to the configuration file of the Application Server (JBOSS) for all transactions:

<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>


In spite of this, deadlocks are still reported.

Questions:
1. how to reproduce the Oracle isolation level?
2. how to confirm the isolation level of the transactions?

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms