Oracle Apps DBA stuff: How to troubleshoot autoconfig errors [ID 845700.1]

How to troubleshoot autoconfig errors [ID 845700.1]

	Modified 22-JUL-2009 Type TROUBLESHOOTING Status PUBLISHED

In this Document
Purpose
Last Review Date
Instructions for the Reader
Troubleshooting Details
1. Check the AutoConfig patch level and code
2. Enable debugging
3. Review the log files

Applies to:

Oracle Applications Technology Stack - Version: 11.5.8 to 12.0.6
Information in this document applies to any platform.
Oracle Applications - Version: 11.5.8 to 12.0.6

Purpose

This troubleshooting note is intended as a guide to help determine the cause of some problems that may arise during autoconfig.

Locations of log files are listed, which should be uploaded when reporting an autoconfig issue to Oracle Support.

Last Review Date

June 19, 2009

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

The list of pre-requisite autoconfig patches can be found on Note 165195.1 and Note 387859.1.

1. Check the AutoConfig patch level and code

Make sure the latest available TXK rollup patch is applied by running the SQL found in Note: 390666.1, and that code and templates are synchronized on the Database Tier by performing the following steps:

a). On the Application Tier (as the APPLMGR user):

Log in to the APPL_TOP environment (source the environment file)
Create appsutil.zip file

perl /bin/admkappsutil.pl

This will create appsutil.zip in $APPL_TOP/admin/out .

b). On the Database Tier (as the ORACLE user):

Copy or FTP the appsutil.zip file to the

cd
unzip -o appsutil.zip

c). Check the version of the files to confirm they are in synch:

-for each apps tier's node:

grep -i '$Header' /bin/adconfig.pl
adident Header /oracle/apps/ad/clone/ApplyDatabase.class

-for each db tier's node:

grep -i '$Header' /appsutil/bin/adconfig.pl
strings -a /appsutil/java/oracle/apps/ad/clone/ApplyDatabase.class | grep -i 'Header'

2. Enable debugging

If a timeout error has occurred while running a child process during autoconfig further debug information is written to the autoconfig's log by setting the following environment variables:

export TIMEDPROCESS_DEBUG=YES
export TIMEDPROCESS_TIMEOUT=

Note: set to -1 for indefinite timeout, 3600000 for 60 minutes etc.

Further increase the level of debug information written to the autoconfig's log by doing the following:

Database tier

a). Backup /perl/ADX/util/Java.pm
b). Modify /perl/ADX/util/Java.pm as follows:

Locate "sub getadjreopts" line. Here is where getadjreopts function is defined.
Locate the following piece of code inside that function

if($javaCmd =~ /jre/) {
return ("-mx256m", 0);
} else {
return ("-Xmx512M",0);
}

modify as follows

if($javaCmd =~ /jre/) {
return ("-mx256m -DDEBUG_MODE=true", 0);
} else {
return ("-Xmx512M -DDEBUG_MODE=true",0);
}

Save the changes.

c). Source the database tier's environment file.
d). Run the following OS commands

cd /appsutil/scripts/$CONTEXT_NAME
pwd
ls -la

Attention: The database server and the database listener must remain available during the AutoConfig run. All the other database tier services should be shut down.

script ~/myadconfigdbg.log
./adautocfg.sh
exit

where: = (month, day, hour, and minute of the AutoConfig run)

Application tier

if($javaCmd =~ /jre/) {
return ("-mx256m", 0);
} else {
return ("-Xmx512M",0);
}

modify as follows

if($javaCmd =~ /jre/) {
return ("-mx256m -DDEBUG_MODE=true", 0);
} else {
return ("-Xmx512M -DDEBUG_MODE=true",0);
}

Save the changes.

c). Source the apps tier's environment file.
d). Run the following OS commands:

cd $COMMON_TOP/admin/scripts/$CONTEXT_NAME (for release 11i)

cd $ADMIN_SCRIPTS_HOME (for release 12)

then continue with the following OS commands:

pwd
ls -la
./adstpall.sh apps/

Attention: The database server and the database listener must remain available during the AutoConfig run. Only the application tier servers should be shut down.

script ~/myadconfigdbg.log
./adautocfg.sh
exit

3. Review the log files

The log file that AutoConfig creates on the database tier is located at:

/appsutil/log///adconfig.log

The log file that AutoConfig creates on the application tier is located at:

/admin//log//adconfig.log (for release 11i)

$INST_TOP/admin/log//adconfig.log (for release 12)

where: = (month, day, hour, and minute of the AutoConfig run)

Provide the latest autoconfig's logs & ~/myadconfigdbg.log files to Oracle Support for review.

Related