BC314 Technical Core Competence (NT/MS SQL

Server)
Technical Core Competence
(NT/MS SQL Server)

BC314
R/3
R/3 Release
Release 4.6B
4.6B 50034331
50034331
 SAP AG 1999
Copyright

Copyright 2000 SAP AG. All rights reserved.

Neither this training manual nor any part thereof may
be copied or reproduced in any form or by any means,
or translated into another language, without the prior
consent of SAP AG. The information contained in this
document is subject to change and supplement without prior
notice.

All rights reserved.

 SAP AG 1999
SAP Basis Administration Training 4.6

Core Competence Expert Competence

BC505 3 days
Database
MBC30 2 days Administration Oracle
R/3-Technical
Implementation and BC511 5 days
Operation Management Database
Administration Informix
BC515 2 days
BCtcc* 5 days BC305 3 days
Database
Technical Core Advanced R/3 Administration SAP DB
Competence System Administration
BC520 3 days
BC315 3 days Database Administration
BC325 3 days MS SQL Server
Software Logistics Workload Analysis BC525 3 days
Database Administration
MY301 2 days BC350** 3 days DB2/400
Workplace TCC Workplace BC530 5 days
Database Administration
*Technical Core Competence Versions DB2/390
BC310 Windows NT / Oracle BC535 3 days
BC312 Windows NT / SAP DB Database Administration
BC314 Windows NT MS SQL Server DB2 UDB
BC317 (Windows NT / UNIX) / DB2
BC360 UNIX / Oracle BC555 2 days
BC361 UNIX / Informix
BC362 UNIX / SAP DB LiveCache Administration
BC370 IBM AS400
Corresponding R/3 Basis Database
BC390 IBM /390
Knowledge Product and/or
**BC350 Workplace (combined with MY301)
SAP Expert Knowledge Book
Administration Training
 SAP AG 1999
 SAP‘s Knowledge Transfer Model
SAP B asis Administration Training 4. 6

Core Competence Expert Competenc e

MB C30 2 day s BC 50 5 3 d ays
R/3 -Tec hni cal Da taba se A dm inistra tion
Imp l eme nta ti on a n d OR AC LE
Op e rati o n Ma n age men t
BC 51 5 2 d ays
BC tcc * 5 da ys BC 30 5 3 day s Da taba se A dm inistra tion

Technical Training and

Tec hni cal C ore Adva nced R/3 SAP DB
C ompeten ce System Adm ini str atio n
BC 52 0 3 d ays
Empower ing Workshops - Application and Cross
Da taba se A dm inistra tion
BC 32 5 3 days
Application MS SQ L S erve r

Workshops
Softwa re L o gis tic s

Expert Knowledge
BC 53 5 3 d ays
Da taba se A dm inistra tion
Empowering WorkshopsDB2 UDB
EWA10 (SD) 2 days EWA12 (PP) 2 da ys
http://sapnet.sap.com/EducationServices
Book Series
EW A18 (CO) 2 days IBU specifi c
Tec hni ca l Op timi zation T ec hnical Opti mi zation and Glo bal
of Pr icing o f Bac kfl ushi ng of Tech nical Optim iz ati on
*T echn ical Core Co mpetence Versions Produc ti on Orders
of Pr ofi t ab ility Ana lysis W orksho ps
EWA11 (SD) 2 days
Tec hni
BC3 10 Windows ca/lOracle
NT Op timi zation EWA20 (PP) 2 da ys
of Due L ist Processin g
BC3 14 Windows NT M S SQL Serve r T ec hnical Opti mi zation
incl udi ng Sch edu lin g of MRP Run an d
BC3 17 (W indows NT / U NIX ) / DB2
EWA13 (SD) 2 days Lon g Term Pla nni ng
BC3 60 UNI X / Oracl e
C or res ponding R/3 Ba sis

http://sapnet.sap.com/Books
Te/cSAP
BC3 62 UNI X hni caDBl Op timi zation EW C13 (PP/ CO ) 2 days
of Batch Determi nation K nowle dge Pr oduct
 SAP AG EWC10 (SD/P P ) 2 da ys Tech nical Optim iz ati on
