{"id":34395,"date":"2024-07-30T16:21:27","date_gmt":"2024-07-30T14:21:27","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=34395"},"modified":"2024-07-30T16:21:30","modified_gmt":"2024-07-30T14:21:30","slug":"why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/","title":{"rendered":"Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must?"},"content":{"rendered":"\n<p>I have been blogging about ZDM Physical Online migration with noncdb to cdb conversion. As you could read in my previous article, the target database name on CDB level should be the same as the source database, knowing physical online migration is using Data Guard. In our case, at customer, we wanted to group the new migrated PDBs is some CDB, and thus the CDB name was not matching any convention any more. This is why we relocated the new migrated PDB from the target CDB database used during ZDM migration to a final one. I could later realise that in any case, if we are migrating and converting from noncdb to pdb with ZDM it is better to relocate the PDB at the end. Let me explain you why.<\/p>\n\n\n<a class=\"wp-block-read-more\" href=\"https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/\" target=\"_self\">Read more<span class=\"screen-reader-text\">: Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must?<\/span><\/a>\n\n\n<h2 class=\"wp-block-heading\" id=\"h-zdm-bug-on-grid-infra-resource\">ZDM bug on Grid Infra resource<\/h2>\n\n\n\n<p>I made some test and migrated a source On-Premise database to the new ExaCC but just stopping after ZDM migration completed. The naming convention will be the same as the previous blog. As we can see the noncdb Source database has been successfully migrated to the new target database on the exaCC.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,13,18,20,24,30]\">\noracle@ExaCC-cl01n1:~\/ [ONPR1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Mon Jul 29 16:45:17 2024\nVersion 19.22.0.0.0\n\nCopyright (c) 1982, 2023, Oracle.  All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.22.0.0.0\n\nSQL&gt; show pdbs\n\n    CON_ID CON_NAME                       OPEN MODE  RESTRICTED\n---------- ------------------------------ ---------- ----------\n         2 PDB$SEED                       READ ONLY  NO\n         3 ONPRZ_APP_001T                 READ WRITE NO\n\nSQL&gt; alter session set container=ONPRZ_APP_001T;\n\nSession altered.\n\nSQL&gt; show pdbs\n\n    CON_ID CON_NAME                       OPEN MODE  RESTRICTED\n---------- ------------------------------ ---------- ----------\n         3 ONPRZ_APP_001T                 READ WRITE NO\n\nSQL&gt; select status, message from pdb_plug_in_violations;\n\nSTATUS     MESSAGE\n---------- ------------------------------------------------------------------------------------------------------------------------\nRESOLVED   PDB needs to import keys from source.\nRESOLVED   Database option RAC mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.\nRESOLVED   PDB plugged in is a non-CDB, requires noncdb_to_pdb.sql be run.\nPENDING    Database option APS mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.\nPENDING    Database option CATJAVA mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.\nPENDING    Database option CONTEXT mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.\nPENDING    Database option DV mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.\nPENDING    Database option JAVAVM mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.\nPENDING    Database option OLS mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.\nPENDING    Database option ORDIM mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.\nPENDING    Database option SDO mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.\nPENDING    Database option XML mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.\nPENDING    Database option XOQ mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.\nPENDING    Tablespace SYSTEM is not encrypted. Oracle Cloud mandates all tablespaces should be encrypted.\nPENDING    Tablespace SYSAUX is not encrypted. Oracle Cloud mandates all tablespaces should be encrypted.\n\n15 rows selected.\n<\/pre>\n<\/br>\n\n\n\n<p>As it was a fast test and as my target database was still on one instance I wanted to configured it to RAC again.<\/p>\n\n\n\n<p>I setup cluster_database instance parameter back to TRUE value.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,13]\">\noracle@ExaCC-cl01n1:~\/ [ONPR1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Mon Jul 29 17:20:27 2024\nVersion 19.22.0.0.0\n\nCopyright (c) 1982, 2023, Oracle.  All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.22.0.0.0\n\nSQL&gt; alter system set cluster_database=TRUE scope=spfile sid='*';\n\nSystem altered.\n<\/pre>\n<\/br>\n\n\n\n<p>I stopped my database.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@ExaCC-cl01n1:~\/ [ONPR1 (CDB$ROOT)] srvctl stop database -d ONPR_CHZ2\n<\/pre>\n<\/br>\n\n\n\n<p>Added back the second instance.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@ExaCC-cl01n1:~\/ [ONPR1 (CDB$ROOT)] srvctl add instance -d ONPR_CHZ2 -i ONPR2 -node ExaCC-cl01n2\n<\/pre>\n<\/br>\n\n\n\n<p>Starting the database I could face some errors.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,5,11,12]\">\noracle@ExaCC-cl01n1:~\/ [ONPR1 (CDB$ROOT)] srvctl start database -d ONPR_CHZ2\nPRCR-1079 : Failed to start resource ora.onpr_chz2.db\nCRS-5017: The resource action \"ora.onpr_chz2.db start\" encountered the following error:\nORA-01078: failure in processing system parameters\nLRM-00109: could not open parameter file '\/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_1\/dbs\/initONPR2.ora'\n. For details refer to \"(:CLSN00107:)\" in \"\/u01\/app\/grid\/diag\/crs\/ExaCC-cl01n2\/crs\/trace\/crsd_oraagent_oracle.trc\".\n\nCRS-2674: Start of 'ora.onpr_chz2.db' on 'ExaCC-cl01n2' failed\nCRS-2632: There are no more servers to try to place resource 'ora.onpr_chz2.db' on that would satisfy its placement policy\nCRS-5017: The resource action \"ora.onpr_chz2.db start\" encountered the following error:\nORA-01122: database file 1 failed verification check\nORA-01110: data file 1: '+DATAC5\/ONPRZ_APP_001T\/datafile\/system.651.1175616809'\nORA-01204: file number is 14 rather than 1 - wrong file\n. For details refer to \"(:CLSN00107:)\" in \"\/u01\/app\/grid\/diag\/crs\/ExaCC-cl01n1\/crs\/trace\/crsd_oraagent_oracle.trc\".\n\nCRS-2674: Start of 'ora.onpr_chz2.db' on 'ExaCC-cl01n1' failed\n<\/pre>\n<\/br>\n\n\n\n<p>Why init or spfile not in the ASM? Why the CDB will look in the ZDM temporary noncdb database folder?<\/p>\n\n\n\n<p>I have got my 2 instances, but none are running.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@ExaCC-cl01n1:~\/ [ONPR1 (CDB$ROOT)] srvctl status database -d ONPR_CHZ2\nInstance ONPR1 is not running on node ExaCC-cl01n1\nInstance ONPR2 is not running on node ExaCC-cl01n2\n<\/pre>\n<\/br>\n\n\n\n<p>I checked the grid resource configuration and could realise that ZDM changed the spfile to the ZDM temporary noncdb database one.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,6]\">\noracle@ExaCC-cl01n1:~\/ [ONPR1 (CDB$ROOT)] srvctl config database -d ONPR_CHZ2\nDatabase unique name: ONPR_CHZ2\nDatabase name: ONPR\nOracle home: \/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_1\nOracle user: oracle\nSpfile: \/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_1\/dbs\/spfileONPRZ_APP_001T1.ora\nPassword file: +DATAC5\/ONPR_CHZ2\/PASSWORD\/pwdonpr_chz2.599.1175606525\nDomain: domain.com\nStart options: open\nStop options: immediate\nDatabase role: PRIMARY\nManagement policy: AUTOMATIC\nServer pools:\nDisk Groups: DATAC5\nMount point paths: \/acfs01\nServices:\nType: RAC\nStart concurrency:\nStop concurrency:\nOSDBA group: dba\nOSOPER group: racoper\nDatabase instances: ONPR1,ONPR2\nConfigured nodes: ExaCC-cl01n1,ExaCC-cl01n2\nCSS critical: no\nCPU count: 0\nMemory target: 0\nMaximum memory: 0\nDefault network number for database services:\nDatabase is administrator managed\n<\/pre>\n<\/br>\n\n\n\n<p>I checked the spfile for the target CDB in the ASM.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,2]\">\n[grid@ExaCC-cl01n1 ~]$ asmcmd\nASMCMD&gt; ls +DATAC5\/ONPR_CHZ2\/PARAMETERFILE\/\nspfile.621.1175607313\n<\/pre>\n<\/br>\n\n\n\n<p>And updated the grid infra resource to match it.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,2,3]\">\noracle@ExaCC-cl01n1:~\/ [ONPR1 (CDB$ROOT)] srvctl modify database -d ONPR_CHZ2 -spfile '+DATAC5\/ONPR_CHZ2\/PARAMETERFILE\/spfile.621.1175607313'\noracle@ExaCC-cl01n1:~\/ [ONPR1 (CDB$ROOT)] srvctl start database -d ONPR_CHZ2\noracle@ExaCC-cl01n1:~\/ [ONPR1 (CDB$ROOT)] srvctl status database -d ONPR_CHZ2\nInstance ONPR1 is running on node ExaCC-cl01n1\nInstance ONPR2 is running on node ExaCC-cl01n2\n<\/pre>\n<\/br>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-placement-of-the-pdb-datafiles\">Placement of the PDB datafiles<\/h2>\n\n\n\n<p>As we can see from the ZDM log, ZDM is doing the noncdb to pdb conversion by creating a pluggable database with the option NOCOPY.<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1]\">\noracle@ExaCC-cl01n1:\/u02\/app\/oracle\/zdm\/zdm_ONPR_CHZ2_280\/zdm\/log\/ [ONPR1] grep -i \"CREATE PLUGGABLE DATABASE\" zdm_noncdbtopdb_conversion_211779.log\nCREATE PLUGGABLE DATABASE ONPRZ_APP_001T AS CLONE USING '\/tmp\/ONPRZ_APP_001T.xml' NOCOPY TEMPFILE REUSE\n<\/pre>\n<\/br>\n\n\n\n<p>This means the PDB datafiles remains at the same position as the noncdb database was having, in our case ONPRZ_APP_001T.<\/p>\n\n\n\n<p>So the new PDB ONPRZ_APP_001T is located in ONPR_CHZ2 CDB but having its datafiles not in one subdirectory from the CDB using the GUID from the PDB but an external folder.<\/p>\n\n\n\n<p>Location of the PDB datafiles:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,2,10]\">\n[grid@ExaCC-cl01n1 ~]$ asmcmd\nASMCMD&gt; ls DATAC5\/ONPRZ_APP_001T\/\nCHANGETRACKING\/\nDATAGUARDCONFIG\/\nTEMPFILE\/\ncontrolfile\/\ndatafile\/\nonlinelog\/\npassword\/\nASMCMD&gt; ls DATAC5\/ONPRZ_APP_001T\/datafile\nAPP1.646.1175616827\nAPP2.644.1175616827\nSYSAUX.650.1175616809\nSYSTEM.651.1175616809\nUNDOTBS1.648.1175616825\nUSERS.647.1175616827\n<\/pre>\n<\/br>\n\n\n\n<p>Location of the CDB and other PDB datafiles:<\/p>\n\n\n\n<pre class=\"brush: sql; gutter: true; first-line: 1; highlight: [1,11,13,15]\">\nASMCMD&gt; ls DATAC5\/ONPR_CHZ2\n0F39DE50B35B3B53E0638A5346646D89\/\n1E622346BAF56871E0630E1FA10AEBC4\/\n1E64CA31F0169FAEE0630E1FA10A0290\/\nCONTROLFILE\/\nDATAFILE\/\nONLINELOG\/\nPARAMETERFILE\/\nPASSWORD\/\nTEMPFILE\/\nASMCMD&gt; ls DATAC5\/ONPR_CHZ2\/1E64CA31F0169FAEE0630E1FA10A0290\/\nTEMPFILE\/\nASMCMD&gt; ls DATAC5\/ONPR_CHZ2\/1E622346BAF56871E0630E1FA10AEBC4\/\nTEMPFILE\/\nASMCMD&gt; ls DATAC5\/ONPR_CHZ2\/F39DE50B35B3B53E0638A5346646D89\/DATAFILE\/\nSYSAUX.613.1175606819\nSYSTEM.612.1175606819\nUNDOTBS1.614.1175606819\n<\/pre>\n<\/br>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-to-wrap-up\">To wrap up<\/h2>\n\n\n\n<p>In case of a ZDM Physical Online Migration using noncdb to pdb conversion I would recommend to relocate the PDB at the end of the migration.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I have been blogging about ZDM Physical Online migration with noncdb to cdb conversion. As you could read in my previous article, the target database name on CDB level should be the same as the source database, knowing physical online migration is using Data Guard. In our case, at customer, we wanted to group the [&hellip;]<\/p>\n","protected":false},"author":48,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[59],"tags":[280,2598,2562,1574,1575],"type_dbi":[],"class_list":["post-34395","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-database","tag-exacc-3","tag-migration-2","tag-zdm","tag-zero-downtime-migration"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.5) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must? - dbi Blog<\/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:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must?\" \/>\n<meta property=\"og:description\" content=\"I have been blogging about ZDM Physical Online migration with noncdb to cdb conversion. As you could read in my previous article, the target database name on CDB level should be the same as the source database, knowing physical online migration is using Data Guard. In our case, at customer, we wanted to group the [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2024-07-30T14:21:27+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-07-30T14:21:30+00:00\" \/>\n<meta name=\"author\" content=\"Marc Wagner\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Marc Wagner\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"2 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\\\/\"},\"author\":{\"name\":\"Marc Wagner\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/225d9884b8467ead9a872823acb14628\"},\"headline\":\"Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must?\",\"datePublished\":\"2024-07-30T14:21:27+00:00\",\"dateModified\":\"2024-07-30T14:21:30+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\\\/\"},\"wordCount\":454,\"commentCount\":0,\"keywords\":[\"database\",\"exacc\",\"migration\",\"zdm\",\"zero downtime migration\"],\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\\\/\",\"name\":\"Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must? - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2024-07-30T14:21:27+00:00\",\"dateModified\":\"2024-07-30T14:21:30+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/225d9884b8467ead9a872823acb14628\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/225d9884b8467ead9a872823acb14628\",\"name\":\"Marc Wagner\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"caption\":\"Marc Wagner\"},\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/marc-wagner\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must? - dbi Blog","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:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/","og_locale":"en_US","og_type":"article","og_title":"Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must?","og_description":"I have been blogging about ZDM Physical Online migration with noncdb to cdb conversion. As you could read in my previous article, the target database name on CDB level should be the same as the source database, knowing physical online migration is using Data Guard. In our case, at customer, we wanted to group the [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/","og_site_name":"dbi Blog","article_published_time":"2024-07-30T14:21:27+00:00","article_modified_time":"2024-07-30T14:21:30+00:00","author":"Marc Wagner","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Marc Wagner","Est. reading time":"2 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/"},"author":{"name":"Marc Wagner","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"headline":"Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must?","datePublished":"2024-07-30T14:21:27+00:00","dateModified":"2024-07-30T14:21:30+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/"},"wordCount":454,"commentCount":0,"keywords":["database","exacc","migration","zdm","zero downtime migration"],"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/","url":"https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/","name":"Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must? - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2024-07-30T14:21:27+00:00","dateModified":"2024-07-30T14:21:30+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/why-relocating-the-pdb-after-zdm-physical-online-migration-with-noncdb-to-cdb-conversion-is-a-must\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Why relocating the PDB after ZDM Physical Online migration with noncdb to cdb conversion is a must?"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628","name":"Marc Wagner","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","caption":"Marc Wagner"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/34395","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/48"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=34395"}],"version-history":[{"count":7,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/34395\/revisions"}],"predecessor-version":[{"id":34404,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/34395\/revisions\/34404"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=34395"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=34395"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=34395"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=34395"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}