Database Reference
In-Depth Information
tools, there is a good chance of making the SAP system data inconsistent. Basis administrat-
ors and SAP security administrators must ensure that proper application security is in place
so that the safeguards implemented by SAP are followed. Over the last three to four dec-
ades, the SAP ERP system has grown in terms of the number of tables. In the ERP6 release
of SAP there are about 71,000 tables in an SAP application.
Now that we have looked into the architecture of SAP NW AS ABAP, let us start looking
into how to start, stop, and verify a proper functioning of SAP systems. SAP installations
will be covered in detail in
Chapters 5
through
8
.
Starting the SAP System
To start a SAP system, log on to your UNIX system as the SAP administrative user
(<SAPSID>adm)—for example, devadm, where SAPSID= DEV—and enter the following
command from your <SAPSID>adm user account home directory:
where:
DB starts the database system.
R3 starts the instances and associated processes of the R/3 system.
ALL starts both the database system and the R/3 system. ALL is the default and can be
omitted.
Please note that in a two-tier setup the ALL option works, but in a three-tier setup, the
database must be started prior to issuing
startsap
.
SAP Parameter Read Sequence During SAP System Start-up
The following sequence is used for reading the system parameters during SAP start-up:
1. SAP kernel code
2. Default profile
3. Instance profile
SAP Profiles
SAP profiles are operating system files that contain SAP instance setup information. These
files are installed as a part of SAP system installation. The SAP system uses profile para-
meters at the system start-up. There are three types of profiles:
