Skip to main content

How to reconfigure patch file system in EBS R12.2

How to reconfigure patch file system in EBS R12.2

We had a scenarios where I need to re-create or again configure the patch file system in ebs.

Steps

1. Run adpreclone.pl on run file system

Source run file system.

$ perl adpreclone.pl appsTier

 

2. Detach PATCH homes:

Below Oracle Homes are registered in the inventory which needs to be deregistered:

/u01/app/fs2/FMW_Home/Oracle_EBS-app1

/u01/app/fs2/FMW_Home/webtier

/u01/app/fs2/FMW_Home/oracle_common

 

cd $FMW_HOME/oracle_common/oui/bin

./runInstaller -removeHome ORACLE_HOME=/u01/app/fs2/FMW_Home/Oracle_EBS-app1 -silent


./runInstaller -removeHome ORACLE_HOME=/u01/app/fs2/FMW_Home/webtier -silent


./runInstaller -removeHome ORACLE_HOME=/u01/app/fs2/FMW_Home/oracle_common -silent

 
 

3. Run adcfgclone.pl on run file system.

 
cd $COMMON_TOP/clone/bin/
[applmgr@funebs bin]$ perl adcfgclone.pl appsTier
Copyright (c) 2002, 2015 Oracle Corporation

Redwood Shores, California, USA

Oracle E-Business Suite Rapid Clone

Version 12.2


***********************************************************

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] : no

Running: Context clone…

Log file located at /u01/app/fs1/EBSapps/comn/clone/bin/CloneContext_0618160140.log

Target System File Edition type [run] : patch

Enter the full path of Run File System Context file : /u01/app/fs1/inst/apps/test_funebs/appl/admin/test_funebs.xml

Provide the values required for creation of the new APPL_TOP Context file.

Target System Fusion Middleware Home set to /u01/app/fs2/FMW_Home

Target System Web Oracle Home set to /u01/app/fs2/FMW_Home/webtier

Target System Appl TOP set to /u01/app/fs2/EBSapps/appl

Target System COMMON TOP set to /u01/app/fs2/EBSapps/comn


A directory with this name already exists and is not empty.

Do you want to continue (y/n) : y

Target System Instance Top set to /u01/app/fs2/inst/apps/test_funebs

Target System Port Pool [0-99] : 11

Checking the port pool 11

done: Port Pool 11 is free

Report file located at /u01/app/fs2/inst/apps/test_funebs/temp/portpool.lst

The new APPL_TOP context file has been created :

/u01/app/fs2/inst/apps/test_funebs/appl/admin/test_funebs.xml


 

Once complete the patch file system configuration.

 

4. Verify as below.

In the new terminal – source PATCH file-system

$ EBSapps.env patch

$ echo $FILE_EDITION

 

Run FS_CLONE

# Run Admin server MUST be up for this step

$ EBSapps.env run

$ adop phase=fs_clone force=yes







Please do like and subscribe to my youtube channel: https://www.youtube.com/@foalabs If you like this post please follow,share and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...