Ok, this is the long winded version of stopping and starting EBS application tier and database tier with some explanation of how to figure out an appl and database tier environments – that you just walked into and don’t necessarily have paths, sids, listener names etc. memorized yet.
Start and Stop The Application Tier
Here’s the environment variable that points you to the directory that contains R12 start and scripts on the applmgr tier.
$ADMIN_SCRIPTS_HOME
On my sandbox server – that looks like this:
ADMIN_SCRIPTS_HOME=/d01/oracle/VIS/fs1/inst/apps/VIS_oel66-79/admin/scripts
[applmgr@oel66-79 scripts]$ cd
[applmgr@oel66-79 ~]$ cd $ADMIN_SCRIPTS_HOME
[applmgr@oel66-79 scripts]$ ls
adadminsrvctl.sh adformsrvctl.sh adstrtal.sh jtffmctl.sh
adalnctl.sh admanagedsrvctl.sh cz64bitengine.pl msc
adapcctl.sh adnodemgrctl.sh EBSProvisioner.log mwactl.sh
adautocfg.sh adopmnctl.sh gsmstart.sh mwactlwrpr.sh
adcmctl.sh adpreclone.pl ieo sqlnet.log
adexecsql.pl adstpall.sh java.sh
[applmgr@oel66-79 scripts]$ env | grep -i admin_scripts_home
ADMIN_SCRIPTS_HOME=/d01/oracle/VIS/fs1/inst/apps/VIS_oel66-79/admin/scripts
[applmgr@oel66-79 scripts]$
How is ADMIN_SCRIPTS_HOME set?
Memorize the path and name of the environment file that sets it? Sure but, if you don’t have it memorized yet, check the inventory (/etc/oraInst.loc points you the way)… well, indirectly. Go to the pointed to by inventory_loc
inventory_loc=/d01/app/oraInventory
# add the contextXML sub-dir
cd /d01/app/oraInventory/contextXML
cat inventory.xml | grep -i “HOME NAME”
The resulting list will be long but the leading edge of the homes tells you what I call the EBS_ROOT – no EBS does not define this – I just did. But for example here is what I see:
cat inventory.xml | grep -i “HOME NAME”
<HOME NAME=”OH1665749111″ LOC=”/d01/oracle/VIS/fs1/FMW_Home/oracle_common” TYPE=”O” IDX=”6″>
<HOME NAME=”OraDB12Home1″ LOC=”/d01/oracle/VIS/12.1.0″ TYPE=”O” IDX=”1″/>
…
So my EBS_ROOT is shown above and it ends with the path before the string “fs1”.
/d01/oracle/VIS
and this “EBS_ROOT” contains the file EBSapps.env. And that file is the enviroment file for most of EBS at the application tier.
So before you start or stop EBS, source this file to set your environment variables usually with the “run” file system but, “patch” is the other option.
. /d01/oracle/VIS/EBSapps.env run
Now.
cd $ADMIN_SCRIPTS_HOME
sh ./adstrtal.sh
or
sh ./adstpall.sh
Start and Stop The Database Tier
How about stopping the Oracle tier, that should be simple, shutdown the listener, and the database, rgiht
cd $ORACLE_HOME/appsutil/scripts
[oracle@oel66-79 scripts]$ ls
VIS_oel66-79
[oracle@oel66-79 scripts]$ cd VIS_oel66-79
[oracle@oel66-79 VIS_oel66-79]$ ls
adautocfg.sh adchknls.pl addbctl.sh addlnctl.sh adexecsql.pl adlsnodes.sh adpreclone.pl adstopdb.sql adstrtdb.sql afiedt.buf
sh ./addbctl.sh stop immediate
or
sh ./addbctl.sh start
The process is a little different with a sqlnet listener for EBS than it is a most Oracle databases.
The command is:
sh ./addlnctl.sh {start|stop} {listener}
But that implies you know the listener name – if the listener is up you can grep for it and figure it out.
ps -ef | grep -i tns
But what if it’s not up, what is the listener name? Well the name is in:
$ORACLE_HOME/network/admin/<ORACLE_SID>/listener.ora
Note this is one sub-directory beneath where you would normally find it… so be careful… if you have listener.ora file in both the parent and the child directory… it could get confusing. So just remove listener.ora from $ORACLE_HOME/network/admin/ dir and always use the listener.ora in $ORACLE_HOME/network/admin/<ORACLE_SID>.
cd $ORACLE_HOME/network/admin/$ORACLE_SID
# to see my listener name – yes it’s VIS and I’ll memorize this from now on
view listener.ora
cd $ORACLE_HOME/applutil/scripts
[oracle@oel66-79 scripts]$ ls
VIS_oel66-79
BTW VIS_oel66-79 is <oracle-home>_<hostname without the domain>
cd VIS_oel66-79
sh ./addlnctl start VIS
Ok, so just verify the listener is started – and show the listener name / process
[oracle@oel66-79 admin]$ lsnrctl status
LSNRCTL for Linux: Version 12.1.0.2.0 – Production on 21-MAY-2017 09:16:13
Copyright (c) 1991, 2014, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
————————
Alias VIS
Version TNSLSNR for Linux: Version 12.1.0.2.0 – Production
Start Date 21-MAY-2017 08:52:03
Uptime 0 days 0 hr. 24 min. 10 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /d01/oracle/VIS/12.1.0/network/admin/VIS_oel66-79/listener.ora
Listener Log File /d01/oracle/VIS/12.1.0/admin/VIS_oel66-79/diag/tnslsnr/oel66-79/vis/alert/log.xml
Listening Endpoints Summary…
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oel66-79.localdomain)(PORT=1521)))
Services Summary…
Service “VIS” has 2 instance(s).
Instance “VIS”, status UNKNOWN, has 1 handler(s) for this service…
Instance “VIS”, status READY, has 1 handler(s) for this service…
Service “ebs_patch” has 1 instance(s).
Instance “VIS”, status READY, has 1 handler(s) for this service…
The command completed successfully
[oracle@oel66-79 admin]$ ps -ef | grep -i tns
root 36 2 0 May15 ? 00:00:00 [netns]
oracle 8325 1 0 08:52 ? 00:00:00 /d01/oracle/VIS/12.1.0/bin/tnslsnr VIS -inherit
oracle 11053 8194 0 09:16 pts/1 00:00:00 grep -i tns
[oracle@oel66-79 admin]$