CRS Fails To Start After Downgrade Following A Failed Upgrade Attempt
Last updated on OCTOBER 13, 2016
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.5 to 220.127.116.11 [Release 10.2 to 11.1]
Information in this document applies to any platform.
Following a failed upgrade attempt to 11.2 the clusterware is downgraded back to 10.2 (or 11.1). When attempting to start the 10.2 clusterware, the CRS stack never fully initializes, crsd.bin & ocssd.bin processes are running but the CRS daemon is not ready (crs_stat returns "Cannot communicate with CRS").
The CRS daemon log (<CRS home>/log/<node>/crsd/crsd.log) repeatedly shows the following message:
The clusterware is downgraded back to 10.2 (or 11.1) after a failed attempt to upgrade to 11..2.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms