How to Applied R12.2 Pataches

As we are knowing that applying patch in ORACLE EBS R12.2 is different than R12.1.

From R12.2.0 onward oracle has introduced online patching functionality called ADOP.

Oracle EBS 12.2 introduces Online Patching, a new feature that greatly reduces the downtime that was needed in previous releases for application of Release Update Packs (RUPs), Critical Patch Updates (CPUs), and other patches and bug fixes of various kinds.

Note: The classic patching model is designed to minimize downtime by running as fast as possible, using whatever resources are needed. In contrast, the online patching model is designed to minimize downtime by allowing patching operations to be performed while users remain on the system.

There are below 5 Phases of ADOP(online patching):

1) PREPARE
2) APPLY
3) FINALIZE
4) CUTOVER
5) CLEANUP

Steps:-

1. Download the patch and unzip on patch_top.

2. Must go through Readme.html or readme.txt.

3. Prepare the system for patching

     a.  we can run the .env file . or the adop utility sets its own environment.
     b. Then run the below command for prepare the System for patching:

$ adop phase=prepare

4. Wait for the prepare phase to be complete.
Please check the status from below points:

$ adop -status 

Enter the APPS username: apps
Enter the APPS password:

5. After completion Prepare phase, go to next phase called Apply phase:

$adop phase=apply patches=1234567

Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials...


6 . After completion of apply phase, goto next phase called Finalize phase:
i.e like Ready the instance for cutover

$ adop phase=finalize

Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials...


7. After completion of Finalize phase, goto next phase called Cutover:

$ adop phase=cutover

Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials...

Note: Keep checking Status after every Phases.

8. After completion of Cutover phase, run next Cleanup Phase
We can do this step after instance is released to Customer.

$adop phase=cleanup

Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:


Note:
If there are some reason either the prepare or apply phase failed or any problems then you can abort this patching cycle.

$adop phase=abort

But always remember, after running abort, you must always run a full cleanup as:

$adop phase=cleanup cleanup_mode=full

So, this will remove all columns that were added by the patches but are no longer needed because of the abort. 

How to Installation TFA(TRACE FILE ANALYZER) COLLECTOR in Oracle database step by step

TFA(Trace File Analyzer) Collector 

TFA Collector - TFA with Database Support Tools Bundle (Doc ID 1513912.1)

As described on MOS, Trace File Analyzer Collector (TFA) is a diagnostic collection utility to simplify diagnostic data collection on Oracle Clusterware/Grid Infrastructure, RAC and Single Instance Database systems.
TFA is similar to the diagcollection utility packaged with Oracle Clusterware in that it collects and packages diagnostic data - however - TFA is MUCH more powerful than diagcollection with its ability to centralize and automate the collection of diagnostic information

My Environment:

oracle linux 6.5

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

1.) Download:

On MOS: 1513912.1
you can download the version below, is the lastest version (04-2016):

TFA 18.2.1.0.0, file: TFA-LINUX_v18.2.1.zip

On this version as reported on MOS:

    New TFA tools - summary, events, changes, ps, pstack and param all with cluster support
    New dbglevel tool to help when setting CRS trace levels for multiple modules across nodes
    Cluster support for existing TFA tools alertsummary, grep and tail
    Version updates to Support Tools - DARDA, SQLT and ORAchk
    Support for diagnostics collection from ODA Dom0
    Support for Dom0 diagnostic collections on Exadata
    Critical Bug Fixes

2.) Preparing the Installation:

As root copy the ZIP file to a directory on Server:
after copy zip file to server:

unzip TFA-LINUX_v18.2.1.zip

[root@qb Trace_File_Analyser]# ls -ltr
total 87440
-rw-r--r-- 1 root root   583593 Jul  27 15:32 TFACollectorDocV121270.pdf
-r-xr-xr-x 1 root root 44414287 Jul  27 15:34 installTFA-LINUX
-rw-r--r-- 1 root root 44534701 Jul  27 04:07 TFA-LINUX_v18.2.1.zip
-rw-r--r-- 1 root root 44534701 Jul  27 04:07 README

Oracle recommends install under $ORACLE_BASE

Note: i will update the bash_profile (root) with the variable below:

export ORACLE_BASE=/oracle

3.) Install

variables:

JAVA_HOME=/oracle/grid/jdk
ORACLE_BASE=/oracle

