CRS Fails To Start After Downgrade Following A Failed Upgrade Attempt (Doc ID 1595418.1)

Last updated on OCTOBER 13, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.5 to 11.1.0.7 [Release 10.2 to 11.1]
Information in this document applies to any platform.

Symptoms

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:


 

Changes

The clusterware is downgraded back to 10.2 (or 11.1) after a failed  attempt to upgrade to 11..2.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms