The previous articles discussed how to recover a node after losing "only the DB BINARIES" and "only the GRID BINARIES." This time, let's try to recover from losing both binaries.
My configuration
Oracle RAC with 2 nodes: ol8-19-rac1 and ol8-19-rac2
CDB: cdbrac1
PBD: pdb1
Grid Version
34318175;TOMCAT RELEASE UPDATE 19.0.0.0.0 (34318175)
34160635;OCW RELEASE UPDATE 19.16.0.0.0 (34160635)
34139601;ACFS RELEASE UPDATE 19.16.0.0.0 (34139601)
34133642;Database Release Update : 19.16.0.0.220719 (34133642)
33575402;DBWLM RELEASE UPDATE 19.0.0.0.0 (33575402)
DB Version
34086870;OJVM RELEASE UPDATE: 19.16.0.0.220719 (34086870)
34160635;OCW RELEASE UPDATE 19.16.0.0.0 (34160635)
34133642;Database Release Update : 19.16.0.0.220719 (34133642)
When you see <dbenv>, load the DB HOME variables.
When you see <gridenv>, load the GRID HOME variables.
When you see <bnode>, execute the command on the broken node.
When you see <anode>, execute the command on any other working node.
I am using an installation where both DB and GRID are installed under the user ORACLE, and I set the variables to access each environment. But the same procedure works even if the installation is done using two different users (usually oracle e grid).
Always validate any procedure before you try it in a production environment.
Scenario C - DB and GRID Binaries Corrupted On ol8-19-rac2 After Applying a Patch
This time, we will combine previous solutions to complete the job. For the sake of simplicity, I'll only provide the steps needed, and you can check how to execute them in the previous articles.
I. From the article on DB Binaries, execute the following steps:
-
Backup the $ORACLE_HOME/network/admin. -
Deinstall the DB binaries.
II. From the article on GRID Binaries, execute all the steps.
III. From the article on DB Binaries, execute the following steps:
Add the node back.Add the instance back.If needed, restore the $ORACLE_HOME/network/admin on the ex-broken node.
Voilà, that's it. Now, your database is supposed to be back online on the ex-broken node.