Oracle Database Provider for DRDA 12c Release 1 (18.104.22.168.0) is now available.
Find it in the Gateways download available with Oracle Database 12c Release 1 (12.1.02.0) - Enterprise Edition
Database Provider for DRDA
Leverage your existing IBM DB2 applications for your Oracle migrationThe Oracle Database Provider for DRDA is a network front-end that enables client programs to connect to Oracle Database using the Distributed Relational Database Architecture (DRDA) protocol. This enables existing DB2 application customers to leverage their current investment in application technology while migrating from DB2 server.
Applications that are written to use the DRDA protocol, generally do not need to change their existing code to connect to Oracle Database through Database Provider for DRDA. Only minimal application configuration changes are necessary to successfully change the client application environment to use Oracle Database.
The Database Provider for DRDA code usually runs on the target database machine, but may also run on a middleware machine. There is never any need to install extra software on a mainframe machine, even when the client program is running on the mainframe.
More about DRDAClient programs or systems that use the DRDA protocol are called Application Requesters (ARs). Server programs or systems that provide DRDA protocol services, such as the Oracle Database Provider for DRDA, are called Application Servers (AS).
Applications may be written directly as ARs, or they use an intermediate interface such as JDBC or precompiled Cobol. In this case the intermediate interface acts as the AR.
Remote v Native ApplicationsA "remote" application accesses the DRDA protocol itself. It may be connected to any Application Server on an accessible network.
A "native" application talks directly to a DB2 server using a local and proprietary RPC mechanism. The DB2 server may be either an actual DB2 database, or the DB2 Connect product. Either of these can then connect to a remote Database Provider for DRDA, and effectively redirect database accesses to a remote database. Using the DB2 Connect product is normally more cost-effective, due to both licensing consideration, and the disk and memory footprint needed by a DB2 database.
Native Application Remote Connectivity
Replacing Oracle Access Manager for AS/400Oracle Access Manager for AS/400 is a discontinued product. Access Manager was a client-side product that enabled native DB2/400 applications to connect to Oracle Database as if it were a remote DB2 database. The Access Manager ran on the AS/400 as a DB2/400 API plug-in and used an OCI method to connect to Oracle Database, as illustrated below.
DB2/400's plug-in interface API behaves like DRDA, and appears to the system as an application requester that uses OCI and SQL*Net internally to connect to an Oracle Database. Hence the complex arrangement of DB2/400 and Oracle Access Manager can be more simply and cost-effectively replaced with DB2/400 and Oracle Database Provider for DRDA. This approach is illustrated below.
After downloading Oracle Database Provider for DRDA, you may wish to look through the white paper Installation Verification Procedure for Oracle Database Provider for DRDA