Unable To Cleanly Shutdown The CRS stack Using "crsctl stop crs -f" (SYSTEMDG in QUIESCING state)

(Doc ID 1233580.1)

Last updated on NOVEMBER 07, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.
Checked Currency on 18-Oct-2014

Symptoms

1) Unable to cleanly shutdown the CRS using any of the next commands:


# <Grid Infrastructure $ORACLE_HOME>/bin/crsctl stop crs



or


<Grid Infrastructure $ORACLE_HOME>/bin/crsctl stop crs -f


It failed with the next errors:


.
.
.
CRS-2678: 'ora.crsd' on 'node1' has experienced an unrecoverable failure
CRS-0267: Human intervention required to resume its availability.
CRS-2795: Shutdown of Oracle High Availability Services-managed resources on 'node1' has failed
CRS-4687: Shutdown command has completed with error(s).
CRS-4000: Command Stop failed, or completed with errors.
.
.
.




2) This leaves the SYSTEMDG diskgroup in QUIESCING state (HTML report from <Document 470211.1> ):


GROUP_NUMBER NAME STATE TYPE TOTAL_MB FREE_MB OFFLINE_DISKS
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3 SYSTEMDG QUIESCING NORMAL 894240 892024 0
0 RECO DISMOUNTED 0 0 0
0 DATA DISMOUNTED 0 0 0



Note: "The QUIESCING state occurs when the CRSCTL utility attempts to dismount a disk group that contains the Oracle Cluster Repository (OCR). The disk group cannot be dismounted until Cluster Ready Services (CRS) exits, because the disk group contains the OCR."

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