Home » Oracle » Oracle Ebuisness Suite » 10 Things you must know about EBS R12.2

10 Things you must know about EBS R12.2

(1) Adop uses SID_patch service_name to connect to database

(2) Adop Connects to other nodes in a multi-node setup via SSH and applies the patch ( similar to RAC patchings). It is executed by the user on the master node.
It is important to enable the ssh from master node to other nodes

If a node unexpectedly becomes inaccessible via SSH, it will be abandoned by adop, and appropriate further actions taken. Consider a scenario where the adop phase=prepare command is run in a system with ten application tier nodes. The command is successful on nine nodes but fails on the tenth. In such a case, adop will identify the services enabled on nodes 1-9. If they are sufficient for Oracle E-Business Suite to continue to run normally, adop will mark node 10 as abandoned and then proceed with its patching actions. If they are not sufficient, adop will proceed no further.


(3) How to find the Oracle EBS Weblogic Server Admin Port Number and URL

Web Logic Server Admin Port

Method 1:

Open the EBS domain config file in the following location.

$EBS_DOMAIN_HOME/config/config.xml

Then check for Admin Server Port.

Method 2:

Open the application tier context file
$CONTEXT_FILE

Then check the value of variable “s_wls_adminport” for the correct Web Logic Server Admin port number

Web Logic Server Console URL

http://<server name>.<domain name>:<WLS Admin Port>/console

(4) adop phase=fs_clone

This method is useful if the APPL_TOPs have become very unsynchronized (meaning that there would be a large number of delta patches to apply). It is a heavyweight process, taking a backup of the entire current patch APPL_TOP and then cloning the run APPL_TOP to create a new patch APPL_TOP. As this method requires more time and disk space, it should only be used when the state of the patch file system is unknown.

See also  Top Questions about JAVA/JRE in Oracle Apps

The fs_clone phase is run using the following command:

$ adop phase=fs_clone
  • This command must be invoked from the run file system before the next prepare phase is run.
  • Note: The patch file system requires at least 25 GB of free disk space to be available for adop operations, including fs_clone. If there is insufficient free space, the adop operation will fail.
  • If desired, you can change the temporary file system location used by fs_clone, by setting the T2P_JAVA_OPTIONS environment variable to point to a temporary location of your choice:
$ T2P_JAVA_OPTIONS="-Djava.io.tmpdir=/home/temp"
$ export T2P_JAVA_OPTIONS

(5) No maintenance mode is required in R12.2

(6) Important new variable in R12.2

$FILE_EDITIONshows which file edition you are using, run or patch
$RUN_BASEshows the absolute path to run file system
$PATCH_BASEshows the absolute path to the patch file system
$NE_BASEshows the absolute path to the non-edition file system
$APPL_TOP_NEnon-editioned appl_top path. Equivalent to $NE_BASE/EBSapps/appl
$LOG_HOMEShell scripts to control processes associated with the application instance
$ADOP_LOG_HOMEOnline patching Specific Log Directory. Equivalent to $NE_BASE/EBSapps/log/adop
$IAS_ORACLE_HOMEFMW Web Tier Home Directory
$ORACLE_HOME10.1.2 ORACLE_HOME
$CONTEXT_FILEApplication Instance context file location
$EBS_DOMAIN_HOMEEBS Weblogic domain location
$ADMIN_SCRIPTS_HOMEShell scripts to control processes associated with the application instance
$EBS_ORACLE_HOMEOracle E-Business Suite 12.2 FMW Deployment directory
$RW10.1.2 reports directory
$APPS_VERSIONto get the EBS version

(7) How to apply the FMW patches in R12.2

(a) adop phase=apply
(b) Apply the FMW patches
(c) adop phase=finalize
(d) adop phase=cutover
(e) adop phase=cleanup

(8) We have the concepts of STUBS with edition-based redefinition

See also  What is disaster Recovery

What is Stubs
“stub objects” are simply pointers to an actual object definition from an ancestor edition that is still being inherited by the given edition.

(9) R12.2.13 is the Latest version of R12.2 available

(10) About Upgrade
If we are R12.2.X, we can upgrade to any upper version by just simply applying the maintenance pack online using Online Patching
If we are R12.0/R12.1/11i and we plan to upgrade to R12.2, then we will need to first upgrade to R12.2 and then enable the online patching and apply the latest release maintenance pack

Related Articles
Oracle Ebusiness Suite Architecture in R12.2
Admin scripts in R12.2
R12.2 Online Patching cycle Summary
ADOP explained R12.2
40 question you must know about R12.2
How to clone R12.2 environment
Logical view of the data model in R12.2
How to add the manage server in R12.2

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top