Oracle Applications Patching :How to Run hrglobal driver in Oracle EBS 12.2.X Version.

Applying hrglobal driver is needed during an oracle applications upgrade or when the  payroll data is required to be analyzed as per latest code pack.


Below are the steps to apply hrglobal driver in a Oracle EBS environment (12.2.x)


Before applying hrglobal driver download the latest hrglobal patch from My Oracle Support.


Start an Oracle online EBS Patching cycle.


1.adop phase=prepare


2. Apply latest hrglobal patch


adop phase=apply patches=<patchnum>


3. Run Datainstall and hrglobal driver using below commands


ADOP utillity is intelligent enough to switch to Patch Filesystem depending on the ADOP phase being run.
For any Other manual operations, we need to set the environment to point to Patch Filesystem explicitly.


. ./EBSapps.env PATCH


+Run DataInstall


java oracle.apps.per.DataInstall apps appspassword thin test.domain.com:1521:DEV


Select the Required localisations and save the changes.


Example of Data Install Changes Summary is shown below.






          DataInstall – Actions confirmation


Do you really wish to exit and save your changes?


      [Y]      – Yes, save then exit
      [N]      – No, don’t save but exit
      [Return] – To return to the DataInstall Main Menu


Enter your choice (for example Y) : Y




          DataInstall – Actions summary
          —————————–


The following actions will be performed:




Localisation         Product(s)               Leg. Data? Action
——————– ———————— ———- ————-
Global               Human Resources          Installed  Install
United Arab Emirates Human Resources          Installed  Install
United Arab Emirates Payroll                  Installed  Install


Localisation   College Data? Action
————– ————- ————-
United Kingdom
United States


Option                         Data?         Action
—————————— ————- ————-
JIT/Geocode




Legislation                            Action
——————————         ————-
ALL  All Legislations




++Apply hrglobal.drv using below syntax.


adop phase=apply patchtop=$PER_TOP/patch/115 patches=driver:hrglobal.drv workers=8




4. adop phase=finalize


5. adop phase=cutover


6. adop phase=cleanup

Oracle Applications Patching : ADOP Prepare phase failed due to missing information in FND_NODES.

Applying Patches to Oracle EBS and Oracle Database is one of the main activities for an Oracle database administration.We Often get errors during Oracle patching, which could be due to environment issue or a configuration issue or an Oracle Bug.


Checking Patch logfiles and Oracle Patching worker logfiles is very important to identify and troubleshoot the patching error.


Recently, while i am applying patch on a Production environment, Prepare phase in Oracle EBS online patching failed due to below  error


Error Details:Information missing in FND_NODES table for one or more application tier nodes.





=================================================
ADOP (C.Delta.9)
Session ID: 19
Node: prodapp01
Phase: prepare
Log: /applmgr/Oracle/PRODAPP/fs_ne/EBSapps/log/adop/19/20171230_095636/adop.log
===========================================================================


Validating configuration on node: [prodapp01].
    Log: /applmgr/Oracle/PRODAPP/fs_ne/EBSapps/log/adop/19/20171230_095636/prepare/validate/rwerpprodapp01
[ERROR]: Information missing in FND_NODES table for one or more application tier nodes. For details, refer to log file on the relevant node.
[WARNING]: There could be issues while validating the ports used for E-Business Suite instance against ports used in /etc/services. Refer the log file for more details.
[WARNING]: Either some of the required entries in /etc/hosts file might be missing (e.g. localhost or hostname) OR the file /etc/hosts could not be read.
[WARNING]: Found invalid cross references in FS config files.
    [UNEXPECTED]Error occurred running “perl /applmgr/Oracle/PRODAPP/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl  -contextfile=/applmgr/Oracle/PRODAPP/fs2/inst/apps/PRODAPP_prodapp01/appl/admin/PRODAPP_prodapp01.xml -patchctxfile=/applmgr/Oracle/PRODAPP/fs1/inst/apps/PRODAPP_prodapp01/appl/admin/PRODAPP_prodapp01.xml -phase=prepare -logloc=/applmgr/Oracle/PRODAPP/fs_ne/EBSapps/log/adop/19/20171230_095636/prepare/validate/prodapp01 -promptmsg=hide”
    [UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script on prodapp01




[STATEMENT] Please run adopscanlog utility, using the command


“adopscanlog -latest=yes”


to get the list of the log files along with snippet of the error message corresponding to each log file.




adop exiting with status = 1 (Fail)
=================================================




Analysis
The environment on which issue is reported has two middle Tier nodes. Primary node is the Master node and DMZ tier is the slave node.
Due to autoconfig failure on Oracle EBS Slave node, Support_Web  column is not updated in FND_NODES after autoconfig execution.
SUPPORT_WEB column for DMZ node is null in FND_NODES



Solution


1. Bring down Middle Tier Services
2. Run autoconfig on all the Middle Tier nodes
3. Startup the Middle Tier Services
4. Verify that FND_NODES table has correct information
5. Restart adop Prepare Phase