DataInstall/HRGLOBAL Technical considerations for EBS Release 12.2
1. Start an online patching cycle
Source the run edi􀆟on environment file: Example: UNIX: $RUN_BASE/EBSapps/appl/APPS$CONTEXT_NAME.env
$ adop phase=prepare
2. Run DataInstall
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
3. 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.
12.2 SPECIFIC: The driver will be applied via the adop patching 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.
4. Complete the online patching cycle by running the following commands in the order shown:
a. $ adop phase=finalize
b. $ adop phase=cutover
c. $ adop phase=cleanup
Reference:
Doc ID 1469456.1
2. Run DataInstall
ReplyDeleteHere sid=testdb NOT USE testdb_patch
Why? since the database install will connect to your patch edition of the database FIRST is you have patch cycle enabled.
3. Apply hrglobal.drv
$PER_TOP/patch/115/driver/hrglobal.drv
where $PER_TOP corresponds to the patch file system
Why? You will think after patch cycle evoked, the hrglobal.drv will be in-sync between Run and Patch. However, you could apply pre-required patches before hrglobal.drv. That it why Oracle $PER_TOP corresponds to the patch file system.
Oracle Doc as usual, not explain too much of why. You will be confused for just reading the doc and try to reasoning WHY THE HECK THAT sid=testdb on 2. and WHY THE HECK ASK YOU TO POINT TO patch system for $PER_TOP.