Thursday, September 23, 2010

Autoconfig errored out in db tier

Autoconfig errored out in database on Linux server. The following is the sample output from adconfig.log.

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor


Ensure that the following two parameters in the database tier context file match each other.


Sometimes this is a source of listener problems.

Also check for the service_name parameter in init.ora. Its value should be SID.Domain_name.
If it is non-RAC database, ensure that the following parameters are disabled in init.ora

remote_listener fails in FE node

perl appsTier fails in the front end node with the error message as follows:

Cannot proceed with ApplyApplTop - the paths/ports in the context file are not valid.
RC-20403: The following port numbers are busy - please make sure the ports are available and try again.
Raised by
        s_fnd_cache_port_range :

Surprisingly, there is no value assigned for this particular variable s_fnd_cache_port_range in the xml file

A simple solution is to delete the particular line of s_fnd_cache_port_range and the autoconfig will choose a port value by itself

Oracle Article Ids: 390901.1 & 365871.1
External url:

adrelink errored for the patch 4653217

adrelink for the patch 4653217 failed with the below error:

/usr/lib/gcc/i386-redhat-linux/3.4.6/ undefined reference to `dl_iterate_phdr@GLIBC_2.2.4'
collect2: ld returned 1 exit status
make: *** [/apps/qtcdv/appl_top/ad/11.5.0/bin/adpchnew] Error 1

This error is specific to linux servers. If this is the same error you are also facing, then immediately check for the below two soft links. The destination should be similar as per this screen shot

# ls -l /usr/bin/gcc
lrwxrwxrwx  1 root root 15 Mar 22 02:45 /usr/bin/gcc -> /usr/bin/gcc296
# ls -l /usr/bin/g++
lrwxrwxrwx  1 root root 15 Mar 22 02:48 /usr/bin/g++ -> /usr/bin/g++296

After rectifying the mentioned softlinks you can restart the patch.

Apps Login page is not being displayed properly

Error messages as found in error logs:
IAS Cache initialization failed. The Distributed Caching System failed to initialize on port: <port#>. The list of hosts in the distributed caching system is: <host_name>. The port <port> should be free on each host running the JVMs. The default port <port#> can be overridden using -Doracle.apps.jtf.cache.IASCacheProvidercacheProvider.port=<port number>

There are many reasons for this error. Some of the possibilites are discussed below:

1) Check for the parameters nprocs in the file jerv.conf and compare this with the no. of ports in
The rule is that the number of ports specified in should be greater than or equal to the total number of processes
mentioned in jserv.conf

2) If this is not the issue, then check for the entries in /etc/hosts file.
The mapping of the ip addresses of virtual name and the physical hostname might be wrong

3) If this also doesn't help then try to enable 'debug' parameter in the files httpd.conf, jserv.conf and and collect additional info w.r.t the error.

Steps to Download the Patch from Unix box

As the ftp got retired, the following procedure can be utilized for downloading patches directly onto the UNIX servers.

    * Login to "My Oracle Support"
    * Search for the patch
    * Go to the download page
    * Click on "show details" link beneath the "Download" button
    * Right click on the patch name and Copy URL

Then to download the patch using "wget" follow these instructions:

    * Check "wget" command is available OR install it.

Run the following command using your My Oracle Support login and password:
         wget --http-user=<username> --http-password=<password>--output-document=<filename> "paste the above copied address here in quotes"


wget --http-password=password ""

By this way one can download the patches faster and easier.

Autoconfig on FE node fails with TNS error or was failing with the below error even though the listener is running in the db server

ORA-12541: TNS: no listener

You may further notice that it is trying to connecto to DB via a different port# whereas the DB listener is running on a different port#.

Well, the reason for your problem is the database context file was not updated with the new port# and hence the Autoconfig on FE node was erroring out.
Please do the following steps to rectify the error:

•    Update the context file on db node with the original port#  and run Autoconfig.
•    Then run the Autoconfig on FE node which will complete successfully.

Library Path issue during DB autoconfig

On HP-UX Itanium server, while running autoconfig on the db tier it might fail with the below error:

  AutoConfig could not successfully execute the following scripts:
    Directory: /oracle/product/              INSTE8_PRF         137

  AutoConfig could not successfully execute the following scripts:
    Directory: /oracle/product/              INSTE8_APPLY       137

AutoConfig is exiting with status 2

Further investigation of the log file will reveal the below two errors:

.end std out./usr/lib/hpux64/ Unable to find library ''.
/oracle/product/<SID>/appsutil/install/<CONTEXT_NAME>/[82]: 14372 Killed

  • exiting with status 137
.end std out.
/usr/lib/hpux64/ Unable to find library ''.
/oracle/product/<SID>/appsutil/install/<CONTEXT_NAME>/[117]: 16041 Killed


Edit xml file to include LD_LIBRARY_PATH=$ORACLE_HOME/lib
and re-run the autoconfig