1. Oracle GoldenGate Classic Documentation
  2. Install and Patch
  3. Prerequisites for Installing Oracle GoldenGate for DB2 for i
  4. Prerequisite Setup the DB2 for i System

Prerequisite Setup the DB2 for i System

Follow these steps before you begin installing Oracle GoldenGate for a DB2 for i system.

Note:

The user profile running the install must have authority to the RSTOBJ command.

  1. On the system where Oracle GoldenGate is to be installed, create a directory for Oracle GoldenGate.
    - MKDIR DIR('/GoldenGate')
  2. You can create a library for Oracle GoldenGate on the installation system, or you can create it through the installation script that you will run later in these steps.
    - CRTLIB LIB(goldengate) TEXT('Oracle GoldenGate Product Library') ASP(1)
  3. Unzip the downloaded file on your system.
  4. FTP the resulting tar file from that system to the folder that you created on the DB2 for i installation system.
    ftp IBMi_IP_address 
.
User (system:(none)):userid 
. 
331 Enter password. 
. Password: password . 
230 userid logged on. . 
ftp> bin 
. 
ftp> cd goldengate 
. 
ftp> put install_file 
. 
ftp> quit
  5. (If you created a library) From a 5250 terminal session, change your current library to the Oracle GoldenGate library.
    CHGCURLIB Oracle_GoldenGate_ library
  6. Run a QP2TERM terminal session.
    - CALL QP2TERM
  7. Extract the installation objects from the tar file.
    tar -xf tar_file
  8. In the Oracle GoldenGate directory, run the shell script ggos400install. 
    ggos400install -l goldengate

    The default is to install the required objects into the current library (set in the preceding steps), but you can create a library by using the -c option. Additional options are available.

    Note:

    There must be a separate Oracle GoldenGate library for each Oracle GoldenGate directory. The install script checks for this condition and will prevent installation to the same library that another installation is using. The reason for this is to prevent mismatches between the Oracle GoldenGate installation and the OGGPRCJRN *SRVPGM object.

    Syntax:

    ./ggos400install [-h] [-f] [-u userid] [[-a aspname] | [-n aspnum]] [-c|-l library name]

    Options:

    • -h shows this usage help.

    • -f forces a change to a new installation library. This argument only affects an existing installation.

    • -u userid specifies the userid that will own the installation.

    • -a aspname specifies the name of the ASP where objects will be restored. If no aspname is provided, the system asp is assumed. This option cannot be used with -n.

    • -n aspnum specifies the number of the user asp where the objects will be restored. This option cannot be used with -a.

    • -c library specifies the name of the library where the objects will be restored. The library will be created.

    • -l library specifies the name of the library where the objects will be restored. The library must exist. If a library is not specified for a new installation, the installer will attempt to use the current library of the user that is running the installer. If a library is not specified for an existing installation, the installer will attempt to use the library that is set in the oggprcjrn.srvpgm link.

    Note:

    If Oracle GoldenGate is reinstalled, you must run ggos400install again. On a reinstall, ggos400install will recognize the prior configuration, so no arguments are needed. If the oggprcjrn.srvpgm link is changed or removed, ggos400install must be run again with the Oracle GoldenGate installation library specified by the link.

  9. Exit QP2TERM.
    - F3

    Note:

    On an DB2 for i system, it is not necessary to create any working directories in the Oracle GoldenGate installation directory. The ggos400install script performs this task.

  10. Install Oracle GoldenGate on the DB2 for i database server, see Installing for all Platforms.