Database Reference
In-Depth Information
•
Start profile
This parameter file will define which SAP services will be started (for
example, message server, dialog, gateway, or enqueue process).
•
Default profile
This parameter file will define the profile parameters applicable for all
instances (application servers) in the system (for example, the name of the database
host, or the host on which the message server is running).
•
Instance profile
This parameter file defines the profile for the specific instance, which
allows individual application servers to be configured differently for specific tasks
and users.
SAP profiles will be discussed in greater detail in
Chapter 7
.
Verifying the System Started Correctly
You can perform the following checks to ensure that the SAP system has started correctly:
1. startsap log (startsap.log) file in the <SAPSID>adm home directory should report that
all the services and processes have started.
2. The database starts without any errors as per startdb.log in the home directory of
<SAPSID>adm.
3. Check at operating system level for the SAP processes (dispatcher and work pro-
cesses).
4. Check the last lines in the available.log file in the following location:
/usr/sap/<SID>/<instance name>/work/
The last line in the available.log file will have a status entry saying the system is either
available or unavailable.
SAP Operating System-Level Processes
When the SAP system is started, it starts several operating system-level processes, as ex-
plained in the architecture section of this chapter. Checking the operating system-level pro-
cesses will ensure that the system has started correctly and is functioning properly. Check
that the dispatcher and the work processes, message server, enqueue server, gateway, icman,
and Oracle database processes are up and running.
Figure 2-6
shows the different processes
that should be available when the system is started correctly.
