{"id":30434,"date":"2024-01-24T16:51:25","date_gmt":"2024-01-24T15:51:25","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=30434"},"modified":"2024-02-13T09:43:02","modified_gmt":"2024-02-13T08:43:02","slug":"how-to-patch-your-oda-to-19-21","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/","title":{"rendered":"How to patch your ODA to 19.21?"},"content":{"rendered":"\n

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

Patch 19.21 is now available for Oracle Database Appliance series. Let’s find out what’s new and how to apply this patch.<\/p>\n\n\n\n

What’s new?<\/h2>\n\n\n\n

The most important new component is Linux 8. X10 series were already running on Linux 8 with a dedicated patch (19.20.0.1), but older ODAs were stuck with Linux 7 since years.<\/p>\n\n\n\n

This version also brings latest 19c RU to database and grid homes (bug and security fixes). 23c is not yet available on ODA and 21.8 is proposed as DB System only. Note that 21c being an innovation release, its main purpose if for testing some 23c features.<\/p>\n\n\n\n

Nothing really new apart from OS major update this time, but this update was a long awaited one as Linux 9 is already available since months.<\/p>\n\n\n\n

Which ODA is compatible with this 19.21 release?<\/h2>\n\n\n\n

The newest ODAs X10-HA, X10-L and X10-S are supported, as well as X9, X8 and X7. And that’s it. X6 series and X5-2HA are no longer supported since last year. X7-2 series becoming rather old now, you should start thinking about renewal this year or in early 2025. I usually recommend keeping your ODA 7 years<\/a>.<\/p>\n\n\n\n

Is this patch a cumulative one?<\/h2>\n\n\n\n

On X10, this 19.21 can be applied on top of 19.20.0.1 for sure, as the OS is already Linux 8.<\/p>\n\n\n\n

For X9\/X8\/X7, you can apply 19.21 starting from 19.16 and later, but there is a catch. Patch will not be applied on top of your system, but system will need a fresh reimaging using DPR (Data Preserving Reprovisioning). It means that internal disks will be erased, OS will be redeployed and you will loose your specific system configurations. DPR will first “unplug” your ODA configuration in a set of files, and then plug in back after reimaging is done. It also means that you will not be able to use ODABR as a safety backup of your filesystems. If you compare this DPR patching to classic patching, it means more risks because it’s not possible to revert to old OS state.<\/p>\n\n\n\n

In my environment, I will use an ODA X8-2M running 19.20 with multiple DB homes, databases, DB Systems and VMs. I will not describe applying this patch on X10 series as I don’t have this kind of ODA.<\/p>\n\n\n\n

Is there also a patch for my databases?<\/h2>\n\n\n\n

Only databases version 19c are supported, and this is OK because this is the only one you should use now.<\/p>\n\n\n\n

If you absolutely need an older release, I would recommend configuring an application VM for that purpose, as described here<\/a>, but it comes without any guarantee of any kind.<\/p>\n\n\n\n

Download the patch, ISO and clone files<\/h2>\n\n\n\n

35938481 => the patch itself
30403673 => the GI clone needed for deploying newer GI version (mandatory)
30403662 => the DB clone for deploying new version of 19c
30403643 => ISO file for reimaging (mandatory if you have X9\/X8\/X7)
32451228 => System image for DB Systems (if you use them)<\/p>\n\n\n\n

Be sure to choose the very latest 19.21 when downloading the clones and the ISO, download link from MOS will first propose older version 19.4.<\/p>\n\n\n\n

Prepare the patching<\/h2>\n\n\n\n

The prerequisites are different compared to a classic patching, just because your current OS configuration will be wiped out:<\/p>\n\n\n\n

    \n
  • make sure you have a procedure to put back your specific system settings<\/li>\n\n\n\n
  • backup your specifics scripts\/files to an external drive<\/li>\n\n\n\n
  • check that backup is external and OK for all your databases (bare metal and DB Systems)<\/li>\n\n\n\n
  • do a VM backup (vDisk backup) on an external drive<\/li>\n\n\n\n
  • plan a confortable downtime for patching (I would recommend 1+ day)<\/li>\n<\/ul>\n\n\n\n

    As ODABR is useless (system disks will be erased), I would recommend doing a backup of the most important files: tnsnames.ora and listener.ora, database list, network configuration files, crontabs, home directory of system users, aso. If something goes wrong, you may need to do a full reimaging, meaning restoring everything from the backups.<\/p>\n\n\n\n

    Version precheck<\/h2>\n\n\n\n

    Start to check current version on all the components:<\/p>\n\n\n\n

    odacli describe-component\nSystem Version\n---------------\n19.20.0.0.0\n\nSystem node Name\n---------------\ndbi-oda1\n\nLocal System Version\n---------------\n19.20.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK\n                                          19.20.0.0.0           up-to-date\nGI\n                                          19.20.0.0.230718      up-to-date\nDB {\n[OraDB19000_home2 [bsn01]]\n                                          19.19.0.0.230418      19.20.0.0.230718\n[OraDB19000_home3 [DBITST,LTTST]]\n                                          19.20.0.0.230718      up-to-date\n[OraDB19000_home4 [WS12C,MYBRCDB,DBWEI]]\n                                          19.20.0.0.230718      up-to-date\n[OraDB19000_home6]\n                                          19.20.0.0.230718      up-to-date\n[OraDB12201_home1]\n                                          12.2.0.1.220118       not-available\n}\nDCSCONTROLLER\n                                          19.20.0.0.0           up-to-date\nDCSCLI\n                                          19.20.0.0.0           up-to-date\nDCSAGENT\n                                          19.20.0.0.0           up-to-date\nDCSADMIN\n                                          19.20.0.0.0           up-to-date\nOS\n                                          7.9                   up-to-date\nILOM\n                                          5.1.1.23.r151750      up-to-date\nBIOS\n                                          52100600              up-to-date\nLOCAL CONTROLLER FIRMWARE {\n[c3]\n                                          80000681              up-to-date\n[c4]\n                                          8000C470              up-to-date\n}\nSHARED CONTROLLER FIRMWARE\n                                          VDV1RL06              up-to-date\nLOCAL DISK FIRMWARE\n                                          XC311132              up-to-date\nSHARED DISK FIRMWARE\n                                          XC311132              up-to-date\nHMP\n                                          2.4.9.0.601           up-to-date<\/code><\/pre>\n\n\n\n
    List the DB homes, databases, DB Systems and VMs:<\/p>\n\n\n\n
    odacli list-dbhomes\nID                                       Name                 DB Version                               DB Edition Home Location                                 Status\n---------------------------------------- -------------------- ---------------------------------------- ---------- --------------------------------------------- ----------\nf5c8e73a-f7dd-4142-a6b9-e571d02a5298     OraDB19000_home2     19.19.0.0.230418                         SE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED\n                                                                                                                  .0\/dbhome_2\n6359448d-fbcd-4063-a677-f061d6f4d196     OraDB19000_home3     19.20.0.0.230718                         SE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED\n                                                                                                                  .0\/dbhome_3\n1a89c106-9c9d-4219-b116-6c84aef5f668     OraDB19000_home4     19.20.0.0.230718                         EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED\n                                                                                                                  .0\/dbhome_4\ncefeaca6-1d68-4f16-91a3-dc3de982cae1     OraDB19000_home6     19.20.0.0.230718                         EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED\n                                                                                                                  .0\/dbhome_6\nde47b591-4040-49f9-99e7-b854a6df1b14     OraDB12201_home1     12.2.0.1.220118                          SE         \/u01\/app\/odaorahome\/oracle\/product\/12.2.0     CONFIGURED\n                                                                                                                  .1\/dbhome_1\n\n\nodacli list-databases\nID                                       DB Name    DB Type  DB Version           CDB     Class    Edition  Shape    Storage  Status       DB Home ID\n---------------------------------------- ---------- -------- -------------------- ------- -------- -------- -------- -------- ------------ ----------------------------------------\n63f06b37-282d-4972-90cd-b60a1a3c853e     DBITST     SI       19.20.0.0.230718     true    OLTP     SE       odb1     ASM      CONFIGURED   6359448d-fbcd-4063-a677-f061d6f4d196\n0f85bd3a-a63e-465c-9285-035a4d7242d7     WS12C      SI       19.20.0.0.230718     false   OLTP     EE       odb1     ACFS     CONFIGURED   1a89c106-9c9d-4219-b116-6c84aef5f668\ne490fe71-d35e-404f-b799-f8fdb388f21f     TST23      SI       19.20.0.0.230718     false   OLTP     SE       odb1     ACFS     CONFIGURED   26794187-3e84-4fdd-b054-82bbd3e1b7fa\ne723b4d7-05bf-4a78-874e-fcfd52b3765d     MYBRCDB    SI       19.20.0.0.230718     false   OLTP     EE       odb1     ASM      CONFIGURED   1a89c106-9c9d-4219-b116-6c84aef5f668\n445b84b1-8c84-4a59-b302-fe96a380abe5     bsn01      SI       19.19.0.0.230418     true    OLTP     SE       odb2     ASM      CONFIGURED   f5c8e73a-f7dd-4142-a6b9-e571d02a5298\na591d3b1-8c59-4edf-a1d4-b662903ccf5c     DBWEI      SI       19.20.0.0.230718     true    OLTP     EE       odb1     ASM      CONFIGURED   1a89c106-9c9d-4219-b116-6c84aef5f668\n110d18aa-f084-4b7f-ac96-6734dddb6d54     LTTST      SI       19.20.0.0.230718     false   OLTP     SE       odb1     ACFS     CONFIGURED   6359448d-fbcd-4063-a677-f061d6f4d196\n\n\nodacli list-dbsystems\nName                  Shape       Cores  Memory      GI version          DB version          Status           Created                   Updated\n--------------------  ----------  -----  ----------  ------------------  ------------------  ---------------  ------------------------  ------------------------\ntestdbs02             odb2        2      16.00 GB    19.20.0.0.230718    N\/A                 CONFIGURED       2024-01-04 13:47:20 CET   2024-01-04 14:20:50 CET\ntestdbs01             odb2        2      16.00 GB    19.20.0.0.230718    19.20.0.0.230718    CONFIGURED       2024-01-04 12:07:05 CET   2024-01-04 12:39:39 CET\n\n\nodacli list-vms\nName                  VM Storage            Current State    Target State     Created                   Updated\n--------------------  --------------------  ---------------  ---------------  ------------------------  ------------------------\nubuntu02              VMstore               ONLINE           ONLINE           2023-12-07 15:06:57 CET   2023-12-07 15:06:57 CET\nVMMAW01               VMstore               ONLINE           ONLINE           2023-12-07 14:51:32 CET   2023-12-07 14:51:32 CET\ndelphix               VMstore               ONLINE           ONLINE           2024-01-03 15:49:57 CET   2024-01-04 10:38:07 CET\nubuntu01              VMstore               ONLINE           ONLINE           2023-12-07 15:05:54 CET   2023-12-07 15:05:54 CET\n<\/code><\/pre>\n\n\n\n
    Update the DCS components<\/h2>\n\n\n\n
    Before reimaging, an update of the DCS components is required for correct unplugging of the ODA system:<\/p>\n\n\n\n
    cd \/opt\/dbi\nunzip p35938481_1921000_Linux-x86-64.zip\n\nodacli update-repository -f \/opt\/dbi\/oda-sm-19.21.0.0.0-231220-server.zip\nsleep 30 ; odacli describe-job -i \"91189839-e855-48ea-a6b1-7d9695da52a5\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  91189839-e855-48ea-a6b1-7d9695da52a5\n            Description:  Repository Update\n                 Status:  Success\n                Created:  January 9, 2024 4:04:55 PM CET\n                Message:  \/opt\/dbi\/oda-sm-19.21.0.0.0-231220-server.zip\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nUnzip bundle                             January 9, 2024 4:04:55 PM CET      January 9, 2024 4:05:30 PM CET      Success\n\n\nodacli describe-component\n\nSystem Version\n---------------\n19.20.0.0.0\n\nSystem node Name\n---------------\ndbi-oda1\n\nLocal System Version\n---------------\n19.20.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK\n                                          19.20.0.0.0           19.21.0.0.0\nGI\n                                          19.20.0.0.230718      19.21.0.0.231017\nDB {\n[OraDB19000_home2 [bsn01]]\n                                          19.19.0.0.230418      19.21.0.0.231017\n[OraDB19000_home3 [DBITST,LTTST]]\n                                          19.20.0.0.230718      19.21.0.0.231017\n[OraDB19000_home4 [WS12C,MYBRCDB,DBWEI]]\n                                          19.20.0.0.230718      19.21.0.0.231017\n[OraDB19000_home6]\n                                          19.20.0.0.230718      19.21.0.0.231017\n[OraDB12201_home1]\n                                          12.2.0.1.220118       not-available\n}\nDCSCONTROLLER\n                                          19.20.0.0.0           19.21.0.0.0\nDCSCLI\n                                          19.20.0.0.0           19.21.0.0.0\nDCSAGENT\n                                          19.20.0.0.0           19.21.0.0.0\nDCSADMIN\n                                          19.20.0.0.0           19.21.0.0.0\nOS\n                                          7.9                   8.8\nILOM\n                                          5.1.1.23.r151750      5.1.3.20.r153596\nBIOS\n                                          52100600              52110200\nLOCAL CONTROLLER FIRMWARE {\n[c3]\n                                          80000681              up-to-date\n[c4]\n                                          8000C470              8000D9AB\n}\nSHARED CONTROLLER FIRMWARE\n                                          VDV1RL06              up-to-date\nLOCAL DISK FIRMWARE\n                                          XC311132              up-to-date\nSHARED DISK FIRMWARE\n                                          XC311132              up-to-date\nHMP\n                                          2.4.9.0.601           2.4.9.1.601<\/code><\/pre>\n\n\n\n
    Let’s update the DCS components to 19.21:<\/p>\n\n\n\n
    odacli update-dcsadmin -v 19.21.0.0.0\n\nsleep 30 ; odacli describe-job -i \"e28f0d1f-aecf-4a5c-a1d9-c8dd4ab4a2ee\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  e28f0d1f-aecf-4a5c-a1d9-c8dd4ab4a2ee\n            Description:  DcsAdmin patching\n                 Status:  Success\n                Created:  January 9, 2024 4:10:12 PM CET\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nPatch location validation                January 9, 2024 4:10:12 PM CET      January 9, 2024 4:10:12 PM CET      Success\nDcs-admin upgrade                        January 9, 2024 4:10:12 PM CET      January 9, 2024 4:10:18 PM CET      Success\n\n\nsleep 30 ;  odacli update-dcscomponents -v 19.21.0.0.0\n{\n  \"jobId\" : \"7e7b3ca7-a23c-4fd6-aa33-67f8cc2afea2\",\n  \"status\" : \"Success\",\n  \"message\" : \" DCS-Agent shutdown is successful. Skipping MySQL upgrade on OL7 Metadata schema update is done. dcsagent RPM upgrade is successful. dcscli RPM upgrade is successful. dcscontroller RPM upgrade is successful.  Successfully reset the Keystore password.  HAMI is not enabled  Skipped removing old Libs. Successfully ran setupAgentAuth.sh \",\n  \"reports\" : null,\n  \"createTimestamp\" : \"January 09, 2024 16:11:44 PM CET\",\n  \"description\" : \"Update-dcscomponents job completed and is not part of Agent job list\",\n  \"updatedTime\" : \"January 09, 2024 16:12:50 PM CET\"\n}\n\n\nodacli update-dcsagent -v 19.21.0.0.0\n\nsleep 180 ; odacli describe-job -i \"8a6af503-3512-43eb-aff1-290ef301f72b\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  8a6af503-3512-43eb-aff1-290ef301f72b\n            Description:  DcsAgent patching\n                 Status:  Success\n                Created:  January 9, 2024 4:13:31 PM CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nDcs-agent upgrade  to version            January 9, 2024 4:13:31 PM CET           January 9, 2024 4:15:48 PM CET           Success\n19.21.0.0.0\nUpdate System version                    January 9, 2024 4:15:48 PM CET           January 9, 2024 4:15:48 PM CET           Success\n<\/code><\/pre>\n\n\n\n
    Create a pre-upgrade report<\/h2>\n\n\n\n
    The pre-upgrade report will tell you if your ODA is OK for unplugging its configuration:<\/p>\n\n\n\n
    odacli create-preupgradereport -bm\n\nodacli describe-preupgradereport -i 12e859fb-5d39-4390-a6a9-a490657727e3\n\nUpgrade pre-check report\n------------------------------------------------------------------------\n                 Job ID:  12e859fb-5d39-4390-a6a9-a490657727e3\n            Description:  Run pre-upgrade checks for Bare Metal\n                 Status:  FAILED\n                Created:  January 9, 2024 4:35:06 PM CET\n                 Result:  One or more pre-checks failed for [DB, DBSYSTEMS]\n\nNode Name\n---------------\ndbi-oda1\n\nCheck                          Status   Message                                Action\n------------------------------ -------- -------------------------------------- --------------------------------------\n__GI__\nCheck presence of databases    Success  No additional database found           None\nnot managed by ODA                      registered in CRS\nCheck custom filesystems       Success  All file systems are owned and used    None\n                                        by OS users provisioned by ODA\nCheck presence of HAVIP        Success  No HAVIP resources found registered    None\nresources not managed by ODA            in CRS\nCheck presence of export       Success  No EXPORT resources found registered   None\nresources not managed by ODA            in CRS\n\n__OS__\nCheck Required OS files        Success  All the required files are present     None\nCheck Additional OS RPMs       Success  No RPMs outside of base ISO were       None\n                                        found on the system\n\n__STORAGE__\nCheck Required Storage files   Success  All the required files are present     None\nValidate OAK Disks             Success  All OAK disks are in valid state       None\nValidate ASM Disk Groups       Success  All ASM disk groups are in valid state None\nValidate ASM Disks             Success  All ASM disks are in valid state       None\nCheck Database Home Storage    Success  The volume(s) orahome_sh,odabase_n0    None\nvolumes                                 state is CONFIGURED.\nCheck space under \/opt         Success  Free space on \/opt: 10441.96 MB is     None\n                                        more than required space: 1188 MB\nCheck space in ASM disk        Success  Space required for creating local      None\ngroup(s)                                homes is present in ACFS database\n                                        home storage. Required: 0 GB\n                                        Available: 38 GB\n\n__SYS__\nValidate Hardware Type         Success  Current hardware is supported          None\nValidate ILOM interconnect     Success  ILOM interconnect is not enabled       None\nValidate System Version        Success  System version 19.21.0.0.0 is          None\n                                        supported\nVerify System Timezone         Success  Succesfully verified the time zone     None\n                                        file\nVerify Grid User               Success  Grid user is verified                  None\nVerify Grid Version            Success  Oracle Grid Infrastructure is running  None\n                                        on the '19.20.0.0.230718' version on\n                                        all nodes\nCheck Audit Files              Success  Local Audit files not found            None\n\n__DB__\nValidate Database Status       Success  Database 'DBITST' is running and is    None\n                                        in 'CONFIGURED' state\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'DBITST' is supported\nValidate Database Datapatch    Success  Database 'DBITST' is completely        None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'DBITST' is not TDE enabled.  None\n                                        Skipping TDE wallet presence check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database DBITST\nValidate Database Status       Success  Database 'WS12C' is running and is in  None\n                                        'CONFIGURED' state\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'WS12C' is supported\nValidate Database Datapatch    Success  Database 'WS12C' is completely         None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'WS12C' is not TDE enabled.   None\n                                        Skipping TDE wallet presence check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database WS12C_SITE1\nValidate Database Status       Failed   DCS-10001:Internal error encountered:  Please check dcs-agent logs\n                                        Did not find the dbhome.\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'TST23' is supported\nValidate Database Datapatch    Failed   Error occurred while checking          Fix the issue and then rerun\nApplication Status                      datapatch application status for       create-preupgradereport' command\n                                        Database 'TST23': DCS-10001:Internal\n                                        error encountered: Database TST23 is\n                                        not registered with clusterware.\nValidate TDE wallet presence   Failed   DCS-10001:Internal error encountered:  Please check dcs-agent logs\n                                        Database TST23 is not registered with\n                                        clusterware.\nValidate Database Home         Failed   ORACLE_HOME for Database TST23 is not  Check why the database home is not\nlocation                                set in CRS                             set in CRS. Please start up the\n                                                                               database if needed.\nValidate Database Status       Success  Database 'MYBRCDB' is running and is   None\n                                        in 'CONFIGURED' state\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'MYBRCDB' is supported\nValidate Database Datapatch    Success  Database 'MYBRCDB' is completely       None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'MYBRCDB' is not TDE          None\n                                        enabled. Skipping TDE wallet presence\n                                        check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database MYBRCDB\nValidate Database Status       Success  Database 'bsn01' is running and is in  None\n                                        'CONFIGURED' state\nValidate Database Version      Success  Version '19.19.0.0.230418' for         None\n                                        database 'bsn01' is supported\nValidate Database Datapatch    Success  Database 'bsn01' is completely         None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'bsn01' is not TDE enabled.   None\n                                        Skipping TDE wallet presence check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database bsn01\nValidate Database Status       Success  Database 'DBWEI' is running and is in  None\n                                        'CONFIGURED' state\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'DBWEI' is supported\nValidate Database Datapatch    Success  Database 'DBWEI' is completely         None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'DBWEI' is not TDE enabled.   None\n                                        Skipping TDE wallet presence check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database DBWEI\nValidate Database Status       Success  Database 'LTTST' is running and is in  None\n                                        'CONFIGURED' state\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'LTTST' is supported\nValidate Database Datapatch    Success  Database 'LTTST' is completely         None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'LTTST' is not TDE enabled.   None\n                                        Skipping TDE wallet presence check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database LTTST\n\n__CERTIFICATES__\nCheck using custom             Success  Using Default key pair                 None\ncertificates\nCheck the agent of the DB      Success  All the agents of the DB systems are   None\nSystem accessible                       accessible\n\n__DBSYSTEMS__\nValidate DB System DCS         Failed   testdbs02: FAIL                        Please ensure DCS components version\ncomponent versions                      [[dcscontroller]:19.20.0.0.0]          match between DB System and BM\n                                        [[dcsagent]:19.20.0.0.0]\n                                        [[dcsadmin]:19.20.0.0.0]\nValidate DB System DCS         Failed   testdbs01: FAIL                        Please ensure DCS components version\ncomponent versions                      [[dcscontroller]:19.20.0.0.0]          match between DB System and BM\n                                        [[dcsagent]:19.20.0.0.0]\n                                        [[dcsadmin]:19.20.0.0.0]<\/code><\/pre>\n\n\n\n
    On my test system, multiple problems are detected.<\/p>\n\n\n\n
    First, I have an orphan database. As this ODA is a sandbox for multiple people, it’s not a problem removing the associated lines from the ODA registry (don’t do that on your production system):<\/p>\n\n\n\n
    systemctl stop initdcsagent\n\ncd \/opt\/oracle\/dcs\/mysql\/bin\/ \r\n.\/mysql -u root --socket=\/opt\/oracle\/dcs\/mysql\/log\/mysqldb.sock \r\nuse dcsagentdb;\n\nmysql> delete from ATTACHED_NETWORKS where db_id='e490fe71-d35e-404f-b799-f8fdb388f21f';\nQuery OK, 1 row affected (0.00 sec)\n\nmysql> commit;\nQuery OK, 0 rows affected (0.00 sec)\n\nmysql> delete from db where name='TST23';\nQuery OK, 1 row affected (0.00 sec)\n\nmysql> commit;\nQuery OK, 0 rows affected (0.00 sec)\n\nexit;\n\nsystemctl start initdcsagent<\/code><\/pre>\n\n\n\n
    I also need to upgrade the DCS components inside each DB System:<\/p>\n\n\n\n
    ssh root@10.36.0.246\nodacli update-dcsadmin -v 19.21.0.0.0\nsleep 30 ;  odacli update-dcscomponents -v 19.21.0.0.0\nodacli update-dcsagent -v 19.21.0.0.0\n...\n<\/code><\/pre>\n\n\n\n
    Now I can go back to my ODA and run the pre-upgrade report again:<\/p>\n\n\n\n
    odacli describe-preupgradereport -i 9526eb2a-6ffa-4f7f-b558-c5a10c09ebc2\n\nUpgrade pre-check report\n------------------------------------------------------------------------\n                 Job ID:  9526eb2a-6ffa-4f7f-b558-c5a10c09ebc2\n            Description:  Run pre-upgrade checks for Bare Metal\n                 Status:  SUCCESS\n                Created:  January 9, 2024 5:04:55 PM CET\n                 Result:  All pre-checks succeeded\n\nNode Name\n---------------\ndbi-oda1\n\nCheck                          Status   Message                                Action\n------------------------------ -------- -------------------------------------- --------------------------------------\n__GI__\nCheck presence of databases    Success  No additional database found           None\nnot managed by ODA                      registered in CRS\nCheck custom filesystems       Success  All file systems are owned and used    None\n                                        by OS users provisioned by ODA\nCheck presence of HAVIP        Success  No HAVIP resources found registered    None\nresources not managed by ODA            in CRS\nCheck presence of export       Success  No EXPORT resources found registered   None\nresources not managed by ODA            in CRS\n\n__OS__\nCheck Required OS files        Success  All the required files are present     None\nCheck Additional OS RPMs       Success  No RPMs outside of base ISO were       None\n                                        found on the system\n\n__STORAGE__\nCheck Required Storage files   Success  All the required files are present     None\nValidate OAK Disks             Success  All OAK disks are in valid state       None\nValidate ASM Disk Groups       Success  All ASM disk groups are in valid state None\nValidate ASM Disks             Success  All ASM disks are in valid state       None\nCheck Database Home Storage    Success  The volume(s) orahome_sh,odabase_n0    None\nvolumes                                 state is CONFIGURED.\nCheck space under \/opt         Success  Free space on \/opt: 10441.57 MB is     None\n                                        more than required space: 1188 MB\nCheck space in ASM disk        Success  Space required for creating local      None\ngroup(s)                                homes is present in ACFS database\n                                        home storage. Required: 0 GB\n                                        Available: 38 GB\n\n__SYS__\nValidate Hardware Type         Success  Current hardware is supported          None\nValidate ILOM interconnect     Success  ILOM interconnect is not enabled       None\nValidate System Version        Success  System version 19.21.0.0.0 is          None\n                                        supported\nVerify System Timezone         Success  Succesfully verified the time zone     None\n                                        file\nVerify Grid User               Success  Grid user is verified                  None\nVerify Grid Version            Success  Oracle Grid Infrastructure is running  None\n                                        on the '19.20.0.0.230718' version on\n                                        all nodes\nCheck Audit Files              Success  Local Audit files not found            None\n\n__DB__\nValidate Database Status       Success  Database 'DBITST' is running and is    None\n                                        in 'CONFIGURED' state\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'DBITST' is supported\nValidate Database Datapatch    Success  Database 'DBITST' is completely        None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'DBITST' is not TDE enabled.  None\n                                        Skipping TDE wallet presence check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database DBITST\nValidate Database Status       Success  Database 'WS12C' is running and is in  None\n                                        'CONFIGURED' state\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'WS12C' is supported\nValidate Database Datapatch    Success  Database 'WS12C' is completely         None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'WS12C' is not TDE enabled.   None\n                                        Skipping TDE wallet presence check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database WS12C_SITE1\nValidate Database Status       Success  Database 'MYBRCDB' is running and is   None\n                                        in 'CONFIGURED' state\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'MYBRCDB' is supported\nValidate Database Datapatch    Success  Database 'MYBRCDB' is completely       None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'MYBRCDB' is not TDE          None\n                                        enabled. Skipping TDE wallet presence\n                                        check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database MYBRCDB\nValidate Database Status       Success  Database 'bsn01' is running and is in  None\n                                        'CONFIGURED' state\nValidate Database Version      Success  Version '19.19.0.0.230418' for         None\n                                        database 'bsn01' is supported\nValidate Database Datapatch    Success  Database 'bsn01' is completely         None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'bsn01' is not TDE enabled.   None\n                                        Skipping TDE wallet presence check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database bsn01\nValidate Database Status       Success  Database 'DBWEI' is running and is in  None\n                                        'CONFIGURED' state\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'DBWEI' is supported\nValidate Database Datapatch    Success  Database 'DBWEI' is completely         None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'DBWEI' is not TDE enabled.   None\n                                        Skipping TDE wallet presence check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database DBWEI\nValidate Database Status       Success  Database 'LTTST' is running and is in  None\n                                        'CONFIGURED' state\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'LTTST' is supported\nValidate Database Datapatch    Success  Database 'LTTST' is completely         None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'LTTST' is not TDE enabled.   None\n                                        Skipping TDE wallet presence check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database LTTST\n\n__CERTIFICATES__\nCheck using custom             Success  Using Default key pair                 None\ncertificates\nCheck the agent of the DB      Success  All the agents of the DB systems are   None\nSystem accessible                       accessible\n\n__DBSYSTEMS__\nValidate DB System DCS         Success  testdbs01: SUCCESS                     None\ncomponent versions\nValidate DB System DCS         Success  testdbs02: SUCCESS                     None\ncomponent versions<\/code><\/pre>\n\n\n\n
    Detach the node<\/h2>\n\n\n\n
    Now, everything is fine and ready for unplugging my ODA configuration:<\/p>\n\n\n\n
    odacli detach-node -all\n********************************************************************************\n                                  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)[no] : yes\n\n{\n  \"jobId\" : \"5b613165-efbb-4de9-b737-2425e6b8471e\",\n  \"status\" : \"Created\",\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  \"reports\" : [ ],\n  \"createTimestamp\" : \"January 09, 2024 17:09:31 PM CET\",\n  \"resourceList\" : [ ],\n  \"description\" : \"Detach node service creation for upgrade\",\n  \"updatedTime\" : \"January 09, 2024 17:09:31 PM CET\",\n  \"jobType\" : null\n}\n\n\nodacli describe-job -i \"5b613165-efbb-4de9-b737-2425e6b8471e\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  5b613165-efbb-4de9-b737-2425e6b8471e\n            Description:  Detach node service creation for upgrade\n                 Status:  Success\n                Created:  January 9, 2024 5:09:31 PM CET\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\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nCreating initialization file             January 9, 2024 5:09:32 PM CET           January 9, 2024 5:09:32 PM CET           Success\nCreating firstnet response file          January 9, 2024 5:09:32 PM CET           January 9, 2024 5:09:32 PM CET           Success\nSaving system information                January 9, 2024 5:09:32 PM CET           January 9, 2024 5:09:32 PM CET           Success\nSaving Appliance data                    January 9, 2024 5:09:32 PM CET           January 9, 2024 5:11:26 PM CET           Success\nSaving OS files                          January 9, 2024 5:09:32 PM CET           January 9, 2024 5:09:32 PM CET           Success\nSaving CPU cores information             January 9, 2024 5:09:32 PM CET           January 9, 2024 5:09:32 PM CET           Success\nSaving storage files                     January 9, 2024 5:09:32 PM CET           January 9, 2024 5:09:32 PM CET           Success\nSaving Volumes                           January 9, 2024 5:09:32 PM CET           January 9, 2024 5:10:02 PM CET           Success\nSaving File Systems                      January 9, 2024 5:10:02 PM CET           January 9, 2024 5:10:26 PM CET           Success\nSaving Quorum Disks                      January 9, 2024 5:10:26 PM CET           January 9, 2024 5:10:27 PM CET           Success\nSaving System                            January 9, 2024 5:10:27 PM CET           January 9, 2024 5:10:28 PM CET           Success\nSaving Networks                          January 9, 2024 5:10:28 PM CET           January 9, 2024 5:10:28 PM CET           Success\nSaving Database Storages                 January 9, 2024 5:10:28 PM CET           January 9, 2024 5:10:46 PM CET           Success\nSaving Database Homes                    January 9, 2024 5:10:46 PM CET           January 9, 2024 5:10:46 PM CET           Success\n+-- Saving OraDB19000_home2              January 9, 2024 5:10:46 PM CET           January 9, 2024 5:10:46 PM CET           Success\n+-- Saving OraDB19000_home3              January 9, 2024 5:10:46 PM CET           January 9, 2024 5:10:46 PM CET           Success\n+-- Saving OraDB19000_home4              January 9, 2024 5:10:46 PM CET           January 9, 2024 5:10:46 PM CET           Success\n+-- Saving OraDB19000_home6              January 9, 2024 5:10:46 PM CET           January 9, 2024 5:10:46 PM CET           Success\n+-- Saving OraDB12201_home1              January 9, 2024 5:10:46 PM CET           January 9, 2024 5:10:46 PM CET           Success\nSaving Databases                         January 9, 2024 5:10:46 PM CET           January 9, 2024 5:11:12 PM CET           Success\n+-- Saving DBITST                        January 9, 2024 5:10:46 PM CET           January 9, 2024 5:10:51 PM CET           Success\n+-- Saving WS12C_SITE1                   January 9, 2024 5:10:51 PM CET           January 9, 2024 5:10:54 PM CET           Success\n+-- Saving MYBRCDB                       January 9, 2024 5:10:54 PM CET           January 9, 2024 5:10:59 PM CET           Success\n+-- Saving bsn01                         January 9, 2024 5:10:59 PM CET           January 9, 2024 5:11:04 PM CET           Success\n+-- Saving DBWEI                         January 9, 2024 5:11:04 PM CET           January 9, 2024 5:11:09 PM CET           Success\n+-- Saving LTTST                         January 9, 2024 5:11:09 PM CET           January 9, 2024 5:11:12 PM CET           Success\nSaving Object swift stores               January 9, 2024 5:11:12 PM CET           January 9, 2024 5:11:12 PM CET           Success\nSaving Database Backups                  January 9, 2024 5:11:12 PM CET           January 9, 2024 5:11:12 PM CET           Success\nSaving NFS Backups                       January 9, 2024 5:11:12 PM CET           January 9, 2024 5:11:12 PM CET           Success\nSaving Certificates and wallets Backup   January 9, 2024 5:11:12 PM CET           January 9, 2024 5:11:12 PM CET           Success\nSaving KVM black-box resources           January 9, 2024 5:11:12 PM CET           January 9, 2024 5:11:16 PM CET           Success\nSaving DB System Resources               January 9, 2024 5:11:16 PM CET           January 9, 2024 5:11:26 PM CET           Success\nCreating databases version list          January 9, 2024 5:11:26 PM CET           January 9, 2024 5:11:26 PM CET           Success\nDeconfiguring Appliance                  January 9, 2024 5:11:26 PM CET           January 9, 2024 5:21:14 PM CET           Success\nDeconfiguring Databases                  January 9, 2024 5:11:26 PM CET           January 9, 2024 5:14:17 PM CET           Success\n+-- Deconfiguring DBITST                 January 9, 2024 5:11:26 PM CET           January 9, 2024 5:11:56 PM CET           Success\n+-- Deconfiguring WS12C_SITE1            January 9, 2024 5:11:56 PM CET           January 9, 2024 5:12:21 PM CET           Success\n+-- Deconfiguring MYBRCDB                January 9, 2024 5:12:21 PM CET           January 9, 2024 5:12:48 PM CET           Success\n+-- Deconfiguring bsn01                  January 9, 2024 5:12:48 PM CET           January 9, 2024 5:13:20 PM CET           Success\n+-- Deconfiguring DBWEI                  January 9, 2024 5:13:20 PM CET           January 9, 2024 5:13:57 PM CET           Success\n+-- Deconfiguring LTTST                  January 9, 2024 5:13:57 PM CET           January 9, 2024 5:14:17 PM CET           Success\nSaving database backup reports           January 9, 2024 5:14:17 PM CET           January 9, 2024 5:14:17 PM CET           Success\nResizing Quorum Disks                    January 9, 2024 5:14:17 PM CET           January 9, 2024 5:14:17 PM CET           Success\nDeconfiguring Grid Infrastructure        January 9, 2024 5:14:17 PM CET           January 9, 2024 5:21:13 PM CET           Success\nBackup Quorum Disks                      January 9, 2024 5:21:13 PM CET           January 9, 2024 5:21:14 PM CET           Success\nCreating the server archive files        January 9, 2024 5:21:14 PM CET           January 9, 2024 5:21:15 PM CET           Success\nZipping the server archive files         January 9, 2024 5:21:15 PM CET           January 9, 2024 5:21:16 PM CET           Success\n<\/code><\/pre>\n\n\n\n
    VERY IMPORTANT<\/strong>: take a copy of files inside \/opt\/oracle\/oak\/restore\/out OUTSIDE the ODA. I would recommend 2 copies on 2 different disks\/systems. Check if you can open the zipfile on your computer. The zipfile name is normaly serverarchive_{hostname}.zip.<\/p>\n\n\n\n
    Reimage the ODA<\/h2>\n\n\n\n
    WARNING: classic reimaging implies using the cleanup.pl script. You must not cleanup anything here: DATA disks content is needed for DPR!<\/p>\n\n\n\n
    Reimaging is done through the ILOM console as if your ODA were brand new. Connect the 19.21 ISO image, select CDROM as next boot drive and do a power cycle of the server. The OS will then be reinstalled from scratch and it should take about 1 hour.<\/p>\n\n\n\n
    Once your ODA is reimaged, don’t forget that credentials have been reset to root\/welcome1.<\/p>\n\n\n\n
    Connect to the ODA remote console from ILOM interface.<\/p>\n\n\n\n
    Configure the initial network settings. You don’t need to remember these settings, you can find them in the configure-firstnet.rsp from the zipfile you picked up after the ODA detach-node operation:<\/p>\n\n\n\n
    cat configure-firstnet.rsp\nHOSTNAME=dbi-oda1\nINTERFACE_NAME=btbond1\nVLAN=NO\nIP_ADDR=10.36.0.241\nSUBNET_MASK=255.255.255.0\nGATEWAY=10.36.0.1<\/code><\/pre>\n\n\n\n
    Patch the microcodes<\/h2>\n\n\n\n
    You now need to copy again the patch file to this “new” ODA. This is because reimaging don’t update the firmware\/BIOS\/ILOM\/storage components:<\/p>\n\n\n\n
    mkdir \/opt\/dbi\n-- patch copy here<\/code><\/pre>\n\n\n\n
    Let’s unzip the patch again and then register it in the ODA registry:<\/p>\n\n\n\n
    unzip p35938481_1921000_Linux-x86-64.zip\nodacli update-repository -f \/opt\/dbi\/oda-sm-19.21.0.0.0-231220-server.zip\n\nsleep 30 ; odacli describe-job -i \"ed4fe6a7-12b4-47c5-a976-0097325d083a\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  ed4fe6a7-12b4-47c5-a976-0097325d083a\n            Description:  Repository Update\n                 Status:  Success\n                Created:  January 10, 2024 7:55:41 AM UTC\n                Message:  \/opt\/dbi\/oda-sm-19.21.0.0.0-231220-server.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nUnzip bundle                             January 10, 2024 7:55:41 AM UTC          January 10, 2024 7:56:06 AM UTC          Success\n<\/code><\/pre>\n\n\n\n
    And now, a prepatch report is needed:<\/p>\n\n\n\n
    odacli create-prepatchreport -s -v 19.21.0.0.0\n\nodacli describe-prepatchreport -i 5512952b-774e-4fab-a3b0-76b5baba1d5b\n\nPatch pre-check report\n------------------------------------------------------------------------\n                 Job ID:  5512952b-774e-4fab-a3b0-76b5baba1d5b\n            Description:  Patch pre-checks for [OS, ILOM, SERVER]\n                 Status:  SUCCESS\n                Created:  January 10, 2024 7:56:56 AM UTC\n                 Result:  All pre-checks succeeded\n\nNode Name\n---------------\noak\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__OS__\nValidate supported versions     Success   Validated minimum supported versions.\nValidate patching tag           Success   Validated patching tag: 19.21.0.0.0.\nIs patch location available     Success   Patch location is available.\nVerify OS patch                 Success   There are no packages available for\n                                          an update\nValidate command execution      Success   Skipped command execution verfication\n                                          - Instance is not provisioned\n\n__ILOM__\nValidate ILOM server reachable  Success   Successfully connected with ILOM\n                                          server using public IP and USB\n                                          interconnect\nValidate supported versions     Success   Validated minimum supported versions.\nValidate patching tag           Success   Validated patching tag: 19.21.0.0.0.\nIs patch location available     Success   Patch location is available.\nChecking Ilom patch Version     Success   Successfully verified the versions\nPatch location validation       Success   Successfully validated location\nValidate command execution      Success   Skipped command execution verfication\n                                          - Instance is not provisioned\n\n__SERVER__\nValidate local patching         Success   Successfully validated server local\n                                          patching\nValidate command execution      Success   Skipped command execution verfication\n                                          - Instance is not provisioned<\/code><\/pre>\n\n\n\n
    Let’s run the update-server. It will skip software updates as our system is brand new:<\/p>\n\n\n\n
    odacli update-server -v 19.21.0.0.0\n\nodacli describe-job -i \"ab669776-c7dd-4f8b-9453-e8c55ad465fa\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  ab669776-c7dd-4f8b-9453-e8c55ad465fa\n            Description:  Server Patching\n                 Status:  Success\n                Created:  January 10, 2024 8:09:08 AM UTC\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nValidate ILOM server reachable           January 10, 2024 8:09:09 AM UTC          January 10, 2024 8:09:09 AM UTC          Success\nStop DCS Admin                           January 10, 2024 8:09:10 AM UTC          January 10, 2024 8:09:11 AM UTC          Success\nGenerate mTLS certificates               January 10, 2024 8:09:11 AM UTC          January 10, 2024 8:09:12 AM UTC          Success\nExporting Public Keys                    January 10, 2024 8:09:12 AM UTC          January 10, 2024 8:09:14 AM UTC          Success\nCreating Trust Store                     January 10, 2024 8:09:14 AM UTC          January 10, 2024 8:09:17 AM UTC          Success\nUpdate config files                      January 10, 2024 8:09:17 AM UTC          January 10, 2024 8:09:17 AM UTC          Success\nRestart DCS Admin                        January 10, 2024 8:09:17 AM UTC          January 10, 2024 8:09:38 AM UTC          Success\nModify BM udev rules                     January 10, 2024 8:09:38 AM UTC          January 10, 2024 8:09:58 AM UTC          Success\nCreating repositories using yum          January 10, 2024 8:09:58 AM UTC          January 10, 2024 8:10:01 AM UTC          Success\nUpdating YumPluginVersionLock rpm        January 10, 2024 8:10:01 AM UTC          January 10, 2024 8:10:01 AM UTC          Success\nApplying OS Patches                      January 10, 2024 8:10:02 AM UTC          January 10, 2024 8:10:06 AM UTC          Success\nCreating repositories using yum          January 10, 2024 8:10:06 AM UTC          January 10, 2024 8:10:06 AM UTC          Success\nApplying HMP Patches                     January 10, 2024 8:10:06 AM UTC          January 10, 2024 8:10:09 AM UTC          Success\nPatch location validation                January 10, 2024 8:10:09 AM UTC          January 10, 2024 8:10:09 AM UTC          Success\nOda-hw-mgmt upgrade                      January 10, 2024 8:10:09 AM UTC          January 10, 2024 8:10:09 AM UTC          Success\nApplying Firmware Disk Patches           January 10, 2024 8:10:10 AM UTC          January 10, 2024 8:10:13 AM UTC          Success\nApplying Firmware Controller Patches     January 10, 2024 8:10:13 AM UTC          January 10, 2024 8:15:07 AM UTC          Success\nChecking Ilom patch Version              January 10, 2024 8:15:07 AM UTC          January 10, 2024 8:15:07 AM UTC          Success\nPatch location validation                January 10, 2024 8:15:07 AM UTC          January 10, 2024 8:15:07 AM UTC          Success\nSave password in Wallet                  January 10, 2024 8:15:07 AM UTC          January 10, 2024 8:15:08 AM UTC          Success\nDisabling IPMI v2                        January 10, 2024 8:15:08 AM UTC          January 10, 2024 8:15:08 AM UTC          Success\nApply Ilom patch                         January 10, 2024 8:15:08 AM UTC          January 10, 2024 8:25:12 AM UTC          Success\nCopying Flash Bios to Temp location      January 10, 2024 8:25:12 AM UTC          January 10, 2024 8:25:12 AM UTC          Success\nUpdate System version                    January 10, 2024 8:25:13 AM UTC          January 10, 2024 8:25:13 AM UTC          Success\nCleanup JRE Home                         January 10, 2024 8:25:13 AM UTC          January 10, 2024 8:25:13 AM UTC          Success\nGenerating and saving BOM                January 10, 2024 8:25:13 AM UTC          January 10, 2024 8:25:17 AM UTC          Success\nPreRebootNode Actions                    January 10, 2024 8:25:17 AM UTC          January 10, 2024 8:25:17 AM UTC          Success\nReboot Ilom                              January 10, 2024 8:25:17 AM UTC          January 10, 2024 8:25:17 AM UTC          Success\n<\/code><\/pre>\n\n\n\n
    It was not needed on my ODA coming from 19.20, but you may also need to update your storage:<\/p>\n\n\n\n
    odacli update-storage -v 19.21.0.0.0\n...\nodacli describe-component\nSystem Version\n---------------\n19.21.0.0.0\n\nSystem node Name\n---------------\noak\n\nLocal System Version\n---------------\n19.21.0.0.0\n\nComponent                                Installed Version    Available Version\n---------------------------------------- -------------------- --------------------\nOAK\n                                          19.21.0.0.0           up-to-date\nDCSCONTROLLER\n                                          19.21.0.0.0           up-to-date\nDCSCLI\n                                          19.21.0.0.0           up-to-date\nDCSAGENT\n                                          19.21.0.0.0           up-to-date\nDCSADMIN\n                                          19.21.0.0.0           up-to-date\nOS\n                                          8.8                   up-to-date\nILOM\n                                          5.1.3.20.r153596      up-to-date\nBIOS\n                                          52110200              up-to-date\nLOCAL CONTROLLER FIRMWARE\n                                          8000D9AB              up-to-date\nSHARED CONTROLLER FIRMWARE\n                                          VDV1RL06              up-to-date\nLOCAL DISK FIRMWARE\n                                          XC311132              up-to-date\nHMP\n                                          2.4.9.1.601           up-to-date\n<\/code><\/pre>\n\n\n\n
    <\/p>\n\n\n\n
    Register the GI clone and the “unplug” file<\/h2>\n\n\n\n
    Copy the 19.21 GI clone and zipfile resulting from detach-node operation:<\/p>\n\n\n\n
    unzip p30403673_1921000_Linux-x86-64.zip\nodacli update-repository -f \/opt\/dbi\/odacli-dcs-19.21.0.0.0-231211-GI-19.21.0.0.zip\n\nsleep 30 ; odacli describe-job -i \"d89b9524-792f-4b14-9b84-e76fd048cafa\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  d89b9524-792f-4b14-9b84-e76fd048cafa\n            Description:  Repository Update\n                 Status:  Success\n                Created:  January 10, 2024 8:44:19 AM UTC\n                Message:  \/opt\/dbi\/odacli-dcs-19.21.0.0.0-231211-GI-19.21.0.0.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nUnzip bundle                             January 10, 2024 8:44:20 AM UTC          January 10, 2024 8:44:51 AM UTC          Success\n\n\nodacli update-repository -f \/opt\/dbi\/serverarchive_dbi-oda1.zip\n\nsleep 10 ; odacli describe-job -i \"4ddd1a16-3c5e-4f05-a81b-00d16032f53c\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  4ddd1a16-3c5e-4f05-a81b-00d16032f53c\n            Description:  Repository Update\n                 Status:  Success\n                Created:  January 10, 2024 8:46:42 AM UTC\n                Message:  \/opt\/dbi\/serverarchive_dbi-oda1.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nUnzip bundle                             January 10, 2024 8:46:42 AM UTC          January 10, 2024 8:46:43 AM UTC          Success<\/code><\/pre>\n\n\n\n
    Restore the GI configuration<\/h2>\n\n\n\n
    Now it’s time to restore your GI configuration on top of a new GI home setup, it’s done with the restore-node operation:<\/p>\n\n\n\n
    odacli 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...\nDCS-10001:Internal error encountered: Failed to validate provision request \/opt\/oracle\/oak\/restore\/metadata\/provisionInstance.json: DCS-10045:Validation error encountered: Hostname 'dbi-oda1' does not resolve to a unique IP address..\n<\/code><\/pre>\n\n\n\n
    At this time, your ODA may not be able to use DNS resolution for host and ILOM hostnames, you can add them to your \/etc\/hosts file and retry the restore-node:<\/p>\n\n\n\n
    vi \/etc\/hosts\n10.36.0.241     dbi-oda1\n10.36.0.240     dbi-oda01-ilom\n\nodacli restore-node -g\nEnter New system password:\nRetype New system password:\n\nodacli describe-job -i \"6183aa14-fdb4-440a-be0c-c3d673082df4\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  6183aa14-fdb4-440a-be0c-c3d673082df4\n            Description:  Restore node service - GI\n                 Status:  Failure (To view Error Correlation report, run \"odacli describe-job -i 6183aa14-fdb4-440a-be0c-c3d673082df4 --ecr\" command)\n                Created:  January 10, 2024 9:54:34 AM CET\n                Message:  DCS-10001:Internal error encountered: Failed to restart network service.\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nRestore node service creation            January 10, 2024 9:54:46 AM CET          January 10, 2024 9:55:03 AM CET          Failure\nRestore node service creation            January 10, 2024 9:54:47 AM CET          January 10, 2024 9:55:03 AM CET          Failure\nRestore node service creation            January 10, 2024 9:54:47 AM CET          January 10, 2024 9:55:03 AM CET          Failure\nProvisioning service creation            January 10, 2024 9:54:47 AM CET          January 10, 2024 9:55:03 AM CET          Failure\nProvisioning service creation            January 10, 2024 9:54:47 AM CET          January 10, 2024 9:55:03 AM CET          Failure\nNetwork setup                            January 10, 2024 9:54:49 AM CET          January 10, 2024 9:55:03 AM CET          Failure\nProvisioning service creation            January 10, 2024 9:54:50 AM CET          January 10, 2024 9:55:03 AM CET          Failure\nSetting up Network                       January 10, 2024 9:54:51 AM CET          January 10, 2024 9:54:51 AM CET          Success\nProvisioning service creation            January 10, 2024 9:54:51 AM CET          January 10, 2024 9:55:03 AM CET          Failure\nRestarting Network Service               January 10, 2024 9:54:51 AM CET          January 10, 2024 9:55:03 AM CET          Failure<\/code><\/pre>\n\n\n\n
    Unfortunately, it didn’t work for me at first try, let’s do the troubleshooting:<\/p>\n\n\n\n
    odacli describe-job -i 6183aa14-fdb4-440a-be0c-c3d673082df4 --ecr\nODA Assistant - Error Correlation report\n----------------------------------------\n          Failed job ID:  6183aa14-fdb4-440a-be0c-c3d673082df4\n            Description:  Restore node service - GI\n             Start Time:  2024-01-10 08:54:46\n               End Time:  2024-01-10 08:55:03\n         EC report path: \/opt\/oracle\/dcs\/da\/da_repo\/d051b53d-e35f-4374-8c6f-7e840b144b63.json\n\nFailed Task Messages\n--------------------\n[Restore node service - GI] -  DCS-10001:Internal error encountered: Failed to restart network service.\n\ndbi-oda1 Log Messages\n----------------------------\n  DCS Agent\n  ~~~~~~~~~\n    Error Logs\n    ==========\n    [Restarting Network Service] - Failed to restart service 'network'\n    [Restarting Network Service] - Fail to restart network service\n    [Restarting Network Service] - Task got exception:\n    [Provisioning service creation] - DCS-10001:Internal error encountered: Failed to restart network service.\n      Error code - DCS-10001\n      Cause: An internal error occurred.\n      Action: Contact Oracle Support for assistance.\n    Warning Logs\n    ============\n    [[ SEND-THREAD 124 ]] - [ [ SEND-THREAD 124 ] dcs0-priv:22001] Request failed: Operation: GET Host: dcs0-priv:22001 Path: \/joblocks\/6183aa14-fdb4-440a-be0c-c3d673082df4 Data: null Status: 404\n\nRelease Notes\n-------------\n  No matching results were found.\n\nDocumentation\n-------------\n  1. Error in restore node process in Data Preserving Reprovisioning\n      Abstract - In the Data Preserving Reprovisioning process, during node restore, an error may be encountered.\n      Link - https:\/\/dbi-oda1.dbi-lab.ch:7093\/docs\/cmtrn\/issues-with-oda-odacli.html#GUID-F1385628-9F87-4FEF-8D27-289A3ED459EC\n  2. Error in restore node process in Data Preserving Reprovisioning\n      Abstract - In the Data Preserving Reprovisioning process, during node restore, an error may be encountered.\n      Link - https:\/\/dbi-oda1.dbi-lab.ch:7093\/docs\/cmtrn\/issues-with-oda-odacli.html#GUID-75D52887-D425-4753-AF44-EFAB5C148873\n  3. Managing Backup, Restore, and Recovery on a Database System in a KVM Deployment\n      Abstract - Understand the backup, restore, and recovery operations supported on a database system in a KVM deployment.\n      Link - https:\/\/dbi-oda1.dbi-lab.ch:7093\/docs\/cmtxn\/managing-oracle-database-appliance-kvm-deployment1.html#GUID-7318F4D7-4CB8-486C-9DC7-A7490925B866\n  4. Backup, Restore and Recover Databases\n      Abstract - Review backup, restore, and recovery operations for your databases.\n      Link - https:\/\/dbi-oda1.dbi-lab.ch:7093\/docs\/cmtxn\/backup-recover-restore.html#GUID-032C43EC-20B9-4036-ADA9-7631EEBBFEF6\n  5. Reimaging an Oracle Database Appliance Baremetal System\n      Abstract - Reimage Oracle Database Appliance to perform a bare metal restore of Oracle Database Appliance.\n      Link - https:\/\/dbi-oda1.dbi-lab.ch:7093\/docs\/cmtxn\/reimaging-oda.html#GUID-C4D52E9A-C516-4B4F-829F-E102317AE986\n\nNOTE: For additional details such as file name and line numbers of error logs, please refer to \/opt\/oracle\/dcs\/da\/da_repo\/d051b53d-e35f-4374-8c6f-7e840b144b63.json<\/code><\/pre>\n\n\n\n
    Something is wrong with my network, let’s try to restart it:<\/p>\n\n\n\n
    service network restart\nRestarting network (via systemctl):  Job for network.service failed because the control process exited with error code.\nSee \"systemctl status network.service\" and \"journalctl -xe\" for details.\n                                                           [FAILED]\nsystemctl status network.service\n\u25cf network.service - LSB: Bring up\/down networking\n   Loaded: loaded (\/etc\/rc.d\/init.d\/network; generated)\n   Active: failed (Result: exit-code) since Wed 2024-01-10 11:41:13 CET; 3s ago\n     Docs: man:systemd-sysv-generator(8)\n  Process: 6948 ExecStart=\/etc\/rc.d\/init.d\/network start (code=exited, status=1\/FAILURE)\n    Tasks: 0 (limit: 79998)\n   Memory: 4.2M\n   CGroup: \/system.slice\/network.service\n\nJan 10 11:41:13 dbi-oda1 network[7709]: RTNETLINK answers: File exists\nJan 10 11:41:13 dbi-oda1 network[7710]: RTNETLINK answers: File exists\nJan 10 11:41:13 dbi-oda1 network[7711]: RTNETLINK answers: File exists\nJan 10 11:41:13 dbi-oda1 network[7712]: RTNETLINK answers: File exists\nJan 10 11:41:13 dbi-oda1 network[7713]: RTNETLINK answers: File exists\nJan 10 11:41:13 dbi-oda1 network[7714]: RTNETLINK answers: File exists\nJan 10 11:41:13 dbi-oda1 network[7715]: RTNETLINK answers: File exists\nJan 10 11:41:13 dbi-oda1 systemd[1]: network.service: Control process exited, code=exited status=1\nJan 10 11:41:13 dbi-oda1 systemd[1]: network.service: Failed with result 'exit-code'.\nJan 10 11:41:13 dbi-oda1 systemd[1]: Failed to start LSB: Bring up\/down networking.\n\n\ntail \/var\/log\/messages\nJan 10 11:47:47 dbi-oda1 network[8003]: Bringing up interface enp0s20f0u8u3c2:\nJan 10 11:47:47 dbi-oda1 network[8534]: Error: Connection activation failed: No suitable device found for this connection (device virbr0 not available because profile is not compatible with device (mismatching interface name)).\nJan 10 11:47:47 dbi-oda1 network[8003]: [FAILED]\n\nls -lrt  \/etc\/sysconfig\/network-scripts\/ifcfg-*\n-rw-r--r--. 1 root root 160 Jan  9 18:54 \/etc\/sysconfig\/network-scripts\/ifcfg-em1\n-rw-r--r--. 1 root root 186 Jan  9 18:54 \/etc\/sysconfig\/network-scripts\/ifcfg-p7p3\n-rw-r--r--. 1 root root 186 Jan  9 18:54 \/etc\/sysconfig\/network-scripts\/ifcfg-p7p4\n-rw-r--r--. 1 root root 218 Jan  9 18:54 \/etc\/sysconfig\/network-scripts\/ifcfg-btbond2\n-rw-r--r--. 1 root root 186 Jan  9 18:54 \/etc\/sysconfig\/network-scripts\/ifcfg-p7p1\n-rw-r--r--. 1 root root 186 Jan  9 18:54 \/etc\/sysconfig\/network-scripts\/ifcfg-p7p2\n-rw-r--r--. 1 root root 264 Jan  9 18:54 \/etc\/sysconfig\/network-scripts\/ifcfg-lo\n-rw-r--r--. 1 root root 177 Jan  9 18:55 \/etc\/sysconfig\/network-scripts\/ifcfg-priv0\n-rw-r--r--  1 root root 263 Jan 10 08:26 \/etc\/sysconfig\/network-scripts\/ifcfg-btbond1\n-rw-r--r--  1 root root 136 Jan 10 09:54 \/etc\/sysconfig\/network-scripts\/ifcfg-pubnet\n-rw-r--r--  1 root root 146 Jan 10 11:48 \/etc\/sysconfig\/network-scripts\/ifcfg-enp0s20f0u8u3c2\n<\/code><\/pre>\n\n\n\n
    I don’t know where interface enp0s20f0u8u3c2 come from. My ODA is using a single Ethernet card with 4 ports (p7px), the em1 interface is there but never used on ODA, the 2-port bondings are here, pubnet virtual interface is here. But enp0s20f0u8u3c2 shouldn’t be there. Let’s remove the script and restart the network:<\/p>\n\n\n\n
    mv \/etc\/sysconfig\/network-scripts\/ifcfg-enp0s20f0u8u3c2 \/opt\/dbi\/\nservice network restart\nRestarting network (via systemctl):                        [  OK  ]<\/code><\/pre>\n\n\n\n
    It’s better now.<\/p>\n\n\n\n
    Let’s retry the restore-node:<\/p>\n\n\n\n
    odacli restore-node -g\nEnter New system password:\nRetype New system password:\nDCS-10045:Validation error encountered: System has already undergone provisioning with status 'FAILED'.\n<\/code><\/pre>\n\n\n\n
    OK, doing the restore-node is no more possible because it already restored some stuff. I need to do a cleanup, and the cleanup MUST destect that DPR is used:<\/p>\n\n\n\n
    \/opt\/oracle\/oak\/onecmd\/cleanup.pl\nINFO: Log file is \/opt\/oracle\/oak\/log\/dbi-oda1\/cleanup\/cleanup_2024-01-23_10-36-34.log\n\nINFO: Log file is \/opt\/oracle\/oak\/log\/dbi-oda1\/cleanup\/dcsemu_diag_precleanup_2024-01-23_10-36-34.log\n\nINFO: Platform is 'BM'\nINFO: *******************************************************************\nINFO: ** Starting process to cleanup provisioned host dbi-oda1         **\nINFO: *******************************************************************\nWARNING: DPR environment detected. DPR specific cleanup involves\nWARNING: deconfiguring the ODA software stack without touching ASM\nWARNING: storage to allow rerunning of the 'odacli restore-node -g'\nWARNING: command. If regular cleanup(which erases ASM disk headers)\nWARNING: is intended, rerun cleanup.pl with '-nodpr' option.\nWARNING: If Multi-User Access is enabled, use '-omausers' option to\nWARNING: delete the custom users created during the previous run.\nDo you want to continue (yes\/no) : yes\nINFO:\nRunning cleanup will delete Grid User - 'grid' and\nINFO: DB user - 'oracle' and also the\nINFO: groups 'oinstall,dba,asmadmin,asmoper,asmdba'\nINFO: nodes will be rebooted\nDo you want to continue (yes\/no) : yes\nINFO: *************************************\nINFO: ** Checking for GI bits presence\nINFO: *************************************\nINFO: No Grid Infrastructure files were found on the system in the \/u01\/app directory.\n\nINFO: *************************************\nINFO: ** DPR Cleanup\nINFO: *************************************\nINFO: Nothing to do.\nSUCCESS: DPR cleanup actions completed.\nINFO: Attempting to stop DCS agent on local node\n\nINFO: *************************************\nINFO: ** Executing AFD cleanup commands\nINFO: *************************************\nINFO: *************************************\nINFO: ** Cleaning Oracle HAMI for ODA\nINFO: *************************************\nINFO: ** - Oracle HAMI for ODA - ensembles cleaned successfully\nINFO: ** - Oracle HAMI for ODA - users cleaned successfully\nINFO: *************************************\nINFO: ** Executing stack deinstall commands\nINFO: *************************************\nINFO: *************************************\nINFO: ** Removing IPC objects\nINFO: *************************************\npgrep: invalid user name: oracle\nINFO: Cleaning up IDM configurations...\nDeleting directory <\/opt\/oracle\/dcs\/idm>INFO: *************************************\nINFO: ** Cleaning miscellaneous components:\nINFO: *************************************\nINFO: ** - reset limits.conf\nINFO: ** - delete users\nINFO: ** - delete groups\nINFO: ** - hostname, gateway and hosts reset commands\nINFO: ** - dcs cleanup and orphan files removal commands\nINFO: Attempting to clean MySQL tables on local node\n\nINFO: Cleaning up network bridges\nINFO: default net is: pubnet\nINFO: \/etc\/sysconfig\/network-scripts\/ifcfg-btbond1 has an ip-address stored in it\nINFO: *************************************\nINFO: ** Removing KVM files\nINFO: *************************************\nINFO: *************************************\nINFO: ** Removing BM CPU Pool files\nINFO: *************************************\nINFO: ** - networking cleaning commands\nINFO: ** - UTC reset commands\nINFO: *************************************\nINFO: ** Removing Oracle AHF RPM\nINFO: *************************************\nINFO: No need to uninstall Oracle AHF RPM\nINFO: Cleaning up ACFS mounts...\nINFO: Reset password for 'root' to default value\nINFO: Executing <command to reset root password to default value>\nINFO: Removing SSH keys on dbi-oda1\n\nINFO: Rebooting the system via <reboot>...\nINFO: Executing <reboot>\n\n\nINFO: Cleanup was successful\nINFO: Log file is \/opt\/oracle\/oak\/log\/dbi-oda1\/cleanup\/cleanup_2024-01-23_10-36-34.log\n\nWARNING: After system reboot, please re-run \"odacli update-repository\" for GI\/DB clones,\nWARNING: before running \"odacli restore-node -g\".<\/code><\/pre>\n\n\n\n
    Now my system reboots and I will need to redo the configure-firstnet for inital network configuration. Hopefully, cleanup will keep my \/opt\/dbi folder with all the needed files. I just need to register the files into the ODA registry again:<\/p>\n\n\n\n
    odacli update-repository -f \/opt\/dbi\/oda-sm-19.21.0.0.0-231220-server.zip\n\nsleep 60 ; odacli describe-job -i \"8a70333a-ebfd-419f-8e99-09b150bf627e\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  8a70333a-ebfd-419f-8e99-09b150bf627e\n            Description:  Repository Update\n                 Status:  Success\n                Created:  January 23, 2024 9:59:18 AM UTC\n                Message:  \/opt\/dbi\/oda-sm-19.21.0.0.0-231220-server.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nUnzip bundle                             January 23, 2024 9:59:18 AM UTC          January 23, 2024 9:59:43 AM UTC          Success\n\nodacli create-prepatchreport -s -v 19.21.0.0.0\n\nsleep 120 ; odacli describe-prepatchreport -i 071ece64-a9be-4f11-a3c0-8aec8c39cb14\n\nPatch pre-check report\n------------------------------------------------------------------------\n                 Job ID:  071ece64-a9be-4f11-a3c0-8aec8c39cb14\n            Description:  Patch pre-checks for [OS, ILOM, SERVER]\n                 Status:  SUCCESS\n                Created:  January 23, 2024 10:02:05 AM UTC\n                 Result:  All pre-checks succeeded\n\nNode Name\n---------------\noak\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__OS__\nValidate supported versions     Success   Validated minimum supported versions.\nValidate patching tag           Success   Validated patching tag: 19.21.0.0.0.\nIs patch location available     Success   Patch location is available.\nVerify OS patch                 Success   There are no packages available for\n                                          an update\nValidate command execution      Success   Skipped command execution verfication\n                                          - Instance is not provisioned\n\n__ILOM__\nValidate ILOM server reachable  Success   Successfully connected with ILOM\n                                          server using public IP and USB\n                                          interconnect\nValidate supported versions     Success   Validated minimum supported versions.\nValidate patching tag           Success   Validated patching tag: 19.21.0.0.0.\nIs patch location available     Success   Patch location is available.\nChecking Ilom patch Version     Success   Successfully verified the versions\nPatch location validation       Success   Successfully validated location\nValidate command execution      Success   Skipped command execution verfication\n                                          - Instance is not provisioned\n\n__SERVER__\nValidate local patching         Success   Successfully validated server local\n                                          patching\nValidate command execution      Success   Skipped command execution verfication\n                                          - Instance is not provisioned\n\n\n\nodacli update-repository -f \/opt\/dbi\/serverarchive_dbi-oda1.zip\nsleep 10 ; odacli describe-job -i \"4f1b792c-6c12-4e15-8d4f-439526df91b4\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  4f1b792c-6c12-4e15-8d4f-439526df91b4\n            Description:  Repository Update\n                 Status:  Success\n                Created:  January 23, 2024 10:07:22 AM UTC\n                Message:  \/opt\/dbi\/serverarchive_dbi-oda1.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nUnzip bundle                             January 23, 2024 10:07:22 AM UTC         January 23, 2024 10:07:22 AM UTC         Success\n\n\n\necho \"10.36.0.241     dbi-oda1\" >> \/etc\/hosts\necho \"10.36.0.240     dbi-oda01-ilom\" >> \/etc\/hosts\n\nodacli restore-node -g\n\nodacli describe-job -i c8b64bc7-5a54-4e77-b8f7-0bd3368c2ec0\n\nJob details\n----------------------------------------------------------------\n                     ID:  c8b64bc7-5a54-4e77-b8f7-0bd3368c2ec0\n            Description:  Restore node service - GI\n                 Status:  Success\n                Created:  January 23, 2024 9:11:49 AM CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nRestore node service creation            January 23, 2024 9:11:57 AM CET          January 23, 2024 9:39:19 AM CET          Success\nSetting up Network                       January 23, 2024 9:11:59 AM CET          January 23, 2024 9:11:59 AM CET          Success\nSetting up Vlan                          January 23, 2024 9:12:27 AM CET          January 23, 2024 9:12:29 AM CET          Success\nSetting up Network                       January 23, 2024 9:13:03 AM CET          January 23, 2024 9:13:03 AM CET          Success\nNetwork update                           January 23, 2024 9:13:39 AM CET          January 23, 2024 9:14:10 AM CET          Success\nUpdating network                         January 23, 2024 9:13:39 AM CET          January 23, 2024 9:14:10 AM CET          Success\nSetting up Network                       January 23, 2024 9:13:39 AM CET          January 23, 2024 9:13:39 AM CET          Success\nOS usergroup 'asmdba' creation           January 23, 2024 9:14:10 AM CET          January 23, 2024 9:14:10 AM CET          Success\nOS usergroup 'asmoper' creation          January 23, 2024 9:14:10 AM CET          January 23, 2024 9:14:10 AM CET          Success\nOS usergroup 'asmadmin' creation         January 23, 2024 9:14:10 AM CET          January 23, 2024 9:14:10 AM CET          Success\nOS usergroup 'dba' creation              January 23, 2024 9:14:10 AM CET          January 23, 2024 9:14:10 AM CET          Success\nOS usergroup 'dbaoper' creation          January 23, 2024 9:14:10 AM CET          January 23, 2024 9:14:11 AM CET          Success\nOS usergroup 'oinstall' creation         January 23, 2024 9:14:11 AM CET          January 23, 2024 9:14:11 AM CET          Success\nOS user 'grid' creation                  January 23, 2024 9:14:11 AM CET          January 23, 2024 9:14:11 AM CET          Success\nOS user 'oracle' creation                January 23, 2024 9:14:11 AM CET          January 23, 2024 9:14:11 AM CET          Success\nDefault backup policy creation           January 23, 2024 9:14:11 AM CET          January 23, 2024 9:14:12 AM CET          Success\nBackup Config name validation            January 23, 2024 9:14:12 AM CET          January 23, 2024 9:14:12 AM CET          Success\nBackup config metadata persist           January 23, 2024 9:14:12 AM CET          January 23, 2024 9:14:12 AM CET          Success\nGrant permission to RHP files            January 23, 2024 9:14:12 AM CET          January 23, 2024 9:14:12 AM CET          Success\nAdd SYSNAME in Env                       January 23, 2024 9:14:12 AM CET          January 23, 2024 9:14:12 AM CET          Success\nInstall oracle-ahf                       January 23, 2024 9:14:12 AM CET          January 23, 2024 9:17:04 AM CET          Success\nStop DCS Admin                           January 23, 2024 9:17:41 AM CET          January 23, 2024 9:17:41 AM CET          Success\nGenerate mTLS certificates               January 23, 2024 9:17:41 AM CET          January 23, 2024 9:17:43 AM CET          Success\nExporting Public Keys                    January 23, 2024 9:17:43 AM CET          January 23, 2024 9:17:45 AM CET          Success\nCreating Trust Store                     January 23, 2024 9:17:45 AM CET          January 23, 2024 9:17:49 AM CET          Success\nUpdate config files                      January 23, 2024 9:17:49 AM CET          January 23, 2024 9:17:49 AM CET          Success\nRestart DCS Admin                        January 23, 2024 9:17:49 AM CET          January 23, 2024 9:18:09 AM CET          Success\nUnzipping storage configuration files    January 23, 2024 9:18:09 AM CET          January 23, 2024 9:18:09 AM CET          Success\nReloading multipath devices              January 23, 2024 9:18:10 AM CET          January 23, 2024 9:18:10 AM CET          Success\nRestart oakd                             January 23, 2024 9:18:10 AM CET          January 23, 2024 9:18:21 AM CET          Success\nRestore Quorum Disks                     January 23, 2024 9:18:48 AM CET          January 23, 2024 9:18:49 AM CET          Success\nCreating GI home directories             January 23, 2024 9:18:49 AM CET          January 23, 2024 9:18:49 AM CET          Success\nExtract GI clone                         January 23, 2024 9:18:49 AM CET          January 23, 2024 9:19:54 AM CET          Success\nRestart oakd                             January 23, 2024 9:19:31 AM CET          January 23, 2024 9:18:48 AM CET          Success\nCreating wallet for Root User            January 23, 2024 9:19:54 AM CET          January 23, 2024 9:19:59 AM CET          Success\nCreating wallet for ASM Client           January 23, 2024 9:19:59 AM CET          January 23, 2024 9:20:03 AM CET          Success\nGrid stack creation                      January 23, 2024 9:20:03 AM CET          January 23, 2024 9:30:47 AM CET          Success\nGI Restore with RHP                      January 23, 2024 9:20:03 AM CET          January 23, 2024 9:27:32 AM CET          Success\nUpdating GIHome version                  January 23, 2024 9:27:33 AM CET          January 23, 2024 9:27:37 AM CET          Success\nPost cluster OAKD configuration          January 23, 2024 9:30:47 AM CET          January 23, 2024 9:31:43 AM CET          Success\nMounting disk group DATA                 January 23, 2024 9:31:43 AM CET          January 23, 2024 9:31:44 AM CET          Success\nMounting disk group RECO                 January 23, 2024 9:31:53 AM CET          January 23, 2024 9:32:01 AM CET          Success\nSetting ACL for disk groups              January 23, 2024 9:32:08 AM CET          January 23, 2024 9:32:11 AM CET          Success\nRegister Scan and Vips to Public Network January 23, 2024 9:32:11 AM CET          January 23, 2024 9:32:13 AM CET          Success\nAdding Volume RDOLTTST to Clusterware    January 23, 2024 9:32:29 AM CET          January 23, 2024 9:32:33 AM CET          Success\nAdding Volume DATWS12C to Clusterware    January 23, 2024 9:32:33 AM CET          January 23, 2024 9:32:36 AM CET          Success\nAdding Volume ACFSCLONE to Clusterware   January 23, 2024 9:32:36 AM CET          January 23, 2024 9:32:40 AM CET          Success\nAdding Volume DATLTTST to Clusterware    January 23, 2024 9:32:40 AM CET          January 23, 2024 9:32:43 AM CET          Success\nAdding Volume RECO to Clusterware        January 23, 2024 9:32:43 AM CET          January 23, 2024 9:32:46 AM CET          Success\nAdding Volume ORAHOME_SH to Clusterware  January 23, 2024 9:32:46 AM CET          January 23, 2024 9:32:49 AM CET          Success\nAdding Volume VMSTORE to Clusterware     January 23, 2024 9:32:49 AM CET          January 23, 2024 9:32:52 AM CET          Success\nAdding Volume RDOTST23 to Clusterware    January 23, 2024 9:32:52 AM CET          January 23, 2024 9:32:55 AM CET          Success\nAdding Volume COMMONSTORE to Clusterware January 23, 2024 9:32:55 AM CET          January 23, 2024 9:32:58 AM CET          Success\nAdding Volume SACD403318 to Clusterware  January 23, 2024 9:32:58 AM CET          January 23, 2024 9:33:01 AM CET          Success\nAdding Volume RDOWS12C to Clusterware    January 23, 2024 9:33:01 AM CET          January 23, 2024 9:33:04 AM CET          Success\nAdding Volume ODABASE_N0 to Clusterware  January 23, 2024 9:33:04 AM CET          January 23, 2024 9:33:07 AM CET          Success\nAdding Volume DATTST23 to Clusterware    January 23, 2024 9:33:07 AM CET          January 23, 2024 9:33:10 AM CET          Success\nAdding Volume S2B0A08932 to Clusterware  January 23, 2024 9:33:10 AM CET          January 23, 2024 9:33:13 AM CET          Success\nAdding Volume DELPHIXBS to Clusterware   January 23, 2024 9:33:13 AM CET          January 23, 2024 9:33:16 AM CET          Success\nEnabling Volume(s)                       January 23, 2024 9:33:16 AM CET          January 23, 2024 9:36:15 AM CET          Success\nDiscover ACFS clones config              January 23, 2024 9:39:02 AM CET          January 23, 2024 9:39:12 AM CET          Success\nConfigure export clones resource         January 23, 2024 9:39:11 AM CET          January 23, 2024 9:39:11 AM CET          Success\nDiscover DbHomes ACFS config             January 23, 2024 9:39:12 AM CET          January 23, 2024 9:39:15 AM CET          Success\nDiscover OraHomeStorage volumes          January 23, 2024 9:39:12 AM CET          January 23, 2024 9:39:15 AM CET          Success\nProvisioning service creation            January 23, 2024 9:39:17 AM CET          January 23, 2024 9:39:17 AM CET          Success\nPersist new agent state entry            January 23, 2024 9:39:17 AM CET          January 23, 2024 9:39:17 AM CET          Success\nPersist new agent state entry            January 23, 2024 9:39:17 AM CET          January 23, 2024 9:39:17 AM CET          Success\nRestart DCS Agent                        January 23, 2024 9:39:17 AM CET          January 23, 2024 9:39:19 AM CET          Success<\/code><\/pre>\n\n\n\n
    Now my system is restored and a 19.21 GI stack should be running.<\/p>\n\n\n\n
    Let’s check the ACFS configuration for binaries:<\/p>\n\n\n\n
    odacli list-dbhome-storages\n=============================================================================================================\nID                                     Node Description          Disk Group Volume      Size(GB)   Status\n-------------------------------------- ---- -------------------- ---------- ----------- ---------- ----------\nd49200b7-5c0a-422b-bab8-2d4392c1fe83   0    ORACLE_HOME          DATA       orahome_sh  100        CONFIGURED\n651512c5-c7b6-4844-883f-a4a31786eba0   0    ORACLE_BASE          DATA       odabase_n0  10         CONFIGURED\n=============================================================================================================\n<\/code><\/pre>\n\n\n\n
    As all DB homes are on ACFS now, no need to manually register them as you would do when using DPR on an old ODA.<\/p>\n\n\n\n
    Restore the database configuration<\/h2>\n\n\n\n
    The restore-node also has a -d for databases, let’s do it:<\/p>\n\n\n\n
    odacli restore-node -d \n\nodacli describe-job -i \"56e62047-6c95-41e8-a0c1-a52b0f3191af\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  56e62047-6c95-41e8-a0c1-a52b0f3191af\n            Description:  Restore node service - DB\n                 Status:  Success\n                Created:  January 23, 2024 11:47:12 AM CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nSetting up SSH equivalence for 'oracle'  January 23, 2024 11:47:15 AM CET         January 23, 2024 11:47:17 AM CET         Success\nRestore BM CPU Pools                     January 23, 2024 11:47:17 AM CET         January 23, 2024 11:47:17 AM CET         Success\nRegister DB home: OraDB19000_home2       January 23, 2024 11:47:17 AM CET         January 23, 2024 11:47:20 AM CET         Success\nRegister DB home: OraDB19000_home6       January 23, 2024 11:47:20 AM CET         January 23, 2024 11:47:23 AM CET         Success\nRegister DB home: OraDB19000_home4       January 23, 2024 11:47:23 AM CET         January 23, 2024 11:47:26 AM CET         Success\nRegister DB home: OraDB12201_home1       January 23, 2024 11:47:27 AM CET         January 23, 2024 11:47:50 AM CET         Success\nRegister DB home: OraDB19000_home3       January 23, 2024 11:47:50 AM CET         January 23, 2024 11:47:53 AM CET         Success\nPersist database storage locations       January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for DBITST                 January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for WS12C_SITE1            January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for bsn01                  January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for DBWEI                  January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for MYBRCDB                January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for TST23                  January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for LTTST                  January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nPersist database storages                January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for DBITST                 January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for WS12C_SITE1            January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for bsn01                  January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for DBWEI                  January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for MYBRCDB                January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for TST23                  January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nSave metadata for LTTST                  January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:53 AM CET         Success\nRestore database: DBITST                 January 23, 2024 11:47:53 AM CET         January 23, 2024 11:49:14 AM CET         Success\n+-- Adding database to GI                January 23, 2024 11:47:53 AM CET         January 23, 2024 11:47:55 AM CET         Success\n+-- Adding database instance(s) to GI    January 23, 2024 11:47:55 AM CET         January 23, 2024 11:47:55 AM CET         Success\n+-- Modifying SPFILE for database        January 23, 2024 11:47:55 AM CET         January 23, 2024 11:48:31 AM CET         Success\n+-- Restore password file for database   January 23, 2024 11:48:31 AM CET         January 23, 2024 11:48:31 AM CET         Skipped\n+-- Start instance(s) for database       January 23, 2024 11:48:31 AM CET         January 23, 2024 11:48:52 AM CET         Success\n+-- Persist metadata for database        January 23, 2024 11:48:52 AM CET         January 23, 2024 11:48:52 AM CET         Success\n+-- Create adrci directory               January 23, 2024 11:48:52 AM CET         January 23, 2024 11:48:52 AM CET         Success\n+-- Run SqlPatch                         January 23, 2024 11:48:52 AM CET         January 23, 2024 11:49:14 AM CET         Success\nRestore database: WS12C                  January 23, 2024 11:49:14 AM CET         January 23, 2024 11:50:14 AM CET         Success\n+-- Adding database to GI                January 23, 2024 11:49:14 AM CET         January 23, 2024 11:49:16 AM CET         Success\n+-- Adding database instance(s) to GI    January 23, 2024 11:49:16 AM CET         January 23, 2024 11:49:16 AM CET         Success\n+-- Modifying SPFILE for database        January 23, 2024 11:49:16 AM CET         January 23, 2024 11:49:51 AM CET         Success\n+-- Restore password file for database   January 23, 2024 11:49:51 AM CET         January 23, 2024 11:49:51 AM CET         Skipped\n+-- Start instance(s) for database       January 23, 2024 11:49:51 AM CET         January 23, 2024 11:50:06 AM CET         Success\n+-- Persist metadata for database        January 23, 2024 11:50:06 AM CET         January 23, 2024 11:50:06 AM CET         Success\n+-- Create adrci directory               January 23, 2024 11:50:06 AM CET         January 23, 2024 11:50:06 AM CET         Success\n+-- Run SqlPatch                         January 23, 2024 11:50:06 AM CET         January 23, 2024 11:50:14 AM CET         Success\nRestore database: bsn01                  January 23, 2024 11:50:14 AM CET         January 23, 2024 11:51:31 AM CET         Success\n+-- Adding database to GI                January 23, 2024 11:50:14 AM CET         January 23, 2024 11:50:16 AM CET         Success\n+-- Adding database instance(s) to GI    January 23, 2024 11:50:16 AM CET         January 23, 2024 11:50:16 AM CET         Success\n+-- Modifying SPFILE for database        January 23, 2024 11:50:16 AM CET         January 23, 2024 11:50:48 AM CET         Success\n+-- Restore password file for database   January 23, 2024 11:50:48 AM CET         January 23, 2024 11:50:48 AM CET         Skipped\n+-- Start instance(s) for database       January 23, 2024 11:50:48 AM CET         January 23, 2024 11:51:09 AM CET         Success\n+-- Persist metadata for database        January 23, 2024 11:51:09 AM CET         January 23, 2024 11:51:09 AM CET         Success\n+-- Create adrci directory               January 23, 2024 11:51:09 AM CET         January 23, 2024 11:51:09 AM CET         Success\n+-- Run SqlPatch                         January 23, 2024 11:51:09 AM CET         January 23, 2024 11:51:31 AM CET         Success\nRestore database: DBWEI                  January 23, 2024 11:51:32 AM CET         January 23, 2024 11:52:55 AM CET         Success\n+-- Adding database to GI                January 23, 2024 11:51:32 AM CET         January 23, 2024 11:51:33 AM CET         Success\n+-- Adding database instance(s) to GI    January 23, 2024 11:51:33 AM CET         January 23, 2024 11:51:33 AM CET         Success\n+-- Modifying SPFILE for database        January 23, 2024 11:51:33 AM CET         January 23, 2024 11:52:11 AM CET         Success\n+-- Restore password file for database   January 23, 2024 11:52:11 AM CET         January 23, 2024 11:52:11 AM CET         Skipped\n+-- Start instance(s) for database       January 23, 2024 11:52:11 AM CET         January 23, 2024 11:52:32 AM CET         Success\n+-- Persist metadata for database        January 23, 2024 11:52:32 AM CET         January 23, 2024 11:52:32 AM CET         Success\n+-- Create adrci directory               January 23, 2024 11:52:32 AM CET         January 23, 2024 11:52:32 AM CET         Success\n+-- Run SqlPatch                         January 23, 2024 11:52:32 AM CET         January 23, 2024 11:52:55 AM CET         Success\nRestore database: MYBRCDB                January 23, 2024 11:52:55 AM CET         January 23, 2024 11:54:02 AM CET         Success\n+-- Adding database to GI                January 23, 2024 11:52:55 AM CET         January 23, 2024 11:52:57 AM CET         Success\n+-- Adding database instance(s) to GI    January 23, 2024 11:52:57 AM CET         January 23, 2024 11:52:57 AM CET         Success\n+-- Modifying SPFILE for database        January 23, 2024 11:52:57 AM CET         January 23, 2024 11:53:34 AM CET         Success\n+-- Restore password file for database   January 23, 2024 11:53:34 AM CET         January 23, 2024 11:53:34 AM CET         Skipped\n+-- Start instance(s) for database       January 23, 2024 11:53:34 AM CET         January 23, 2024 11:53:54 AM CET         Success\n+-- Persist metadata for database        January 23, 2024 11:53:54 AM CET         January 23, 2024 11:53:54 AM CET         Success\n+-- Create adrci directory               January 23, 2024 11:53:54 AM CET         January 23, 2024 11:53:54 AM CET         Success\n+-- Run SqlPatch                         January 23, 2024 11:53:54 AM CET         January 23, 2024 11:54:02 AM CET         Success\nRestore database: LTTST                  January 23, 2024 11:54:02 AM CET         January 23, 2024 11:54:53 AM CET         Success\n+-- Adding database to GI                January 23, 2024 11:54:03 AM CET         January 23, 2024 11:54:04 AM CET         Success\n+-- Adding database instance(s) to GI    January 23, 2024 11:54:04 AM CET         January 23, 2024 11:54:05 AM CET         Success\n+-- Modifying SPFILE for database        January 23, 2024 11:54:05 AM CET         January 23, 2024 11:54:30 AM CET         Success\n+-- Restore password file for database   January 23, 2024 11:54:30 AM CET         January 23, 2024 11:54:30 AM CET         Skipped\n+-- Start instance(s) for database       January 23, 2024 11:54:30 AM CET         January 23, 2024 11:54:45 AM CET         Success\n+-- Persist metadata for database        January 23, 2024 11:54:45 AM CET         January 23, 2024 11:54:45 AM CET         Success\n+-- Create adrci directory               January 23, 2024 11:54:45 AM CET         January 23, 2024 11:54:45 AM CET         Success\n+-- Run SqlPatch                         January 23, 2024 11:54:45 AM CET         January 23, 2024 11:54:53 AM CET         Success\nRestore Object Stores                    January 23, 2024 11:54:53 AM CET         January 23, 2024 11:54:53 AM CET         Success\nRemount NFS backups                      January 23, 2024 11:54:53 AM CET         January 23, 2024 11:54:53 AM CET         Success\nRestore BackupConfigs                    January 23, 2024 11:54:53 AM CET         January 23, 2024 11:54:53 AM CET         Success\nReattach backupconfigs to DBs            January 23, 2024 11:54:53 AM CET         January 23, 2024 11:54:53 AM CET         Success\nRestore backup reports                   January 23, 2024 11:54:53 AM CET         January 23, 2024 11:54:53 AM CET         Success\n\nodacli list-databases\nID                                       DB Name    DB Type  DB Version           CDB     Class    Edition  Shape    Storage  Status       DB Home ID                  \n---------------------------------------- ---------- -------- -------------------- ------- -------- -------- -------- -------- ------------ ----------------------------------------\n7390837e-3d0f-4457-9e18-8a06fc5be359     DBITST     SI       19.20.0.0.230718     true    OLTP     SE       odb1     ASM      CONFIGURED   f8998897-34f2-435c-9898-710eb960e361\n3d689dde-b7d7-4d75-b04e-d1ed77fbebfd     WS12C      SI       19.20.0.0.230718     false   OLTP     EE       odb1     ACFS     CONFIGURED   80aaed91-d1ff-42c5-be16-590120c7a7f2\n3d187e6a-0381-454b-8034-7545821106ff     bsn01      SI       19.19.0.0.230418     true    OLTP     SE       odb2     ASM      CONFIGURED   d8aa26c6-be94-4a79-a653-48095961d9a2\n6b2d8aaa-825f-40c0-96c4-0bbc81d84e28     DBWEI      SI       19.20.0.0.230718     true    OLTP     EE       odb1     ASM      CONFIGURED   80aaed91-d1ff-42c5-be16-590120c7a7f2\n95426fd1-5434-4c99-9704-194735d84b33     MYBRCDB    SI       19.20.0.0.230718     false   OLTP     EE       odb1     ASM      CONFIGURED   80aaed91-d1ff-42c5-be16-590120c7a7f2\nf836307f-5dae-4a0b-bb86-0752e1b1948c     LTTST      SI       19.20.0.0.230718     false   OLTP     SE       odb1     ACFS     CONFIGURED   f8998897-34f2-435c-9898-710eb960e361<\/code><\/pre>\n\n\n\n
    Databases are now restored and available. <\/p>\n\n\n\n
    Note that it only works for bare metal databases. For now, there is no VMs and no DB Systems:<\/p>\n\n\n\n
    odacli list-vms\nNo data found for VM\n\nodacli list-dbsystems\nNo data found for DB System<\/code><\/pre>\n\n\n\n
    Restore the VMs and DB Systems<\/h2>\n\n\n\n
    There are some specifics commands for VMs and DB Systems restore:<\/p>\n\n\n\n
    odacli restore-node -kvm\nodacli describe-job -i \"6704768e-d931-4e87-931d-37562bd61f04\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  6704768e-d931-4e87-931d-37562bd61f04\n            Description:  Restore node service - KVM\n                 Status:  Success\n                Created:  January 23, 2024 11:57:08 AM CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nValidate backup files                    January 23, 2024 11:57:08 AM CET         January 23, 2024 11:57:08 AM CET         Success\nRead backup metadata                     January 23, 2024 11:57:08 AM CET         January 23, 2024 11:57:08 AM CET         Success\nCheck existing resources                 January 23, 2024 11:57:08 AM CET         January 23, 2024 11:57:08 AM CET         Success\nCreate ACFS mount point                  January 23, 2024 11:57:08 AM CET         January 23, 2024 11:57:08 AM CET         Success\nRegister ACFS resources                  January 23, 2024 11:57:08 AM CET         January 23, 2024 11:57:10 AM CET         Success\nRestore VM Storages metadata             January 23, 2024 11:57:10 AM CET         January 23, 2024 11:57:10 AM CET         Success\nRestore VDisks metadata                  January 23, 2024 11:57:10 AM CET         January 23, 2024 11:57:10 AM CET         Success\nRestore CPU Pools                        January 23, 2024 11:57:10 AM CET         January 23, 2024 11:57:10 AM CET         Success\nRestore VNetworks                        January 23, 2024 11:57:10 AM CET         January 23, 2024 11:57:16 AM CET         Success\nPatch VM's domain config files           January 23, 2024 11:57:16 AM CET         January 23, 2024 11:57:24 AM CET         Success\nRestore VMs                              January 23, 2024 11:57:24 AM CET         January 23, 2024 11:57:26 AM CET         Success\nRestore VMs metadata                     January 23, 2024 11:57:26 AM CET         January 23, 2024 11:57:26 AM CET         Success\nStart VMs                                January 23, 2024 11:57:26 AM CET         January 23, 2024 11:57:30 AM CET         Success\n\n\nodacli restore-node -dbs\n\nodacli describe-job -i \"b720c6dc-7f46-4373-9359-40f8bafe777f\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  b720c6dc-7f46-4373-9359-40f8bafe777f\n            Description:  Restore node service - DBSYSTEM\n                 Status:  Success\n                Created:  January 23, 2024 11:58:30 AM CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nValidate DB System json files            January 23, 2024 11:58:31 AM CET         January 23, 2024 11:58:31 AM CET         Success\nProcess DB Systems for restore operation January 23, 2024 11:58:31 AM CET         January 23, 2024 11:58:31 AM CET         Success\nCreate DB System ACFS mount points       January 23, 2024 11:58:31 AM CET         January 23, 2024 11:58:31 AM CET         Success\nPatch libvirt xml for DB Systems         January 23, 2024 11:58:31 AM CET         January 23, 2024 11:58:35 AM CET         Success\nRestore DB System Networks               January 23, 2024 11:58:35 AM CET         January 23, 2024 11:58:35 AM CET         Success\nAdd DB Systems to Clusterware            January 23, 2024 11:58:35 AM CET         January 23, 2024 11:58:36 AM CET         Success\nValidate start dependencies              January 23, 2024 11:58:36 AM CET         January 23, 2024 11:58:36 AM CET         Success\nStart DB Systems                         January 23, 2024 11:58:36 AM CET         January 23, 2024 11:58:42 AM CET         Success\nWait for DB Systems bootstrap            January 23, 2024 11:58:42 AM CET         January 23, 2024 11:59:51 AM CET         Success\nExport clones repository for DB          January 23, 2024 11:59:51 AM CET         January 23, 2024 11:59:51 AM CET         Success\nSystems post restore\nExport ASM client cluster config on BM   January 23, 2024 11:59:51 AM CET         January 23, 2024 11:59:56 AM CET         Success\nImport ASM client cluster config to      January 23, 2024 11:59:56 AM CET         January 23, 2024 12:01:46 PM CET         Success\nOLR (within DB Systems)\nImport ASM client cluster config to      January 23, 2024 12:01:46 PM CET         January 23, 2024 12:04:36 PM CET         Success\nOCR (within DB Systems)\nUpdate DB System status to after         January 23, 2024 12:04:36 PM CET         January 23, 2024 12:04:37 PM CET         Success\nrestore operation\n\n\nodacli list-vms\nName                  VM Storage            Current State    Target State     Created                   Updated\n--------------------  --------------------  ---------------  ---------------  ------------------------  ------------------------\nubuntu02              VMstore               ONLINE           ONLINE           2023-12-07 15:06:57 CET   2024-01-23 11:57:26 CET\nVMMAW01               VMstore               ONLINE           ONLINE           2023-12-07 14:51:32 CET   2024-01-23 11:57:26 CET\ndelphix               VMstore               ONLINE           ONLINE           2024-01-03 15:49:57 CET   2024-01-23 11:57:26 CET\nubuntu01              VMstore               ONLINE           ONLINE           2023-12-07 15:05:54 CET   2024-01-23 11:57:26 CET\n\nodacli list-dbsystems\nName                  Shape       Cores  Memory      GI version          DB version          Status           Created                   Updated\n--------------------  ----------  -----  ----------  ------------------  ------------------  ---------------  ------------------------  ------------------------\ntestdbs02             odb2        2      16.00 GB    19.20.0.0.230718    N\/A                 CONFIGURED       2024-01-04 13:47:20 CET   2024-01-23 12:04:36 CET\ntestdbs01             odb2        2      16.00 GB    19.20.0.0.230718    19.20.0.0.230718    CONFIGURED       2024-01-04 12:07:05 CET   2024-01-23 12:04:37 CET<\/code><\/pre>\n\n\n\n
    My VMs are back to life. Fine!<\/p>\n\n\n\n
    Patching the DB homes<\/h2>\n\n\n\n
    Once your ODA is fully restored on top of the new OS version, next step is to update the DB homes\/databases. Nothing new here compared to the previous versions. You need to download, unzip and register the new DB clone first:<\/p>\n\n\n\n
    unzip p30403662_1921000_Linux-x86-64.zip\n\nodacli update-repository -f \/opt\/dbi\/odacli-dcs-19.21.0.0.0-231211-DB-19.21.0.0.zip\n\nsleep 30; odacli describe-job -i \"169a08ae-897a-49e4-b9f9-3db22c9d8940\"\r\n\r\nJob details\n----------------------------------------------------------------\n                     ID:  169a08ae-897a-49e4-b9f9-3db22c9d8940\n            Description:  Repository Update\n                 Status:  Success\n                Created:  January 24, 2024 9:30:01 AM CET\n                Message:  \/opt\/dbi\/odacli-dcs-19.21.0.0.0-231211-DB-19.21.0.0.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nUnzip bundle                             January 24, 2024 9:30:01 AM CET          January 24, 2024 9:30:39 AM CET          Success<\/code><\/pre>\n\n\n\n
    You will need to choose between patching at the DB home level or database level:<\/p>\n\n\n\n
    odacli list-dbhomes\nID                                       Name                 DB Version                     DB Edition Home Location                                           Status\n---------------------------------------- -------------------- ------------------------------ ---------- ------------------------------------------------------- ----------\n80aaed91-d1ff-42c5-be16-590120c7a7f2     OraDB19000_home4     19.20.0.0.230718               EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_4    CONFIGURED\na684a7cc-1ebd-425c-90df-31fad25c3295     OraDB12201_home1     12.2.0.1.220118                SE         \/u01\/app\/odaorahome\/oracle\/product\/12.2.0.1\/dbhome_1    CONFIGURED\naa3cab94-8a6d-4230-9aa9-8c517ce24836     OraDB19000_home6     19.20.0.0.230718               EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_6    CONFIGURED\nd8aa26c6-be94-4a79-a653-48095961d9a2     OraDB19000_home2     19.19.0.0.230418               SE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_2    CONFIGURED\nf8998897-34f2-435c-9898-710eb960e361     OraDB19000_home3     19.20.0.0.230718               SE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_3    CONFIGURED\n\nodacli list-databases\nID                                       DB Name    DB Type  DB Version           CDB     Class    Edition  Shape    Storage  Status       DB Home ID            \n---------------------------------------- ---------- -------- -------------------- ------- -------- -------- -------- -------- ------------ ----------------------------------------\n7390837e-3d0f-4457-9e18-8a06fc5be359     DBITST     SI       19.20.0.0.230718     true    OLTP     SE       odb1     ASM      CONFIGURED   f8998897-34f2-435c-9898-710eb960e361\n3d689dde-b7d7-4d75-b04e-d1ed77fbebfd     WS12C      SI       19.20.0.0.230718     false   OLTP     EE       odb1     ACFS     CONFIGURED   80aaed91-d1ff-42c5-be16-590120c7a7f2\n3d187e6a-0381-454b-8034-7545821106ff     bsn01      SI       19.19.0.0.230418     true    OLTP     SE       odb2     ASM      CONFIGURED   d8aa26c6-be94-4a79-a653-48095961d9a2\n6b2d8aaa-825f-40c0-96c4-0bbc81d84e28     DBWEI      SI       19.20.0.0.230718     true    OLTP     EE       odb1     ASM      CONFIGURED   80aaed91-d1ff-42c5-be16-590120c7a7f2\n95426fd1-5434-4c99-9704-194735d84b33     MYBRCDB    SI       19.20.0.0.230718     false   OLTP     EE       odb1     ASM      CONFIGURED   80aaed91-d1ff-42c5-be16-590120c7a7f2\nf836307f-5dae-4a0b-bb86-0752e1b1948c     LTTST      SI       19.20.0.0.230718     false   OLTP     SE       odb1     ACFS     CONFIGURED   f8998897-34f2-435c-9898-710eb960e361<\/code><\/pre>\n\n\n\n
    I usually work at the DB home level. Let’s patch the first DB home here:<\/p>\n\n\n\n
    odacli create-prepatchreport -d -i f8998897-34f2-435c-9898-710eb960e361 -v 19.21.0.0.0\n\nsleep 600; odacli describe-prepatchreport -i 74b70078-c1cd-41b0-8980-f61b40b75504\n\nPatch pre-check report\n------------------------------------------------------------------------\n                 Job ID:  74b70078-c1cd-41b0-8980-f61b40b75504\n            Description:  Patch pre-checks for [DB, ORACHKDB]: DbHome is OraDB19000_home3\n                 Status:  FAILED\n                Created:  January 24, 2024 9:31:54 AM CET\n                 Result:  One or more pre-checks failed for [ORACHK]\n\nNode Name\n---------------\ndbi-oda1\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__DB__\nValidate DB Home ID             Success   Validated DB Home ID:\n                                          f8998897-34f2-435c-9898-710eb960e361\nValidate patching tag           Success   Validated patching tag: 19.21.0.0.0.\nIs system provisioned           Success   Verified system is provisioned\nValidate minimum agent version  Success   Validated minimum agent version\nIs GI upgraded                  Success   Validated GI is upgraded\nValidate available space for    Success   Validated free space required under\ndb                                        \/u01\nValidate dbHomesOnACFS          Success   User has configured disk group for\nconfigured                                Database homes on ACFS\nValidate Oracle base            Success   Successfully validated Oracle Base\nIs DB clone available           Success   Successfully validated clone file\n                                          exists\nEvaluate DBHome patching with   Success   Successfully validated updating\nRHP                                       dbhome with RHP.  and local patching\n                                          is possible\nValidate command execution      Success   Validated command execution\n\n__ORACHK__\nRunning orachk                  Failed    ORAchk validation failed: .\nValidate command execution      Success   Validated command execution\nVerify the Fast Recovery Area   Failed    AHF-2929: FRA space management\n(FRA) has reclaimable space               problem file types are present\n                                          without an RMAN backup completion\n                                          within the last 7 days\nVerify the Fast Recovery Area   Failed    AHF-2929: FRA space management\n(FRA) has reclaimable space               problem file types are present\n                                          without an RMAN backup completion\n                                          within the last 7 days<\/code><\/pre>\n\n\n\n
    Sometimes ORACHK will show failurea for different things, but your database may accept some different settings or status ORACHK doesn’t like. So, at some point, you may need to force the DB home update with -f.<\/p>\n\n\n\n
    odacli update-dbhome -i f8998897-34f2-435c-9898-710eb960e361 -v 19.21.0.0.0\nDCS-10227:cannot proceed; prepatchreport has errors for version: 19.21.0.0.0, components: orachk, on node: dbi-oda1\n\nodacli update-dbhome -i f8998897-34f2-435c-9898-710eb960e361 -v 19.21.0.0.0 -f\r\nsleep 600;  odacli describe-job -i \"34e41b4e-b845-4f44-b73b-429fec2d84f5\"\r\n\nodacli describe-job -i \"34e41b4e-b845-4f44-b73b-429fec2d84f5\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  34e41b4e-b845-4f44-b73b-429fec2d84f5\n            Description:  DB Home Patching: Home ID is f8998897-34f2-435c-9898-710eb960e361\n                 Status:  Success\n                Created:  January 24, 2024 10:05:55 AM CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nCreating wallet for DB Client            January 24, 2024 10:06:48 AM CET         January 24, 2024 10:06:48 AM CET         Success\nPatch databases by RHP - [DBITST]        January 24, 2024 10:06:48 AM CET         January 24, 2024 10:12:10 AM CET         Success\nUpdating database metadata               January 24, 2024 10:12:10 AM CET         January 24, 2024 10:12:10 AM CET         Success\nSet log_archive_dest for Database        January 24, 2024 10:12:10 AM CET         January 24, 2024 10:12:13 AM CET         Success\nSet target_pdbs parameter                January 24, 2024 10:12:13 AM CET         January 24, 2024 10:13:12 AM CET         Success\nPatch databases by RHP - [LTTST]         January 24, 2024 10:13:12 AM CET         January 24, 2024 10:17:09 AM CET         Success\nUpdating database metadata               January 24, 2024 10:17:09 AM CET         January 24, 2024 10:17:09 AM CET         Success\nSet log_archive_dest for Database        January 24, 2024 10:17:09 AM CET         January 24, 2024 10:17:11 AM CET         Success\nUpdate System version                    January 24, 2024 10:17:11 AM CET         January 24, 2024 10:17:11 AM CET         Success\nGenerating and saving BOM                January 24, 2024 10:17:11 AM CET         January 24, 2024 10:18:52 AM CET         Success\nTDE parameter update                     January 24, 2024 10:20:07 AM CET         January 24, 2024 10:20:07 AM CET         Success\n<\/code><\/pre>\n\n\n\n
    Let’s check if a new DB home has been provisioned and if my 2 databases are using this new home:<\/p>\n\n\n\n
    odacli list-dbhomes\nID                                       Name                 DB Version                     DB Edition Home Location                                           Status\n---------------------------------------- -------------------- ------------------------------ ---------- ------------------------------------------------------- ----------\n80aaed91-d1ff-42c5-be16-590120c7a7f2     OraDB19000_home4     19.20.0.0.230718               EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_4    CONFIGURED\na684a7cc-1ebd-425c-90df-31fad25c3295     OraDB12201_home1     12.2.0.1.220118                SE         \/u01\/app\/odaorahome\/oracle\/product\/12.2.0.1\/dbhome_1    CONFIGURED\naa3cab94-8a6d-4230-9aa9-8c517ce24836     OraDB19000_home6     19.20.0.0.230718               EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_6    CONFIGURED\nd8aa26c6-be94-4a79-a653-48095961d9a2     OraDB19000_home2     19.19.0.0.230418               SE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_2    CONFIGURED\nf8998897-34f2-435c-9898-710eb960e361     OraDB19000_home3     19.20.0.0.230718               SE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_3    CONFIGURED\na248cb7f-8bb7-459d-95e3-09081a71991d     OraDB19000_home7     19.21.0.0.231017               SE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0.0\/dbhome_7    CONFIGURED\n\n\nodacli list-databases | grep 19.21\n7390837e-3d0f-4457-9e18-8a06fc5be359     DBITST     SI       19.21.0.0.231017     true    OLTP     SE       odb1     ASM      CONFIGURED   a248cb7f-8bb7-459d-95e3-09081a71991d\nf836307f-5dae-4a0b-bb86-0752e1b1948c     LTTST      SI       19.21.0.0.231017     false   OLTP     SE       odb1     ACFS     CONFIGURED   a248cb7f-8bb7-459d-95e3-09081a71991d<\/code><\/pre>\n\n\n\n
    Everything is fine!<\/p>\n\n\n\n
    Don’t forget that the previous DB home will not be deleted unless you do it manually, maybe later.<\/p>\n\n\n\n
    Cleanse the old patches<\/h2>\n\n\n\n
    There is no need to cleanse the old patches as the system was reimaged.<\/p>\n\n\n\n
    Post-patching tasks<\/h2>\n\n\n\n
    You will need to put back your specific configuration as your ODA was reimaged. Depending on your configuration, it may be few simple tasks or a more complex setup.<\/p>\n\n\n\n
    The tasks could be:<\/p>\n\n\n\n
      \n
    • add your additional tools if needed<\/li>\n\n\n\n
    • create additional users and groups<\/li>\n\n\n\n
    • put back folder and files<\/li>\n\n\n\n
    • put back your profile scripts for grid and oracle users<\/li>\n\n\n\n
    • configure monitoring again\u2026<\/li>\n<\/ul>\n\n\n\n
      Patching DB Systems<\/h2>\n\n\n\n
      If you use DB Systems on your ODA, meaning that some of your databases are running in dedicated VMs, you will need to apply the patch inside each DB System. It will use the same “reimaging” principle: you won’t need an ISO but the system disk of your VMs will be replaced by the brand new VM image running on Linux 8.8. Your system settings will be lost, for example your additional users, packages, folders. Make sure to backup everything before patching each DB System.<\/p>\n\n\n\n
      First, download, unzip and register the new 19.21 DB System template on your ODA:<\/p>\n\n\n\n
      unzip p32451228_1921000_Linux-x86-64.zip\nodacli update-repository -f \/opt\/dbi\/odacli-dcs-19.21.0.0.0-ODAVM.zip\n\nodacli describe-job -i \"011509ff-6022-4420-8e10-706b3cf804d1\"\n\nJob details\n----------------------------------------------------------------\n                     ID:  011509ff-6022-4420-8e10-706b3cf804d1\n            Description:  Repository Update\n                 Status:  Success\n                Created:  January 23, 2024 6:03:57 PM CET\n                Message:  \/opt\/dbi\/odacli-dcs-19.21.0.0.0-ODAVM.zip\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nUnzip bundle                             January 23, 2024 6:03:57 PM CET          January 23, 2024 6:06:09 PM CET          Success<\/code><\/pre>\n\n\n\n
      List the DB Systems running on your appliance:<\/p>\n\n\n\n
      odacli list-dbsystems\nName                  Shape       Cores  Memory      GI version          DB version          Status           Created                   Updated\n--------------------  ----------  -----  ----------  ------------------  ------------------  ---------------  ------------------------  ------------------------\ntestdbs02             odb2        2      16.00 GB    19.20.0.0.230718    N\/A                 CONFIGURED       2024-01-04 13:47:20 CET   2024-01-23 12:04:36 CET\ntestdbs01             odb2        2      16.00 GB    19.20.0.0.230718    19.20.0.0.230718    CONFIGURED       2024-01-04 12:07:05 CET   2024-01-23 12:04:37 CET\n<\/code><\/pre>\n\n\n\n
      I will patch testdbs01 in this example. You don’t need to connect to the DB Systems: operations are done on the ODA itself. There is a prepatch report to create before appyling the patch:<\/p>\n\n\n\n
      odacli create-preupgradereport -dbs testdbs01\n\nodacli describe-preupgradereport -i 33fc4317-272c-4cd9-9a73-f7204253cb06\n\nUpgrade pre-check report\n------------------------------------------------------------------------\n                 Job ID:  33fc4317-272c-4cd9-9a73-f7204253cb06\n            Description:  Run pre-upgrade checks for DB System: testdbs01\n                 Status:  SUCCESS\n                Created:  January 23, 2024 6:06:27 PM CET\n                 Result:  All pre-checks succeeded\n\nNode Name\n---------------\ndbi-oda1\n\nCheck                          Status   Message                                Action\n------------------------------ -------- -------------------------------------- --------------------------------------\n__DBSYSTEM__\nValidate DB System State       Success  DB System 'testdbs01' is in            None\n                                        'CONFIGURED' state\nVerify existence of DBVM image Success  DB System image version '19.21.0.0.0'  None\n                                        is present in repository\nVerify existence of Database   Success  Database clone version                 None\nclone                                   '19.20.0.0.230718' is present in\n                                        repository\nVerify existence of GI clone   Success  GI clone version '19.21.0.0.231017'    None\n                                        is  present in repository\n\n\nNode Name\n---------------\ntestdbs01\n\nCheck                          Status   Message                                Action\n------------------------------ -------- -------------------------------------- --------------------------------------\n__OS__\nCheck Required OS files        Success  All the required files are present     None\nCheck Additional OS RPMs       Success  No RPMs outside of base ISO were       None\n                                        found on the system\n\n__SYS__\nValidate Hardware Type         Success  Current hardware is supported          None\nValidate System Version        Success  System version 19.20.0.0.0 is          None\n                                        supported\nVerify System Timezone         Success  Succesfully verified the time zone     None\n                                        file\nVerify Grid User               Success  Grid user is verified                  None\nVerify Grid Version            Success  Oracle Grid Infrastructure is running  None\n                                        on the '19.20.0.0.230718' version on\n                                        all nodes\nCheck Audit Files              Alert    Audit files found under                These files will be lost after\n                                        \/u01\/app\/oracle\/audit                  reimage. Backup the audit files to a\n                                                                               location outside the ODA system\nVerify number of Databases     Success  Only one database is active            None\nVerify number of Database      Success  Only one database home is configured   None\nHomes\n\n__DB__\nValidate Database Status       Success  Database 'DBTST1' is running and is    None\n                                        in 'CONFIGURED' state\nValidate Database Version      Success  Version '19.20.0.0.230718' for         None\n                                        database 'DBTST1' is supported\nValidate Database Datapatch    Success  Database 'DBTST1' is completely        None\nApplication Status                      applied with datapatch\nValidate TDE wallet presence   Success  Database 'DBTST1' is not TDE enabled.  None\n                                        Skipping TDE wallet presence check.\nValidate Database Home         Success  Database home location check passed    None\nlocation                                for database DBTST1\n\n__CERTIFICATES__\nCheck using custom             Success  Using Default key pair                 None\ncertificates\nCheck the agent of the DB      Success  All the agents of the DB systems are   None\nSystem accessible                       accessible\n<\/code><\/pre>\n\n\n\n
      Obviously, audit files will be lost as they reside on the OS filesystems. On my DB System, I also have additional system users, folders and scripts. They will be lost without any warning.<\/p>\n\n\n\n
      As the prepatch is OK, let’s patch this DB System:<\/p>\n\n\n\n
      odacli upgrade-dbsystem -n testdbs01\nEnter password for system testdbs01:\nRetype password for system testdbs01:\n\n\nsleep 1800 ; odacli describe-job -i 7abe8461-2247-4243-ab9c-9278ffb45594\n\nJob details\n----------------------------------------------------------------\n                     ID:  7abe8461-2247-4243-ab9c-9278ffb45594\n            Description:  DB System testdbs01 upgrade\n                 Status:  Success\n                Created:  January 23, 2024 6:18:58 PM CET\n                Message:\n\nTask Name                                Start Time                               End Time                                 Status\n---------------------------------------- ---------------------------------------- ---------------------------------------- ----------\nRun DB System upgrade prechecks          January 23, 2024 6:18:58 PM CET          January 23, 2024 6:19:33 PM CET          Success\nSave provisioning payload                January 23, 2024 6:19:33 PM CET          January 23, 2024 6:19:33 PM CET          Success\nSet DB System as detaching               January 23, 2024 6:19:33 PM CET          January 23, 2024 6:19:33 PM CET          Success\nDetach node - DPR                        January 23, 2024 6:19:33 PM CET          January 23, 2024 6:23:15 PM CET          Success\nCopy server archive file from DB System  January 23, 2024 6:23:15 PM CET          January 23, 2024 6:23:16 PM CET          Success\nSet DB System as recreating              January 23, 2024 6:23:16 PM CET          January 23, 2024 6:23:16 PM CET          Success\nRemove DB System from Clusterware        January 23, 2024 6:23:16 PM CET          January 23, 2024 6:23:22 PM CET          Success\nDelete ASM client cluster config         January 23, 2024 6:23:22 PM CET          January 23, 2024 6:23:28 PM CET          Success\nDeprovision DB System VM(s)              January 23, 2024 6:23:28 PM CET          January 23, 2024 6:23:29 PM CET          Success\nDelete DB System ACFS filesystem         January 23, 2024 6:23:29 PM CET          January 23, 2024 6:23:32 PM CET          Success\nDelete DB System ACFS mount point        January 23, 2024 6:23:32 PM CET          January 23, 2024 6:23:32 PM CET          Success\nDelete DB System ASM volume              January 23, 2024 6:23:32 PM CET          January 23, 2024 6:23:37 PM CET          Success\nDelete imported certificates             January 23, 2024 6:23:37 PM CET          January 23, 2024 6:23:38 PM CET          Success\nDelete DB System metadata                January 23, 2024 6:23:38 PM CET          January 23, 2024 6:23:38 PM CET          Success\nLoad provisioning payload                January 23, 2024 6:23:38 PM CET          January 23, 2024 6:23:38 PM CET          Success\nValidate DB System prerequisites         January 23, 2024 6:23:38 PM CET          January 23, 2024 6:23:42 PM CET          Success\nCreate DB System metadata                January 23, 2024 6:23:42 PM CET          January 23, 2024 6:23:44 PM CET          Success\nCreate DB System ASM volume              January 23, 2024 6:23:44 PM CET          January 23, 2024 6:23:52 PM CET          Success\nCreate DB System ACFS mount point        January 23, 2024 6:23:52 PM CET          January 23, 2024 6:23:52 PM CET          Success\nCreate DB System ACFS filesystem         January 23, 2024 6:23:52 PM CET          January 23, 2024 6:24:00 PM CET          Success\nCreate DB System VM ACFS snapshots       January 23, 2024 6:24:00 PM CET          January 23, 2024 6:24:36 PM CET          Success\nCreate temporary SSH key pair            January 23, 2024 6:24:36 PM CET          January 23, 2024 6:24:37 PM CET          Success\nCreate DB System cloud-init config       January 23, 2024 6:24:37 PM CET          January 23, 2024 6:24:38 PM CET          Success\nProvision DB System VM(s)                January 23, 2024 6:24:38 PM CET          January 23, 2024 6:24:42 PM CET          Success\nAttach disks to DB System                January 23, 2024 6:24:42 PM CET          January 23, 2024 6:24:42 PM CET          Success\nAdd DB System to Clusterware             January 23, 2024 6:24:42 PM CET          January 23, 2024 6:24:43 PM CET          Success\nStart DB System                          January 23, 2024 6:24:43 PM CET          January 23, 2024 6:24:47 PM CET          Success\nWait DB System VM first boot             January 23, 2024 6:24:47 PM CET          January 23, 2024 6:25:48 PM CET          Success\nSetup Mutual TLS (mTLS)                  January 23, 2024 6:25:48 PM CET          January 23, 2024 6:26:07 PM CET          Success\nExport clones repository                 January 23, 2024 6:26:07 PM CET          January 23, 2024 6:26:07 PM CET          Success\nSetup ASM client cluster config          January 23, 2024 6:26:07 PM CET          January 23, 2024 6:26:09 PM CET          Success\nCopy ASM client cluster config           January 23, 2024 6:26:09 PM CET          January 23, 2024 6:26:10 PM CET          Success\nInstall DB System                        January 23, 2024 6:26:10 PM CET          January 23, 2024 6:43:04 PM CET          Success\nCopy server archive file to DB System    January 23, 2024 6:43:04 PM CET          January 23, 2024 6:43:05 PM CET          Success\nUnpack server archive zip file           January 23, 2024 6:43:05 PM CET          January 23, 2024 6:43:11 PM CET          Success\nCleanup temporary SSH key pair           January 23, 2024 6:43:11 PM CET          January 23, 2024 6:43:11 PM CET          Success\nSet DB System as reconfiguring           January 23, 2024 6:43:11 PM CET          January 23, 2024 6:43:11 PM CET          Success\nChange Database file ownership           January 23, 2024 6:43:11 PM CET          January 23, 2024 6:43:16 PM CET          Success\nRestore node - DPR                       January 23, 2024 6:43:16 PM CET          January 23, 2024 6:48:21 PM CET          Success\nSet upgraded DB System as configured     January 23, 2024 6:48:21 PM CET          January 23, 2024 6:48:21 PM CET          Success<\/code><\/pre>\n\n\n\n
      It took about 30 minutes to patch one DB System.<\/p>\n\n\n\n
      Let’s check OS version and database version on it:<\/p>\n\n\n\n
      ssh root@10.36.0.246\ncat \/etc\/oracle-release\nOracle Linux Server release 8.8\n\nodacli list-databases\nID                                       DB Name    DB Type  DB Version           CDB     Class    Edition  Shape    Storage  Status       DB Home ID            \n---------------------------------------- ---------- -------- -------------------- ------- -------- -------- -------- -------- ------------ ----------------------------------------\n1d42028d-3f5f-4f0f-af9f-966e8a627363     DBTST1     SI       19.20.0.0.230718     false   OLTP     EE       odb2     ASM      CONFIGURED   e21938ca-474a-4892-a806-26261e34ff36\n\nexit\n<\/code><\/pre>\n\n\n\n
      My OS is Linux 8.8, and my database is still using 19.20, as expected. It’s now possible to update the database to 19.21 like you did for bare metal databases, if you need to.<\/p>\n\n\n\n
      Conclusion<\/h2>\n\n\n\n
      This patch release is the first one using Data Preserving Reprovisioning for X7\/X8\/X9. It means that you’ll get a cleaner system after applying this patch, but it also means that there are more risks during patching as you will replace the system with a fresh Linux setup. At some point, the restore-node may hang, and there is no possibility to revert back to the old system. Make sure to protect your databases with Data Guard or Dbvisit Standby.<\/p>\n","protected":false},"excerpt":{"rendered":"
      Introduction Patch 19.21 is now available for Oracle Database Appliance series. Let’s find out what’s new and how to apply this patch. What’s new? The most important new component is Linux 8. X10 series were already running on Linux 8 with a dedicated patch (19.20.0.1), but older ODAs were stuck with Linux 7 since years. […]<\/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-30434","post","type-post","status-publish","format-standard","hentry","category-oracle"],"acf":[],"yoast_head":"\nHow to patch your ODA to 19.21? - 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\/how-to-patch-your-oda-to-19-21\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to patch your ODA to 19.21?\" \/>\n<meta property=\"og:description\" content=\"Introduction Patch 19.21 is now available for Oracle Database Appliance series. Let’s find out what’s new and how to apply this patch. What’s new? The most important new component is Linux 8. X10 series were already running on Linux 8 with a dedicated patch (19.20.0.1), but older ODAs were stuck with Linux 7 since years. […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2024-01-24T15:51:25+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-02-13T08:43:02+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=\"9 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\/how-to-patch-your-oda-to-19-21\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/\"},\"author\":{\"name\":\"J\u00e9r\u00f4me Dubar\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"headline\":\"How to patch your ODA to 19.21?\",\"datePublished\":\"2024-01-24T15:51:25+00:00\",\"dateModified\":\"2024-02-13T08:43:02+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/\"},\"wordCount\":1975,\"commentCount\":4,\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/\",\"name\":\"How to patch your ODA to 19.21? - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2024-01-24T15:51:25+00:00\",\"dateModified\":\"2024-02-13T08:43:02+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to patch your ODA to 19.21?\"}]},{\"@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":"How to patch your ODA to 19.21? - 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\/how-to-patch-your-oda-to-19-21\/","og_locale":"en_US","og_type":"article","og_title":"How to patch your ODA to 19.21?","og_description":"Introduction Patch 19.21 is now available for Oracle Database Appliance series. Let’s find out what’s new and how to apply this patch. What’s new? The most important new component is Linux 8. X10 series were already running on Linux 8 with a dedicated patch (19.20.0.1), but older ODAs were stuck with Linux 7 since years. […]","og_url":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/","og_site_name":"dbi Blog","article_published_time":"2024-01-24T15:51:25+00:00","article_modified_time":"2024-02-13T08:43:02+00:00","author":"J\u00e9r\u00f4me Dubar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"J\u00e9r\u00f4me Dubar","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/"},"author":{"name":"J\u00e9r\u00f4me Dubar","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"headline":"How to patch your ODA to 19.21?","datePublished":"2024-01-24T15:51:25+00:00","dateModified":"2024-02-13T08:43:02+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/"},"wordCount":1975,"commentCount":4,"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/","url":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/","name":"How to patch your ODA to 19.21? - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2024-01-24T15:51:25+00:00","dateModified":"2024-02-13T08:43:02+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-patch-your-oda-to-19-21\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to patch your ODA to 19.21?"}]},{"@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\/30434","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=30434"}],"version-history":[{"count":4,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/30434\/revisions"}],"predecessor-version":[{"id":30438,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/30434\/revisions\/30438"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=30434"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=30434"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=30434"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=30434"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}