Version: 19c classict to 21.9 Microservices migration
DB : Oracle 19c
OS : RHEL 7.9
I am currently doing migration of Goldengate 19c classic architecture implementations to 21c Microservices architecture.
I have a server with 19C GG classic installed. It has 8 extracts with corresponding pumps and 10 replicats.
The Extracts+pumps and Replicats are of mixed scenarios as described below:
For some extract+Pumps, it Sends trails to servers where GG classic software is still installed.
For some extract+Pumps, it Sends trails to servers where GG microservices software installed.
Similarly,
This server has replicats which receives trails from pumps which are still in 19c classic architecture.
It has replicats which receives trails from distribution paths which are already in 21c Microservices.
Multiple scenarios are involved:
For eg, for those servers where the source servers are already in Microservices, first, I need to make a note trail sequence number and RBA and the the distribution paths need to rebuilt
for those source servers which are still in classic, I need to change the mgrport in the pump parmameter file to the new one (9003 in my case)
etc
Because of multiple scenarios, I thought of migrating Extract+Pump, Replicats individually.
But, in the help menu of the java-based migration utility, I do not see the option to specify extract or replicat names (individually).
$ export OGG_HOME=/u02/oracle/goldengate/version/21.3
$ export LD_LIBRARY_PATH=$OGG_HOME/lib:$LD_LIBRARY_PATH
$ export PATH=/u02/oracle/agent/agent_13.4.0.0.0/jdk/bin:$PATH
$
$ cd /u02/oracle/software/images/gg/goldengate_ma_migration_tool
$
$ java -jar ogg-migration-package-21.1.0.0.0.jar -help
************************************************************************************
** Oracle GoldenGate Classic to Microservices Migration Utility **
** Version 21.1.0.0.0 Build 73 at Tue Feb 08 04:27:02 UTC 2022 **
** **
** Copyright (C) 1995, 2021, Oracle and/or its affiliates. All rights reserved. **
** **
** Operating system character set identified as UTF-8. **
************************************************************************************
Usage:
-classicHome <value> -debug -dryrun
Where:
-classicHome Specifies the Classic Install Home Directory.
-debug Specifies the Debug Level Logging.
-dryrun Specifies the Simulate Migration but do not Migrate (Do a Dry Run).
$