Oracle Database Gateways (DG4MSQL, DG4DRDA, DG4SYBS, DG4TERA, DG4IFMX, DG4ODBC) and Locking on Non-Oracle Databases
(Doc ID 1380465.1)
Last updated on FEBRUARY 01, 2019
Applies to:
Oracle Database Gateway for SQL Server - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]Oracle Database Gateway for Informix - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]
Oracle Database Gateway for Sybase - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]
Oracle Database Gateway for DRDA - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]
Oracle Database Gateway for Teradata - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 26-NOV-2013***
Symptoms
By default every Oracle database gateway starts a dedicated transaction as soon as it connects to the foreign database. So even when you are just selecting data then locking of the remote tables might take place.
Changes
Starting with 11.1.0.6 a couple of fixes were released <Bug:7417128> and <Bug:8204019> that introduced new gateway parameters impacting the locking mechanism of the gateway.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |