Pre-Reqs
  • User ID and Group ID should be consistent across all nodes to avoid file access permission issues.
  • The same absolute path must be retained for the shared file system mount points on each node.
  • The value for the context variable "s_atName" must be same across all the application tier node context files.
  • Password less ssh between the nodes.
  • The database and TNS listener must be running before the steps listed below are performed.


Steps:

 1. Ensure that value of the AutoConfig variable s_shared_file_system is set to true on the primary application node.(Node Where you weblogic admin server runs)
Please change it to true if not already present and run AutoConfig on both RUN & PATCH FS

 2. Source Run Filesystem make sure all services are down.

 3.Execute adpreclone Utility on the Run and Patch File System

 On the run file system:

 $ cd <inst-top-run-fs>/admin/scripts 
$ ./adadminsrvctl.sh start
$ ./adpreclone.pl appsTier
Once the utility completes, shut down the application tier processes:
$ ./adstpall.sh <apps-user-name>/<apps-password>
On the patch file system:

 $ cd <inst-top-patch-fs>/admin/scripts 
$ ./adadminsrvctl.sh start forcepatchfs 
$ ./adpreclone.pl appsTier
Once the utility completes, shut down the application tier processes.
$ ./adstpall.sh <apps-user-name>/<apps-password> forcepatchfs

The AD/TXK D7 patch introduce a new flow that adds both the run and patch edition file system with a single command. The steps given below configures both Run and Patch edition file system for a new node that is going to be added to the farm. 

 1. Ensure the correct perl utility is in the $PATH. You must use the perl utility installed in the Fusion Middleware Oracle Home.

 For example:

 $ export PATH=/u01/12.2/fs1/FMW_Home/webtier/perl/bin:$PATH

 2. Ensure the WebLogic Administration Server is running from both run and Patch file system on the primary application tier node.

 3. A sample pairsfile for the run/patch file system is instantiated into the instance home on the primary application tier node. The file is called <SID>_<primary_node_name>_.txt, and located in the <inst_top>/appl/admin/ directory. For a configuration with an instance name of VIS, the pairsfile will be /u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1.txt.

 4.Create the required directories and copy the pairsfile into a directory of your choice on the secondary application tier node. For example:

 $ /bin/mkdir -p /u01/12.2/pairsfiles
$ cd /u01/12.2/pairsfile
$ /bin/cp /u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1.txt mypairsfile.txt
Make changes to pairs file as needed
5. Execute adclonectx utility to configure both run and Patch file system

 $ cd /u01/12.2/fs1/EBSapps/comn/clone/bin
$ /u01/12.2/fs1/FMW_Home/webtier/perl/bin/perl ./adclonectx.pl \
addnode contextfile=/u01/12.2/fs1/inst/apps/VIS_appstier1/appl/admin/VIS_appstier1.xml \ 
pairsfile=/u01/12.2/pairsfile/mypairsfile.txt \
dualfs=yes
4. Review the log files displayed by the add node utility to ensure that the add node operation has gone through successfully. 
Reference:
Sharing The Application Tier File System in Oracle E-Business Suite Release 12.2 (Doc ID 1375769.1)