Monthly Archives: July 2014

R12.2 ERROR Exit Code 255

when attempting to run perl appsTier, the following error occurs:


Log file located at /local/FDEV/fs2/inst/apps/FDEV_lapdev01/admin/log/clone/ApplyAppsTier_05301531.log
– 50% completed
ERROR while running Apply…
Fri May 30 17:37:39 2014
ERROR: Failed to execute /fs02/app/FDEV/apps/fs2/EBSapps/comn/clone/bin/



The admin server logs are located under:
$EBS_DOMAIN_HOME/servers/AdminServer/logs directory /var/tmp/.ovdlock.tmp (Permission denied)
Caused By: JPS-02592: Failed to push ldap config data to libOvd for service instance “idstore.ldap” in JPS context “default”, cause: /var/tmp/.ovdlock.tmp (Permission denied)

This is caused by the file “/var/tmp/.ovdlock.tmp” having been created by another test iteration by a different UNIX user.
The current clone cannot succeed because the file cannot be over-written.


1. Rename or delete the file:
$ mv /var/tmp/.ovdlock.tmp /var/tmp/.ovdlock.tmp.bak

2. Restart the clone command:
$ perl appsTier


Thank You !!



During the R12.2 cloning process adcfgclone fails with below error message:


Below Oracle Homes are already registered in the global inventory:


Make sure that the above Oracle Homes are unregistered from the global inventory. we should always clean the oraInventory directory by using the following commands.

cd $ORACLE_HOME/oui/bin  (/u01/oracle/R122/fs1/EBSapps/10.1.2/oui/bin)

./runInstaller -silent -deinstall REMOVE_HOMES={“/u01/oracle/R122/fs1/FMW_Home/Oracle_EBS-app1”}
./runInstaller -silent -deinstall REMOVE_HOMES={“/u01/oracle/R122/fs1/FMW_Home/oracle_common”}
./runInstaller -silent -deinstall REMOVE_HOMES={“/u01/oracle/R122/fs1/FMW_Home/webtier”}

Then restart the appsTier


Thank You !!


It is advisable to review the relevant log files after any patching operation. The adop log files are located on the non-editioned file system (fs_ne), under:


For example, if s_ne_base was /u01/R122_EBS/fs_ne, the session ID was 15, and the <CONTEXT_NAME> was patch01_testsys, the path to the adop log files from 9th June 2013 would resemble this:



Thank You !!

ADOP – EBS R12.2

ADOP – Applications DBA Online Patching Tool 

ADOP: Oracle E-Business R12.2 introduced new patching mechanism that allow the application of patches while your environment is up and running which is called as Online patch.

The online patching cycle consists of a number of phases:

1) Prepare – Prepare the instance for patch application.
2) Apply – Apply patches (to the patch edition).
3) Finalize – Ready the instance for cutover.
4) Cutover – Make the patch edition the new run edition.
5) Cleanup – Drop obsolete objects and data from old editions.

Steps to apply patch on R12.2 using ADOP:

1) Download and unzip the patch, Before proceeding with patching activity please go through the patch radme.
2) Source the environment.
$ source <run APPL_TOP path>/APPS<CONTEXT_NAME>.env
3) Check the staus of adop using below command.
$ adop -status

4) Prepare the system for patching.
$ adop phase=prepare

5) Apply the patch to patch edition.
$ adop phase=apply patches=<patch number>

4) After patch has been applied successfully, Complete the below patch cycles.
$ adop phase=finalize
$ adop phase=cutover
$ adop phase=cleanup

5) Synchronize the file system, which copy the new run edition code and configuration to the patch file system.
$ adop phase=fs_clone


Thank You !!