« Java memory leak in XML Parser 2.0.2.9 leads to thousands of workflow notification emails with ORA-29532: Java call terminated by uncaught Java exception: java.lang.NullPointerException | Main | Common Incorrect beliefs about process address limits on 32bit platforms »

Misleading adcfgclone.pl ERROR: OUI files not found at their expected location...please make sure that the pre-requisite OUI patch was applied correctly...

If you ever got this ERROR while adcfgclone.pl, then it would do you good to check if you have existing directories named in the context file.

As misleading the below error message is, if you debug the perl
scripts and check the code a base path is not being able to be
constructed by adcdfclone.pl.

To make a long story short, if you just
double check all the directory paths that have been mentioned in the
context file, you can just get around this problem easily.



This misleading error message is fixed in R12.

Here is an example of such an instance..

        perl /apsd01/apps/apsdcomn/clone/bin/adclone.pl
java=/apsd01/apps/apsdcomn/clone/bin/../jre mode=apply stage=/apsd01/apps/apsdcomn/clone/bin/.. component=appsTier method=CUSTOM appctxtg=/apsd01/apps/apsdappl/admin/APSD_apsd.xml  showProgress contextValidated=false

ERROR: OUI files not found at their expected location.
Setting OUI path to: /appsoui

ERROR: OUI files not found at their expected location. Please make sure that the pre-requisite OUI patch was applied correctly: patch should be unzipped directly at the ORACLE_HOME root level so that OraInstaller.jar exists in either
1/oui/jlib/
or
1/oui/lib/

Restart adclone.pl after performing required corrections.
ERROR: Failed to execute /apsd01/apps/apsdcomn/clone/bin/adclone.pl


TrackBack

TrackBack URL for this entry:
http://blogs.oracle.com/mte1521/mt-tb.cgi/2114

Comments (1)

Your post helped me and saved a lot of time.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on February 15, 2008 6:04 AM.

The previous post in this blog was Java memory leak in XML Parser 2.0.2.9 leads to thousands of workflow notification emails with ORA-29532: Java call terminated by uncaught Java exception: java.lang.NullPointerException.

The next post in this blog is Common Incorrect beliefs about process address limits on 32bit platforms.

Many more can be found on the main index page or by looking through the archives.

Top Tags

Creative Commons License
This weblog is licensed under a Creative Commons License.
Powered by
Movable Type and Oracle