{"id":33653,"date":"2024-06-12T16:30:00","date_gmt":"2024-06-12T14:30:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=33653"},"modified":"2024-06-12T15:19:07","modified_gmt":"2024-06-12T13:19:07","slug":"is-dpr-compatible-with-12-1-databases-running-on-your-oda","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/","title":{"rendered":"Is DPR compatible with 12.1 databases running on your ODA?"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\" id=\"h-introduction\">Introduction<\/h2>\n\n\n\n<p>Since patch version 19.21 (current one is 19.23), ODA (Oracle Database Appliance) X7, X8 and X9 will require the use of Data Preserving Reprovisioning (DPR) to get the patch. Unlike traditional patching, DPR erases the system disks but keeps data on ASM\/ACFS disks. Data includes databases, ACFS volumes, DB homes, vDisks for DB Systems and VMs. But it doesn&#8217;t keep your system settings: specific OS configurations, additional tools, monitoring, users and groups, aso. The reason for not being able to use classic patching method: the embedded OS upgrade from Linux 7 to Linux 8. Actually, it&#8217;s much easier to setup a brand new system than applying a major patch onto an existing one. But what about your old (and unsupported) Oracle database releases? Let&#8217;s find out for 12cR1 databases.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-oda-s-hardware-and-software-support\">ODA&#8217;s hardware and software support<\/h2>\n\n\n\n<p>According to MOS note Doc ID 2757884.1, only ODAs X7, X8, X9 and X10 series are currently supported. The support is valid if you run at least patch version 19.19. The only database versions supported are 19c in bare metal, and 21c and 19c as DB Systems.<\/p>\n\n\n\n<p>There is no more support for older releases, like 12cR1 for example. But it doesn&#8217;t mean that 12cR1 will stop working as soon as you&#8217;re deploying patch 19.19 or higher. With classic patching, your old databases will still be OK. Patching with DPR is another story. As old releases are no more supported, you may struggle to plug in back your old databases to the new Linux system. One could advice to upgrade all your databases to 19c prior using DPR, but it&#8217;s not so easy for a lot of my clients. Many old databases are legacy and must run for another couple of years. And 12cR1 is the main release that must survive through patching.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-environment-and-context\">Environment and context<\/h2>\n\n\n\n<p>I worked on this following example 2 weeks ago:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>an ODA X8-2M running patch 19.18<\/li>\n\n\n\n<li>patching is done once a year, and this time I need to update to version 19.22 and I must use DPR<\/li>\n\n\n\n<li>most of the databases are running 19.18<\/li>\n\n\n\n<li>4 databases are still running 12cR1 from initial version (19.15)<\/li>\n\n\n\n<li>these 12cR1 databases were not patched during last year&#8217;s update from 19.15 to 19.18 as no more patch existed for 12cR1 in 19.18<\/li>\n<\/ul>\n\n\n\n<p>There is no reason 12cR1 would stop working after this OS upgrade: 12cR1 is supported (so to say) on Linux 8, as mentioned in the certification matrix on MOS.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-dpr-preupgrade\">DPR preupgrade<\/h2>\n\n\n\n<p>DPR means reimaging the ODA, but before reimaging, you will need to register the 19.22 patch and update the DCS components. The adequate preupgrade and detach-node operations resides within the patch.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-repository -f \/backup\/patch\/19_22\/oda-sm-19.22.0.0.0-240306-server.zip\nsleep 60 ; odacli describe-job -i \"16596d34-9b93-4c7d-b502-4ad27804fa69\"\n...\n\nodacli update-dcsadmin -v 19.22.0.0.0\nsleep 120 ; odacli describe-job -i \"aed1c8ef-713b-43c2-9355-cb364387dcd0\"\n...\n\nodacli update-dcscomponents -v 19.22.0.0.0\n...\n\u2003\nodacli update-dcsagent -v 19.22.0.0.0\nsleep 180 ; odacli describe-job -i 1a10900c-2fc7-4535-8f9b-879a43243e66\n...<\/code><\/pre>\n\n\n\n<p>Once your ODA has the knowledge of what&#8217;s needed for DPR to 19.22, let&#8217;s do the preupgrade operation:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli create-preupgradereport -bm \n<\/code><\/pre>\n\n\n\n<p>Preupgrade will check a lot of prerequisites, but let&#8217;s focus on 12cR1:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli describe-preupgradereport -i b1f6dddb-c531-45d5-842f-bf3cf10231fe\nUpgrade pre-check report\n------------------------------------------------------------------------\n                 Job ID:  b1f6dddb-c531-45d5-842f-bf3cf10231fe\n            Description:  Run pre-upgrade checks for Bare Metal\n                 Status:  FAILED\n                Created:  April 15, 2024 1:47:17 PM CEST\n                 Result:  One or more pre-checks failed for &#091;DB]\n\n...\n\nValidate Database Version      Failed   Version '12.1.0.2.220419' for          Please update the database to the\n                                        database 'BRCLATST' is lower than      minimum supported version or higher\n                                        minimum supported version\n                                        '12.1.0.2.220719'\n...\nValidate Database Version      Failed   Version '12.1.0.2.220419' for          Please update the database to the\n                                        database 'BRSLTST' is lower than       minimum supported version or higher\n                                        minimum supported version\n                                        '12.1.0.2.220719'\n...\nValidate Database Version      Failed   Version '12.1.0.2.220419' for          Please update the database to the\n                                        database 'BRRTST' is lower than        minimum supported version or higher\n                                        minimum supported version\n                                        '12.1.0.2.220719'\n\n...\nValidate Database Version      Failed   Version '12.1.0.2.220419' for          Please update the database to the\n                                        database 'BRFTST' is lower than        minimum supported version or higher\n                                        minimum supported version\n                                        '12.1.0.2.220719'\n...\n<\/code><\/pre>\n\n\n\n<p>Hopefully, my 4 databases are not declared unsupported or not compatible with 19.22. But they are using patch 12.1.0.2.220419 as deployed with ODA version 19.15, and I will need to upgrade them to 12.1.0.2.220719. This is the latest version embedded in the latest ODA patch that supports 12cR1: 19.16. It should be quite easy to apply.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-registering-the-db-home-and-apply-the-patch\">Registering the DB home and apply the patch?<\/h2>\n\n\n\n<p>I thought I could simply download the DB clone, register it in the repository, and apply the patch, but applying the patch on a DB home will also need the system patch. Because the target version for updating a DB home is an ODA patch number, and metadata inside the system patch makes the link to the associated DB home. No problem to register this old patch, even if you currently run a higher version:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-repository -f \/backup\/patch\/19_22\/odacli-dcs-19.16.0.0.0-220805-DB-12.1.0.2.zip\nsleep 60 ; odacli describe-job -i \"304762d3-948b-419b-9954-0d402da8304d\"\n...\n\nodacli update-repository -f \/backup\/patch\/19_22\/oda-sm-19.16.0.0.0-220809-server.zip\nsleep 60 ; odacli describe-job -i \"4e75492b-60d4-4351-9966-80fdec97b312\"\n...\n\nodacli list-dbhomes\nID                                       Name                 DB Version           DB Edition Home Location                                            Status\n---------------------------------------- -------------------- -------------------- ---------- -------------------------------------------------------- ----------\n1cbe3f74-2746-4ab0-81f9-2d1b9f5c3d56     OraDB12102_home1     12.1.0.2.220419      EE         \/u01\/app\/odaorahome\/oracle\/product\/12.1.0.2\/dbhome_1     CONFIGURED\n94aba6b1-850b-45d5-b123-c9eade003fa8     OraDB19000_home2     19.18.0.0.230117     EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_2     CONFIGURED\nodacli create-prepatchreport -d -i 1cbe3f74-2746-4ab0-81f9-2d1b9f5c3d56 -v 19.16.0.0\nsleep 180 ; odacli describe-prepatchreport -i 55a5e235-096d-4d26-b922-4194c361b16f\n...\nodacli update-dbhome -i 1cbe3f74-2746-4ab0-81f9-2d1b9f5c3d56 -v 19.16.0.0.0 -f\n...\n<\/code><\/pre>\n\n\n\n<p>Once the update is finished, the old DB home can be safely removed:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli list-dbhomes\nID                                       Name                 DB Version           DB Edition Home Location                                            Status\n---------------------------------------- -------------------- -------------------- ---------- -------------------------------------------------------- ----------\n1cbe3f74-2746-4ab0-81f9-2d1b9f5c3d56     OraDB12102_home1     12.1.0.2.220419      EE         \/u01\/app\/odaorahome\/oracle\/product\/12.1.0.2\/dbhome_1     CONFIGURED\n94aba6b1-850b-45d5-b123-c9eade003fa8     OraDB19000_home2     19.18.0.0.230117     EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_2     CONFIGURED\nf715ab11-12a7-4fef-940a-19b71500a93d     OraDB12102_home3     12.1.0.2.220719      EE         \/u01\/app\/odaorahome\/oracle\/product\/12.1.0.2\/dbhome_3     CONFIGURED\n\nodacli delete-dbhome -i 1cbe3f74-2746-4ab0-81f9-2d1b9f5c3d56\n\u2003\nodacli describe-job -i 1b1162a5-38d8-439b-af93-aa7246e69ff9\n...<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-running-again-the-preupgrade\">Running again the preupgrade<\/h2>\n\n\n\n<p>Let&#8217;s retry the preupgrade:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli create-preupgradereport -bm \n<\/code><\/pre>\n\n\n\n<p>Status is now OK:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli describe-preupgradereport -i a2cc67c4-fb43-4556-9e3c-a02b9e53736d\nUpgrade pre-check report\n------------------------------------------------------------------------\n\t\t\t\t Job ID:  a2cc67c4-fb43-4556-9e3c-a02b9e53736d\n\t\t\tDescription:  Run pre-upgrade checks for Bare Metal\n\t\t\t\t Status:  SUCCESS\n\t\t\t\tCreated:  May 27, 2024 2:02:41 PM CEST\n\t\t\t\t Result:  All pre-checks succeeded\n...\n<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-detach-the-configuration\">Detach the configuration<\/h2>\n\n\n\n<p>Now let&#8217;s do the detach to prepare our ODA for reimaging:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli detach-node -all\n********************************************************************************\n\t\t\t\t\t\t\t\t  IMPORTANT\n********************************************************************************\n'odacli detach-node' will bring down the databases and grid services on the\nsystem. The files that belong to the databases, which are stored on ASM or ACFS,\nare left intact on the storage. The databases will be started up back after\nre-imaging the ODA system using 'odacli restore-node' commands. As a good\nprecautionary measure, please backup all the databases on the system before you\nstart this process. Do not store the backup on this ODA machine since the local\nfile system will be wiped out as part of the re-image.\n********************************************************************************\n\nDo you want to continue (yes\/no)&#091;no] : yes\n\nodacli describe-job -i \"37cbd5df-708f-4631-872d-f574dd1279e0\"\nJob details\n----------------------------------------------------------------\n                     ID:  37cbd5df-708f-4631-872d-f574dd1279e0\n            Description:  Detach node service creation for upgrade\n                 Status:  Success\n                Created:  May 27, 2024 2:35:38 PM CEST\n                Message:  On successful job completion, the server archive file will be generated at \/opt\/oracle\/oak\/restore\/out. Please copy the server archive file outside of the ODA system before re-image\n...<\/code><\/pre>\n\n\n\n<p>Detach is OK. You must now copy the content of \/opt\/oracle\/oak\/restore\/out outside the ODA, for example on a NFS share and\/or your local computer. YOU MUST DO THIS BACKUP BEFORE REIMAGING unless you will not be able to use your data anymore. These files are mandatory for attaching again your data to the new system version.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-reimaging\">Reimaging<\/h2>\n\n\n\n<p>Reimaging is done through the ILOM as described in the ODA documentation. Just connect the 19.22 ISO under the storage menu of the remote console of the server, define CDROM as the next boot device, and do a power cycle.<\/p>\n\n\n\n<p>Reimaging is an automated process and it takes less than 1 hour to complete.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-firstnet-configuration\">Firstnet configuration<\/h2>\n\n\n\n<p>Our system is now &#8220;brand new&#8221;, and you will need to connect with default credentials (root\/welcome1) on the remote console to do the firstnet configuration:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>configure-firstnet\n<\/code><\/pre>\n\n\n\n<p>You can find parameters for this initial network configuration inside the detach zipfile:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>cat serverarchive_oratest04\/restore\/configure-firstnet.rsp\n# ------------------------------------------------------------\n# This file was generated by the ODA detach-node code flow.\n# Don't modify this file\n# \n# Created On: 2024-05-27 14:35:38\n# Version: 19.22.0.0.0\n# Feature: Data Preserving\n# Re-provisioning\n# \n# To be used for configure-firstnet post\n# reimage\n# ------------------------------------------------------------\n\nHOSTNAME=oratest04\nINTERFACE_NAME=btbond1\nVLAN=NO\nIP_ADDR=10.10.32.126\nSUBNET_MASK=255.255.255.0\nGATEWAY=10.10.32.1<\/code><\/pre>\n\n\n\n<p>Now the server is back online in your network, and you may connect your NFS shares, for example the one where the patchfiles reside:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>echo \"10.10.32.100:\/data\/vol_data_490\/ODA_backups \/backup nfs defaults  0 0\" &gt;&gt; \/etc\/fstab\nsystemctl daemon-reload\nmkdir \/backup\nmount -a<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-update-the-microcodes\">Update the microcodes<\/h2>\n\n\n\n<p>Reimaging never updates the firmwares (BIOS, ILOM, etc), you&#8217;ll have to update them right now:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli describe-component\nSystem Version\n---------------\n19.22.0.0.0\n\nSystem node Name\n---------------\noak\n\nLocal System Version\n---------------\n19.22.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSCONTROLLER\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSCLI\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSAGENT\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSADMIN\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nOS\n\t\t\t\t\t\t  8.9                   up-to-date\nILOM\n\t\t\t\t\t\t  5.1.0.23.r146986      5.1.3.20.r153596\nBIOS\n\t\t\t\t\t\t  52080100              52110200\nLOCAL CONTROLLER FIRMWARE\n\t\t\t\t\t\t  8000C470              8000D9AB\nSHARED CONTROLLER FIRMWARE\n\t\t\t\t\t\t  VDV1RL05              VDV1RL06\nLOCAL DISK FIRMWARE\n\t\t\t\t\t\t  D3MU001               up-to-date\nHMP\n\t\t\t\t\t\t  2.4.9.2.600           up-to-date\n\n\nodacli update-repository -f \/backup\/patch\/19_22\/Server\/oda-sm-19.22.0.0.0-240306-server.zip\n\nsleep 60 ; odacli describe-job -i \"b341b9cd-0294-4112-a080-24466a3a13e7\"\n...\n\nodacli create-prepatchreport -s -v 19.22.0.0.0\n\nsleep 180 ; odacli describe-prepatchreport -i afd38dae-69f7-46a2-abe6-cff15b31ad37\nPatch pre-check report\n------------------------------------------------------------------------\nJob ID:  afd38dae-69f7-46a2-abe6-cff15b31ad37\nDescription:  Patch pre-checks for &#091;OS, ILOM, SERVER]\nStatus:  SUCCESS\nCreated:  May 27, 2024 2:35:22 PM UTC\nResult:  All pre-checks succeeded\n\n...\n\nodacli update-server -v 19.22.0.0.0\n\nodacli describe-job -i \"3bf82e72-eda6-4e03-b363-ee872b7ca8e8\"\nJob details\n----------------------------------------------------------------\nJob ID:  3bf82e72-eda6-4e03-b363-ee872b7ca8e8\nDescription:  Server Patching\nStatus:  Success\nCreated:  May 27, 2024 2:37:02 PM UTC\nMessage:\n\n...<\/code><\/pre>\n\n\n\n<p>Server reboots at the end of this update. Note that you may need to wait several minutes after the reboot to see BIOS and ILOM updated.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli describe-component\nSystem Version\n---------------\n19.22.0.0.0\n\nSystem node Name\n---------------\noak\n\nLocal System Version\n---------------\n19.22.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSCONTROLLER\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSCLI\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSAGENT\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSADMIN\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nOS\n\t\t\t\t\t\t  8.9                   up-to-date\nILOM\n\t\t\t\t\t\t  5.1.3.20.r153596      up-to-date\nBIOS\n\t\t\t\t\t\t  52110200              up-to-date\nLOCAL CONTROLLER FIRMWARE\n\t\t\t\t\t\t  8000D9AB              up-to-date\nSHARED CONTROLLER FIRMWARE\n\t\t\t\t\t\t  VDV1RL05              VDV1RL06\nLOCAL DISK FIRMWARE\n\t\t\t\t\t\t  D3MU001               up-to-date\nHMP\n\t\t\t\t\t\t  2.4.9.2.600           up-to-date<\/code><\/pre>\n\n\n\n<p>Now let&#8217;s patch the storage:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-storage -v 19.22.0.0.0\n\nodacli describe-job -i f829abeb-5755-491c-9463-825b0eca5409\n...\n<\/code><\/pre>\n\n\n\n<p>The server reboots again, then checking the version shows that everything is &#8220;up-to-date&#8221;:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli describe-component\nSystem Version\n---------------\n19.22.0.0.0\n\nSystem node Name\n---------------\noak\n\nLocal System Version\n---------------\n19.22.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSCONTROLLER\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSCLI\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSAGENT\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nDCSADMIN\n\t\t\t\t\t\t  19.22.0.0.0           up-to-date\nOS\n\t\t\t\t\t\t  8.9                   up-to-date\nILOM\n\t\t\t\t\t\t  5.1.3.20.r153596      up-to-date\nBIOS\n\t\t\t\t\t\t  52110200              up-to-date\nLOCAL CONTROLLER FIRMWARE\n\t\t\t\t\t\t  8000D9AB              up-to-date\nSHARED CONTROLLER FIRMWARE\n\t\t\t\t\t\t  VDV1RL06              up-to-date\nLOCAL DISK FIRMWARE\n\t\t\t\t\t\t  D3MU001               up-to-date\nHMP\n\t\t\t\t\t\t  2.4.9.2.600           up-to-date\n<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-restore-node-gi-part\">Restore node &#8211; GI part<\/h2>\n\n\n\n<p>Let&#8217;s register the GI clone version 19.22 as well as the detach files, then restore the ODA configuration:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-repository -f \/backup\/patch\/19_22\/Grid\/odacli-dcs-19.22.0.0.0-240306-GI-19.22.0.0.zip\n\nodacli describe-job -i \"d8b33efb-9f66-461c-89ea-f0db33e22cba\"\n...\n\nodacli update-repository -f \/backup\/patch\/19_22\/oratest04\/root\/oda_nodes\/serverarchive_oratest04.zip\n\nodacli describe-job -i \"e0c5b0cf-86bb-4961-9861-1ef598b9d6d9\"\n...\n\nodacli restore-node -g\nEnter New system password: *************\nRetype New system password: *************\nEnter an initial password for Web Console account (oda-admin): *************\nRetype the password for Web Console account (oda-admin): *************\nUser 'oda-admin' created successfully...\n\nodacli describe-job -i 3f2aed36-b654-4df5-ab63-23a740adb5cc\n...<\/code><\/pre>\n\n\n\n<p>Restore node takes 25+ minutes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-restore-node-databases\">Restore node &#8211; databases<\/h2>\n\n\n\n<p>Now it&#8217;s time to restore our databases:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli restore-node -d\n\nodacli describe-job -i \"0081ba7a-f987-40ef-95af-62654c18e354\"\nJob details\n----------------------------------------------------------------\nJob ID:  0081ba7a-f987-40ef-95af-62654c18e354\nDescription:  Restore node service - DB\nStatus:  Success\nCreated:  May 27, 2024 5:51:25 PM CEST\nMessage:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- -------\t\nSetting up SSH equivalence for 'oracle'  May 27, 2024 5:51:29 PM CEST             May 27, 2024 5:51:30 PM CEST             Success\nRestore BM CPU Pools                     May 27, 2024 5:51:30 PM CEST             May 27, 2024 5:51:30 PM CEST             Success\nRegister DB home: OraDB19000_home2       May 27, 2024 5:51:30 PM CEST             May 27, 2024 5:51:33 PM CEST             Success\nRegister DB home: OraDB12102_home3       May 27, 2024 5:51:33 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nPersist database storage locations       May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for MCHDEV                 May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for MCHREF                 May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for LV01DEV                May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for LV02DEV                May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for MCHTST                 May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for LV02TST                May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for MCHBAC                 May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for BRRTST                 May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for LV01TST                May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for DBTEST                 May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for KGED19TS               May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for BRFTST                 May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for BRSLTST                May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nSave metadata for BRCLATST               May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Success\nPersist database storages                May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:57 PM CEST             Skipped\nRestore database: MCHDEV                 May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:53:03 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 5:51:57 PM CEST             May 27, 2024 5:51:59 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 5:51:59 PM CEST             May 27, 2024 5:51:59 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 5:51:59 PM CEST             May 27, 2024 5:52:33 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 5:52:33 PM CEST             May 27, 2024 5:52:33 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 5:52:33 PM CEST             May 27, 2024 5:52:49 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 5:52:49 PM CEST             May 27, 2024 5:52:49 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 5:52:49 PM CEST             May 27, 2024 5:52:49 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 5:52:49 PM CEST             May 27, 2024 5:53:03 PM CEST             Success\nRestore database: MCHREF                 May 27, 2024 5:53:03 PM CEST             May 27, 2024 5:54:03 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 5:53:03 PM CEST             May 27, 2024 5:53:04 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 5:53:04 PM CEST             May 27, 2024 5:53:04 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 5:53:04 PM CEST             May 27, 2024 5:53:38 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 5:53:39 PM CEST             May 27, 2024 5:53:39 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 5:53:39 PM CEST             May 27, 2024 5:53:54 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 5:53:54 PM CEST             May 27, 2024 5:53:54 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 5:53:54 PM CEST             May 27, 2024 5:53:54 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 5:53:54 PM CEST             May 27, 2024 5:54:03 PM CEST             Success\nRestore database: LV01DEV                May 27, 2024 5:54:03 PM CEST             May 27, 2024 5:55:15 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 5:54:03 PM CEST             May 27, 2024 5:54:05 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 5:54:05 PM CEST             May 27, 2024 5:54:05 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 5:54:05 PM CEST             May 27, 2024 5:54:40 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 5:54:40 PM CEST             May 27, 2024 5:54:40 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 5:54:40 PM CEST             May 27, 2024 5:54:55 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 5:54:55 PM CEST             May 27, 2024 5:54:55 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 5:54:55 PM CEST             May 27, 2024 5:54:56 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 5:54:56 PM CEST             May 27, 2024 5:55:15 PM CEST             Success\nRestore database: LV02DEV                May 27, 2024 5:55:15 PM CEST             May 27, 2024 5:56:29 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 5:55:15 PM CEST             May 27, 2024 5:55:17 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 5:55:17 PM CEST             May 27, 2024 5:55:17 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 5:55:17 PM CEST             May 27, 2024 5:55:51 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 5:55:51 PM CEST             May 27, 2024 5:55:51 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 5:55:51 PM CEST             May 27, 2024 5:56:07 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 5:56:07 PM CEST             May 27, 2024 5:56:07 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 5:56:07 PM CEST             May 27, 2024 5:56:07 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 5:56:07 PM CEST             May 27, 2024 5:56:29 PM CEST             Success\nRestore database: MCHTST                 May 27, 2024 5:56:29 PM CEST             May 27, 2024 5:57:30 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 5:56:29 PM CEST             May 27, 2024 5:56:30 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 5:56:30 PM CEST             May 27, 2024 5:56:30 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 5:56:30 PM CEST             May 27, 2024 5:57:05 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 5:57:05 PM CEST             May 27, 2024 5:57:05 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 5:57:05 PM CEST             May 27, 2024 5:57:20 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 5:57:20 PM CEST             May 27, 2024 5:57:20 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 5:57:20 PM CEST             May 27, 2024 5:57:21 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 5:57:21 PM CEST             May 27, 2024 5:57:30 PM CEST             Success\nRestore database: LV02TST                May 27, 2024 5:57:30 PM CEST             May 27, 2024 5:58:30 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 5:57:30 PM CEST             May 27, 2024 5:57:32 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 5:57:32 PM CEST             May 27, 2024 5:57:32 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 5:57:32 PM CEST             May 27, 2024 5:58:06 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 5:58:06 PM CEST             May 27, 2024 5:58:06 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 5:58:06 PM CEST             May 27, 2024 5:58:22 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 5:58:22 PM CEST             May 27, 2024 5:58:22 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 5:58:22 PM CEST             May 27, 2024 5:58:22 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 5:58:22 PM CEST             May 27, 2024 5:58:30 PM CEST             Success\nRestore database: MCHBAC                 May 27, 2024 5:58:30 PM CEST             May 27, 2024 5:59:41 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 5:58:30 PM CEST             May 27, 2024 5:58:32 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 5:58:32 PM CEST             May 27, 2024 5:58:32 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 5:58:32 PM CEST             May 27, 2024 5:59:07 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 5:59:07 PM CEST             May 27, 2024 5:59:07 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 5:59:07 PM CEST             May 27, 2024 5:59:23 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 5:59:23 PM CEST             May 27, 2024 5:59:23 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 5:59:24 PM CEST             May 27, 2024 5:59:24 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 5:59:24 PM CEST             May 27, 2024 5:59:41 PM CEST             Success\nRestore database: BRRTST                 May 27, 2024 5:59:41 PM CEST             May 27, 2024 6:01:24 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 5:59:41 PM CEST             May 27, 2024 5:59:42 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 5:59:42 PM CEST             May 27, 2024 5:59:42 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 5:59:42 PM CEST             May 27, 2024 6:00:16 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 6:00:16 PM CEST             May 27, 2024 6:00:16 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 6:00:16 PM CEST             May 27, 2024 6:00:38 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 6:00:38 PM CEST             May 27, 2024 6:00:38 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 6:00:38 PM CEST             May 27, 2024 6:00:39 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 6:00:39 PM CEST             May 27, 2024 6:01:24 PM CEST             Success\nRestore database: LV01TST                May 27, 2024 6:01:24 PM CEST             May 27, 2024 6:02:40 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 6:01:24 PM CEST             May 27, 2024 6:01:26 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 6:01:26 PM CEST             May 27, 2024 6:01:26 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 6:01:26 PM CEST             May 27, 2024 6:02:01 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 6:02:01 PM CEST             May 27, 2024 6:02:01 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 6:02:01 PM CEST             May 27, 2024 6:02:18 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 6:02:18 PM CEST             May 27, 2024 6:02:18 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 6:02:18 PM CEST             May 27, 2024 6:02:18 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 6:02:18 PM CEST             May 27, 2024 6:02:40 PM CEST             Success\nRestore database: DBTEST                 May 27, 2024 6:02:40 PM CEST             May 27, 2024 6:03:59 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 6:02:40 PM CEST             May 27, 2024 6:02:42 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 6:02:42 PM CEST             May 27, 2024 6:02:42 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 6:02:42 PM CEST             May 27, 2024 6:03:17 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 6:03:17 PM CEST             May 27, 2024 6:03:17 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 6:03:17 PM CEST             May 27, 2024 6:03:34 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 6:03:34 PM CEST             May 27, 2024 6:03:34 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 6:03:35 PM CEST             May 27, 2024 6:03:35 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 6:03:35 PM CEST             May 27, 2024 6:03:59 PM CEST             Success\nRestore database: KGED19TS               May 27, 2024 6:03:59 PM CEST             May 27, 2024 6:06:32 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 6:03:59 PM CEST             May 27, 2024 6:04:02 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 6:04:02 PM CEST             May 27, 2024 6:04:02 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 6:04:02 PM CEST             May 27, 2024 6:04:37 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 6:04:37 PM CEST             May 27, 2024 6:04:38 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 6:04:38 PM CEST             May 27, 2024 6:04:57 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 6:04:58 PM CEST             May 27, 2024 6:04:58 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 6:04:58 PM CEST             May 27, 2024 6:04:58 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 6:04:58 PM CEST             May 27, 2024 6:06:32 PM CEST             Success\nRestore database: BRFTST                 May 27, 2024 6:06:32 PM CEST             May 27, 2024 6:08:28 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 6:06:32 PM CEST             May 27, 2024 6:06:34 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 6:06:34 PM CEST             May 27, 2024 6:06:34 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 6:06:35 PM CEST             May 27, 2024 6:07:09 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 6:07:09 PM CEST             May 27, 2024 6:07:09 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 6:07:09 PM CEST             May 27, 2024 6:07:33 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 6:07:33 PM CEST             May 27, 2024 6:07:33 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 6:07:33 PM CEST             May 27, 2024 6:07:33 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 6:07:33 PM CEST             May 27, 2024 6:08:28 PM CEST             Success\nRestore database: BRSLTST                May 27, 2024 6:08:28 PM CEST             May 27, 2024 6:10:16 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 6:08:28 PM CEST             May 27, 2024 6:08:30 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 6:08:31 PM CEST             May 27, 2024 6:08:31 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 6:08:31 PM CEST             May 27, 2024 6:09:05 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 6:09:05 PM CEST             May 27, 2024 6:09:05 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 6:09:05 PM CEST             May 27, 2024 6:09:27 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 6:09:27 PM CEST             May 27, 2024 6:09:27 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 6:09:27 PM CEST             May 27, 2024 6:09:27 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 6:09:27 PM CEST             May 27, 2024 6:10:16 PM CEST             Success\nRestore database: BRCLATST               May 27, 2024 6:10:16 PM CEST             May 27, 2024 6:12:13 PM CEST             Success\n+-- Adding database to GI                May 27, 2024 6:10:17 PM CEST             May 27, 2024 6:10:18 PM CEST             Success\n+-- Adding database instance(s) to GI    May 27, 2024 6:10:18 PM CEST             May 27, 2024 6:10:18 PM CEST             Success\n+-- Modifying SPFILE for database        May 27, 2024 6:10:19 PM CEST             May 27, 2024 6:10:53 PM CEST             Success\n+-- Restore password file for database   May 27, 2024 6:10:54 PM CEST             May 27, 2024 6:10:54 PM CEST             Skipped\n+-- Start instance(s) for database       May 27, 2024 6:10:54 PM CEST             May 27, 2024 6:11:16 PM CEST             Success\n+-- Persist metadata for database        May 27, 2024 6:11:16 PM CEST             May 27, 2024 6:11:16 PM CEST             Success\n+-- Create adrci directory               May 27, 2024 6:11:16 PM CEST             May 27, 2024 6:11:16 PM CEST             Success\n+-- Run SqlPatch                         May 27, 2024 6:11:16 PM CEST             May 27, 2024 6:12:13 PM CEST             Success\nRestore Object Stores                    May 27, 2024 6:12:13 PM CEST             May 27, 2024 6:12:13 PM CEST             Success\nRemount NFS backups                      May 27, 2024 6:12:13 PM CEST             May 27, 2024 6:12:13 PM CEST             Success\nRestore BackupConfigs                    May 27, 2024 6:12:13 PM CEST             May 27, 2024 6:12:13 PM CEST             Success\nReattach backupconfigs to DBs            May 27, 2024 6:12:13 PM CEST             May 27, 2024 6:12:13 PM CEST             Success\nRestore backup reports                   May 27, 2024 6:12:13 PM CEST             May 27, 2024 6:12:13 PM CEST             Success<\/code><\/pre>\n\n\n\n<p>Our 12cR1 databases are restored without any problem, as well as 19c ones.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-next-steps-when-using-dpr\">Next steps when using DPR<\/h2>\n\n\n\n<p>Your 12.1 databases will never get another update, but it does not apply to 19c databases. Using DPR will not update your 19.18 databases to 19.22: you need to apply classic patching method to update them. Download the 19.22 DB clone, register this clone into the ODA repository and do the prepatch report on your first 19c DB home. Then patch the DB home to 19.22:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli update-repository -f \/backup\/patch\/19_22\/DB\/odacli-dcs-19.22.0.0.0-240306-DB-19.22.0.0.zip\n...\n\nodacli create-prepatchreport -d -i 84cb4f9a-7c45-432b-9e4a-c58f2fe53ca0 -v 19.22.0.0.0\n...\n\nodacli describe-prepatchreport -i a9811a90-0f62-4648-86e5-c9a5adaf1be5\n...\n\nodacli update-dbhome -i 84cb4f9a-7c45-432b-9e4a-c58f2fe53ca0 -v 19.22.0.0.0 -f\n...<\/code><\/pre>\n\n\n\n<p>As all databases from this 19.18 are now linked to a new 19.22 DB home, the old DB home is not needed anymore, let&#8217;s remove it:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>odacli delete-dbhome -i 84cb4f9a-7c45-432b-9e4a-c58f2fe53ca0\n\u2003\nodacli describe-job -i 814d1792-95a6-4592-90b5-42d0b271917b\n...\n\nodacli list-dbhomes\nID                                       Name                 DB Version           DB Edition Home Location                                            Status\n---------------------------------------- -------------------- -------------------- ---------- -------------------------------------------------------- ----------\nda2a5bef-9e79-49e2-b811-b7a8b9283bd9     OraDB12102_home3     12.1.0.2.220719      EE         \/u01\/app\/odaorahome\/oracle\/product\/12.1.0.2\/dbhome_3     CONFIGURED\nf221039f-1430-488e-b853-e3a3fc518020     OraDB19000_home3     19.22.0.0.240116     EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_3     CONFIGURED<\/code><\/pre>\n\n\n\n<p>If you have multiple 19c DB homes, you will need to repeat this update for each DB home.<\/p>\n\n\n\n<p>If your ODA is also running VMs and\/or DB Systems, you will need to do a restore-node -kvm then a restore-node -dbs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-conclusion\">Conclusion<\/h2>\n\n\n\n<p>Keeping 12cR1 is still possible when upgrading to 19.21 or later, but you should know that it&#8217;s because there is no reason for Oracle to remove your existing DB homes and databases. For a fresh setup without using DPR, I would recommend putting old DB homes and databases inside a VM. Unlike DB Systems, VM content is not managed by odacli, therefore you can use whatever OS and whatever Oracle release you need. Without any support of any kind, for sure.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction Since patch version 19.21 (current one is 19.23), ODA (Oracle Database Appliance) X7, X8 and X9 will require the use of Data Preserving Reprovisioning (DPR) to get the patch. Unlike traditional patching, DPR erases the system disks but keeps data on ASM\/ACFS disks. Data includes databases, ACFS volumes, DB homes, vDisks for DB Systems [&hellip;]<\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[59],"tags":[],"type_dbi":[],"class_list":["post-33653","post","type-post","status-publish","format-standard","hentry","category-oracle"],"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>Is DPR compatible with 12.1 databases running on your ODA? - 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\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Is DPR compatible with 12.1 databases running on your ODA?\" \/>\n<meta property=\"og:description\" content=\"Introduction Since patch version 19.21 (current one is 19.23), ODA (Oracle Database Appliance) X7, X8 and X9 will require the use of Data Preserving Reprovisioning (DPR) to get the patch. Unlike traditional patching, DPR erases the system disks but keeps data on ASM\/ACFS disks. Data includes databases, ACFS volumes, DB homes, vDisks for DB Systems [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2024-06-12T14:30:00+00:00\" \/>\n<meta name=\"author\" content=\"J\u00e9r\u00f4me Dubar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"J\u00e9r\u00f4me Dubar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 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\\\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\\\/\"},\"author\":{\"name\":\"J\u00e9r\u00f4me Dubar\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"headline\":\"Is DPR compatible with 12.1 databases running on your ODA?\",\"datePublished\":\"2024-06-12T14:30:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\\\/\"},\"wordCount\":1156,\"commentCount\":0,\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\\\/\",\"name\":\"Is DPR compatible with 12.1 databases running on your ODA? - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2024-06-12T14:30:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Is DPR compatible with 12.1 databases running on your ODA?\"}]},{\"@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\\\/0fb4bbf128b4cda2f96d662dec2baedd\",\"name\":\"J\u00e9r\u00f4me Dubar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g\",\"caption\":\"J\u00e9r\u00f4me Dubar\"},\"description\":\"J\u00e9r\u00f4me Dubar has more than 15 years of experience in the field of Information Technology. Ten years ago, he specialized in the Oracle Database technology. His expertise is focused on database architectures, high availability (RAC), disaster recovery (DataGuard), backups (RMAN), performance analysis and tuning (AWR\\\/statspack), migration, consolidation and appliances, especially ODA (his main projects during the last years). Prior to joining dbi services, J\u00e9r\u00f4me Dubar worked in a Franco-Belgian IT service company as Database team manager and main consultant for 7 years. He also worked for 5 years in a software editor company as technical consultant across France. He was also teaching Oracle Database lessons for 9 years. J\u00e9r\u00f4me Dubar holds a Computer Engineering degree from the Lille Sciences and Technologies university in northern France. His branch-related experience covers the public sector, retail, industry, banking, health, e-commerce and IT sectors.\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/author\\\/jerome-dubar\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Is DPR compatible with 12.1 databases running on your ODA? - 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\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/","og_locale":"en_US","og_type":"article","og_title":"Is DPR compatible with 12.1 databases running on your ODA?","og_description":"Introduction Since patch version 19.21 (current one is 19.23), ODA (Oracle Database Appliance) X7, X8 and X9 will require the use of Data Preserving Reprovisioning (DPR) to get the patch. Unlike traditional patching, DPR erases the system disks but keeps data on ASM\/ACFS disks. Data includes databases, ACFS volumes, DB homes, vDisks for DB Systems [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/","og_site_name":"dbi Blog","article_published_time":"2024-06-12T14:30:00+00:00","author":"J\u00e9r\u00f4me Dubar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"J\u00e9r\u00f4me Dubar","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/"},"author":{"name":"J\u00e9r\u00f4me Dubar","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"headline":"Is DPR compatible with 12.1 databases running on your ODA?","datePublished":"2024-06-12T14:30:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/"},"wordCount":1156,"commentCount":0,"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/","url":"https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/","name":"Is DPR compatible with 12.1 databases running on your ODA? - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2024-06-12T14:30:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/is-dpr-compatible-with-12-1-databases-running-on-your-oda\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Is DPR compatible with 12.1 databases running on your ODA?"}]},{"@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\/0fb4bbf128b4cda2f96d662dec2baedd","name":"J\u00e9r\u00f4me Dubar","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/efaa5a7def0aa4cdaf49a470fb4a7641a3ea6e378ae1455096a0933f99f46d6b?s=96&d=mm&r=g","caption":"J\u00e9r\u00f4me Dubar"},"description":"J\u00e9r\u00f4me Dubar has more than 15 years of experience in the field of Information Technology. Ten years ago, he specialized in the Oracle Database technology. His expertise is focused on database architectures, high availability (RAC), disaster recovery (DataGuard), backups (RMAN), performance analysis and tuning (AWR\/statspack), migration, consolidation and appliances, especially ODA (his main projects during the last years). Prior to joining dbi services, J\u00e9r\u00f4me Dubar worked in a Franco-Belgian IT service company as Database team manager and main consultant for 7 years. He also worked for 5 years in a software editor company as technical consultant across France. He was also teaching Oracle Database lessons for 9 years. J\u00e9r\u00f4me Dubar holds a Computer Engineering degree from the Lille Sciences and Technologies university in northern France. His branch-related experience covers the public sector, retail, industry, banking, health, e-commerce and IT sectors.","url":"https:\/\/www.dbi-services.com\/blog\/author\/jerome-dubar\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/33653","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\/45"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=33653"}],"version-history":[{"count":7,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/33653\/revisions"}],"predecessor-version":[{"id":33660,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/33653\/revisions\/33660"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=33653"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=33653"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=33653"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=33653"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}