./installTFA-LINUX $ORACLE_BASE -javahome $JAVA_HOME

On my case the option:
[root@qb Trace_File_Analyser]$ ./installTFA-LINUX
TFA Installation Log will be written to File : /tmp/tfa_install_12114_2018_07_27-16_58_53.log


Starting TFA installation

TFA Version: 182100 Build Date: 201805291110

Enter a location for installing TFA (/tfa will be appended if not supplied) [/tmp/Trace_File_Analyser/tfa]:
/u02/ora11g/app/ora11g/product/11.2.0/dbhome_1

Running Auto Setup for TFA as user ora11g...

Would you like to do a [L]ocal only or [C]lusterwide installation ? [L|l|C|c] [C] : L
Installing TFA now...

Discovering Nodes and Oracle resources

Starting Discovery...


No Grid Infrastructure Discovered on this system . . . . .

qb
Searching for running databases...
1. DEV
1. qborcl11g


Searching out ORACLE_HOME for selected databases...


Getting Oracle Inventory...

ORACLE INVENTORY: /u02/ora11g/oraInventory


Discovery Complete...



TFA Will be Installed on qb...

TFA will scan the following Directories
++++++++++++++++++++++++++++++++++++++++++++

.------------------------------------------------------------------------.
|                                   qb                                   |
+-------------------------------------------------------------+----------+
| Trace Directory                                             | Resource |
+-------------------------------------------------------------+----------+
| /u02/ora11g/app/ora11g/cfgtoollogs                          | CFGTOOLS |
| /u02/ora11g/app/ora11g/diag/rdbms/qborcl11g/qborcl11/cdump  | RDBMS    |
| /u02/ora11g/app/ora11g/diag/rdbms/qborcl11g/qborcl11/trace  | RDBMS    |
| /u02/ora11g/app/ora11g/diag/rdbms/qborcl11g/qborcl11g/cdump | RDBMS    |
| /u02/ora11g/app/ora11g/diag/rdbms/qborcl11g/qborcl11g/trace | RDBMS    |
| /u02/ora11g/app/ora11g/diag/tnslsnr                         | TNS      |
| /u02/ora11g/app/ora11g/diag/tnslsnr/qb/listener/cdump       | TNS      |
| /u02/ora11g/app/ora11g/diag/tnslsnr/qb/listener/trace       | TNS      |
| /u02/ora11g/app/ora11g/product/11.2.0/dbhome_1/cfgtoollogs  | CFGTOOLS |
| /u02/ora11g/app/ora11g/product/11.2.0/dbhome_1/install      | INSTALL  |
| /u02/ora11g/oraInventory/ContentsXML                        | INSTALL  |
| /u02/ora11g/oraInventory/logs                               | INSTALL  |
'-------------------------------------------------------------+----------'


Installing TFA on qb:
HOST: qb TFA_HOME: /u02/ora11g/app/ora11g/product/11.2.0/dbhome_1/tfa/qb/tfa_home

.--------------------------------------------------------------------------.
| Host | Status of TFA | PID   | Port  | Version    | Build ID             |
+------+---------------+-------+-------+------------+----------------------+
| qb   | RUNNING       | 12713 | 25897 | 18.2.1.0.0 | 18210020180529111033 |
'------+---------------+-------+-------+------------+----------------------'

Running Inventory in All Nodes...

Summary of TFA Installation:
.--------------------------------------------------------------------------------------.
|                                          qb                                          |
+---------------------+----------------------------------------------------------------+
| Parameter           | Value                                                          |
+---------------------+----------------------------------------------------------------+
| Install location    | /u02/ora11g/app/ora11g/product/11.2.0/dbhome_1/tfa/qb/tfa_home |
| Repository location | /u02/ora11g/app/ora11g/product/11.2.0/dbhome_1/tfa/repository  |
| Repository usage    | 0 MB out of 10240 MB                                           |
'---------------------+----------------------------------------------------------------'

TFA is successfully installed...

Usage : /u02/ora11g/app/ora11g/product/11.2.0/dbhome_1/tfa/bin/tfactl <command> [options]
    commands:diagcollect|collection|analyze|ips|run|start|stop|enable|disable|status|print|access|purge|directory|host|receiver|set|toolstatus|uninstall|diagnosetfa|syncnodes|setupmos|upload|availability|rest
