X

Welcome to All Things Data Integration: Announcements, Insights, Best Practices, Tips & Tricks, and Trend Related...

Zero Down Time (ZDT) Patching for Oracle GoldenGate

Thomas Vengal
Director, Product Management

 

This document explains how to apply a patch or upgrade an OGG environment without taking any downtime.  This assumes that OGG is already up and running and that the user is already very familiar with how OGG works, and the actual upgrade process.  Like any mission critical, 24x7 environment, this expectation is that the user takes the necessary precautions to test this process prior to implementing it in production, and is aware of any differences between versions.  All of these items are covered in other documents. 

Terminology

“New” – This refers to the new OGG installation.   This “new” environment is where everything will be running once you have completed the procedure.

“Old” – This refers to the old OGG installation.  This “old” environment is the existing OGG installation that you want to upgrade.  After the process is completed, you will be removing this installation.

Patching OGG Homes where there are Extract(s) running.

  1. Install the new OGG version into a new directory. This location will be referred to as the “new” OGG installation.
  2. In the new installation
    1. Apply any necessary patches to bring the releases to the most recent bundle patch, and then apply any required one-off patches on top of that.
    2. Create new Extract process(es) with different names than the old OGG environment.
    3. Create a new set of trail files (different names than the old OGG installation.
    4. Copy the parameter files from the old installation into the new one.  Modify them to account for new directories, names, and address any deprecated / modified parameters.
  3. On the target
    1. Create a new Replicat to receive data from the new OGG installation.
  4. In the new Installation
    1. Start the Extract
    2. Start the Extract pump (if necessary)
  5. In the old installation
    1. Wait.   How long to wait for?  It depends.  When you started the new Extract in step 4a, it will not process any transactions that were open when it was started.  You will want to wait until any open transactions during that time are closed.  SEND EXTRACT … SHOWTRANS may help in this case.
    2. Stop the Extract
  6. On the target
    1. If the old Replicat is not using a checkpoint table ,add one for it.
    2. Once the Replicat from the old installation is at EOF (SEND REPLICAT … GETLAG) stop the old replicat.
    3. Start the new replicat using START REPICAT … AFTERCSN [scn].  Where the [scn] is the log_cmplt_csn column from the checkpoint table for the old replicat. This will tell the new replicat to pick up right where the old replicat left off.
  7. In the old installation
    1. Stop the extract pump (optional)
  8. Clean up the old installation and remove it.

 

Patching OGG Homes where there are Replicat(s) running.

  1. Install the new OGG version into a new directory. This location will be referred to as the “new” OGG installation.
  2. In the new installation
    1. Apply any necessary patches to bring the releases to the most recent bundle patch, and then apply any required one-off patches on top of that.
    2. Create new Replicat process(es) with different names than the old OGG environment.  The new replicat will read from the existing trail files.
    3. Copy the parameter files from the old installation into the new one.  Modify them to account for new directories, names, and address any deprecated / modified parameters.
  3. In the Old installation.
    1. If the old Replicat is not using a checkpoint table ,add one for it.
    2. Stop the Replicat when it is at EOF (SEND REPLICAT … GETLAG)
  4. In the New Installation
    1. Start the new replicat using START REPICAT … AFTERCSN [scn].  Where the [scn] is the log_cmplt_csn column from the checkpoint table for the old replicat. This will tell the new replicat to pick up right where the old replicat left off.
  5. In the old installation
    1. Clean up the old replicat and remove it.

 

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.