EWA14 (SD) (author)
1999 i
f e
l name 2 da/2ys o f Calculat i on of
T ec hnical Opti mi zation
Tec hni ca l Op timi zation Pro duc ti on Orders
of the Availa bil i ty Check
of Credi t Ma nag em en t
EWA15 (SD) 1 day EWC11 (S D/PP) 2 days
Tec hni ca l Op timi zation Techn ica l Op tim i zation
of Text Determin ati o n o f Configu rati o n
of Va riants
EWA16 (SD) 1 day
Tec hni ca l Op timi zation
of Pr oduc t Sel ectio n
EWC16 (S D) 2 days
EWA17 (SD) 1 day T ec hnical Opti mi zation
Tec hni ca l Op timi zation S hi pp i ng an d
o f Partn er Dete rm in ati on W are hou se M an ageme nt

 SA P AG KTMmyS AP .c om for Techn. Impl. , IT Cons. , Sys. Integrat io n UH / 7

SAP GoingLive Check http://sapnet.sap.com/GoingLiveCheck

SAP EarlyWatch Service http://sapnet.sap.com/EarlyWatch

SAP EarlyWatchAlert http://sapnet.sap.com/EWA

SAP Consulting Services http://sapnet.sap.com/ConsultingServices

http://sapnet.sap.com/BasisKnProd
TeamSAP Support http://sapnet.sap.com/TeamSAPsupport
Knowledge
Products

Technical
Certifications
http://sapnet.sap.com/pa

http://sapnet.sap.com/TechNet
 SAP AG 1999
Introduction

1 Introduction 8 Software Logistics

2 Starting and Stopping 9 Users and Authorizations

3 System Administration
10 Spool and Print
Assistant

4 CCMS Configuration 11 SAP Data Archiving

5 Database Administration
12 System Monitoring
and Backups

6 DB Administration:
13 SAPNet
Periodic Checks

7 Background Processing

 SAP AG 1999
Introduction

Contents
 Review of essential R/3 terms and concepts
 Outline of some basic R/3 System steps
(as described in SAP50)

Objectives
At the end of this unit, you will be able to:
 Explain certain important R/3 concepts and terminology
 Describe the system steps triggered during an R/3 logon
or while a transaction is being executed

 SAP AG 1999
Data Structure of R/3 Systems

Application Data
(Sales Orders, ...)
User
(Authorizations,
User Master
Client-specific Customizing Record, ...)
(Company Code, Plant, Warehouse, Client
Sales Organization, Personnel Area, ...)

Cross-client Customizing

Repository
(Dictionary, Reports, Transactions, Development
Function Modules, ...) classes

Basis FI CO HR PP MM SD ...
 SAP AG 1999
R/3 System Logon Steps

Ex.: IP: a.b.c.73

Ex.: IP: X.Y.Z.10 SAP GUI
2 10
IP: X.Y.Z.20 1 IP: X.Y.Z.10
3
M
Dispatcher Dispatcher
4 9

D V E B S ... D V B D ...

8
5

Database processes
7
6

Database
 SAP AG 1999
Defining Instance and Application Server

Instance A Instance B

Dispatcher Dispatcher

S S ... B ...

Central Instance C

Dispatcher

Message
D V E B S ... server

 SAP AG 1999
System Dialog Step

Dialog request queue

2 Dialog work process
1 3 5 Taskhandler

Dynpro processor 6

Dispatcher
Dispatcher
GUI

9
SAPGUI

8 ABAP processor
SAP

Database interface

12 10

Roll in 7
4
Roll out
11

User context in main memory Database

 SAP AG 1999
Work Process Multiplexing

Dynpro100
Request queues
Dynpro200 SAP GUI
... ...
9 18
Request queues
1 10 2 11
M
Dispatcher Dispatcher
8 17
3 12

D V E B S ... D V B D ...
7 16

4 13

Database processes
6 15
5

14

Database
 SAP AG 1999
Summary of this Unit

In this unit, you have reviewed the following:

 The steps executed in R/3 during logon

 The terms “instance” and “application server”

as used in the R/3 environment
 Processing of a system dialog step

 Work process multiplexing as performed by

dialog work processes

 SAP AG 1999
Further Documentation

 SAP50 - Basis Technology

 SAP Technology Infrastructure

Brochure available in SAPNet under:
Information  R/3 System  Basis Technology
 SAP Online Documentation

 SAP Notes:
 39412 Number of workprocesses
 21960 Two instances on one computer
 5424 FAQ: enqueue/locking
 and others in BC-KRN-CST

 SAP AG 1999
Starting and Stopping

1 Introduction 8 Software Logistics

2 Starting and Stopping 9 Users and Authorizations

