Start and stop an SAP Central instance : UNIX / ORACLE
Hello, this is the first post of a series of blogs about performing basic tasks for BC admin beginners.
So first things first : how to start / stop an SAP instance running on Unix / Oracle.
We consider being working on a central instance :
1. Stop SAP and Oracle
Connect to the operating system as user sidadm and start the following commands :
sapdev:devadm 10> stopsap NB : stopsap stops the SAP instance and the Oracle database
Checking DEV Database
——————————
ABAP Database is running
Stopping the SAP instance DVEBMGS01
———————————-
Shutdown-Log is written to /home/devadm/stopsap_DVEBMGS01.log
Instance on host sapdev stopped
Waiting for cleanup of resources………………..
Running /usr/sap/DEV/SYS/exe/run/stopdb
Trying to stop DEV database …
Log file: /home/devadm/stopdb.log
DEV database stopped
/usr/sap/DEV/SYS/exe/run/stopdb completed successfully
Checking DEV Database
——————————
ABAP Database is not available via R3trans
sapdev:devadm 11> saposcol -k
Setting Stop Flag :
09:11:49 05.10.2006 LOG: ==== Stop Flag was set by saposcol (kill_collector()).
09:11:49 05.10.2006 LOG: ==== The collection process will stop as soon as possible
Collecting process has stopped.
09:11:50 05.10.2006 LOG: Shared memory deleted.
As orasid user :
sapdev:oradev 2> lsnrctl stop
LSNRCTL for HPUX: Version 10.2.0.2.0 – Production on 05-OCT-2006 09:12:55
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV.WORLD))
The command completed successfully
The SAP instance and the Oracle database are then fully stopped.
There should not be any SAP or Oracle processes running anymore.
2. Oracle and SAP startup
As user ora<sid> start :
sapdev:oradev 3> lsnrctl start
LSNRCTL for HPUX: Version 10.2.0.2.0 – Production on 05-OCT-2006 09:13:53
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Starting /oracle/DEV/102_64/bin/tnslsnr: please wait…
TNSLSNR for HPUX: Version 10.2.0.2.0 – Production
System parameter file is /oracle/DEV/102_64/network/admin/listener.ora
Log messages written to /oracle/DEV/102_64/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=DEV.WORLD)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=DEV)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sapdev)(PORT=1528)))
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=DEV.WORLD))
STATUS of the LISTENER
————————
Alias LISTENER
Version TNSLSNR for HPUX: Version 10.2.0.2.0 – Production
Start Date 05-OCT-2006 09:13:53
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /oracle/DEV/102_64/network/admin/listener.ora
Listener Log File /oracle/DEV/102_64/network/log/listener.log
Listening Endpoints Summary…
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=DEV.WORLD)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=DEV)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sapdev)(PORT=1528)))
Services Summary…
Service “DEV” has 1 instance(s).
Instance “DEV”, status UNKNOWN, has 1 handler(s) for this service…
The command completed successfully
As user <sid>adm use the following commands :
sapdev:devadm 12> startsap NB : startsap starts the SAP instance AND the oracle database.
Checking DEV Database
——————————
ABAP Database is not available via R3trans
Starting SAP-Collector Daemon
——————————
09:14:34 05.10.2006 LOG: Effective User Id is root
******************************************************************************
* This is Saposcol Version COLL 20.89 700 – v2.02 for HP-UX – 24.1.2006
* Usage: saposcol -l: Start OS Collector
* saposcol -k: Stop OS Collector
* saposcol -d: OS Collector Dialog Mode
* saposcol -s: OS Collector Status
* Starting collector (create new process)
******************************************************************************
saposcol on host sapdev started
Running /usr/sap/DEV/SYS/exe/run/startdb
Trying to start DEV database …
Log file: /home/devadm/startdb.log
DEV database started
/usr/sap/DEV/SYS/exe/run/startdb completed successfully
Starting SAP Instance DVEBMGS01
——————————
Startup-Log is written to /home/devadm/startsap_DVEBMGS01.log
Instance Service on host sapdev started
Instance on host sapdev started
The Oracle database is started.
The SAP instance is then up and running.
You should be able to connect it through SAPGUI for example.
I am having an issue with our sap database when the startsap is starting the oracle server with user sidadm instead of orasid. Do you know what is wrong?
Thanks,
Jonathan.
Hi Jonathan,
This can be due to wrong users rights / ownership set on the Oracle binaries.
You should have a look at the following notes to fix this if needed :
583861 : shows how the user rights / ownership should be set.
592393 ( point 31 ) : states that this may not be a problem as long as the oracle binary has the right authorizations ( see note 583861 ).
You can also have a look at Note 206916 - Oracle processes run under "incorrect" user .
In the end this may not be a real problem as long as the rights are set correctly.
Best regards,
Steve.
No it is not really wrong in the sense to cause of concern. I have observed this behaviour different SAP products for a while now. No issues with this.
Anyways Steve has mentioned the note 206916 which explains this.
Regards.
Ruchit.
sapdev:devadm 10> stopsap NB : stopsap stops the SAP instance and the Oracle database
If I do the same with the SAP Management Console tool using Windows and Oracle
Is it the same?
Oracle stops?
Regards.
No. On windows the SAP appl server stgops. Oracle stays up.
You have to shut it down afterwards.
regards,
Steve.
No. On windows the SAP appl server stgops. Oracle stays up.
You have to shut it down afterwards.
regards,
Steve.