Administration

Symbol Legend:

¬ Press Enter

<sid> System ID lower case

<SID> System ID upper case

1. System Tasks

Starting the SAP Instance

The normal SAP instance start up consists of three parts: starting the SAP OS

Collector, starting the Oracle Listener, and starting the SAP instance. The

process mainly goes like this: ora<sid> logs on and starts the Oracle Listener

then <sid>adm logs on and runs the startsap script.

Here you may get one doubt? What happened to the SAP OS Collector?

The startsap script takes care of the SAP OS Collector for us. When the SAP

Instance starts up via the startsap script, it checks to see if saposcol is up

and running – whether from the root user starting it manually or from another SAP

Instance already starting it up, it doesn’t matter. If saposcol is up and

running, the script simply moves on to the next step. If it is not, the script

starts saposcol as root and then proceeds. So the SAP OS Collector gets handled

one way or another.

Even if you have multiple SAP instances on a server, the process is pretty much

the same unless the Oracle databases were installed using the MCOD installation

option. Then only one Oracle Listener is used since both databases share one

Oracle listening port which is normally 1527. Normally each SAP database – ie

SAP instance - has it’s own listener.

 here is how to start a SAP instance.

1. Verify that the SAP instance is down.

2. Log on to the appropriate server as ora<sid>.

3. Type in the following:

        lsnrctl start￢

4. Log on to the same server as <sid>adm.

5. Type in the following – the saposcol will come up automatically:

startsap￢

If you only need to start the database and not the SAP instance too, type

instead:

startsap DB￢

And do not do the rest of the start up procedures listed below, you can stop

now.

6. Wait until the startup messages have scrolled by. There may be other minor

programs that start at the time as well. If you try to logon and are

refused connection, check the logs in the /home/<sid>adm for applicable

errors.

Verifying that the SAP Instance is up

The easiest way to confirm that the SAP instance has started successfully is to

log on to the instance. If it has not had a successful start up, look at the

logs in the /home/<sid>adm directory. Sort them with “ls – ltr” is see the list

sorted in descending order for the ease of viewing.

If nothing obvious is found, go to the /usr/sap/<SID>/DVEBMGS00/work directory

and do the same thing in this directory. The most useful information can be

found in the dev_wx, dev_ms, dev_disp, dev_rfcx, and stderrx files.

If you need further assistance, please refer to the section

SAP System Start Up Troubleshooting.

Stopping the SAP Instance

The stopping of a SAP instance is practically the reversal of the start up

Process; stop the SAP instance, stop the Oracle Listener, and stop the SAP OS

Collector. The only real difference is that the stopsap script will NOT stop the

SAP OS Collector for you, you have to stop that manually once everything else it

down. There could be other SAP instances still running so the OS Collector needs

to continue to gather information.

1. Log on to the appropriate server as <sid>adm.

2. Type in the following:

     stopsap￢

     If you only need to stop the SAP instance and not the database too, type

     instead:

     stopsap R3￢

     And do not do the rest of the start up procedures listed below, you can stop

     now.

3. Log on to the same server as ora<sid>.

4. Type in the following:

      lsnrctl stop￢

5. Log on to the same server as root.

6. Type in the following:

      cd /usr/sap/<SID>/SYS/exe/run￢

      ./saposcol -k￢

7. Log off the server.

Starting the SAP OS Collector

1. Log on to the appropriate server as <sid>adm.

2. Type in the following:

      cd /usr/sap/<SID>/SYS/exe/run￢

      ./saposcol￢

 3. Log off the server.

 Stopping the SAP OS Collector

1. Log on to the appropriate server as <sid>adm.

2. Type in the following:

      cd /usr/sap/<SID>/SYS/exe/run￢

      ./saposcol -k￢

3. Log off the server.