Problems with Database File System Mounting on Second Managed Server Node

This topic does not apply to Oracle Cloud at Customer.

When you mount Oracle Database File System on non Administration Pods, Oracle Database File System mounts on first Managed Server node but not on the second Managed Server node.

To mount Oracle Database File System on a second Managed Server node:.

Use the ssh command to connect to the scaled out Virtual Machine (VM) or the VM where you have created two or more node clusters:

ssh -i private_key opc@VM_IP_address

For example:
```
ssh -i opc_rsa opc@123.123.12.34
```
Change to the oracle user.
```
sudo su - oracle
```
Copy the existing workaround script to /tmp directory.
```
cp /u01/data/domains/<domain>/dbfs/dbfswa.sh /tmp
```
Change the permission on the /tmp/dbfswa.sh script file.
```
chmod 777 /tmp/dbfswa.sh
```
Change to the opc user.
```
sudo su - opc
```
Run the workaround script from tmp directory
```
cd /tmp/
./dbfswa.sh
```

Verify Oracle Database File System on Second Managed Server Node

Change to the oracle user.
```
sudo su - oracle
```

Run the following commands:

df —h
touch /u01/soacs/dbfs/share/test

Use the ssh command to connect to the Administration Server:

ssh -i opc_rsa opc@VM_IP_address
List the file that was touched on VM 2:
```
ls -ltr /u01/soacs/dbfs/share/
```
If you see the test file on VM 1, then the mount on the second Managed Server node and file sharing is successful on Oracle Database File System.