CRS Is Not Cleanly Shutting Down After ACFS Was Configured
Last updated on APRIL 20, 2018
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2]
Information in this document applies to any platform.
'# crsctl stop crs' is not cleanly shutting down CRS after ACFS was configured:
CRS-5014: Agent "/u01/app/11.2.0/grid/bin/orarootagent.bin" timed out starting process "/u01/app/11.2.0/grid/bin/acfssinglefsmount" for action "stop": details at "(:CLSN00009:)" in "/u01/app/11.2.0/grid/log/devdb1/agent/crsd/orarootagent_root/orarootagent_root.log"
CRS-2675: Stop of 'ora.acfs_fs_1.oraadm.acfs' on 'devdb1' failed
CRS-2679: Attempting to clean 'ora.acfs_fs_1.oraadm.acfs' on 'devdb1'
CRS-2677: Stop of 'ora.registry.acfs' on 'devdb1' succeeded
CRS-5016: Process "/u01/app/11.2.0/grid/bin/acfssinglefsmount" spawned by agent "/u01/app/11.2.0/grid/bin/orarootagent.bin" for action "clean" failed: details at "(:CLSN00010:)" in "/u01/app/11.2.0/grid/log/devdb1/agent/crsd/orarootagent_root/orarootagent_root.log"
ACFS-9252: The following process IDs have open references on /acfsmount/oraadm:
acfssinglefsmount: ACFS-9253: Failed to unmount /acfsmount/oraadm. Device likely in use.
acfssinglefsmount: ACFS-9254: Manual intervention is required.
ACFS was enabled on Existing ASM RAC configuration.
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