{"id":306,"date":"2022-09-05T01:16:00","date_gmt":"2022-09-05T05:16:00","guid":{"rendered":""},"modified":"2024-07-05T18:39:45","modified_gmt":"2024-07-05T22:39:45","slug":"zdm-troubleshooting-part-2-migration","status":"publish","type":"post","link":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration","title":{"rendered":"ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC"},"content":{"rendered":"<h2 align=\"justify\"><img loading=\"lazy\" decoding=\"async\" width=\"825\" height=\"378\" alt=\"This image has an empty alt attribute; its file name is image-3.png\" src=\"https:\/\/brokedba.files.wordpress.com\/2022\/09\/image-3.png?w=1024\"><\/h2>\n<p><font style=\"font-weight: normal;\"><\/p>\n<h2 align=\"justify\">\nIntro<\/h2>\n<p><\/font><\/p>\n<p align=\"justify\" data-pm-slice=\"1 3[]\"><font face=\"Courier New\"><font face=\"Arial\"><font style=\"font-weight: normal;\">I didn\u2019t anticipate to have a series of posts around ZDM, but I had few issues that were worth sharing so here I am. T<font style=\"font-weight: normal;\">his post will describe what caused a failure of an online physical migration ExaCC right at the Data guard configuration phase. The good thing about ZDM, is as soon as any detected issue is fixed manually, the resume job action will get you going which is the perfect design for a migration solution. <\/font><\/font><\/font><\/font><\/p>\n<h3><\/h3>\n<h3><\/h3>\n<h3 align=\"justify\">&nbsp;<br \/>\n<\/h3>\n<h2 align=\"justify\">1. My ZDM environment<br \/>\n<\/h2>\n<ul>\n<li>\n<h3><font style=\"font-weight: normal;\"><strong>ZDM:<\/strong> 21.3 build <\/font><\/h3>\n<\/li>\n<\/ul>\n<p><font style=\"font-weight: normal;\"><\/p>\n<h3>\n<table border=\"1\" cellspacing=\"0\" cellpadding=\"2\">\n<tbody>\n<tr>\n<td valign=\"top\">Property&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <\/td>\n<td valign=\"top\">Source&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <\/td>\n<td valign=\"top\">Target&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <\/td>\n<\/tr>\n<tr>\n<td valign=\"top\">RAC<\/td>\n<td valign=\"top\"> NO<\/td>\n<td valign=\"top\">YES<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\">Encrypted<\/td>\n<td valign=\"top\"> NO<\/td>\n<td valign=\"top\"> YES<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\">CDB<\/td>\n<td valign=\"top\"> NO<\/td>\n<td valign=\"top\"> YES<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\">Release<\/td>\n<td valign=\"top\"> 12.2<\/td>\n<td valign=\"top\">12.2<\/td>\n<\/tr>\n<tr>\n<td valign=\"top\">Platform<\/td>\n<td valign=\"top\">On prem Linux<\/td>\n<td valign=\"top\">ExaCC<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/h3>\n<h3>\n<\/h3>\n<p><\/font><\/p>\n<h3><font style=\"font-weight: normal;\"><strong>&nbsp;<br \/>\n<\/strong><\/font><\/h3>\n<h2 align=\"justify\">Prerequisites<\/h2>\n<h3 align=\"justify\"><font style=\"font-weight: normal;\"> All the prerequisites related to the <a href=\"https:\/\/docs.oracle.com\/en\/database\/oracle\/zero-downtime-migration\/21.3\/zdmug\/installing-zero-downtime-migration-software.html#GUID-A19ADA5C-755B-468B-86BC-A6642D3F3F34\" target=\"_blank\" rel=\"noopener\">ZDM VM<\/a>, the <a href=\"https:\/\/docs.oracle.com\/en\/database\/oracle\/zero-downtime-migration\/21.3\/zdmug\/preparing-for-database-migration.html#GUID-25B07C59-8143-41CB-B431-3D9225CCFDD6\" target=\"_blank\" rel=\"noopener\">Source<\/a> and <a href=\"https:\/\/docs.oracle.com\/en\/database\/oracle\/zero-downtime-migration\/21.3\/zdmug\/preparing-for-database-migration.html#GUID-FD1B3A13-8723-4DFE-8776-B57CAC0FA38B\" target=\"_blank\" rel=\"noopener\">Target Database system<\/a> were satisfied before running the migration <\/p>\n<p><\/font><\/h3>\n<h2>Responsefile<br \/>\n<\/h2>\n<h3 align=\"justify\"><font style=\"font-weight: normal;\">Prepare a responsefile for a <font style=\"font-weight: bold;\">P<\/font>hysical <font style=\"font-weight: bold;\">O<\/font>nline <font style=\"font-weight: bold;\">M<\/font>igration with the required parameters.The parameters themselves are not important in our case. I will just point out that <font style=\"font-weight: bold;\">ZDM 21.3<\/font> now supports <font style=\"font-weight: bold;\">Data Guard Broker <\/font>configuration <\/font><\/h3>\n<pre class=\"pre codeblock\" style=\"padding: 9.5px; border-radius: 4px; border: 1px solid rgb(204, 204, 204); border-image: none; width: 789px; height: 221px; line-height: 1.4285; overflow: auto; font-size: 16px; margin-bottom: 10px; -ms-word-break: break-all; box-sizing: border-box; background-color: rgb(3, 47, 32); overflow-wrap: break-word;\"><p><font color=\"#ffffff\"><font color=\"#ffffff\"><strong>$ <\/strong><font color=\"#ffffff\"><strong>cat <font color=\"#00ff00\">physical_online_demo.rsp<\/font> | grep -v ^#\n<\/strong><font color=\"#ffffff\"><font color=\"#b1c5fe\"><strong>TGT_DB_UNIQUE_NAME=TGTCDB\nMIGRATION_METHOD=ONLINE_PHYSICAL\nDATA_TRANSFER_MEDIUM=DIRECT\nPLATFORM_TYPE=EXACC\n<font color=\"#00ff00\">ZDM_USE_DG_BROKER=<font color=\"#ef3b7d\">TRUE<\/font><\/font>\n...\n<\/strong><\/font><\/font><\/font><\/font><\/font><\/p><\/pre>\n<h3 align=\"justify\">&nbsp;<\/h3>\n<h3 align=\"justify\">Run ZDMCLI Eval command<\/h3>\n<ul>\n<li>\n<p align=\"justify\" data-pm-slice=\"1 3[]\">The <strong>eval <\/strong>command successfully ran all prechecks to ensure migration readiness, so we\u2019re good to go<\/p>\n<\/li>\n<\/ul>\n<pre class=\"pre codeblock\" style=\"padding: 9.5px; border-radius: 4px; border: 1px solid rgb(204, 204, 204); border-image: none; width: 789px; height: 215px; line-height: 1.4285; overflow: auto; font-size: 16px; margin-bottom: 10px; -ms-word-break: break-all; box-sizing: border-box; background-color: rgb(3, 47, 32); overflow-wrap: break-word;\"><p><font color=\"#ffffff\">$ZDM_HOME\/bin\/zdmcli <font color=\"#00ff00\">migrate database <font color=\"#b1c5fe\">\u2013sourcedb<\/font> SRCDB <font color=\"#ffffff\"><\/font>\n<font color=\"#b1c5fe\">-sourcenode<\/font> srcHost <font color=\"#b1c5fe\">-srcauth<\/font> zdmauth <font color=\"#ffffff\"><\/font>\n<font color=\"#b1c5fe\">-srcarg1<\/font> user:zdmuser  <font color=\"#ffffff\"><\/font>\n<font color=\"#b1c5fe\">-targetnode<\/font> tgtNode <font color=\"#ffffff\"><\/font>\n<font color=\"#b1c5fe\">-tgtauth<\/font> zdmauth <font color=\"#ffffff\"><\/font>\n<font color=\"#b1c5fe\">-tgtarg1<\/font> user:opc <\/font>\n-rsp .\/<font color=\"#00ff00\">physical_online_demo.rsp<\/font>&nbsp;<font color=\"#ef3b7d\">\u2013eval<\/font><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#ffffff\">\n<\/font><\/font><\/font><\/font><\/font><\/font><\/font><\/p><\/pre>\n<h3 align=\"justify\">\n<\/h3>\n<p><font style=\"font-weight: normal;\"><\/p>\n<h3 align=\"justify\" style=\"font-size: 16px; -webkit-font-smoothing: antialiased;\" data-pm-slice=\"1 3[]\">\n<h3 align=\"justify\" style=\"font-size: 16px; -webkit-font-smoothing: antialiased;\" data-pm-slice=\"1 3[]\">\n<h2 align=\"justify\">Run migration until the DG config <\/h2>\n<p><\/font><\/p>\n<p align=\"justify\" data-pm-slice=\"1 3[]\">Now, It\u2019s time to run the migrate command with the <font face=\"Courier New\"><strong>-pauseafter <font color=\"#0000ff\">ZDM_CONFIGURE_DG_SRC<\/font><\/strong><font face=\"Arial\"> because the goal is to stop when the replication is configured in order to resume the full migration a later time.<\/font>&nbsp;<\/font><\/p>\n<pre class=\"pre codeblock\" style=\"padding: 9.5px; border-radius: 4px; border: 1px solid rgb(204, 204, 204); border-image: none; width: 789px; height: 227px; line-height: 1.4285; overflow: auto; font-size: 16px; margin-bottom: 10px; -ms-word-break: break-all; box-sizing: border-box; background-color: rgb(3, 47, 32); overflow-wrap: break-word;\"><p><font color=\"#ffffff\"><font color=\"#ef3b7d\"><font color=\"#ffffff\"><font color=\"#00ff00\"><font color=\"#b1c5fe\"><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#ffffff\">$ZDM_HOME\/bin\/zdmcli <font color=\"#00ff00\">migrate database <font color=\"#b1c5fe\">\u2013sourcedb<\/font> SRCDB <font color=\"#ffffff\"><\/font>\n<font color=\"#b1c5fe\">-sourcenode<\/font> srcHost <font color=\"#b1c5fe\">-srcauth<\/font> zdmauth <font color=\"#ffffff\"><\/font>\n<font color=\"#b1c5fe\">-srcarg1<\/font> user:zdmuser  <font color=\"#ffffff\"><\/font>\n<font color=\"#b1c5fe\">-targetnode<\/font> tgtNode <font color=\"#ffffff\"><\/font>\n<font color=\"#b1c5fe\">-tgtauth<\/font> zdmauth <font color=\"#ffffff\"><\/font>\n<font color=\"#b1c5fe\">-tgtarg1<\/font> user:opc <font color=\"#ffffff\"><\/font><\/font>\n-rsp .\/<font color=\"#00ff00\">physical_online_demo.rsp <font color=\"#ffffff\">\u2013ignore ALL <font color=\"#ef3b7d\">-pauseafter<\/font> ZDM_CONFIGURE_DG_SRC<\/font><\/font><\/font>\n<\/font><\/font><\/font><\/font><\/font><\/font><\/font><\/font><\/font><\/font><\/font><\/p><\/pre>\n<p align=\"justify\" data-pm-slice=\"1 3[]\"><strong><strong>Querying job status<\/strong><\/strong><\/p>\n<h3><font style=\"font-weight: normal;\">As you can see even if the standby was prepared successfully the Data guard configuration failed.<\/font>&nbsp;<\/h3>\n<pre class=\"pre codeblock\" style=\"padding: 9.5px; border-radius: 4px; border: 1px solid rgb(204, 204, 204); border-image: none; width: 789px; height: 952px; line-height: 1.4285; overflow: auto; font-size: 16px; margin-bottom: 10px; -ms-word-break: break-all; box-sizing: border-box; background-color: rgb(3, 47, 32); overflow-wrap: break-word;\"><p><font color=\"#ffffff\"><font color=\"#ffffff\"><strong>$ zdmservice query job \u2013jobid <\/strong><font color=\"#00ff00\"><strong>2\n<\/strong><font color=\"#ffffff\">zdmhost.domain.com: Audit ID: 39\nJob ID: <font color=\"#00ff00\">2<\/font>\nUser: zdmuser\nClient: zdmhost\nJob Type: \"MIGRATE\"\n<font color=\"#ffffff\">Current status: <font color=\"#ff0000\">FAILED<\/font>\nResult file path: \"\/u01\/app\/oracle\/zdmbase\/chkbase\/scheduled\/job-2-*log\"\n...\nJob execution elapsed time: 1 hours 25 minutes 41 seconds\nZDM_GET_SRC_INFO .............. COMPLETED\nZDM_GET_TGT_INFO .............. COMPLETED\nZDM_PRECHECKS_SRC ............. COMPLETED\nZDM_PRECHECKS_TGT ............. COMPLETED\nZDM_SETUP_SRC ................. COMPLETED\nZDM_SETUP_TGT ................. COMPLETED\nZDM_PREUSERACTIONS ............ COMPLETED\nZDM_PREUSERACTIONS_TGT ........ COMPLETED\nZDM_VALIDATE_SRC .............. COMPLETED\nZDM_VALIDATE_TGT .............. COMPLETED\nZDM_DISCOVER_SRC .............. COMPLETED\nZDM_COPYFILES ................. COMPLETED\nZDM_PREPARE_TGT ............... COMPLETED\nZDM_SETUP_TDE_TGT ............. COMPLETED\nZDM_RESTORE_TGT ............... COMPLETED\nZDM_RECOVER_TGT ............... COMPLETED\nZDM_FINALIZE_TGT .............. COMPLETED\nZDM_CONFIGURE_DG_SRC .......... <font color=\"#ff0000\">FAILED<\/font>\nZDM_SWITCHOVER_SRC ............ PENDING\nZDM_SWITCHOVER_TGT ............ PENDING\nZDM_POST_DATABASE_OPEN_TGT .... PENDING\nZDM_DATAPATCH_TGT ............. PENDING\nZDM_NONCDBTOPDB_PRECHECK ...... PENDING\nZDM_NONCDBTOPDB_CONVERSION .... PENDING\nZDM_POST_MIGRATE_TGT .......... PENDING\nZDM_POSTUSERACTIONS ........... PENDING\nZDM_POSTUSERACTIONS_TGT ....... PENDING\nZDM_CLEANUP_SRC ............... PENDING\nZDM_CLEANUP_TGT ............... PENDING<font color=\"#ffffff\"><font color=\"#ffffff\"><strong>\n<\/strong><\/font><\/font><\/font><\/font><\/font><\/font><\/font><\/p><\/pre>\n<h2><strong><\/strong><\/h2>\n<h2 align=\"justify\"><strong><br \/>\n<\/strong><\/h2>\n<h2 align=\"justify\"><strong>Troubleshooting<\/strong><\/h2>\n<p align=\"justify\" data-pm-slice=\"1 3[]\">We can check the result file to investigate the error, but I always like to dig into the specific ZDM_BASE logs hosted locally in specific src\/target nodes. Here it\u2019s in the source server (see below)<\/p>\n<pre class=\"pre codeblock\" style=\"padding: 9.5px; border-radius: 4px; border: 1px solid rgb(204, 204, 204); border-image: none; width: 789px; height: 328px; line-height: 1.4285; overflow: auto; font-size: 16px; margin-bottom: 10px; -ms-word-break: break-all; box-sizing: border-box; background-color: rgb(3, 47, 32); overflow-wrap: break-word;\"><p><font color=\"#ffffff\">--- On the source \n$ cd $ORACLE_BASE\/zdm\/zdm_SRCDB_$jobID\/zdm\/log\n$ tail -f .\/<font color=\"#00ff00\">zdm_configure_dg_src_5334.log<\/font> \n[mZDM_Queries.pm:6136]:[DEBUG] <font color=\"#b1c5fe\">None of DB_CREATE_FILE_DEST,\nDB_CREATE_ONLINE_LOG_DEST_%,DB_RECOVERY_FILE_DEST is configured for <font color=\"#ffffff\">SRCDB<\/font><\/font> \n[mZDM_Queries.pm:*]:[DEBUG] <font color=\"#b1c5fe\">Will be running following sql as user: oracle:<\/font>\n[mZDM_Queries.pm:3377]:[<font color=\"#ef3b7d\">ERROR<\/font>] unable to created undo tablespace <font color=\"#ff0000\">UNDOTBS2\n<font color=\"#ef3b7d\"><font color=\"#ffffff\">CREATE UNDO TABLESPACE UNDOTBS2 DATAFILE '\/oradata\/<font color=\"#00ff00\">undotbs2.dbf<\/font>' SIZE 98300M \nAUTOEXTEND ON<\/font> \n* \nERROR at line 1: ORA-01144: File size (12582400 blocks) \nexceeds maximum of 4194303 blocks<\/font><\/font><\/font><\/p><\/pre>\n<h3 align=\"justify\"><font style=\"font-weight: normal;\">Looks like ZDM wanted to create a large second UNDO tablespace in the source, with one Data file that\u2019s greater than 32GB. But why does ZDM need to create a second undo tablespaces in source DB.<\/font><font style=\"font-weight: normal;\"><font style=\"font-weight: normal;\"><br \/>\n<\/font><\/font><\/h3>\n<h2>\n<\/h2>\n<h2 align=\"justify\">Why is a second UNDO needed ?<font style=\"font-weight: normal;\"><br \/>\n<\/font><\/h2>\n<h3><font style=\"font-weight: normal;\">In the 21.3 release Note, you\u2019ll find that:<br \/>\n`<a href=\"https:\/\/docs.oracle.com\/en\/database\/oracle\/zero-downtime-migration\/21.3\/zdmrn\/index.html#ZDMRN-GUID-C9F066A5-C085-4680-9EE6-6C6EB644320C\" target=\"_blank\" rel=\"noopener\">ZDM adds UNDO tablespaces to the production database to match target instance count<\/a><\/font><font style=\"font-weight: normal;\">, if source database has fewer instances<\/font><em><font style=\"font-weight: normal;\">`<\/font><\/em><font style=\"font-weight: normal;\">&nbsp; <\/font><\/h3>\n<ul>\n<li>\n<h3><font style=\"font-weight: normal;\">Hence, an ExaCC 2 node RAC will require ZDM to create a 2nd UNDO tablespaces in the source&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <font style=\"font-weight: normal;\"><font style=\"font-weight: normal;\"><font style=\"font-weight: normal;\"><br \/>\n<\/font><\/font><\/font><\/font><\/h3>\n<\/li>\n<\/ul>\n<h2>\nWhat really Happened<\/h2>\n<h3><font style=\"font-weight: normal;\"><br \/>\nOk so far it makes sense, but what really caused our failure is that ZDM tried to create a 2nd <font style=\"font-weight: bold;\">UNDO<\/font> with a datafile of 98GB. Let\u2019s check our source UNDO tablespace to learn more. <\/font><\/h3>\n<pre class=\"pre codeblock\" style=\"padding: 9.5px; border-radius: 4px; border: 1px solid rgb(204, 204, 204); border-image: none; width: 789px; height: 304px; line-height: 1.4285; overflow: auto; font-size: 16px; margin-bottom: 10px; -ms-word-break: break-all; box-sizing: border-box; background-color: rgb(3, 47, 32); overflow-wrap: break-word;\"><ol><\/ol><p><font color=\"#ffffff\">SRCDB&gt; @check_tbs UNDO\n<\/font><\/p><p><font color=\"#ffffff\"><font color=\"#b1c5fe\">TABLESPACE_NAME&nbsp; ALLOCATED_MB MAX_SIZE_MB&nbsp; FREE_PCT\n---------------- ------------ ------------ ----------\nUNDO&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <font color=\"#ef3b7d\">98301<\/font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 97681&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 99<\/font>&nbsp;&nbsp; <\/font><\/p><p><font color=\"#ffffff\"><font color=\"#b1c5fe\">FILE_NAME&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Size \n---------------------- ------<\/font>\n\/oradata\/undo_1.dbf&nbsp;&nbsp;&nbsp;&nbsp; <font color=\"#ef3b7d\">32<\/font>GB \n\/oradata\/undo_2.dbf&nbsp;&nbsp;&nbsp;&nbsp; <font color=\"#ef3b7d\">32<\/font>GB \n\/oradata\/undo_3.dbf&nbsp;&nbsp;&nbsp;&nbsp; <font color=\"#ef3b7d\">32<\/font>GB <\/font><\/p><\/pre>\n<h3>Root cause:<br \/>\n <font style=\"font-weight: normal;\">It turns out ZDM was trying to create a<\/font> second UNDO tablespace <font style=\"font-weight: normal;\">based on the<\/font> total size of the tablespace using one datafile <font style=\"font-weight: normal;\">which<\/font><font style=\"font-weight: normal;\"> would have not triggered an error if the total tablespace size was lower than 32GB.&nbsp; <\/font><\/h3>\n<h2>\n<\/h2>\n<h2>Solution: Recreate as Bigfile<\/h2>\n<h3><font style=\"font-weight: normal;\"><br \/>\n<font style=\"font-weight: normal;\">Although an ER has already been filed by Oracle support after I told them about it, I still needed a quick fix.<br \/>\nSo <font style=\"font-weight: bold;\">here\u2019s what I did<\/font>:<font style=\"font-weight: normal;\"> (On <font style=\"font-weight: bold;\">Source DB<\/font>) <\/font><\/font><\/font><\/h3>\n<ul>\n<li>\n<h3><font style=\"font-weight: normal;\">Create a new dummy <font style=\"font-weight: bold;\">UNDO<\/font> tablespaces (Ideally same size as the original UNDO)<\/font><\/h3>\n<pre class=\"pre codeblock\" style=\"padding: 9.5px; border-radius: 4px; border: 1px solid rgb(204, 204, 204); border-image: none; width: 789px; height: 261px; line-height: 1.4285; overflow: auto; font-size: 16px; margin-bottom: 10px; -ms-word-break: break-all; box-sizing: border-box; background-color: rgb(3, 47, 32); overflow-wrap: break-word;\"><ol><\/ol><p><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#b1c5fe\"><font color=\"#ffffff\">SQL&gt; CREATE UNDO TABLESPACE <font color=\"#00ff00\">UNDOTBS3<\/font> DATAFILE '\/oradata\/undotbs3.dbf' SIZE 10G;<\/font>\n<font color=\"#ffffff\">SQL&gt; ALTER SYSTEM SET UNDO_TABLESPACE = <font color=\"#00ff00\">UNDOTBS3<\/font> SCOPE=BOTH;\n<font color=\"#ffffff\">SQL&gt; SELECT tablespace_name, status, count(*) from dba_rollback_segs \ngroup by tablespace_name, status;\n\nTABLESPACE_NAME&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATUS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; COUNT(*)\n------------------------------ ------------ ----------\nUNDOTBS3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ONLINE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10\n<font color=\"#b1c5fe\">UNDO&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OFFLINE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 24  &lt;--- ready to be dropped<\/font><\/font><\/font><\/font><\/font><\/font><\/p><\/pre>\n<\/li>\n<li>\n<h3><font style=\"font-weight: normal;\">When the old Undo tablespace is of status OFFLINE, drop it<\/font><\/h3>\n<pre class=\"pre codeblock\" style=\"padding: 9.5px; border-radius: 4px; border: 1px solid rgb(204, 204, 204); border-image: none; width: 789px; height: 82px; line-height: 1.4285; overflow: auto; font-size: 16px; margin-bottom: 10px; -ms-word-break: break-all; box-sizing: border-box; background-color: rgb(3, 47, 32); overflow-wrap: break-word;\"><ol><\/ol><p><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#b1c5fe\"><font color=\"#ffffff\">SQL&gt; DROP TABLESPACE UNDO including contents and datafiles;<\/font><\/font><\/font><\/font><\/p><\/pre>\n<\/li>\n<li>\n<h3>Now recreate the old UNDO <font style=\"font-weight: normal;\">using one Bigfile datafile&nbsp; <\/font>&nbsp;<\/h3>\n<pre class=\"pre codeblock\" style=\"padding: 9.5px; border-radius: 4px; border: 1px solid rgb(204, 204, 204); border-image: none; width: 789px; height: 101px; line-height: 1.4285; overflow: auto; font-size: 16px; margin-bottom: 10px; -ms-word-break: break-all; box-sizing: border-box; background-color: rgb(3, 47, 32); overflow-wrap: break-word;\"><ol><\/ol><p><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#b1c5fe\"><font color=\"#ffffff\">CREATE <font color=\"#00ff00\">BIGFILE <\/font>UNDO TABLESPACE UNDO DATAFILE '\/oradata\/undotbs.dbf' SIZE 90G;\nALTER SYSTEM SET UNDO_TABLESPACE = UNDO SCOPE=BOTH;<\/font><\/font><\/font><\/font><\/p><\/pre>\n<\/li>\n<li>\n<h3><font style=\"font-weight: normal;\">Drop the dummy UNDO tablespace <\/font><\/h3>\n<pre class=\"pre codeblock\" style=\"padding: 9.5px; border-radius: 4px; border: 1px solid rgb(204, 204, 204); border-image: none; width: 789px; height: 81px; line-height: 1.4285; overflow: auto; font-size: 16px; margin-bottom: 10px; -ms-word-break: break-all; box-sizing: border-box; background-color: rgb(3, 47, 32); overflow-wrap: break-word;\"><ol><\/ol><p><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#b1c5fe\"><font color=\"#ffffff\">SQL&gt; DROP TABLESPACE <font color=\"#00ff00\">UNDOTBS3<\/font> including contents and datafiles;<\/font><\/font><\/font><\/font><\/p><\/pre>\n<h3><font style=\"font-weight: normal;\"><font style=\"font-weight: bold;\">Note:<\/font> I have not named it UNDOTBS2 because ZDM will use it when creating the second UNDO later.&nbsp; <\/font><\/h3>\n<\/li>\n<\/ul>\n<h3><\/h3>\n<h2 align=\"justify\">Resume the job <\/h2>\n<h3><\/h3>\n<h3 align=\"justify\"><font style=\"font-weight: normal;\">Now that we have one bigfile in the UNDO tablespace we can resume the ZDM job and the phase will not complain <\/font><\/h3>\n<pre class=\"pre codeblock\" style=\"padding: 9.5px; border-radius: 4px; border: 1px solid rgb(204, 204, 204); border-image: none; width: 789px; height: 450px; line-height: 1.4285; overflow: auto; font-size: 16px; margin-bottom: 10px; -ms-word-break: break-all; box-sizing: border-box; background-color: rgb(3, 47, 32); overflow-wrap: break-word;\"><ol><strong><\/strong><\/ol><p><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#b1c5fe\"><font color=\"#ffffff\"><strong>$<\/strong> <strong>zdmservice resume job \u2013jobid <\/strong><\/font><\/font><\/font><\/font><font color=\"#00ff00\"><strong>2\n<font color=\"#ffffff\">$ <strong>zdmservice query job \u2013jobid <\/strong><strong>2<font color=\"#00ff00\"><\/font><\/strong><\/font><font color=\"#00ff00\"><\/font><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#b1c5fe\"><font color=\"#ffffff\"><font color=\"#00ff00\"><strong>\n...\n<font color=\"#ffffff\">ZDM_CONFIGURE_DG_SRC ..........<\/font> <font color=\"#00ff00\">COMPLETED\n<font color=\"#ffffff\">ZDM_SWITCHOVER_SRC ............ PENDING\nZDM_SWITCHOVER_TGT ............ PENDING\nZDM_POST_DATABASE_OPEN_TGT .... PENDING\nZDM_DATAPATCH_TGT ............. PENDING\nZDM_NONCDBTOPDB_PRECHECK ...... PENDING\nZDM_NONCDBTOPDB_CONVERSION .... PENDING\nZDM_POST_MIGRATE_TGT .......... PENDING\nZDM_POSTUSERACTIONS ........... PENDING\nZDM_POSTUSERACTIONS_TGT ....... PENDING\nZDM_CLEANUP_SRC ............... PENDING\nZDM_CLEANUP_TGT ............... PENDING<\/font><\/font><\/strong><\/font><\/font><\/font><\/font><\/font><\/strong><\/font><\/p><p><font color=\"#00ff00\"><strong><font color=\"#ffffff\"><font color=\"#ffffff\"><font color=\"#b1c5fe\"><font color=\"#ffffff\"><font color=\"#00ff00\"><strong><font color=\"#00ff00\"><font color=\"#ffffff\">Pause After Phase: \"ZDM_CONFIGURE_DG_SRC\"<\/font><\/font><\/strong><\/font><\/font><\/font><\/font><\/font><\/strong><\/font><\/p><\/pre>\n<h2 align=\"justify\">Tip: <\/h2>\n<h3 align=\"justify\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Best way to avoid this issue is to convert the source UNDO into Big file in the first place .<\/h3>\n<h2 align=\"justify\">\n<\/h2>\n<h2 align=\"justify\">\nConclusion<\/h2>\n<ul>\n<li>\n<p align=\"justify\" data-pm-slice=\"1 3 []\">Although ZDM allows you to run one command to automate the entire migration you still need to troubleshoot issue that might occur here and there&nbsp;&nbsp;<\/p>\n<\/li>\n<li>\n<p align=\"justify\" data-pm-slice=\"1 3 []\">The automation with a resume option in case failure makes the process more reassuring to us DBAs<\/p>\n<\/li>\n<li>\n<p align=\"justify\" data-pm-slice=\"1 3 []\">Hope this will help anyone who runs into the same error to quickly fix it and go on with the migration<\/p>\n<\/li>\n<li>\n<p align=\"justify\" data-pm-slice=\"1 3 []\">On my next post I\u2019ll be talking about another issue I faced which required a little hack, stay tuned<\/p>\n<\/li>\n<\/ul>\n<p align=\"center\" data-pm-slice=\"1 3 []\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank you for reading<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Intro I didn\u2019t anticipate to have a series of posts around ZDM, but I had few issues that were worth sharing so here I am. This post will describe what caused a failure of an online physical migration ExaCC right at the Data guard configuration phase. The good thing about ZDM, is as soon as &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration\" class=\"more-link\">Read more<span class=\"screen-reader-text\"> &#8220;ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC&#8221;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_editorskit_title_hidden":false,"_editorskit_reading_time":0,"_editorskit_is_block_options_detached":false,"_editorskit_block_options_position":"{}","footnotes":""},"categories":[1],"tags":[37,48],"class_list":["post-306","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-oracle-database","tag-zdm"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC - Cloudthrill<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC - Cloudthrill\" \/>\n<meta property=\"og:description\" content=\"Intro I didn\u2019t anticipate to have a series of posts around ZDM, but I had few issues that were worth sharing so here I am. This post will describe what caused a failure of an online physical migration ExaCC right at the Data guard configuration phase. The good thing about ZDM, is as soon as &hellip; Read more &quot;ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC&quot;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration\" \/>\n<meta property=\"og:site_name\" content=\"Cloudthrill\" \/>\n<meta property=\"article:published_time\" content=\"2022-09-05T05:16:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-07-05T22:39:45+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/brokedba.files.wordpress.com\/2022\/09\/image-3.png?w=1024\" \/>\n<meta name=\"author\" content=\"CloudDude\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@couddude_\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"CloudDude\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration\"},\"author\":{\"name\":\"CloudDude\",\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/#\\\/schema\\\/person\\\/aaac9d7e544fd61849e31ac4230a57f3\"},\"headline\":\"ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC\",\"datePublished\":\"2022-09-05T05:16:00+00:00\",\"dateModified\":\"2024-07-05T22:39:45+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration\"},\"wordCount\":843,\"publisher\":{\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/brokedba.files.wordpress.com\\\/2022\\\/09\\\/image-3.png?w=1024\",\"keywords\":[\"Oracle Database\",\"ZDM\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration\",\"url\":\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration\",\"name\":\"ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC - Cloudthrill\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/brokedba.files.wordpress.com\\\/2022\\\/09\\\/image-3.png?w=1024\",\"datePublished\":\"2022-09-05T05:16:00+00:00\",\"dateModified\":\"2024-07-05T22:39:45+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration#primaryimage\",\"url\":\"https:\\\/\\\/brokedba.files.wordpress.com\\\/2022\\\/09\\\/image-3.png?w=1024\",\"contentUrl\":\"https:\\\/\\\/brokedba.files.wordpress.com\\\/2022\\\/09\\\/image-3.png?w=1024\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/zdm-troubleshooting-part-2-migration#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/cloudthrill.ca\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/#website\",\"url\":\"https:\\\/\\\/cloudthrill.ca\\\/\",\"name\":\"cloudthrill.ca\",\"description\":\"CloudThrill is focused on providing Cloud &amp; DevOps consulting services to clients looking to maximize their cloud\\\/on-prem estate.\",\"publisher\":{\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/cloudthrill.ca\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/#organization\",\"name\":\"cloudthrill.ca\",\"url\":\"https:\\\/\\\/cloudthrill.ca\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/cloudthrill.ca\\\/wp-content\\\/uploads\\\/2024\\\/07\\\/Cloudthrill.png\",\"contentUrl\":\"https:\\\/\\\/cloudthrill.ca\\\/wp-content\\\/uploads\\\/2024\\\/07\\\/Cloudthrill.png\",\"width\":1599,\"height\":588,\"caption\":\"cloudthrill.ca\"},\"image\":{\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/company\\\/cloudthrill\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/cloudthrill.ca\\\/#\\\/schema\\\/person\\\/aaac9d7e544fd61849e31ac4230a57f3\",\"name\":\"CloudDude\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/02bba403d23c390a42783246ef373bf8a8111b022c06a373d6cb9d3cabe12587?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/02bba403d23c390a42783246ef373bf8a8111b022c06a373d6cb9d3cabe12587?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/02bba403d23c390a42783246ef373bf8a8111b022c06a373d6cb9d3cabe12587?s=96&d=mm&r=g\",\"caption\":\"CloudDude\"},\"sameAs\":[\"http:\\\/\\\/cloudthrill.io\",\"https:\\\/\\\/x.com\\\/couddude_\"],\"url\":\"https:\\\/\\\/cloudthrill.ca\\\/author\\\/clouddude\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC - Cloudthrill","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration","og_locale":"en_US","og_type":"article","og_title":"ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC - Cloudthrill","og_description":"Intro I didn\u2019t anticipate to have a series of posts around ZDM, but I had few issues that were worth sharing so here I am. This post will describe what caused a failure of an online physical migration ExaCC right at the Data guard configuration phase. The good thing about ZDM, is as soon as &hellip; Read more \"ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC\"","og_url":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration","og_site_name":"Cloudthrill","article_published_time":"2022-09-05T05:16:00+00:00","article_modified_time":"2024-07-05T22:39:45+00:00","og_image":[{"url":"https:\/\/brokedba.files.wordpress.com\/2022\/09\/image-3.png?w=1024","type":"","width":"","height":""}],"author":"CloudDude","twitter_card":"summary_large_image","twitter_creator":"@couddude_","twitter_misc":{"Written by":"CloudDude","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration#article","isPartOf":{"@id":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration"},"author":{"name":"CloudDude","@id":"https:\/\/cloudthrill.ca\/#\/schema\/person\/aaac9d7e544fd61849e31ac4230a57f3"},"headline":"ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC","datePublished":"2022-09-05T05:16:00+00:00","dateModified":"2024-07-05T22:39:45+00:00","mainEntityOfPage":{"@id":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration"},"wordCount":843,"publisher":{"@id":"https:\/\/cloudthrill.ca\/#organization"},"image":{"@id":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration#primaryimage"},"thumbnailUrl":"https:\/\/brokedba.files.wordpress.com\/2022\/09\/image-3.png?w=1024","keywords":["Oracle Database","ZDM"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration","url":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration","name":"ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC - Cloudthrill","isPartOf":{"@id":"https:\/\/cloudthrill.ca\/#website"},"primaryImageOfPage":{"@id":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration#primaryimage"},"image":{"@id":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration#primaryimage"},"thumbnailUrl":"https:\/\/brokedba.files.wordpress.com\/2022\/09\/image-3.png?w=1024","datePublished":"2022-09-05T05:16:00+00:00","dateModified":"2024-07-05T22:39:45+00:00","breadcrumb":{"@id":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration#primaryimage","url":"https:\/\/brokedba.files.wordpress.com\/2022\/09\/image-3.png?w=1024","contentUrl":"https:\/\/brokedba.files.wordpress.com\/2022\/09\/image-3.png?w=1024"},{"@type":"BreadcrumbList","@id":"https:\/\/cloudthrill.ca\/zdm-troubleshooting-part-2-migration#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cloudthrill.ca\/"},{"@type":"ListItem","position":2,"name":"ZDM troubleshooting part 2: Migration failing at ZDM_CONFIGURE_DG_SRC"}]},{"@type":"WebSite","@id":"https:\/\/cloudthrill.ca\/#website","url":"https:\/\/cloudthrill.ca\/","name":"cloudthrill.ca","description":"CloudThrill is focused on providing Cloud &amp; DevOps consulting services to clients looking to maximize their cloud\/on-prem estate.","publisher":{"@id":"https:\/\/cloudthrill.ca\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cloudthrill.ca\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/cloudthrill.ca\/#organization","name":"cloudthrill.ca","url":"https:\/\/cloudthrill.ca\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/cloudthrill.ca\/#\/schema\/logo\/image\/","url":"https:\/\/cloudthrill.ca\/wp-content\/uploads\/2024\/07\/Cloudthrill.png","contentUrl":"https:\/\/cloudthrill.ca\/wp-content\/uploads\/2024\/07\/Cloudthrill.png","width":1599,"height":588,"caption":"cloudthrill.ca"},"image":{"@id":"https:\/\/cloudthrill.ca\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/cloudthrill"]},{"@type":"Person","@id":"https:\/\/cloudthrill.ca\/#\/schema\/person\/aaac9d7e544fd61849e31ac4230a57f3","name":"CloudDude","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/02bba403d23c390a42783246ef373bf8a8111b022c06a373d6cb9d3cabe12587?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/02bba403d23c390a42783246ef373bf8a8111b022c06a373d6cb9d3cabe12587?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/02bba403d23c390a42783246ef373bf8a8111b022c06a373d6cb9d3cabe12587?s=96&d=mm&r=g","caption":"CloudDude"},"sameAs":["http:\/\/cloudthrill.io","https:\/\/x.com\/couddude_"],"url":"https:\/\/cloudthrill.ca\/author\/clouddude"}]}},"brizy_media":[],"_links":{"self":[{"href":"https:\/\/cloudthrill.ca\/wp-json\/wp\/v2\/posts\/306","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cloudthrill.ca\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cloudthrill.ca\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cloudthrill.ca\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/cloudthrill.ca\/wp-json\/wp\/v2\/comments?post=306"}],"version-history":[{"count":1,"href":"https:\/\/cloudthrill.ca\/wp-json\/wp\/v2\/posts\/306\/revisions"}],"predecessor-version":[{"id":527,"href":"https:\/\/cloudthrill.ca\/wp-json\/wp\/v2\/posts\/306\/revisions\/527"}],"wp:attachment":[{"href":"https:\/\/cloudthrill.ca\/wp-json\/wp\/v2\/media?parent=306"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cloudthrill.ca\/wp-json\/wp\/v2\/categories?post=306"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cloudthrill.ca\/wp-json\/wp\/v2\/tags?post=306"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}