For detailed help on each command use:
  /u02/ora11g/app/ora11g/product/11.2.0/dbhome_1/tfa/bin/tfactl <command> -help


[rootg@qb Trace_File_Analyser]$

How to Clone the Oracle Database using Cold Backup

STEP 1:Create a control file from source instance env

SQL > alter database backup controlfile to trace;

Control File Script:

STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "qbay11g" NORESETLOGS NOARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 2
    MAXDATAFILES 240
    MAXINSTANCES 1
    MAXLOGHISTORY 113
LOGFILE
  GROUP 1 '/u03/oracle11g/oracle11g/oradata/qbay11g/redo01.log'  SIZE 50M,
  GROUP 2 '/u03/oracle11g/oracle11g/oradata/qbay11g/redo02.log'  SIZE 50M,
  GROUP 3 '/u03/oracle11g/oracle11g/oradata/qbay11g/redo03.log'  SIZE 50M
DATAFILE
  '/u03/oracle11g/oracle11g/oradata/qbay11g/system01.dbf',
  '/u03/oracle11g/oracle11g/oradata/qbay11g/undotbs01.dbf',
  '/u03/oracle11g/oracle11g/oradata/qbay11g/sysaux01.dbf',
  '/u03/oracle11g/oracle11g/oradata/qbay11g/users01.dbf'
;
# Recovery is required if any of the datafiles are restored
# backups, or if the last shutdown was not normal or immediate.
RECOVER DATABASE
# Database can now be opened normally.
ALTER DATABASE OPEN;

STEP 2: Shutdown the Source database

SQL>shutdown immediate;

STEP 3: Copy all data files into the new directories on the new server.

You may change the file names if you want, but you must edit the controlfile to reflect the new data files names on the new server

Example:

scp -r  /u01/oracle/oradata  oracle@targetdatabse.com:/u01/oracle/oradata

STEP 4: Copy and Edit the Control file – Using the output syntax from STEP 1, modify the controlfile creation script by changing the following:

Old:

CREATE CONTROLFILE REUSE DATABASE "qbay11g" NORESETLOGS

New:

CREATE CONTROLFILE SET DATABASE "qborcl" RESETLOGS

STEP 5: Remove the "recover database" and "alter database open" syntax

# Recovery is required if any of the datafiles are restored

# backups, or if the last shutdown was not normal or immediate.

RECOVER DATABASE

# Database can now be opened normally.

ALTER DATABASE OPEN;

STEP 6: Re-names of the data files names that have changed

Save as db_create_controlfile.sql.

Old:

DATAFILE

  '/u03/oracle11g/oracle11g/oradata/qbay11g/system01.dbf',

  '/u03/oracle11g/oracle11g/oradata/qbay11g/undotbs01.dbf',

  '/u03/oracle11g/oracle11g/oradata/qbay11g/sysaux01.dbf',

  '/u03/oracle11g/oracle11g/oradata/qbay11g/users01.dbf'

New:

DATAFILE

  '/u02/oracle11g/oracle11g/oradata/qborcl/system01.dbf',

  '/u02/oracle11g/oracle11g/oradata/qborcl/undotbs01.dbf',

  '/u02/oracle11g/oracle11g/oradata/qborcl/sysaux01.dbf',

  '/u02/oracle11g/oracle11g/oradata/qborcl/users01.dbf'

STEP 7: Create the bdump, udump and cdump directories

cd $DBA/admin

mkdir newlsq

cd newlsq

mkdir bdump

mkdir udump

mkdir cdump

mkdir pfile

STEP 8: Copy-over the old init.ora file

