DataInstall and HRGLOBAL Application: 12.2 Specifics

Apply hrglobal.drv
This step comprises 4  sub-steps:
a) Start an online patching cycle
Source the run edition environment file: Example: UNIX: $RUN_BASE/EBSapps/appl/APPS$CONTEXT_NAME.env

$ adop phase=prepare

b) Run DataInstall from PATCH edition
The command line DataInstall java utility should be run on the tier which has the $APPL_TOP available.
It will perform view creation actions against the database pertaining to the options selected.
For multi-node/RAC setups, DataInstall need only to be run on the primary node.


Run the DataInstall java utility in order to select the legislations you want to apply as follows:
java oracle.apps.per.DataInstall <un> <pw> thin <host:port: sid >
where
< un > is the username of the main apps account
<pw> is the password for this account
<host:port: sid > represents the database connection information

For example: java oracle.apps.per.DataInstall apps apps thin dbsvr1:1521:testdb
12.2 SPECIFIC: For an Online patch enabled instance, DataInstall will only be runnable against the Patch Edition (Environment is prepared using “adop phase=prepare”).
In order to retain the same command line usage from previous codelines, if the connect information passed to the DataInstall utility points to the Run Edition, then DataInstall will internally switch to operate against the Patch Edition.
Aside from this scenario, or for environments that are not Online patch enabled, DataInstall will operate exactly as before.
RUP Upgrade best practice:
On upgrade to a newer RUP, it is advised to apply all live localisations and Core (even if no new prereqs are listed).
For customers running non supported localisations, they should install just Core on RUP upgrade

Usage of DataInstall is fairly straightforward, basically select/deselect legislations to install using the index number of the legislation shown in the list in menu 1 followed by I for install or C for clear;
e.g. In menu 1, to install Global choose 1I, to cancel a selected operation, choose 1C etc. Menu 4 to choose to save your changes when you are OK with them.

c) Apply hrglobal.drv

The driver is located at $PER_TOP/patch/115/driver/hrglobal.drv and should be run on the tier which has the $APPL_TOP available.
In most cases this will be the Apps tier.
hrglobal.drv is a pure “database, d type” driver so the actions in the driver apply only to the database.
As such, for RAC/multi-node setups, it is only required to run the hrglobal.drv on one node.
Be mindful to only run the driver located in the directory $PER_TOP/patch/115/driver
hrglobal.drv driver should be applied as per a normal patch using the adop utility.

12.2 SPECIFIC: The driver will be applied via the adop patcing utility, as opposed to adpatch which was used prior to 12.2.

Care must be taken when applying hrglobal.drv via adop that the following parameters are passed with the adop command line:

options=nocopyportion,nogenerateportion,forceapply

Example: adop phase=apply patchtop=$PER_TOP/patch/115 patches=driver:hrglobal.drv options=nocopyportion,nogenerateportion,forceapply
where $PER_TOP corresponds to the patch file system

These options are mandatory in order to
a) avoid adop trying to sync the file system when applying a patch (in this case the hrglobal.drv file) that contains database operations only and
b) ensure that adop will not consider during an upgrade to have been installed previously and proceed with the current request.
Please also ensure the forceapply parameter is at the end of the options list.

Note:

  • adop apply phase by default runs in autoskip mode, meaning that if there is failure, it will be skipped and the failed file will be mentioned in the autoskip.log
  • users wont see the failures on the screen where the adop command is running
  • users need to review the autoskip.log file after the completion of hrglobal to find any failed files which are skipped and take appropriate action

Once completed and no issues are reported in the autoskip.log file, you have successfully installed your legislative HRMS data.

d) Complete the online patching cycle by running the following commands in the order shown:

1. $ adop phase=finalize
2. $ adop phase=cutover
3. $ adop phase=cleanup