The CRS is Not Coming up Post Patching and ora.mdnsd is Not Coming Online due to Permissions Changes
(Doc ID 2671222.1)
Last updated on JULY 27, 2020
Applies to:
Oracle Exadata Storage Server Software - Version 19.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
During an Exadata Firmware patching pre-check from 19.2.1 to 19.3.6. one of the DBNodes has thrown various errors related to identifying an unexpected lower GI version .
: The following minimum Grid Infrastructure versions are supported to proceed the upgrade:
: - 19.4.0.0.190716
: - required patches: 30177140,29391849, 18.7.0.0.190716
: - required patches: 29637526,29391849
: - 12.2.0.1.190716
: - required patches: 29637526
: - 12.1.0.2.190716
: - required patches: 30139389
The CRS is not coming up post patching and error ora.mdnsd is not coming online post Exadata patching on one node.
Changes
Pre-check for patching firmware
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |