How to Recreate the Patch File System in Oracle EBS R12.2 – Step-by-Step Guide

Env details:-

EBS Version: R12.2.5

AD/TXK Delta Patch level: 10

OS : OEL 7.9

Step 1: Source the Run Edition Environment

Before beginning, source the environment of the currently active run edition:

[appltest@testapp ~]$ . /apdata/erp/EBSapps.env run       E-Business Suite Environment Information   ----------------------------------------   RUN File System           : /apdata/erp/fs2/EBSapps/appl   PATCH File System         : /apdata/erp/fs1/EBSapps/appl   Non-Editioned File System : /apdata/erp/fs_ne       DB Host: testdb.suprajit.com  Service/SID: TEST       Sourcing the RUN File System ...

 

Step 2. Verify Admin Server Status:

[appltest@testapp ~]$ $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh status   You are running adadminsrvctl.sh version 120.10.12020000.10   Enter the WebLogic Admin password: Enter the APPS Schema password:    The AdminServer is not running

 

If not running, start it:

[appltest@testapp ~]$ $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start Enter the WebLogic Admin password: Enter the APPS Schema password: Starting WLS Admin Server...

 

 

 

Step 3. Execute Preclone on Apps Tier:

[appltest@testapp ~]$ cd $INST_TOP/admin/scripts [appltest@testapp scripts]$ perl adpreclone.pl appsTier

 

Step 4: Detach Existing Patch Oracle Homes

Navigate to the OUI Binary Directory:

[appltest@testapp scripts]$  cd $FMW_HOME/oracle_common/oui/bin

 

This step is performed from the RUN file-system which will detach oracle_homes on the PATCH file-system

Replace {oracle_home_path} with the actual paths:

Please note that we are removing ORACLE_HOME registered with patch file system only.

 

./runInstaller -detachhome ORACLE_HOME={oracle_home_path} -silent

 

For example:

[appltest@testapp bin]$ ./runInstaller -detachhome ORACLE_HOME=/apdata/erp/fs1/FMW_Home/Oracle_EBS-app1 -silent   [appltest@testapp bin]$ ./runInstaller -detachhome ORACLE_HOME=/apdata/erp/fs1/FMW_Home/webtier -silent   [appltest@testapp bin]$ ./runInstaller -detachhome ORACLE_HOME=/apdata/erp/fs1/FMW_Home/oracle_common -silent

 

 

Remove the 10.1.2 Oracle Home

[appltest@testapp bin]$ ./runInstaller -removeHome ORACLE_HOME=/apdata/erp/fs1/EBSapps/10.1.2 -silent

 

Step 5: Replicate Run File System to Patch File System

Ensure Run Environment is Down (optional but recommended):

[appltest@testapp bin]$ $ADMIN_SCRIPTS_HOME/adstpall.sh

 

 

Copy directories from RUN to Patch filesystem

[appltest@testapp bin]$ cd $RUN_BASE [appltest@testapp fs2]$ pwd /apdata/erp/fs2 [appltest@testapp fs2]$ ls EBSapps  FMW_Home  inst [appltest@testapp fs2]$ cp -r EBSapps /apdata/erp/fs1/

 

Remove Existing FMW_Home in Patch File System:

[appltest@testapp]$  rm -rf /apdata/erp/fs1/FMW_Home

 

Step 6: Disable ebs_logon Trigger

Connect to the Database:

[oratest@testdb ~]$ sqlplus / as sysdba   SQL> ALTER TRIGGER system.ebs_logon DISABLE;   Trigger altered.

 

Step 7: Configure the Patch File System

Login to application server and open a new termina.

Unset any application environment file

Navigate to Clone Directory:

[appltest@testapp ~]$ cd /apdata/erp/fs1/EBSapps/comn/clone/bin/ [appltest@testapp bin]$ perl adcfgclone.pl appsTier                        Copyright (c) 2002, 2015 Oracle Corporation                         Redwood Shores, California, USA                           Oracle E-Business Suite Rapid Clone                                    Version 12.2                         adcfgclone Version 120.63.12020000.60                   ***********************************************************                 In AD-TXK Delta 7, we recommend you clone the run and patch                 file systems in a single operation using the 'dualfs' option.                 Separate cloning of the run and patch file systems will be deprecated                 ************************************************************   Enter the APPS password :   Enter the Weblogic AdminServer password :   Do you want to add a node (yes/no) [no] :     Running: Context clone...   Log file located at /apdata/erp/fs1/EBSapps/comn/clone/bin/CloneContext_0607140046.log   Target System File Edition type [run] : patch   Enter the full path of Run File System Context file : /apdata/erp/fs2/inst/apps/TEST_testapp/appl/admin/TEST_testapp.xml   Provide the values required for creation of the new APPL_TOP Context file.   Target System Fusion Middleware Home set to /apdata/erp/fs1/FMW_Home   Target System Web Oracle Home set to /apdata/erp/fs1/FMW_Home/webtier   Target System Appl TOP set to /apdata/erp/fs1/EBSapps/appl   Target System COMMON TOP set to /apdata/erp/fs1/EBSapps/comn   Target System Instance Top set to /apdata/erp/fs1/inst/apps/TEST_testapp   Target System Port Pool [0-99] : 21

  

During the prompts:

• Add a Node: no
• Run File System Context File: Provide the absolute path.
• Port Pool: Choose a value different from the run file system (e.g., if run uses 0, patch can use 10).

Step 8: Verify File System Roles

 

[appltest@testapp bin]$ source /apdata/erp/EBSapps.env patch   [appltest@testapp bin]$ echo $FILE_EDITION Patch

 

Step 9: Synchronize File Systems Using fs_clone

[appltest@testapp bin]$ source /apdata/erp/EBSapps.env run   [appltest@testapp scripts]$ adop phase=fs_clone force=yes

 

This step ensures both file systems are in sync.

 

Step 10: Re-enable ebs_logon Trigger

[oratest@testdb admin]$ sqlplus / as sysdba   SQL> ALTER TRIGGER system.ebs_logon enable;

 

Conclusion

Recreating the patch file system in Oracle EBS R12.2 is a meticulous process that ensures the integrity and availability of your application. By following these steps diligently, you can maintain a robust environment ready for online patching and minimal downtime.