{"id":29757,"date":"2023-12-13T18:04:42","date_gmt":"2023-12-13T17:04:42","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=29757"},"modified":"2023-12-13T18:04:44","modified_gmt":"2023-12-13T17:04:44","slug":"oda-hybrid-patching-19-20-19-19","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/","title":{"rendered":"ODA hybrid patching: 19.20\/19.19"},"content":{"rendered":"\n

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

Patching your Oracle Database Appliance (ODA) is highly recommended: once a year being the minimum you could do. It prevents security risks, fixes some bugs and eventually provides new features. And it also keeps your appliance supported: according to MOS note 2757884.1, your ODA should be running version 19.16 for X7-2 series, X8-2 series and X9-2 series, and version 19.20.0.1 for X10 series.<\/p>\n\n\n\n

Regular patching also allows one step patching: you can jump to the latest release without intermediate versions. But patching all the components to the very latest release is not always possible. In my example for today, patching the database to 19.20 was not possible because of a bug that would have a big impact on customer’s application. The ODA was running on 19.17, and the plan was to apply 19.20, the latest one available at this time. What is the alternate plan for keeping the databases to previous 19.19?<\/p>\n\n\n\n

Keep everything aligned, yes but\u2026<\/h2>\n\n\n\n

The first option would be patching all the components to 19.19. So everything would have been aligned in the describe-component command. The problem is that 19.19 is rather old, from May 2023. For a patching done in December, my ODA wouldn’t have been so up-to-date staying in 19.19.<\/p>\n\n\n\n

The second option would be patching the system and storage components to 19.20 and patching the database to 19.19. This is a supported configuration, and I could eventually upgrade my databases later from 19.19 to 19.20 if needed.<\/p>\n\n\n\n

Here is how you can achieve this hybrid configuration.<\/p>\n\n\n\n

Patching the system and storage components to 19.20<\/h2>\n\n\n\n

First steps of patching won’t be different compared to a full 19.20 patch. You will need to download the 19.20 patch, the 19.20 GI home, register these files in the ODA registry, patch the DCS components, do the precheck for the system patch, apply the system patch, do the precheck for the storage patch and apply the storage patch. Here are the commands I used in this case:<\/p>\n\n\n\n

odacli update-repository -f \/backup\/ODA_patch\/oda-sm-19.20.0.0.0-230802.1-server.zip,\/backup\/ODA_patch\/odacli-dcs-19.20.0.0.0-230720-GI-19.20.0.0.zip\nodacli update-dcsadmin -v 19.20.0.0.0\nodacli update-dcscomponents -v 19.20.0.0.0\nodacli update-dcsagent -v 19.20.0.0.0\nodacli create-prepatchreport -s -v 19.20.0.0.0\nodacli update-server -v 19.20.0.0.0\nodacli create-prepatchreport -st -v 19.20.0.0.0\nodacli update-storage -v 19.20.0.0.0<\/code><\/pre>\n\n\n\n
Don’t forget to check the versions with odacli describe-component after each update.<\/p>\n\n\n\n
Once done, your system and storage are updated to 19.20, and your databases are still running on 19.17 DB homes.<\/p>\n\n\n\n
Updating your DB homes to 19.19<\/h2>\n\n\n\n
I will patch the DB homes, meaning it will also patch all the databases using these DB homes. First, list your DB homes:<\/p>\n\n\n\n
odacli list-dbhomes\nID                                       Name                 DB Version                               DB Edition Home Location                                 Status\n---------------------------------------- -------------------- ---------------------------------------- ---------- --------------------------------------------- ----------\n896ce25f-c05f-4765-986b-db807a26e150     OraDB19000_home6     19.17.0.0.221018                         EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED\n                                                                                                                  .0\/dbhome_6                  \n2caf70b0-8af1-4b17-8410-00de77f0949d     OraDB19000_home7     19.17.0.0.221018                         EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t  .0\/dbhome_7                  <\/code><\/pre>\n\n\n\n
Now, you will need to register the 19.19 patch. When applying a patch, the target version should be in the ODA registry, only registering the DB clone is not enough:<\/p>\n\n\n\n
odacli update-repository -f \/backup\/ODA_patch\/oda-sm-19.19.0.0.0-230510-server.zip\n\nodacli describe-job -i \"b7f966c0-4996-44a2-a2ac-11e2175c2404\"\nJob details\n----------------------------------------------------------------\n                     ID:  b7f966c0-4996-44a2-a2ac-11e2175c2404\n            Description:  Repository Update\n                 Status:  Success\n                Created:  December 2, 2023 10:12:35 AM CET\n                Message:  \/backup\/ODA_patch\/oda-sm-19.19.0.0.0-230510-server.zip\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nUnzip bundle                             December 2, 2023 10:12:36 AM CET    December 2, 2023 10:13:05 AM CET    Success\n\n\n\nodacli update-repository -f \/backup\/ODA_patch\/odacli-dcs-19.19.0.0.0-230510-DB-19.19.0.0.zip\n\nodacli describe-job -i \"70c965dc-1b13-4c55-80bf-a028fcc9b5ef\"\nJob details\n----------------------------------------------------------------\n                     ID:  70c965dc-1b13-4c55-80bf-a028fcc9b5ef\n            Description:  Repository Update\n                 Status:  Success\n                Created:  December 2, 2023 10:17:53 AM CET\n                Message:  \/backup\/ODA_patch\/odacli-dcs-19.19.0.0.0-230510-DB-19.19.0.0.zip\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nUnzip bundle                             December 2, 2023 10:17:53 AM CET    December 2, 2023 10:18:32 AM CET    Success<\/code><\/pre>\n\n\n\n
I will need to do a precheck on both DB homes, let’s start with the first one:<\/p>\n\n\n\n
odacli create-prepatchreport -d -i 896ce25f-c05f-4765-986b-db807a26e150 -v 19.19.0.0.0\n\nodacli describe-prepatchreport -i 1ff22fc8-9613-483f-bb83-3f245452a6eb\nPatch pre-check report\n------------------------------------------------------------------------\n                 Job ID:  1ff22fc8-9613-483f-bb83-3f245452a6eb\n            Description:  Patch pre-checks for [DB, ORACHKDB]: DbHome is OraDB19000_home6\n                 Status:  FAILED\n                Created:  December 2, 2023 10:36:21 AM CET\n                 Result:  One or more pre-checks failed for [ORACHK]\n\nNode Name\n---------------\nuns-oda1\n\nPre-Check                      Status   Comments\n------------------------------ -------- --------------------------------------\n__DB__\nValidate DB Home ID             Success   Validated DB Home ID:\n                                          896ce25f-c05f-4765-986b-db807a26e150\nValidate patching tag           Success   Validated patching tag: 19.19.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\nCheck for parameter             Failed    AHF-3744: Database parameter\nglobal_names                              GLOBAL_NAMES is not set to\n                                          recommended value\nCheck for parameter recyclebin  Failed    AHF-1679: RECYCLEBIN on PRIMARY\n                                          should be set to the recommended value<\/code><\/pre>\n\n\n\n
Most often, the precheck will fail on Orachk, but having different parameters than those recommended will not prevent your database to be patched. If everything but Orachk is OK, you can apply the patch with the force option. Note that the patching won’t upgrade your DB home but will create a new one and move the databases in this new home, then will apply the datapatch on all the databases. If your DB home runs Standby databases, they will be moved but no datapatch will be applied.<\/p>\n\n\n\n
odacli update-dbhome -i 896ce25f-c05f-4765-986b-db807a26e150 -v 19.19.0.0.0 -f\nodacli describe-job -i \"059d3052-9e17-4397-8551-c3a9e1df0b24\"\nJob details\n----------------------------------------------------------------\n                     ID:  059d3052-9e17-4397-8551-c3a9e1df0b24\n            Description:  DB Home Patching: Home Id is 896ce25f-c05f-4765-986b-db807a26e150\n                 Status:  Success\n                Created:  December 2, 2023 10:49:35 AM CET\n                Message:\n\nTask Name                                Start Time                          End Time                            Status\n---------------------------------------- ----------------------------------- ----------------------------------- ----------\nCreating wallet for DB Client            December 2, 2023 10:49:43 AM CET    December 2, 2023 10:49:43 AM CET    Success\nPatch databases by RHP - [PCSW]          December 2, 2023 10:49:43 AM CET    December 2, 2023 10:55:10 AM CET    Success\nUpdating database metadata               December 2, 2023 10:55:10 AM CET    December 2, 2023 10:55:10 AM CET    Success\nSet log_archive_dest for Database        December 2, 2023 10:55:10 AM CET    December 2, 2023 10:55:12 AM CET    Success\nUpdate System version                    December 2, 2023 10:55:12 AM CET    December 2, 2023 10:55:12 AM CET    Success\nGenerating and saving BOM                December 2, 2023 10:55:12 AM CET    December 2, 2023 10:56:03 AM CET    Success\nTDE parameter update                     December 2, 2023 10:56:03 AM CET    December 2, 2023 10:56:03 AM CET    Success<\/code><\/pre>\n\n\n\n
Then I’ve done the same tasks for the second DB home. Your databases should normally use these new DB homes:<\/p>\n\n\n\n
odacli list-databases\nID                                       DB Name    DB Type  DB Version           CDB     Class    Edition  Shape    Storage  Status       DB Home ID\n---------------------------------------- ---------- -------- -------------------- ------- -------- -------- -------- -------- ------------ ----------------------------------------\nffdfcee3-c646-43ee-925b-2ae6f339b0e4     VCSGU      SI       19.19.0.0.230418     false   OLTP     EE       odb10    ACFS     CONFIGURED   121f642f-2233-483d-9f39-57450fd9ddd9\ncf99a1b1-4c9c-4431-b7b7-e906c4be0fb6     VCSW       SI       19.19.0.0.230418     false   OLTP     EE       odb6     ACFS     CONFIGURED   c069c4f2-4add-4670-a103-d29fd0bac832<\/code><\/pre>\n\n\n\n
Removing old DB homes<\/h2>\n\n\n\n
Now you can safely remove the 19.17 DB homes:<\/p>\n\n\n\n
odacli list-dbhomes\nID                                       Name                 DB Version                               DB Edition Home Location                                 Status\n---------------------------------------- -------------------- ---------------------------------------- ---------- --------------------------------------------- ----------\n896ce25f-c05f-4765-986b-db807a26e150     OraDB19000_home6     19.17.0.0.221018                         EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED                                                                                                             .0\/dbhome_6                  \n2caf70b0-8af1-4b17-8410-00de77f0949d     OraDB19000_home7     19.17.0.0.221018                         EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED                                                                                                             .0\/dbhome_7                  \n\u2003\nc069c4f2-4add-4670-a103-d29fd0bac832     OraDB19000_home8     19.19.0.0.230418                         EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED\n                                                                                                                  .0\/dbhome_8                  \n121f642f-2233-483d-9f39-57450fd9ddd9     OraDB19000_home9     19.19.0.0.230418                         EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED\n\n\nodacli delete-dbhome -i 896ce25f-c05f-4765-986b-db807a26e150\nodacli delete-dbhome -i 2caf70b0-8af1-4b17-8410-00de77f0949d\n\nodacli list-dbhomes\nID                                       Name                 DB Version                               DB Edition Home Location                                 Status\n---------------------------------------- -------------------- ---------------------------------------- ---------- --------------------------------------------- ----------\nc069c4f2-4add-4670-a103-d29fd0bac832     OraDB19000_home8     19.19.0.0.230418                         EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED                                                                                                                .0\/dbhome_8                  \n121f642f-2233-483d-9f39-57450fd9ddd9     OraDB19000_home9     19.19.0.0.230418                         EE         \/u01\/app\/odaorahome\/oracle\/product\/19.0.0     CONFIGURED\n .0\/dbhome_9                           <\/code><\/pre>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
Is it better mixing versions or aligning system, storage and DB homes? Definitely, having a system using the highest possible version is more secure. And having databases’ patch level to something a little bit older is not a problem at all. But try keeping the gap as small as possible. I won’t recommend using 18c, 12c or 11gR2 with latest 19.20, as it’s not supported at all. If you need this kind of configuration, think about virtualizing your old databases as described here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Introduction Patching your Oracle Database Appliance (ODA) is highly recommended: once a year being the minimum you could do. It prevents security risks, fixes some bugs and eventually provides new features. And it also keeps your appliance supported: according to MOS note 2757884.1, your ODA should be running version 19.16 for X7-2 series, X8-2 series […]<\/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":[3192,3195,3194,2568,3193,3078,1536,1696,2569],"type_dbi":[],"class_list":["post-29757","post","type-post","status-publish","format-standard","hentry","category-oracle","tag-hybrid-patching","tag-odacli-update-dbhome-2","tag-odacli-update-system","tag-oracle-database-appliance-2","tag-patch-oda-and-databases-to-different-versions","tag-x10","tag-x7-2","tag-x8-2","tag-x9-2"],"acf":[],"yoast_head":"\nODA hybrid patching: 19.20\/19.19 - 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\/oda-hybrid-patching-19-20-19-19\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"ODA hybrid patching: 19.20\/19.19\" \/>\n<meta property=\"og:description\" content=\"Introduction Patching your Oracle Database Appliance (ODA) is highly recommended: once a year being the minimum you could do. It prevents security risks, fixes some bugs and eventually provides new features. And it also keeps your appliance supported: according to MOS note 2757884.1, your ODA should be running version 19.16 for X7-2 series, X8-2 series […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2023-12-13T17:04:42+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-12-13T17:04:44+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=\"3 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\\\/oda-hybrid-patching-19-20-19-19\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oda-hybrid-patching-19-20-19-19\\\/\"},\"author\":{\"name\":\"J\u00e9r\u00f4me Dubar\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"headline\":\"ODA hybrid patching: 19.20\\\/19.19\",\"datePublished\":\"2023-12-13T17:04:42+00:00\",\"dateModified\":\"2023-12-13T17:04:44+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oda-hybrid-patching-19-20-19-19\\\/\"},\"wordCount\":631,\"commentCount\":0,\"keywords\":[\"hybrid patching\",\"odacli update-dbhome\",\"odacli update-system\",\"oracle database appliance\",\"patch oda and databases to different versions\",\"X10\",\"x7-2\",\"x8-2\",\"x9-2\"],\"articleSection\":[\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oda-hybrid-patching-19-20-19-19\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oda-hybrid-patching-19-20-19-19\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oda-hybrid-patching-19-20-19-19\\\/\",\"name\":\"ODA hybrid patching: 19.20\\\/19.19 - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2023-12-13T17:04:42+00:00\",\"dateModified\":\"2023-12-13T17:04:44+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/0fb4bbf128b4cda2f96d662dec2baedd\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oda-hybrid-patching-19-20-19-19\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oda-hybrid-patching-19-20-19-19\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/oda-hybrid-patching-19-20-19-19\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ODA hybrid patching: 19.20\\\/19.19\"}]},{\"@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":"ODA hybrid patching: 19.20\/19.19 - 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\/oda-hybrid-patching-19-20-19-19\/","og_locale":"en_US","og_type":"article","og_title":"ODA hybrid patching: 19.20\/19.19","og_description":"Introduction Patching your Oracle Database Appliance (ODA) is highly recommended: once a year being the minimum you could do. It prevents security risks, fixes some bugs and eventually provides new features. And it also keeps your appliance supported: according to MOS note 2757884.1, your ODA should be running version 19.16 for X7-2 series, X8-2 series […]","og_url":"https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/","og_site_name":"dbi Blog","article_published_time":"2023-12-13T17:04:42+00:00","article_modified_time":"2023-12-13T17:04:44+00:00","author":"J\u00e9r\u00f4me Dubar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"J\u00e9r\u00f4me Dubar","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/"},"author":{"name":"J\u00e9r\u00f4me Dubar","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"headline":"ODA hybrid patching: 19.20\/19.19","datePublished":"2023-12-13T17:04:42+00:00","dateModified":"2023-12-13T17:04:44+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/"},"wordCount":631,"commentCount":0,"keywords":["hybrid patching","odacli update-dbhome","odacli update-system","oracle database appliance","patch oda and databases to different versions","X10","x7-2","x8-2","x9-2"],"articleSection":["Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/","url":"https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/","name":"ODA hybrid patching: 19.20\/19.19 - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2023-12-13T17:04:42+00:00","dateModified":"2023-12-13T17:04:44+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/0fb4bbf128b4cda2f96d662dec2baedd"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/oda-hybrid-patching-19-20-19-19\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"ODA hybrid patching: 19.20\/19.19"}]},{"@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\/29757","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=29757"}],"version-history":[{"count":8,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/29757\/revisions"}],"predecessor-version":[{"id":29765,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/29757\/revisions\/29765"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=29757"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=29757"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=29757"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=29757"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}