The Oracle GoldenGate Extract process calls the DB2READLOG function in the Administrative API to read the transaction log files of a DB2 LUW source database. In addition to DB2READLOG, Extract uses a small number of other API routines to check the source database configuration on startup.

The Oracle GoldenGate Replicat process uses the DB2 CLI interface on a DB2 LUW target database. For instructions on installing this interface, see the DB2 documentation.

The database can reside on a different server from the one where Oracle GoldenGate is installed, so long as the database is defined locally. For example, the following enables you to use database mydb locally with data that is on abc123:

catalog tcpip node abc123 remote abc123.us.mycompany.com server 00000
catalog db mydb as abc123 at node abc123 AUTHENTICATION server

The DB2 Universal Database has an internal trace facility called db2trc, which acquires Interprocess Communication resources (IPC) (both semaphore and shared memory). Even though a DB2 trace is not turned on, it may issue semget() calls to the operating system. These calls fail since no IPC resources are acquired so you must issue the following command on the DB2 client:

db2trc alloc 

For best performance for DB2 clients with a local database, Oracle recommends that you create a local node catalog instead of TCP/IP when connecting Oracle GoldenGate to a database that resides on the same machine. This is because local node uses IPC, which is much faster than a TCP/IP node that uses a socket API to access the local database.

To connect to DB2 LUW remotely from another system, you must use the following driver packages from IBM:

• IBM Data Server Runtime Client

• IBM Data Server Driver Package (DS Driver)

• IBM Data Server Client

The IBM Data Server Driver for ODBC and CLI (CLI Driver) is not supported for DB2 LUW.