SEHA Patching on Windows: CRS startup encounters - Patch Levels don't match. Local Patch Level [XXXXXXXXXXX] != Cache Writer Patch Level [XXXXXXXXXXX]
(Doc ID 2923424.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Standard Edition - Version 19.3.0.0.0 and laterMicrosoft Windows x64 (64-bit)
--
- This is a 2-node SEHA (Standard Edition with High Availability) setup on Windows.
- Quarterly patches being applied on GI and RDBMS.
- First the Passive Host (DB not running) is being patched and then the Active Host.
- Failure encountered post patching on Passive Host during CRS Startup.
Symptoms
NOTE:
- 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.
- In a 2 node SEHA, environment the Passive Host where the database was not running was patched first. Active Host is not patched yet and the services are up and running on Active Host.
- Patching successful but CRS startup fails with below errors in alert log.
Changes
* GI and RDBMS was patched with RU on one host.
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 |