Skip to main content

How to unmount and mount ACFS FILESYSTEM



How to unmount and mount ACFS FileSystem in Linux

Unmounting ACFS File Systems

ACFS file systems can be used by Oracle RAC for hosting software files for the database. It can also be used as a general purpose file system for non-database files. The ACFS file system is managed and administered by the Oracle Grid Infrastructure, So ACFS file systems will be impacted when shutting down the GI stack for patching GI homes.
Shut down the processes (including non-Oracle processes) that use the files on ACFS, then unmount the ACFS file system.
If the ACFS file system is used by Oracle database software, then perform Steps 1 and 2.
1.      Execute the following command to find the names of the CRS managed ACFS file system resource.
 # crsctl stat res -w "TYPE = ora.acfs.type" -p | grep VOLUME
2.      Execute the following command to stop the CRS managed ACFS file system resource with the resource name found from Step 1.
As root user execute: 
 # srvctl stop filesystem -d <volume device path> -n <node to stop file system on>

If the ACFS file system is not used for Oracle Database software and is registered in the ACFS registry, perform the following steps.
1.      Execute the following command to find all ACFS file system mount points.
As root user execute: 
 # /sbin/acfsutil registry
2.      Unmount ACFS file systems found in Step 1.
As root user execute: 
 # /bin/umount <mount-point>
Note:
On Linux, use: /bin/umount
On Solaris, use: /sbin/umount
On AIX, use: /usr/sbin/umount
 
3.      Verify that the ACFS file systems are unmounted. Execute the following command to verify.
As the root user execute:
 # /sbin/acfsutil info fs
The previous command should return the following message if there is no ACFS file systems mounted.
 "acfsutil info fs: ACFS-03036: no mounted ACFS file systems"
  

Mounting ACFS File Systems

If the ACFS file system is used by Oracle database software, then perform Steps 1 and 2.
1.      Execute the following command to find the names of the CRS managed ACFS file system resource.
As root user execute: 
 # crsctl stat res -w "TYPE = ora.acfs.type" -p | grep VOLUME
2.      Execute the following command to start and mount the CRS managed ACFS file system resource with the resource name found from Step 1.
As root user execute: 
 # srvctl start filesystem -d <volume device path> -n <node to start file system on>

If the ACFS file system is not used for Oracle Database software and is registered in the ACFS registry, these file systems should get automatically mounted when the CRS stack comes up. Perform Steps 1 and 2 if it is not already mounted.
1.      Execute the following command to find all ACFS file system mount points.
As the root user execute: 
 # /sbin/acfsutil registry
2.      Mount ACFS file systems found in Step 1.
As the root user execute:
 # /bin/mount <mount-point>

Note:
On Linux, use: /bin/mount
On Solaris, use: /sbin/mount
On AIX, use: /usr/sbin/mount

Reference Doc Id:
How to Mount or Unmount ACFS File System While Applying GI Patches? (Doc ID 1494652.1)

Comments

Popular posts from this blog

How to perform GRID/RDBMS patching of DB systems deployed in OCI using dbcli command line utility

This procedure covers OS, Grid and RDBMS home patching for Oracle Cloud Infrastructure (OCI) DB systems using the dbcli utility. Run every step as root . Advantages of dbcli patching Simple command line, with no manual patch download or copy to the nodes. Patches are downloaded automatically if the service gateway can reach Oracle Object Storage and the YUM repos. Applied in a rolling fashion, so no downtime is needed. Disadvantages You can't choose the patch version; the latest available in OCI is applied. Rollback isn't possible from the console, and dbcli support is limited (see the note at the end). Steps 1. Backup Make sure a recent full backup exists before patching. 2. Blackout Create a blackout for both nodes (console or emctl ) to avoid unnecessary alerts. 3. Check patch availability # dbcli describe-component 4. Pre-checks Grid home: # dbcli update-server -p # dbcli describe-job -i <jobId> RDBMS home: # dbcli list-dbhomes...

To fix huge lag between primary and DR using 12c feature: 12c Recover from service

Scope If transport or apply lag is huge difference, then we can fix using 12c new feature “Recover from Service”. Prerequisites : Oracle Net connectivity is established between the physical standby database and the primary database. You can do this by adding an entry corresponding to the primary database in the tnsnames.ora file of the physical standby database. The password files on the primary database and the physical standby database are the same. The COMPATIBLE parameter in the initialization parameter file of the primary database and physical standby database is set to 12.0 or higher. Start RMAN and connect as target to the physical standby database. Detailed Steps: Step 1: Stop the MRP process in standby database. If dg broker: Edit database <dbname> set state=’APPLY-OFF’; Step 2:   Shut down the standby database and mount the same. Shut immediate;   (srvctl stop database –d <dbname>)  ...