My Oracle Support Banner

ODA (Oracle Database Appliance): GI Patching Troubleshooting (Doc ID 1665754.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance Software - Version to
Information in this document applies to any platform.


There are cases for which the GI patching fails and the customer will need to reapply the GI patching.
How to debug where the GI patching fail, where are the logs, how the inventory.xml should be, it is the intent of this article


Basic Grid Infrastructure & oakcli knowledge is required.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 In the images, examples and document that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.
 GI Patching Troubleshooting
 Acronyms, Terms and Procedures Used in This Note
 Relevant Log and Trace location
 Location of OAK GI patching needed log/trace
 Location of runInstaller(OUI) needed log/trace
 Location of needed GI log/trace
 Case Studies
 1. GI update is failing due to invalid response file
 2. Out of place upgrade failing
 3. During GI update the did not complete successfully (due to OC4J resource failed to start)
 4. During GI update the did not complete successfully (due to OC4J resource failed to stop)
 5. During GI update the did not complete successfully (due to ASM not able to start up succesfully)
 6. Successfully GI upgrade but ASM is crashing with ODA-600 [kfdJoin3]
 7. GI upgrade failure after a previous failure

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.