3 System Administration
10 Spool and Print
Assistant

4 CCMS Configuration 11 SAP Data Archiving

5 Database Administration
12 System Monitoring
and Backups

6 DB Administration:
13 SAPNet
Periodic Checks

7 Background Processing

 SAP AG 1999
Starting and Stopping

Contents
 Processes and services in an R/3-NT-MS SQL
Server environment
 Start and stop processes and procedures

Objectives
At the end of this unit, you will be able to:
 Explain the concept of services used by R/3 and MS SQL Server
 Describe R/3 start and stop processes
 Explain the relationship between database processes, R/3
processes, and operating system processes
 Start and stop an R/3 System
 Analyze error situations during startup or shutdown

 SAP AG 1999
Overview of Processes and Services

MS SQL Server
database process R/3 processes

... ... ...

Database services Operating system R/3 services
services

Operating system: Windows NT

 SAP AG 1999
Starting R/3: Operating System Tasks

Operating system: Windows NT

NT Service Control Manager NT

Registry

MSSQLServer
SAP<SID>_<Instance no.> SAPOSCOL ... Services
SQLServerAgent

 SAP AG 1999
Starting R/3: R/3 Administrator Tasks

Operating system: Windows NT

Logon
1
Start 2 Microsoft Management Console
via SAP R/3 Systems Snap-in
<SID>adm

3 4 5

Database Central Additional

Start Instance Instance

 SAP AG 1999
Starting R/3: Process Startup Sequence

Microsoft Management Console

Start profile
1 Message via named pipe

NT Services SAP<SID>_<instance no.>

2
3

4
Default and instance profile
MS Disp+work.exe
R/3 Processes
D V E B S ... 5
6

Database Processes

 SAP AG 1999
Parameter Read Sequence

Instance profile
3 <SID>_<INSTANCE>_<hostname>

2
R/3 work Default profile Parameter
processes DEFAULT.PFL read / replace
1 sequence
• R/3 kernel
• NT system
environment
variables
• NT Registry
environment
variables

 SAP AG 1999
Database Logs

<drive>:\Mssql7\Log\...

Errorlog
Errorlog.1
MS SQL Server
MSSQLServer Errorlog.2 error log
Errorlog.3 files
Errorlog.4
Errorlog.5
Errorlog.6

Sqlagent.out
Sqlagent.1
Sqlagent.2 SQLServerAgent
Sqlagent.3 message files
Sqlagent.4
Sqlagent.5

 SAP AG 1999
Startup Logs and Traces in Windows NT

SAP<SID>_<no>

Event Viewer - … Log on \\Host1

SAPOsCOL
Date Time Source Category Event
MSSQLServer
25.06. 14:22 SAP None 2405
Services

MMC SAP R/3

System Snap-in
System Security
log log

Application
log
Windows NT

EVENTLOG log files

 SAP AG 1999
MMC SAP R/3 Systems Snap-In

General overview of
key SAP processes

Current statistics on
major system and
SAP components

Alert statistics from

CCMS monitoring
sets in RZ20

Process overview Information and

Process queue
information errors in the
statistics
SM50 R/3 System log

 SAP AG 1999
Startup Logs and Traces in R/3

\\<SAPLOCALHOST>\saploc\<SID>\<Instance><No>\work\ ...

Standard error files of R/3 startup procedure

executed by SAP service SAP<SID>_<instance no.>
stderr1 … 3

sapstart.trc Trace files of program SAPNTSTARTB

Startup log and trace files of the database,

sapstart.log message server, and dispatcher

dev_ms Trace file of the message server

Trace file of the dispatcher

dev_disp

Trace files of the work processes

Time dev_w0 … n

 SAP AG 1999
Startup Diagnostics

MMC

SAP<SID>_<instance no.>
Event Viewer
MSSQLServer Services
Date Time Source
SqlServerAgent 25.08.14:22 SAP

R/3
Sqlagent.out
central
Errorlog instance R/3 System log

R/3 trace files

 SAP AG 1999
Reasons for R/3 Downtime

Planned Downtime
• Profile parameter changes

... Start / Stop ...

Parameter_1 = 0 Parameter_1 = 3
Parameter_2 = 0 Parameter_2 = 5
Activation

R/3 System
• System maintenance, upgrades of
operating system, database, or R/3 ad e
g r
Up
Unplanned Downtime
• Hardware failure
• Configuration problems

Data

 SAP AG 1999
