{"id":31203,"date":"2024-02-25T21:06:27","date_gmt":"2024-02-25T20:06:27","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=31203"},"modified":"2024-04-06T21:40:15","modified_gmt":"2024-04-06T19:40:15","slug":"physical-online-migration-to-exacc-with-oracle-zero-downtime-migration-zdm","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/physical-online-migration-to-exacc-with-oracle-zero-downtime-migration-zdm\/","title":{"rendered":"Physical Online Migration to ExaCC with Oracle Zero Downtime Migration (ZDM)"},"content":{"rendered":"\n

A while ago I had been testing and blogging about ZDM, see my previous articles. And I finally had the chance to implement it at one of our customer to migrate on-premise databases to Exadata Cloud @Customer. After having been implementing Logical Offline migration with ZDM, see my previous article, https:\/\/www.dbi-services.com\/blog\/logical-offline-migration-to-exacc-with-oracle-zero-downtime-migration-zdm\/<\/a>, I had the opportunity to implement a Physical Online Migration and testing it with one database taken as pilot. In this article I would like to share with you my experience I could get from migrating an on-premises database to ExaCC using ZDM Physical Online Migration. This method will use Data Guard and we can then only use it to migrate Oracle Enterprise Edition databases. We call it Physical Online, because ZDM will create a Standby database either through a backup or with Direct Data Transfer (active duplication with rman or restore from service) and synchronise it with the primary. During all the preparation the database is still available for the application, and the maintenance windows will be shorter with less downtime. It will just be needed for the switchover operation. Of course ZDM can include non-cdb to pdb conversion which will make it a little bit longer. The Physical Online is the only ZDM method including fallback. We intended to use this method at customer side, as mandatory one for Large Oracle EE databases, and preferred one for Small Oracle EE databases.<\/p>\n\n\nRead more: Physical Online Migration to ExaCC with Oracle Zero Downtime Migration (ZDM)<\/span><\/a>\n\n\n

Introduction<\/h2>\n\n\n\n

The on-premise databases are single-tenant (non-cdb) database running for all version 19.10.<\/p>\n\n\n\n

The target databases are Oracle RAC databases running on ExaCC with Oracle version 19.21.<\/p>\n\n\n\n

The Oracle Net port used on the on-premise site is 13000 and the Oracle Net port used on the ExaCC is 1521.<\/p>\n\n\n\n

We will use ZDM to migrate the on-premise single-tenant database, to a PDB within a CDB. ZDM will then be in charge of migrating the database to the exacc using Data Guard, run datapatch, convert non-cdb database to pdb within a target cdb, upgrade Time Zone. The creation of the standby database will be done through a direct connection. Without any backup.<\/p>\n\n\n\n

Of course I have anonymised all outputs to remove customer infrastructure names. So let\u2019s take following convention.<\/p>\n\n\n\n

ExaCC Cluster 01 node 01 : ExaCC-cl01n1
ExaCC Cluster 01 node 02 : ExaCC-cl01n2
On premises Source Host : vmonpr
Target db_unique_name on the ExaCC : ONPR_RZ2
Database Name to migrate : ONPR
ZDM Host : zdmhost
ZDM user : zdmuser
Domain : domain.com
ExaCC PDB to migrate to : ONPRZ_APP_001T<\/p>\n\n\n\n

We will then migrate on-premise Single-Tenant database, named ONPR, to a PDB on the ExaCC. The PDB will be named ONPRZ_APP_001T.<\/p>\n\n\n\n

<\/p>\n\n\n\n

Ports<\/h2>\n\n\n\n

It is important to mention that following ports are needed:<\/p>\n\n\n\n

\n \n
Source<\/strong><\/td>Destination<\/strong><\/td>Port<\/strong><\/td><\/tr>\n
ZDM Host<\/td>On-premise Host<\/td>22<\/td><\/tr>\n
ZDM Host<\/td>ExaCC VM (both nodes)<\/td>22<\/td><\/tr>\n
On-premise Host<\/td>ExaCC VM (scan listener and vip)<\/td>Oracle Net (1521)<\/td><\/tr>\n
ExaCC<\/td>On-premise Host<\/td>Oracle Net<\/td><\/tr>\n <\/tbody><\/table>\n<\/figure>\n\n\n\n

If Oracle Net ports are for example not opened from the Exacc to the on-premise host, the migration evaluation will immediately stopped at one of the first steps named ZDM_PRECHECKS_TGT, and following errors will be found in the log file:<\/p>\n\n\n\n

PRGZ-1132 : -eval failed for the phase ZDM_PRECHECKS_TGT with exception\nPRGZ-3176 : a database connection cannot be established from target node ExaCC-cl01n1 to source node vmonpr\nPRCC-1021 : One or more of the submitted commands did not execute successfully.\nPRCZ-2103 : Failed to execute command \"\/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_2\/bin\/tnsping\" on node \"ExaCC-cl01n1\" as user \"root\". Detailed error:\nTNS Ping Utility for Linux: Version 19.0.0.0.0 - Production on 06-FEB-2024 10:06:37\n\nCopyright (c) 1997, 2023, Oracle.  All rights reserved.\n\nUsed parameter files:\n\nUsed HOSTNAME adapter to resolve the alias\nAttempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=(PROTOCOL=tcp)(HOST=X.X.X.15)(PORT=13000)))\nTNS-12535: TNS:operation timed out\nPRCC-1025 : Command submitted on node ExaCC-cl01n2 timed out after 60 seconds..<\/code><\/pre>\n\n\n\n
If Oracle Net ports are for example not opened from the on-premise host to ExaCC, the migration evaluation will immediately stopped at one of the other steps named ZDM_PRECHECKS_SRC, and following errors will be found in the log file:<\/p>\n\n\n\n
PRGZ-1132 : -eval failed for the phase ZDM_PRECHECKS_SRC with exception\nPRGZ-3130 : failed to establish connection to target listener from nodes [vmonpr]\nPRCC-1021 : One or more of the submitted commands did not execute successfully.\nPRCC-1025 : Command submitted on node vmonpr timed out after 15 seconds...<\/code><\/pre>\n\n\n\n
<\/p>\n\n\n\n
Requirements… To be known before starting<\/h2>\n\n\n\n
There are few requirements that are needed.<\/p>\n\n\n\n
ZDM Host<\/h4>\n\n\n\n