I completely agree with the points you've mentioned.
In addition, I’d like to bring a few more considerations to your attention:
Manual Oracle Home Check: Before the patching day, we will manually verify that the Oracle Home exists. If it doesn't, we will need to push the installations manually, one by one, using the same OEM procedures. This process is time-consuming and adds significant effort during weekdays.
Validation of Invalid Objects: It's important to note that having invalid objects or components doesn't help the patching process and often requires manual fixes. This should be addressed before patching to ensure a smooth process.
Post-Patching Health Check: After patching is complete, we must perform a thorough Health Check (HC), specifically ensuring the database is not in restricted mode. This step is crucial for confirming everything is functioning correctly post-patch.
Oracle Home Cleanup: I’ve noticed that the Oracle Home cleanup has not been happening post-patching. I’m unsure if this was under discussion or is still being worked upon, but I want to emphasize that cleaning up the old Oracle Home is a crucial step to avoid outages and prevent unnecessary alerting incidents.
Given the effort involved in the pre-tasks during weekdays and the subsequent patching on weekends, the process can be quite hectic. Streamlining some of these steps or finding ways to automate them could significantly reduce the workload.
Please let me know your thoughts or if we need to discuss this further.
0 comments:
Post a Comment