This document describes how to upgrade to a new release of the Oracle GoldenGate data replication software for HP NonStop (Guardian).

This topic contains the following section on Upgrading Oracle GoldenGate.

1.1 Upgrading Oracle GoldenGate

Upgrading Oracle GoldenGate requires three phases: backup, installation, and migration.

  • Backup: Perform a full backup of your Oracle GoldenGate environment before installing and migrating to the latest Oracle GoldenGate release.

  • Installation: Install Oracle GoldenGate following the steps in the Installation Guide, Installing for HP NonStop (Guardian). Ensure to specify a new subvolume for your upgraded Oracle GoldenGate instance.

  • Migration: Once you have installed Oracle GoldenGate, you must migrate to the latest instance. Follow the steps in Migrating from a Previous Release of Oracle GoldenGate to complete the migration.

1.1.1 Migrating from a Previous Release of Oracle GoldenGate

Following are the steps to migrate from a previous release of Oracle GoldenGate:

  1. Bring down your current Oracle GoldenGate instance:
    TACL> RUN GGSCI
    GGSCI> STOP SYNCFILE *
    GGSCI> STOP REPLICAT *
    GGSCI> STOP EXTRACT *
    GGSCI> STOP MANAGER
    GGSCI> EXIT
    
  2. If you plan to HOTSWAP LOGGER process(s), then skip this step:

    GGSCI> STOP LOGGER.

  3. After you install Oracle GoldenGate, GGSUNPAK prompts you:
    Would you like to Migrate information from another GGS environment (Y/N): Y
    
  4. Enter your previous Oracle GoldenGate volume and subvolume:
    Enter old OGG vol.subvol or X to quit: $data01.tssoj06n
    
    PID: $Y2VX \THOR.$SYSTEM.SYS21.FUP
    STOPPED: $Y2VX
    CPU time: 0:00:00.004
    
    Copying OGG data from $DATA01.TSSOJ06N...
    
    PID: $Y2VY \THOR.$SYSTEM.SYS21.FUP
    STOPPED: $Y2VY
    CPU time: 0:00:00.015
    File Utility Program - T6553H02 - (11FEB2015)    System  \THOR
    (C)1981 Tandem (C)2014 Hewlett Packard Development Company, L.P.
    ALLOW ABENDS ON
    ALTER CONTEXT, NO AUDIT
    ALTER CONTEXT, AUDIT
    ALTER GROUP, NO AUDIT
    COPY $DATA01.TSSOJ06N.GROUP, GROUP
    1 RECORDS TRANSFERRED
    ALTER GROUP, AUDIT
    ALTER EXTCTXT, NO AUDIT
    COPY $DATA01.TSSOJ06N.EXTCTXT, EXTCTXT
    1 RECORDS TRANSFERRED
    ALTER EXTCTXT, AUDIT
    ALTER REPGRP, NO AUDIT
    ALTER REPGRP, AUDIT
    ALTER REPCTXT, NO AUDIT
    COPY $DATA01.TSSOJ06N.REPCTXT, REPCTXT
    3 RECORDS TRANSFERRED
    ALTER REPCTXT, AUDIT
    ALTER REMCTXT, NO AUDIT
    ALTER REMCTXT, AUDIT
    ALTER RMTCTXT, NO AUDIT
    ALTER RMTCTXT, AUDIT
    LOAD $DATA01.TSSOJ06N.LOGGGS, LOGGGS, SORTED
    RECORDS LOADED: 609
    ALTER LOGCONF, NO AUDIT
    ALTER LOGCONF, AUDIT
    ALTER MRKRGGS, NO AUDIT
    ALTER MRKRGGS, AUDIT
    ALTER SYNCGRP, NO AUDIT
    ALTER SYNCGRP, AUDIT
    ALTER COORDGRP, NO AUDIT
    ALTER COORDGRP, AUDIT
    
    PID: $Y2VZ \THOR.$DATA03.TSSOJ06N.SCANGRP
    Oracle GoldenGate Checkpoint Conversion
    Version 12.2.0.1.4 J06 2018-02-05 Debug System \THOR
    Copyright (C) 1995, 2018, Oracle and/or its affiliates. All rights reserved.
    
    Scanning to fixup program, params, report,and process name
    Processing GROUP
      Reads        1
      Updates      1
    Processing REPGRP
      Reads        0
      Updates      0
    Processing SYNCGRP
      Reads        0
      Updates      0
    Processing COORDGRP
      Reads        0
      Updates      0
    STOPPED: $Y2VZ
    CPU time: 0:00:00.003
    Checkpoint conversion successful
    Migration successful.
    
    $DATA03 TSSOJ06N 8>
    $DATA03 TSSOJ06N 8>
  5. If you have a running Logger process, then you are asked if you want to HOTSWAP the Logger object.

    Logger was running during migrate
    Do you want to HOWSWAP logger to the new ENV  (Y?N)
    

    If you answer yes, then the program will change to the Logger object running in the migration process installation location.

    Caution:

    You must coordinate HOTSWAP with any manual steps to upgrade BASELIB as part of the upgrade process.
  6. DUP any Obey files you use in your current Oracle GoldenGate environment. This step is particularly critical if your Obey files contain table define names or startup/shutdown commands.
  7. There are no changes to the supplied header files that require a recompile. However, with the removal of the TNS mode objects, User Exit not compiled Native must be recompiled as such. Then use NLDEXIT to link or use the new DLL method described in the reference manual.
  8. Point your applications to the new release of GGSLIB for Non Audited Logger change capture.
    GGSCI> BIND PROGRAMS, CHANGELIB

    Enter the list of applications you want to bind.

    Enter your new GGSLIB when prompted.

    Enter GO to bind your new library to your applications.

    GGSCI> LINK PROGRAMS, CHANGELIB

  9. Restart your Oracle GoldenGate components in your new environment.