LLI Wiki — My Digital Knowledge Base

SAP on Oracle: start and stop order, SYSTEM password

Start and stop order for SAP ABAP, Java and TREX systems on Oracle databases, and changing the SYSTEM password with brconnect.

This article describes the stop and start order for several SAP systems (ABAP, Java, TREX) hosted on one Linux server with Oracle databases, plus the rules to follow for DEV, QAS and PRO environments.

Example architecture

System SID Role Note
Solution Manager ABAP SAA ABAP, Oracle database with the same name Reached through SAP GUI
Solution Manager Java SAJ Java, Oracle database with the same name User management is delegated to the ABAP part
TREX development TRD Search engine Reached through an X-window session or transaction TREXADMIN
TREX production TRP Search engine Same

Each system has an OS user <sid>adm (for example saaadm) and each Oracle database has an ora<sid> user with a dedicated listener (LISTENER_SAA, LISTENER_SAJ).

Stopping the instances

Stop the Java system first, because its users depend on the ABAP system.

  1. As sajadm: stopsap. The database is stopped as well.
  2. As saaadm: stopsap. The database is stopped as well.
  3. For each TREX instance, as trdadm then trpadm, run stopsap with the instance and host name (syntax depends on the version, see SAP documentation).

Starting the instances

Start the Oracle listeners first.

# as orasaj
lsnrctl start LISTENER_SAJ

# as orasaa
lsnrctl start LISTENER_SAA

Then:

  1. As saaadm: startsap (also starts the Oracle database).
  2. When the ABAP system is up and running, as sajadm: startsap (also starts the database).
  3. Start the TREX instances with startsap as trdadm and trpadm.

Changing the SYSTEM password of an SAP Oracle database

With the SAP tools, brconnect changes a database user's password:

brconnect -c -u / -f chpass -o SYSTEM -password '<PASSWORD>'

Example DEV / QAS / PRO landscape

The order depends on where the database lives.

Topology Start Stop
Application and database on the same server (DEV, QAS) Nothing starts at boot. In order: startlistener, startsap, then startsaprouter if used stopsap stops application and database
Application and database on two servers (PRO) The database starts and stops with its server; start the database server before the application server, then run startsap on the application server Run stopsap on the application server before stopping the database or its server

To act on the database alone, first stop everything with stopsap.

Notes

Mastodon LLIMastodon SocialFosstodon