5 Managing the Zero Downtime Migration Service
Perform Zero Downtime Migration service life cycle operations using
zdmservice
.
Starting and Stopping the Zero Downtime Migration Service
You must start the Zero Downtime Migration service before you can migrate your databases using Zero Downtime Migration.
Start the Zero Downtime Migration service, zdmservice
, as user
zdmuser, with the following command.
zdmuser> $ZDM_HOME/bin/zdmservice start
If you must stop the Zero Downtime Migration service, run the following command.
zdmuser> $ZDM_HOME/bin/zdmservice stop
Checking Zero Downtime Migration Service Status
Check the status of the Zero Downtime Migration to see if it is running, and other service details.
To check the Zero Downtime Migration service status use the following command.
zdmuser> $ZDM_HOME/bin/zdmservice status
---------------------------------------
Service Status
---------------------------------------
Running: true
Tranferport: 5000-7000
Conn String: jdbc:mysql://localhost:8897/
RMI port: 8895
HTTP port: 8896
Wallet path: /u01/app/zdmbase/crsdata/fopds/security
Updating Zero Downtime Migration Software
If you already have Zero Downtime Migration software installed on a host, you can update it to the latest release. Zero Downtime Migration software updates give you the latest fixes while retaining existing job information, metadata, and log files.
Before you begin the software update, review the following requirements.
-
Updating from Zero Downtime Migration 19c to 21c can only be done from the latest Zero Downtime Migration 19c software kit. Verify your 19c software kit using the following command:
zdmuser> $ZDM_HOME/bin/zdmcli -build full version: 19.8.0.0.0 label date: 200907 ZDM kit build date: Thu Sep 24 06:22:07 PDT 2020
-
Verify that your existing Zero Downtime Migration software install location has at least 15GB free space.
-
Verify that you have enough space to back up the existing Zero Downtime Migration home (
ZDM_HOME
) andZDM_BASE
to the software download location. -
Important: Run the update script from outside of the currently installed Zero Downtime Migration home.
Running the script from within a Zero Downtime Migration home results in home install and uninstall failures and leaves the service in an inconsistent state.
-
The path specified in
ziploc
should have read/write access for zdmuser. -
All of the commands in the following procedure should be run as the existing Zero Downtime Migration software owner. For example, run as
zdmuser
in the examples that follow.
Uninstalling Zero Downtime Migration Software
Remove Zero Downtime Migration software from the Zero Downtime Migration service host.
Performing a Silent Update or Deinstallation
You can skip the confirmation prompt during Zero Downtime Migration software update or deinstallation to ensure these operations run smoothly.
A -silent
option is available for zdminstall.sh
update
or deinstall
operations to avoid being
asked for confirmation, as shown in the following examples.
Example of silent update:
zdmuser> cd zdm_download_directory
zdmuser> unzip zdmversion.zip
...
zdmuser>./zdminstall.sh update -silent oraclehome=absolute_path_to_zdm_home
ziploc=zdm_software_location -zdm
Example of silent deinstall:
zdmuser> $ZDM_HOME/bin/zdmservice deinstall -silent
Setting the MySQL Port
You can discover and set the port number that Zero Downtime Services uses for MySQL.
MySQL Default Port Number
Zero Downtime Migration uses MySQL internally, configuring it by default on port 3306. If a port number is not specified and the default is not available, Zero Downtime Migration increases the port value by one and retries up to five times.
Finding the Current Port Number
Run zdmservice status
to see the current MySQL port number in the
connection string, as shown here.
zdmuser> $ZDM_HOME/bin/zdmservice status
Conn String: jdbc:mysql://localhost:8897/
Changing the Port Number
You can change this default to another value using the zdmservice modify
mysqlPort=port
option.
zdmuser> $ZDM_HOME/bin/zdmservice modify mysqlPort=port