rcp $DBA/admin/source/pfile/*.ora targethost:/u01/oracle/admin/target/pfile

STEP 9: Start the new database

SQL> startup mount pfile=initqborcl.ora;

SQL>@db_create_controlfile.sql

STEP 10: Open the new Cloned database

SQL> alter database open resetlogs;

                    ****ALL THE BEST****

Oracle EBS R12.2.7 Full Installation Step by Step

High level Steps Involved to do the R12.2.7 upgrade steps are:
1.Checked Pre requestions for R12.2.7
2.Run ETCC in both database tier and Application tier to get the list of required patches and apply.
3.Upgrade to  AD and TXK Delta 10
4.Apply the R12.2.7 upgrade patch
5.FS_CLONE for filesystem cloning
6.Apply the Help patch.

1.Checked Pre requestions for R12.2.7

In Release 12.2.0 and higher, patching is performed by running the new adop (AD Online Patching) utility. You must use adop instead of the adpatch utility that was provided in previous releases

Download and unzip all the patches to the default Patch Top location for R12.2 ($APPL_TOP_NE/../patch)

If your Oracle E-Business Suite instance is currently on Database version 11.2.0.3, then you should now upgrade to Database 11.2.0.4 or 12.1.0.2 before proceeding with next steps, by following process documented in the oracle


Note: Database desupport schedules have important operational and planning implications for Oracle E-Business Suite environments. Oracle recommends that you review the following document that details the latest database support policies and desupport schedules: My Oracle Support Knowledge Document 742060.1, Release Schedule of Current Database Patch Sets

2.Run ETCC in both database tier and Application tier to get the list of required patches and apply.

EBS Technology Codelevel Checker (ETCC)

ETCC can be downloaded via Patch 17537119 from My Oracle Support

Download the Patch 17537119
p17537119_R12_GENERIC.zip

Unzip p17537119_R12_GENERIC.zip

The two scripts that make up ETCC are:

checkDBpatch.sh

This is the Database EBS Technology Codelevel Checker (DB-ETCC), which determines if all the needed bugfixes exist in the specified database ORACLE_HOME.

./checkDBpatch.sh

checkMTpatch.sh 

 This is the Application Tier EBS Technology Codelevel Checker (MT-ETCC), which determines if all the needed bugfixes exist in the application tier file system.

./checkMTpatch.sh


Note: This patch verifies the missing bugfixes which is not applied for db and middle tiers

For DB Node :

copy all files in the patch directory
cd $PATCH_TOP/17537119

./checkDBpatch.sh

Apply the patches using opatch


Example:

export PATH=$PATH:$ORACLE_HOME/OPatch

To Check the patch:
opatch lsinventory | grep 19908836

cd 18793246

opatch apply

For APP Node :
./checkMTpatch.sh


=================================
PATCH RECOMMENDATION SUMMARY
=================================

Oracle Forms and Reports 10.1.2.3.0
---------------------------------------------
  Patch 25768948
    - Filename: p25768948_101232_LINUX.zip


Oracle Fusion Middleware (FMW) - oracle_common 11.1.1.9.0
------------------------------------------------------------------------------
  Patch 17428617
    - Filename: p17428617_111190_Generic.zip

  Patch 24606362
    - Filename: p24606362_111190_Generic.zip

  Patch 24843064
    - Filename: p24843064_111190_Generic.zip

Oracle WebLogic Server (WLS) 10.3.6.0.12
---------------------------------------------------------
  Patch 23743997 [SU Patch [K25M]: WLS PSU 10.3.0.6.161018]
    - Filename: p23743997_1036_Generic.zip

  Patch 25333306 [SU Patch [SUY4]]
    - Filename: p25333306_1036_Generic.zip


Apply the required patches and rerun this script.

+--------------------------------------------------------------------------------------------------------+
A consolidated zip file with the required application tier patches is
available on My Oracle Support via:

  Patch 26328262
    - EBS RELEASE 12.2 CONSOLIDATED FMW FIXES FOR JUL 2017

+--------------------------------------------------------------------------------------------------------+
[WARNING]  Patch 23743997 [SU Patch [K25M]: WLS PSU 10.3.0.6.161018] is missing.
This is the recommended minimum WLS patch set.
You should install it now, and then rerun this script to check for any
further fixes available.
+--------------------------------------------------------------------------------------------------------+

For APPS Tier Node :

Connecting to database.
Database connection successful.


Oracle Forms and Reports
-------------------------

1.unzip Patch file
2.set Oracle home
  export ORACLE_HOME=/u02/oracle/TST/fs1/EBSapps/10.1.2.
3.set path
  export PATH=$ORACLE_HOME/OPatch:$PATH
4.opatch lsinventory|grep 25768948
5.cd 25768948
6.opatch apply


Oracle Fusion Middleware (FMW) - oracle_common
------------------------------------------------

1.unzip Patch file
2.set Oracle home
  export ORACLE_HOME=/u02/oracle/TST/fs1/FMW_Home/oracle_common
3.set path
  export PATH=$ORACLE_HOME/OPatch:$PATH
4.opatch lsinventory|grep 17428617
5.cd 17428617
6.cd oui
7.opatch apply

Oracle WebLogic Server (WLS)
------------------------------------
1. copy file 23743997 to /u02/oracle/TST/fs1/FMW_Home/util/bsu/cache_dir
2. unzip file (23743997)
3. check the .jar file
    ls -ltr *.jar
4. cd  /u02/oracle/TST/fs1/FMW_Home/util/bsu

5. check the Display
    echo$DISPLAY
    echo$DISPLAY=:1:0

6 To apply the Patch
   . ./bsu.sh -install -patch_download_dir=/u01/oracle/CRP/fs1/FMW_Home/utils/bsu/
   cache_dir -patchlist=EJUW - prod_dir=/u01/oracle/CRP/fs1/FMW_Home/wlserver_10.3

7.  To apply patches, first you have to apply patch number 23743997 but you may have conflict warning with the previous patches which has older PSU patches because 23743997 patch number is PSU 10.3.6.0.12 patch

we removed the below patches using following commands
 Delete the files - YSAP,BLTC,1LRI,VKXF,2GYW,CWGT,FCX7
   ./bsu.sh -remove -patchlist=Y5AP -prod_dir=/u01/oracle/CRP/fs1/FMW_Home/wlserver_10.3 –verbose
   ./bsu.sh -remove -patchlist=BLTC -prod_dir=/u01/oracle/CRP/fs1/FMW_Home/wlserver_10.3 –verbose
   ./bsu.sh -remove -patchlist=1LRI -prod_dir=/u01/oracle/CRP/fs1/FMW_Home/wlserver_10.3 –verbose
   ./bsu.sh -remove -patchlist=VKXF -prod_dir=/u01/oracle/CRP/fs1/FMW_Home/wlserver_10.3 –verbose
   ./bsu.sh -remove -patchlist=2GYW -prod_dir=/u01/oracle/CRP/fs1/FMW_Home/wlserver_10.3 –verbose
   ./bsu.sh -remove -patchlist=CWGT -prod_dir=/u01/oracle/CRP/fs1/FMW_Home/wlserver_10.3 –verbose
   ./bsu.sh -remove -patchlist=FCX7 -prod_dir=/u01/oracle/CRP/fs1/FMW_Home/wlserver_10.3 –verbose

8. Once again apply
  ./bsu.sh -install -patch_download_dir=/u02/oracle/TST/fs1/FMW_Home/utils/bsu/cache_dir - patchlist=EJUW -prod_dir=/u02/oracle/TST/fs1/FMW_Home/wlserver_10.3

9. Run ETCC again to get the patch list

    24608998 [QMJP]
    13729611 [Z9PC]
    17319481 [9KCT]
    19259028 [KRDE]
    25804598 [EQDE]

9. Download the above patch list

10.Unzip patches.

11.To install the the patches using following commands

    bsu.sh -install -patch_download_dir=/u02/oracle/TST/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=QMJP -prod_dir=/u02/oracle/TST/fs1/FMW_Home/wlserver_10.3
    bsu.sh -install -patch_download_dir=/u02/oracle/TST/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=Z9PC -prod_dir=/u02/oracle/TST/fs1/FMW_Home/wlserver_10.3
    bsu.sh -install -patch_download_dir=/u02/oracle/TST/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=9KCT -prod_dir=/u02/oracle/TST/fs1/FMW_Home/wlserver_10.3
    bsu.sh -install -patch_download_dir=/u02/oracle/TST/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=KRDE -prod_dir=/u02/oracle/TST/fs1/FMW_Home/wlserver_10.3
    bsu.sh -install -patch_download_dir=/u02/oracle/TST/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=EQDE -prod_dir=/u02/oracle/TST/fs1/FMW_Home/wlserver_10.3


12. To check  the MTpatchlist again run the following

      ./checkMTpatch.sh

   Now you should get the message as "All required patches are present"

Set Database Parameter (Conditional) 

Oracle Database 12c Release 1 uses cost based optimization. If you are using Oracle Database 12.1.0.2, the following optimizer parameter should always be set to 'false'. This setting should be completed before proceeding with the next steps and should not be changed thereafter.

[appltst@qb]$ #optimizer_adaptive_features=false

You can verify the parameter was set correctly by running the following command, which should return the value FALSE:
SQL>show parameter optimizer_adaptive_features

3.Upgrade to  AD and TXK Delta 10

Note: This step is applicable only for new installation customers and customers upgrading from Oracle E-Business Suite Release 12.2.2 to Release 12.2.7

If you haven't already applied Consolidated Seed Table Upgrade Patch 17204589:12.2.0, then you must first apply Patch 17204589:12.2.0 on the run file system.

Note: If you have upgraded to Release 12.2.0 using Consolidated Upgrade Patch 24690520:12.2.0 (CUP8) or Patch 22742071:12.2.0 (CUP7) or
Patch 19796566:12.2.0 (CUP6) or Patch 18007406:12.2.0 (CUP5) or Patch 17197281:12.2.0 (CUP4), then you can skip this step.

1. Stop all application tier services on the run file system.

sh $ADMIN_SCRIPTS_HOME/adstpall.sh


2. Start up only the Oracle Weblogic Admin Server on the run file system

$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

3. Apply the consolidated seed table upgrade Patch 17204589:12.2.0 on the run file system using adop hotpatch mode.
$ adop phase=apply patches=17204589 hotpatch=yes

Note: If the Release 12.2.0 Vision or PROD instance (New Installation) was created using startCD 12.2.0.51 (Patch 22066363), you must apply Consolidated Seed Table Upgrade Patch 17204589:12.2.0 by merging with Patch 21900871:12.2.0 on the run file system using adop hotpatch mode.
 $ adop phase=apply patches=17204589,21900871 merge=yes hotpatch=yes


4. Start up all application tier services.

$ sh $ADMIN_SCRIPTS_HOME/adstrtal.sh


Section 6: Apply the Latest AD and TXK Delta Release Update Packs

Note: Follow this Oracle Document 1617461.1


Download and unzip the following patches:
Patch 25820806 (R12.AD.C.Delta.10)
Patch 25828573 (R12.TXK.C.Delta.10)
Patch 26720905:R12.AD.C
Patch 19259764:R12.FND.C.

All Downloaded files are moved to /u01/oracle/CRP/fs_ne/EBSapps/Patch
Unzip the patch files.
online patches apply

$ adop phase=prepare
$ adop phase=apply patches=25820806,26720905 merge=yes
$ adop phase=apply patches=25828573
$ adop phase=apply patches=19259764
$ . <EBS_ROOT>/EBSapps.env run
$ adop phase=finalize
$ adop phase=cutover
$ . <EBS_ROOT>/EBSapps.env run
$ adop phase=cleanup
$ adop phase=fs_clone

Critical AD Patches

Patch 24591000:R12.AD.C
Patch 26482811:R12.AD.C

Critical TXK Patches

Patch 26400116:R12.TXK.C
Patch 26720231:R12.TXK.C
Patch 25994411:R12.TXK.C

online patches apply

$ adop phase=prepare
$ adop phase=apply patches=24591000
$ adop phase=apply patches=26482811
$ adop phase=apply patches=26400116
$ adop phase=apply patches=26720231
$ adop phase=apply patches=25994411
$ . <EBS_ROOT>/EBSapps.env run
$ adop phase=finalize
$ adop phase=cutover
$ . <EBS_ROOT>/EBSapps.env run
$ adop phase=cleanup
$ adop phase=fs_clone

4.Apply the R12.2.7 upgrade patch

1. Source the run edition applications environment

UNIX:
$ . <INSTALL_BASE>/EBSapps.env run

2. Start an online patching cycle.
$ adop phase=prepare

3. Apply Oracle E-Business Suite Release 12.2.7 Patch 24690690. UNIX:
$ adop phase=apply patches=24690690

4. Complete the online patching cycle by running the following commands in the order shown.

 UNIX:
$ adop phase=finalize 
$ adop phase=cutover 
$ . <INSTALL_BASE>/EBSapps.env run 
$ adop phase=cleanup

5.FS_CLONE for filesystem cloning

Synchronize file systems Synchronize the file systems using the command shown below.
This action will copy the new run edition code and configuration to the other file system,
to help the next online patching cycle complete faster.


$ adop phase=fs_clone

6.Post-Update Steps

Note: If you are upgrading from Release 11i, 12.0.x or 12.1.x to Release 12.2.7, then you must continue with 12.2.0 post upgrade steps mentioned in the Upgrade guides before performing the below steps

$ adop phase=apply patches=24690800 hotpatch=yes

Health checking application

http://<hostname>:port/OA_HTML/OA.jsp


**All the Best**