DB2 for i
DB2 LUW
DB2 z/OS
MySQL
SQL Server
Teradata
Topics:
The upgrade instructions perform a minimal upgrade only to deploy the updated core Oracle GoldenGate functionality, without implementing any of the major new 12c (12.3.0.1) features at this time, such as coordinated Replicat, updated globalization support, new SQL-92 defaults, and enhanced security features. The best practice is to perform a minimal upgrade first, so that you can troubleshoot more easily in the event that any problems arise. Once you know your environment is upgraded successfully, you can implement the new functionality.
If you are upgrading multiple Extract processes that operate in a consolidation configuration (many sources to one target), follow these steps fully to upgrade one Extract at a time.
All Replicat installations should be upgraded at the same time. It is critical to ensure that all trails leading to all Replicat groups on all target systems are processed until empty, according to these instructions.
WARNING:
The hash calculation used by the @RANGE function to partition data among Replicat processes has been changed. This change is transparent, and no re-partitioning of rows in the parameter files is required, so long as the upgrade is performed as directed in these instructions. To ensure data continuity, make certain to allow all Replicat processes on all systems to finish processing all of the data in their trails before stopping those processes, according to the upgrade instructions. Note that if the Replicat processes are not upgraded all at the same time, or the trails are not cleaned out prior to the upgrade, rows may shift partitions as a result of the new hash method, which may result in collision errors.
For more information on obtaining the Oracle GoldenGate distribution for heterogeneous databases, see Understanding and Obtaining the Oracle GoldenGate Distribution.
Even though you may only be upgrading Extract or Replicat, rather than both, all processes are involved in the upgrade. All processes must be stopped in the correct order for the upgrade, regardless of which component you upgrade, and the trails must be processed until empty.
(Source and target systems) Back up the current Oracle GoldenGate installation directory on the source and target systems, and any working directories that you have installed on a shared drive in a cluster (if applicable).
(Source and target systems, as applicable) Expand version 12c (12.3.0.1) of Oracle GoldenGate into a new directory on each system (not the current Oracle GoldenGate directory). Do not create the sub-directories; just complete the steps to the point where the installation files are expanded.
(Source system) Stop user activity on objects in the Oracle GoldenGate configuration.
(Source system) In GGSCI on the source system, issue the SEND EXTRACT command with the LOGEND option until it shows there is no more data in transaction log to process.
GGSCI> SEND EXTRACT group LOGEND
(Source system) In GGSCI, stop Extract and data pumps.
GGSCI> STOP EXTRACT group
(Target systems) In GGSCI on each target system, issue the SEND REPLICAT command with the STATUS option until it shows a status of "At EOF" to indicate that it finished processing all of the data in the trail. This must be done on all target systems until all Replicat processes return "At EOF."
GGSCI> SEND REPLICAT group STATUS
(Target systems) In GGSCI, stop all Replicat processes.
GGSCI> STOP REPLICAT group
(Source and target systems) In GGSCI, stop Manager on the source and target systems.
GGSCI> STOP MANAGER
If you want to upgrade the source or target database, or both, do so at this time according to the upgrade instructions provided by the database vendor. Make certain to start the databases after the upgrade, but do not permit transactions on the objects in the Oracle GoldenGate configuration.
(Source and target systems) Move the expanded Oracle GoldenGate files from the new directory to your existing Oracle GoldenGate directory on the source and target systems.
(DB2 for i) Run ggos400install without arguments. For an upgrade, no arguments are necessary; however, if you change the library, the old library is left on the system until you remove it. For more information about ggos400install, see Using Oracle GoldenGate for Heterogeneous Databases.
(Target systems, if upgrading Replicat from version 11.2.1.0.0 or earlier only) In GGSCI on each target system, issue the following commands to upgrade the Replicat checkpoint tables on those systems. This step updates the table definition.
GGSCI> DBLOGIN {[SOURCEDB data_source] |[, database@host:port] |USERID {/ | userid}[, PASSWORD password] [algorithm ENCRYPTKEY {keyname | DEFAULT}] |USERIDALIAS alias [DOMAIN domain] |[SYSDBA | SQLID sqlid][SESSIONCHARSET character_set]}
GGSCI> UPGRADE CHECKPOINTTABLE [owner.table]
Note:
owner.table can be omitted if the checkpoint table was created with the name listed with CHECKPOINTTABLE in the GLOBALS file.
(Source and target systems) Updates to the trail version, the checkpoint storage format, and integrated capture require that you perform the following steps:
In GGSCI, alter the primary Extract process and the associated data-pump Extract processes to write to a new trail sequence number. The command should return "Rollover performed."
GGSCI> ALTER EXTRACT group ETROLLOVER
In GGSCI, issue the INFO EXTRACT command with DETAIL for the primary Extract and the data pumps to verify the trail sequence number.
GGSCI> INFO EXTRACT group, DETAIL
In GGSCI, reposition the data pumps and the Replicat processes to start at the new trail sequence number.
GGSCI> ALTER EXTRACT pump, EXTSEQNO seqno, EXTRBA RBA
GGSCI> ALTER REPLICAT group, EXTSEQNO seqno, EXTRBA RBA
(Source system if not upgrading Extract) Add the SOURCECHARSET parameter to the Replicat parameter file. Specify the character set of the source database with this parameter. For more information, see Reference for Oracle GoldenGate.
(Source system if not upgrading Replicat) If you are not upgrading Replicat on the target systems at this time, add the following parameter to the Extract parameter file to specify the version of Oracle GoldenGate that is running on the target. This parameter causes Extract to write a version of the trail that is compatible with the older version of Replicat.
{EXTTRAIL | RMTTRAIL} file_name FORMAT RELEASE major.minor
where: version specifies an Oracle GoldenGate release version. major is the major version number, and minor is the minor version number, such as 11.2. Make certain to include the dot.
(Oracle GoldenGate upgrades on DB2 z/OS) You might need to re-set the "a" attribute for the Extract process and its DLLs to APF-authorize them to use the privileged API. For more information, see the installation instructions in Using Oracle GoldenGate for Heterogeneous Databases.
If you made copies of the parameter files to make parameter changes, move the new parameter files into the Oracle GoldenGate directory where the old parameter files were stored, and give them the same names as the old parameter files. If using case-sensitivity support, make certain that you either added NOUSEANSISQLQUOTES to your parameter files, or that you ran the convprm utility to convert the quotes as required. See "Upgrade Considerations if Using Character-Set Conversion" for more information.
In GGSCI, start the Oracle GoldenGate processes on the source and target systems in the following order.
GGSCI> START MANAGER GGSCI> START EXTRACT group GGSCI> START EXTRACT pump GGSCI> START REPLICAT group
If you need to restore any log files, Extract will abend with an error that indicates the log to restore. Restore the logs back to, and including that log, and then restart Extract.