Oracle: How to solve error "CLSRSC-494" while patching GI 19c

This is how to solve error "CLSRSC-494" 19c, which says "Failed to execute this command. Current directory is under an ACFS mount point", although ACFS is not used

Oracle: How to solve error "CLSRSC-494" while patching GI 19c

I was recently pathing Oracle Grid Infrastructure as Oracle Restart on an Oracle system. But when executing opatchauto apply, which mostly runs without issues, I was facing this issue:

Command execution failed during patching in home: /oracle/19/grid, host: qs0001db0081.  
Command failed:  bash -c "LD_LIBRARY_PATH=/oracle/19/grid/lib:/oracle/19/grid/srvm/lib:/oracle/patches/19.28/37957391/37962946/files/lib:/oracle/19/grid/lib:/oracle/19/grid/lib:/oracle/19/grid/srvm/lib:/oracle/19/grid/lib:/oracle/19/grid/srvm/lib:/oracle/19/grid/lib /oracle/19/grid/perl/bin/perl -I/oracle/19/grid/perl/lib -I/oracle/19/grid/opatchautocfg/db/dbtmp/bootstrap_qs0001db0081/patchwork/crs/install -I/oracle/19/grid/opatchautocfg/db/dbtmp/bootstrap_qs0001db0081/patchwork/xag /oracle/19/grid/opatchautocfg/db/dbtmp/bootstrap_qs0001db0081/patchwork/crs/install/[roothas.pl](http://roothas.pl) -prepatch"  
Command failure output:  
Using configuration parameter file: /oracle/19/grid/opatchautocfg/db/dbtmp/bootstrap_qs0001db0081/patchwork/crs/install/crsconfig_params  
The log of current session can be found at:  
  /oracle/crsdata/qs0001db0081/crsconfig/hapatch_2025-08-07_10-07-12AM.log  
2025/08/07 10:07:12 CLSRSC-494: Failed to execute this command. Current directory is under an ACFS mount point.  
  
After fixing the cause of failure Run opatchauto resume  
  
\]  
OPATCHAUTO-68061: The orchestration engine failed.  
OPATCHAUTO-68061: The orchestration engine failed with return code 1  
OPATCHAUTO-68061: Check the log for more details.  
OPatchAuto failed.

Unfortunately, I do not use ACFS on this system.

After some investigation I found Oracle Support document 2184058.1. It tells me to stop and disable ACFS like this:

# acfsload stop
# acfsroot uninstall

After that, patching GI using opatchauto was successful.

Happy patching 😄

Subscribe to Martin's Blog

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe