Important stuff on R12.2
- Adop uses SID_patch service_name to connect to database
2) Adop Connects to other nodes in multinodes setup via ssh and applies the patch ( similar to RAC patchings).It is executed by user on 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 the 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 Oracle EBS Weblogic Server Admin Port Number and URL
Web Logic Server Admin Port
Open the EBS domain config file in following location.
Then check for Admin Server Port.
Open the application tier context file
Then check the value of variable “s_wls_adminport” in the 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.
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:
$ export T2P_JAVA_OPTIONS
5) No maintenance mode is required in R12.2
6) Important new variable in R12.2
|$FILE_EDITION||shows which file edition you are using, run or patch|
|$RUN_BASE||shows absolute path to run file system|
|$PATCH_BASE||shows absolute path to patch file system|
|$NE_BASE||shows absolute path to non-edition file system|
|$APPL_TOP_NE||non-editioned appl_top path. Equivalent to $NE_BASE/EBSapps/appl|
|$LOG_HOME||Application Instance Specific Log Directory|
|$ADOP_LOG_HOME||Online patching Specific Log Directory. Equivalent to $NE_BASE/EBSapps/log/adop|
|$IAS_ORACLE_HOME||FMW Web Tier Home Directory|
|$CONTEXT_FILE||Source for information populating template files (autoconfig)|
|$EBS_DOMAIN_HOME||WLS Deployment of Oracle E-Business Suite 12.2 Domain (instance specific|
|$ADMIN_SCRIPTS_HOME||Shell scripts to control processes associated to the Applications Instance|
|$EBS_ORACLE_HOME||Oracle E-Business Suite 12.2 FMW Deployment directory|
|$RW||10.1.2 reports directory|
|$APPS_VERSION||to 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