Before Stopping the R/3 System

 Check background and batch input jobs with SM37

and SM35:
SAP R/3
 Are any jobs active/planned? Display System Help

 Will R/3 jobs be triggered from external systems? Job log Display Release

 Check update status with SM13

 Send system message with SM02
 Check logged-on users with SM04
 Check external interfaces

R/3 System
External
application

 SAP AG 1999
Stopping the R/3 System

R/3 <SID>adm
administrator

Edit Select Monitoring Control Utilities System Help

?
ChooseRefreshDetails Choose

MMC SAP R/3 SQL Server NT Service

System Snap-in Service Manager Control Manager
R/3 CCMS

2 3
1a 1b
SAP<SID>_<Inst. No.>

MSSQLServer SAP Slave Service

R/3 R/3
additional central SQLServerAgent SAPOSCOL
instances instance

 SAP AG 1999
Database Maintenance: Database Reconnect

Instance profile

Dispatcher
R/3 buffer
preserved
WP ... WP gwrd

Application server
running in status reconnect

Database server
down MS SQL Server
 SAP AG 1999
Stopping R/3: Error Diagnostics

SQL Server Service Manager _ x

Server: NTServer

Services: MSSQLServer

Start/Continue
Start/Continue

Pause

Stop

Auto-start services when OS starts

\\NTServer - MSSQL Server - Running

Database cannot be stopped

MSSQLServer

 SAP AG 1999
Summary of this Unit

Now you are able to:

 Explain the services used by R/3 and MS SQL Server

 Describe R/3 start and stop processes
 Explain the relationship between database processes,
R/3 processes, and operating system processes
 Start and stop an R/3 System
 Analyze error situations during startup or shutdown

 SAP AG 1999
Unit Actions

?  Exercises

 Solutions

 SAP AG 1999
Starting and Stopping: Exercises

No. Exercise
1 Prepare your R/3 System to start
1.1 Log on to the operating system as user <sid>adm. What services related to the R/3 System are activated by
the operating system?
1.2 Check if an R/3 System is already running.
1.3 If your R/3 System is active, shut it down.
1.4 If the database is still running, shut it down.
2 Starting
2.1 Start your R/3 System using the MS Management Console. Trace the startup phase by monitoring the
processes of your system using the Task Manager.
2.2 Which processes are running at the end of the startup phase?
2.3 Check the log files and the trace files for errors and warnings, and analyze the causes.
2.4 Log on to your R/3 System
2.4 Compare the processes that are displayed in the R/3 Process Overview with the work processes displayed at
operating system level.
3 Stopping
3.1 Which users are active in your system? Send them a message that you are stopping the system.
3.2 Stop the R/3 System using the MS Management Console. Shut down the database.
No. Solution
1
1.1 Use the NT Service Manager. In addition to other services, two R/3-related services are displayed: SAPOSCOL and
the R/3 Service SAP<sid>_<Instance No.>.
1.2 Start the MS Management Console. Expand the SAP R/3 Systems snap-in. If the icon for the R/3 System is green,
the R/3 System is running.
1.3 In the MS Management Console, select the R/3 instance and choose Action  Stop. If necessary, repeat this
action on the central instance.
1.4 Start the MS Management Console. Stop the Database Services. In the MS Management Console, select the
server, then choose Action  Stop.
2
2.1 Use the Windows NT Task Manager. Choose Processes.
2.2 Use the Task Manager of Windows NT. Choose Processes.
Look for disp+work.exe, msg_server.exe
2.3 Check the log and the trace files in the directory \usr\sap\<SID>\<Instance Name>\work, in particular, the
dispatcher trace file dev_disp and the trace files of work process 0 and 1 (dev_w0 and dev_w1,
respectively).
2.4 Select the R/3 System from the SAP Logon Menu.
2.4 From the R/3 main menu, select Tools  Administration  Monitoring  System monitoring  Process overview
(Transaction SM50) and use Quick Slice. Compare the number of work processes. The OS output displays
one more process, the dispatcher.
3 Stopping
3.1 To display the users active in your R/3 System:
From the R/3 main menu, select Tools  Administration  Monitoring  System monitoring  User overview
(Transaction SM04), and Tools  Administration  Administration  System Messages (Transaction SM02).
Or select Tools  Administration  Monitor  Performance  Exceptions/Users  Active users  Users
global (Transaction AL08).
3.2 Compare 1.3 and 1.4.