For those who don’t know yet, patch 19.13 brings 21.4 for database management systems along with the usual bug fixes. Since 21c is an innovation release and some users have been expecting something new, they’ll be interested in the multi-user mode available for odacli operations. In this article, we’ll explain how to download this patch and whether it’s helpful for Oracle SQL performance tuning.
In other words, users won’t have to be root to take charge of the appliance. On the downside, users can only enable this feature during provisioning – not once the patching is complete. They can also make use of the new parameter deployment feature that’s helpful in handling parameters through various instances.
More About this Patch
The patch we’re talking about is cumulative like the majority of them. This means users can apply it over a version that’s older than the last one. In this case, you can apply 19.13 over 19.9 or later. Experts also suggest applying patches on a yearly basis at the minimum. This saves users from being forced to apply multiple patches to reach the target version and ensure optimal performance.
Specialists also recommend reimaging rather than patching for versions older than 18 for a cleaner, more convenient experience.
If you’re looking for help on how to create index Oracle, refer to one of our previous articles.
What Files Do You Need to Download?
Not a lot as the patch doesn’t include GI and DB patches, making it lighter in comparison with its predecessors. There are the patch files along with their corresponding DB and GI clones to facilitate the application.
Since the patch numbers remain the same for multiple options, make sure to select the newest patch if you already have the clones. Otherwise, you may follow My Oracle Support’s suggestion of choosing an older version that also contains the DB and GI clones.
You’ll receive a mandatory pre-patch to test the patch that takes around ten minutes, leaving plenty of time for Oracle SQL performance tuning once the patch is installed. However, you’ll need to check for certain prerequisites before you proceed:
- Making preparations for the downtime is important as this process (patching and possible issue-resolving) will take at least four hours. For stress-free operations, consider taking one day.
- Check to see whether the filesystems have at least a fifth of available free space
- You’ll likely have to delete any additional RPMs you previously installed manually.
- Grid users will have to change the profile scripts back to the default.
Steps to Make File Preparations and Update the Necessary Tools
Step 1: Use a temp directory in the database where you can copy and unzip the downloaded patch files.
Step 2: Register the patch but don’t update the DB and GI clones yet.
Step 3: Update your database’s DCS tools.
Step 4: You are now ready to register the DB and GI clones.
This update doesn’t affect other tasks either, so you can create index Oracle easily.
Things to Consider Once Patching Begins
When you initiate the update-server, you will find the server reboots within five minutes of the completion of the process. After it does, there are a few things to check to ensure the process went as planned:
- Check the components’ versions.
- Check the ACFS volumes. This is necessary even if they appear normal because they may not mount after the reboot – manual or otherwise. It will require reinstallation of the drivers from the new GI home before restarting them to ensure smooth Oracle SQL performance tuning in the future.
Soon after, the time will come to patch the storage – a step only older patch levels or ODAs will require. This process also follows the pre-patch before patch method. Most users prefer the rolling method for HA databases that use RAC. Still, the process is quite straightforward and doesn’t require too much effort, nor are you likely to face any issues as you complete it.
The next phase involves patching the DB homes that exist on an ACFS filesystem. This system has been followed since patch 19.11, so if your version is older than that (say 19.9 or 19.10) you will have to configure the filesystem to adopt it.
The time it takes to patch the DB homes may vary on the basis of the quantity of the databases and DB homes. Again, you will require pre-patching, especially in the case of multiple homes. Once you’ve completed pre-patching, you can apply the patch on the DB homes. You may also create a new DB home and link your database to it before eliminating the old DB home safely.
