Scribd
Upload
154 views

Apps Dba Notes: Adstrtal - SH Exits With Status 150

This document provides information on log files created during the Oracle Applications Release 12 installation using RapidWiz. It describes the locations of database tier logs, applications tier logs, and inventory registration logs. It also provides instructions on finding the version of a .pld file and steps to remove unnecessary context files after cloning.

Uploaded by

amoussaa
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
154 views

Apps Dba Notes: Adstrtal - SH Exits With Status 150

This document provides information on log files created during the Oracle Applications Release 12 installation using RapidWiz. It describes the locations of database tier logs, applications tier logs, and inventory registration logs. It also provides instructions on finding the version of a .pld file and steps to remove unnecessary context files after cloning.

Uploaded by

amoussaa
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Author – A.

Kishore/Sachin
http://appsdba.info

APPS DBA Notes

 adstrtal.sh exits with status 150


We may get this error when we start all apps tier services.

[applmgr@erp scripts]$ ./adstrtal.sh


You are running adstrtal.sh version 120.13
Enter the APPS username: apps
Enter the APPS password:****
Executing service control script:
/d01/oracle/PROD/inst/apps/PROD_erp/admin/scripts/adopmnctl.sh start
script returned:
****************************************************
You are running adopmnctl.sh version 120.4
Starting Oracle Process Manager (OPMN) ...
adopmnctl.sh: exiting with status 0
adopmnctl.sh: check the logfile
/d01/oracle/PROD/inst/apps/PROD_erp/logs/appl/admin/log/adopmnctl.txt
for more information ...
.end std out.
.end err out.
****************************************************

Executing service control script:


/d01/oracle/PROD/inst/apps/PROD_erp/admin/scripts/adapcctl.sh start
script returned:
****************************************************
You are running adapcctl.sh version 120.6
Starting OPMN managed Oracle HTTP Server (OHS) instance ...
adapcctl.sh: exiting with status 150
adapcctl.sh: check the logfile
/d01/oracle/PROD/inst/apps/PROD_erp/logs/appl/admin/log/adapcctl.txt
for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/d01/oracle/PROD/inst/apps/PROD_erp/admin/scripts/adoacorectl.sh start
script returned:

1
Author – A.Kishore/Sachin
http://appsdba.info

****************************************************

You are running adoacorectl.sh version 120.11


Starting OPMN managed OACORE OC4J instance ...
adoacorectl.sh: exiting with status 150
adoacorectl.sh: check the logfile
/d01/oracle/PROD/inst/apps/PROD_erp/logs/appl/admin/log/adoacorectl.tx
t for more information ...
.end std out.
.end err out.
****************************************************
/d01/oracle/PROD/inst/apps/PROD_erp/admin/scripts/adformsctl.sh start
script returned:
****************************************************
You are running adformsctl.sh version 120.12
Starting OPMN managed FORMS OC4J instance ...
adformsctl.sh: exiting with status 150
adformsctl.sh: check the logfile
/d01/oracle/PROD/inst/apps/PROD_erp/logs/appl/admin/log/adformsctl.txt
for more information...

Solution :

 Open a new shell and set your apps environment,run the follwing:

# cd $ADMIN_SCRIPTS_HOME
adopmnctl.sh stop
 Now Check if it is really down:
ps -ef | grep -i opm
 Delete the following:
$ rm -fr $INST_TOP/ora/10.1.3/j2ee/oacore/persistence/*
$ rm -fr $INST_TOP/ora/10.1.3/j2ee/oafm/persistence/*
$ rm -fr $INST_TOP/ora/10.1.3/j2ee/forms/persistence/*

 Run the following script


# adopmnctl.sh start
 Start all applications services and check if it completes with status 0
# adstrtal.sh.sh apps/appspassword
Now the error should be fixed.

2
Author – A.Kishore/Sachin
http://appsdba.info

 RapidWiz log files for Oracle Applications Release 12


During the installation of Release 12 using RapidWiz, the following log files are
created.
Before the installation starts:
The Rapidwiz Configuration File is saved in three locations,these are follows.

$TMP//conf_.txt
$INST_TOP/conf_.txt
/appsutil/conf_.txt

Database Tier log files are located as follows:

$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/.logRDBMS
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDBTechStack_.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ohclone.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/make_.log
ORACLE_HOME/appsutil/log/$CONTEXT_NAME/installdbf.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/adcrdb_.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME/ApplyDatabase_.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME//adconfig.log
$ORACLE_HOME/appsutil/log/$CONTEXT_NAME//NetServiceHandler.log

Applications Tier(s) log files are located as follows:

$INST_TOP/logs/.log
$APPL_TOP/admin/$CONTEXT_NAME/log/ApplyAppsTechStack.log
$INST_TOP/logs/ora/10.1.2/install/make_.log
$INST_TOP/logs/ora/10.1.3/install/make_.log
$INST_TOP/admin/log/ApplyAppsTechStack.log
$INST_TOP/admin/log/ohclone.log
$APPL_TOP/admin/$CONTEXT_NAME/log/installAppl.log
$APPL_TOP/admin/$CONTEXT_NAME/log/ApplyAppltop_.log
$APPL_TOP/admin/$CONTEXT_NAME/log/adconfig.log
$APPL_TOP/admin/$CONTEXT_NAME/log/NetServiceHandler.log

3
Author – A.Kishore/Sachin
http://appsdba.info

Inventory Registration log files are as follows:


/logs/cloneActions.log
/logs/oraInstall.log
/logs/silentInstall.log

In case of any errors during the installation, we can use these log file locations for
the troubleshooting.

 How To Find The Version Of A pld File?

The *.pld files are the source code of *.pll files which are the source of the
executable *.plx files.

The *.pld file itself does not get installed. To find the version of the *.pld file, we
need to look into the corresponding *.pll file.

The *.pll files are located in $AU_TOP/resource

To identify the version of pld file, lets say ABC.pld,we can use the following string at
OS level:
adident Header $AU_TOP/resource/ABC.pll

 Steps to remove not needed context files after cloning

Step 1. Look at the $APPL_TOP/admin

Make sure that there is only the Target Machine's .xml available under:
$APPL_TOP/admin/
Step 2. Remove the source *.xml file if it is there.
Step 3. Then run the following.

SQL*Plus:
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN; COMMIT; EXIT;

Step4. Re-run AutoConfig on every tiers(DB Tier/s then on Apps Tier/s) to


repopulate the required system tables.

Step 5. Bounce the Applications Services.

You might also like