{"id":16971,"date":"2021-12-11T10:55:01","date_gmt":"2021-12-11T09:55:01","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/oracle-database-appliance-19-13-whats-new-and-how-to-patch\/"},"modified":"2021-12-11T10:55:01","modified_gmt":"2021-12-11T09:55:01","slug":"oracle-database-appliance-19-13-whats-new-and-how-to-patch","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/oracle-database-appliance-19-13-whats-new-and-how-to-patch\/","title":{"rendered":"Oracle Database Appliance 19.13: what’s new and how to patch?"},"content":{"rendered":"

Introduction<\/h2>\n

Patch 19.13 is now available on ODA. It’s time to test it.<\/p>\n

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

This version brings October’s PSU to database and grid homes with their bug fixes, as usual. It also brings 21.4 for DB Systems (21c being an innovation release, understand just for testing). Something new that some of us have been waiting for a while, a multi-user mode for odacli tasks: you don’t need to be root anymore for managing the appliance. This new feature can only be enabled when provisioning, so don’t expect to catch it after patching. A parameter deployment feature is also available now, helping managing parameters across multiple instances (bare metal only). <\/p>\n

This 19.13 will be the latest one for those still using virtualized ODA: virtualization is now integrated in all bare metal ODAs with KVM (instead of OVM), check this blog post if you’re not aware about that<\/a>. Plan to redeploy your virtualized ODA to bare metal if your system is still supported for a couple of years.<\/p>\n

Which ODA is compatible with 19.13?<\/h2>\n

For sure, ODA X8 in its 3 flavors (S, M, HA) is compatible as this is the current one (but it should be replaced quite soon). X7 and X6 are also compatible without any problem. X5-2HA is also still supported, this could be one of the latest patch for this nearly 7-year old ODA.<\/p>\n

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

Most of the patches are cumulative, meaning that you can apply them on top of a version older than the previous one. This 19.13 can be applied on top of 19.9 or later, 19.9 being 1 year old. This is something I would recommend to each of my customer: apply patches at least once a year to avoid longer patching, longer meaning multiple patches to apply to reach target version.<\/p>\n

If you are still using an old version, I would say 18.x or older, consider reimaging instead of patching. Reimaging is much more comfortable and cleaner compared to 3 or more patches to apply.<\/p>\n

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

If you’re using 12.1, 12.2 or 19c, these databases can be patched. 11gR2 and 18c are no more supported on ODA, meaning that your databases will continue working but you should definitely consider an upgrade quite soon. Remember that if you choose to reimage to this latest version, you will not find any 18c or 11gR2 DB homes to deploy.<\/p>\n

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

Since months now, the patch is lighter because it doesn’t include DB and GI patches anymore. Patching DB or GI is deploying a new home and migrating from the older one. As this new way of patching is based on DB and GI clones, download the corresponding clones to be able to apply the complete patch.<\/p>\n

33518928 => the patch itself
\n30403673 => the GI clone needed for deploying new version (mandatory)
\n30403662 => the DB clone for deploying new version of 19c (if you use 19c databases)
\n27119402 => the DB clone for deploying new version of 12.2 (if you use 12.2 databases)
\n23494992 => the DB clone for deploying new version of 12.1 (if you use 12.1 databases)<\/p>\n

Be sure to choose the very latest 19.13 when downloading, as most of the time My Oracle Support will propose an older version for GI clones and DB clones (patch number is the same for older versions). <\/p>\n

Prepare the patching<\/h2>\n

A pre-patch is now provided and needed before applying an ODA patch, but prior running it, please check these prerequisites:<\/p>\n