Perl lib version (v5.8.8) doesn’t match executable version (v5.10.0)

Issue while running adcfgclone on target database node, I can see below error messages in logfiles..


perl dbTechStack
RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack
Perl lib version (v5.8.8) doesn’t match executable version (v5.10.0) at /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/ line 46.
Compilation failed in require at /u01/oracle/product/11.2.0/appsutil/clone/ line 35.
BEGIN failed–compilation aborted at /u01/oracle/product/11.2.0/appsutil/clone/ line 35.

AutoConfig is exiting with status 1

RC-50013: Fatal: Instantiate driver did not complete successfully.


1. Make a backup copy of your existing Database Contextfile.

2. Modify the context file as shown.

<PERL5LIB oa_var=”s_perl5lib” osd=”unix”>/<complete path>/db/tech_st/11.2.0/perl/lib/5.8.3: \\
/<complete path>/db/tech_st/11.2.0/perl/lib/site_perl/5.8.3:/<complete path>/db/tech_st/11.2.0/appsutil/perl</PERL5LIB>


<PERL5LIB oa_var=”s_perl5lib” osd=”unix”>/<complete path>/db/tech_st/11.2.0/perl/lib/5.10.0: \\
<complete path>/db/tech_st/11.2.0/perl/lib/site_perl/5.10.0:/<complete path>/db/tech_st/11.2.0/appsutil/perl</PERL5LIB>

3. Execute Autoconfig to get the modifications implemented.


Thank You!!


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 !!

ERROR: OPatch failed because of Inventory problem

I was trying to apply EBS R12 patch on ORACLE_HOME(10.1.2) application node and got the below issue because of inventory issue.


opatch lsinventory
Oracle Interim Patch Installer version
Copyright (c) 2011 Oracle Corporation. All Rights Reserved..
Oracle recommends you to use the latest OPatch version
and read the OPatch documentation available in the OPatch/docs
directory for usage. For information about the latest OPatch and
other support-related issues, refer to document ID 293369.1
available on My Oracle Support (
Cannot open the file: /etc/oraInst.loc
Please use -invPtrLoc option and specify the correct file for OPatch to look for central inventory.

ERROR: OPatch failed because of Inventory problem.


The cause of the error is due to inventory pointer file /etc/oraInst.loc not present in the default location
In Oracle Applications Release 12.x , if oraInst.loc is not present in the default location it will be present in the following locations

Database Tier :

<RDBMS $ORACLE_HOME>/oraInst.loc
<RDBMS $ORACLE_HOME>/admin/oui/$CONTEXT_NAME/oraInst.loc

Applications Tier :

Tools $ORACLE_HOME/oraInst.loc


Please check if the file oraInst.loc is present in ORACLE_HOME to which the patch is being applied

opatch lsinventory -invPtrLoc $ORACLE_HOME/oraInst.loc

Run the patch as below
cd patch directory
opatch apply -invPtrLoc $ORACLE_HOME(10.1.2)/oraInst.loc


Thank You !!

FRM-92050: Failed to connect to the Server: /forms/servlet:- 1

Facing below issue when attempt to log into forms EBS R12


FRM-92050: Failed to connect to the Server: /forms/servlet:- 1

Java Exception: Negative content-length from http://hostname.domainname:port/forms/frmservlet?



Internet Explorer settings are not correct.


1)      Open Internet Explorer => Go to “Tools” => Click on “Internet Options” => Click on “Security” Tab

2)      Select “Internet” under => Set “Security level for this zone” to “Medium”.

3)      Select “Local intranet” under => Set “Security level for this zone” to “Medium-low” => Click on “Sites” for “Local intranet” => Click on    “Advanced” => Add the Instance URL. => Click on “Close” => Click on “Ok”.

4)     Retest the issue.



Thank You !!




Sometimes we need to skip the worker via adctrl then we can use the below steps to do the same.

  • Run adctrl utility
  • We can only see option till 7 in the main menu. But there is an 8th option that is hidden.
  • Use option 8 to skip a failed worker. Enter 8 and the worker will be skipped.

AD Controller Menu

1.    Show worker status
2.    Tell worker to restart a failed job
3.    Tell worker to quit
4.    Tell manager that a worker failed its job
5.    Tell manager that a worker acknowledges quit
6.    Restart a worker on the current machine
7.    Exit

Enter your choice [1] : 8


Thank You !!

AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora


Encounter the following error when running autoconfig on the Application  Tier.


Updating s_tnsmode to ‘generateTNS’
UpdateContext exited with status: 0
AC-50480: Internal error occurred: java.lang.Exception: Error while generating listener.ora.
Error generating tnsnames.ora from the database, temporary tnsnames.ora will be generated using templates
Instantiating Tools tnsnames.ora
Tools tnsnames.ora instantiated
Web tnsnames.ora instantiated exiting with status 2
.end std out.


There is no information in the table FND_NODES for the database node. Which means that autoconfig has not executed on the Database Tier.
First need to run autoconfig on the database tier to populate the database node values in FND_NODES table then run autoconfig on Application Tier.

please execute the following steps:

1. Loging to as oracle user and perform the below steps
sqlplus apps/$apps
exec fnd_conc_clone.setup_clean

2. Run on db node.

3. Run on apps node.

Thank You !!

ORA-19693: backup piece already included


Encounter the following errors when trying to duplicate the database to another server using the RMAN backup:

ORA-19693: backup piece E:\RMAN_BACKUP\xxxxxxxxxxx already included



The location of the RMAN backup pieces at the target and auxiliary/duplicate databases are
different. So, RMAN cannot see the RMAN backup pieces, because they are stored in a different directory at the auxiliary/duplicate database server.

Try with below command which may resolve issue
RMAN> catalog start with ‘E:\RMAN_BACKUP’;


Thank You !!