Professional Documents
Culture Documents
1 SAP R/3.........................................................................................................................2
1.1 TABLES.................................................................................................................2
1.2 TRANSACTIONS..................................................................................................3
1.2.2 ABAP-related..................................................................................................2
1.2.3 Backgroundjob-related....................................................................................2
1.3 COMMANDS........................................................................................................5
1.5 PROFILEPARAMETERS.....................................................................................5
1.6 USERIDS...............................................................................................................5
1.7 LOGFILES.............................................................................................................6
2 Database........................................................................................................................4
2.1.1 Database-commands........................................................................................4
2.2 ORACLE................................................................................................................4
2.2.2 OSlevel-commands..........................................................................................4
2.2.3 Brbackup/brrestore..........................................................................................4
2.3 MS SQL..................................................................................................................9
2.4 DB 2/400..............................................................................................................10
3 Operating system...........................................................................................................6
3.1 GENERAL...........................................................................................................10
3.1.1 ftp.....................................................................................................................6
3.2 UNIX......................................................................................................................6
3.3 NT.........................................................................................................................12
4 General issues...............................................................................................................8
4.1.1 dbmon..............................................................................................................8
4.1.2 gwmon.............................................................................................................8
4.1.3 R3load..............................................................................................................8
4.1.4 R3setup............................................................................................................8
4.1.5 R3trans.............................................................................................................8
4.1.8 saprouter..........................................................................................................8
1 SAP R/3
This document is created to get a comprehensive list of all actions that I have taken
during the maintenance of the SAP. This to make sure that I forget as little as possible.
This document can be a good handle for basis consultants who are starting on the job.
1.1 Tables
DBSTATC status of statistics-information per SAP-table
E070 Change-requests and their tasks and properties
E071 Objects in change-requests
KNA1 Necessary at sapscript-ABAP’s
MARA Materiallist
PAT01, Supportpackages and their status, also see table TEPSIN
PAT03
TBATG Holds runtime-transportinformation (don’t know yet what it exactly
holds)
TBTCO Batchjobinformation
TTZZ Timezones.
USR01 Userdata
~ ...12
1.2 Transactions
Good advise: don’t learn the transactioncodes by heart at first, but use the menu-paths.
This way you will sooner get an overview of the systems possibilities.
SM21 Systemlog
SM37 Check the batchjobs
SM50/51 Show all processes on one server / all servers
SM66 Show all active process on the system
ST11 Display developer-traces
ST22 ABAP-dumps
1.2.2 ABAP-related
1.2.3 Backgroundjob-related
1.3 Commands
/$sync Synchronise the buffers. ABAP’s on the application servers will be
refreshed, so possibly changed. Not recommended on productionsystems
in use.
/h Turning on the debugging mode
/n New command
/o New session
1.5 Profileparameters
rdisp/* gui-parameters
rdisp/gui_max_wait maximum time of no response (in 3.x: rdisp/gui_auto_logout)
1.6 Userids
SAP* Sapsuperuser, has all authorizations. Its default password is available in the
OSS.
CPIC eh
1.6.2 Userids on databaselevel
SAPR3 User that connect SAP R/3 to the Oracle (or SQL or ..) database
During changing the Transport Management System using STMS you need to be logged
on as TMSADM in client 000 on the transportdomaincontroller.
1.7 Logfiles
SAP logs almost any action and has a lot of trace-options. Here is a short listing for them:
developertraces, viewed via ST11 or SM50 and doubleclick the process (as of 4.x),
stored in /work
dev_wX log for workproces number X
dev_ms log for workproces for the messageservice
dev_gw log for workproces for the gateway
dev_disp log for workproces for the dispatcher
dev_tp log for workproces for the transports
1.8 Traces
ST05 (System, Utilities, Performance trace) allows you to set a trace per user,
transaction, program or process-id.
SM50. Here you see the processes. Per proces you can see it’s corresponding
tracefile via button ‘Show file’. The default trace-level is 1. You can change the
tracelevel via Process, Trace, Dispatcher, Change tracelevel (of all processes, not per
process).
2 Database
2.1.1 Database-commands
The V$-files contain the dynamic performance tables which hold the runtime information
of R/3. To see all V$-files listed, go to ST04, detailed analysis, button display V$ values.
alter tablespace <tablespacename> end backup; the tablespace will end its status of being
backed up.
drop tablename from ??; deletes the table from the database.
2.2 Oracle
2.2.1 important files
init<SID>.ora
init<SID>.sap
init<SID>.dba
2.2.2 OSlevel-commands
smit (or smitty) characterbased menu for handling of filesystems, logical volumes,
drives etc.
2.2.3 Brbackup/brrestore
BRRESTORE –m file01/dir01 .. filen/dirn restore the backup and places the files in the
given directories instead of the original directories
2.3 MS SQL
2.3.1 Services
SAP<SID>_<Instance-number>
SAPoscol
sp_helpsort show the SQL-server’s sortorder and characterset (thus the codepage)
2.4 DB 2/400
enddbmon stop the databasecollector-program when it is running
3 Operating system
3.1 General
3.1.1 ftp
3.2 UNIX
chgrp grp Change the group that the file(s) belong to.
filelist
chmod 777 Change the rights of the file(s). 777: owner-world-user. 7: read-write-
filelist delete (=111)
chown user Change the owner of the file(s)
filelist
cp file1 file2 Copy file1 to file2
cp /dev/null Clear all contents of file
file
errpt Hardware error-report (IBM-unix)
ls –ltr <dir> Show filelist, –parameters: l: show fileattributes , t: sort by time, r:
reverse sortorder
more <dir>
mv file1 file2 Move command
ps –ef Show all running processes, -e, -f
vi The famous vi-editor
kill <PID> Kill a process as if it is cancelled. Child processes are killed as well.
kill –1 <PID> Kill a process as if the user is logging out. Child processes are killed as
well.
kill –9 <PID> Kill a process as brutal as possible. Child-processes are not touched.
kill –USR2 Increases TRACE by 1
<PID>
kill –USR1 Decreases TRACE by 1. When TRACE = 0 all open trace files are
<PID> closed and can be cleared using ‘cp /dev/null filename’.
lslv Show the logical volumes
lsvg Show the volumegroups
sappfpar check Checks the profileparameter. Do they exist and do they have correct
pf=<profile> values.
set VAR VAL set environment variable VAR to value VAL
printenv prints the environementvariables
ps –ef |grep Monitor processes with name containing xxx
xxx
ps –u Monitor processes run by user <username>
<username>
Crontab
To schedule tasks you have to edit file crontab. Every line starts with five numbers and
then a command. The numbers stand for minute, hour, day-of-month, month-of-year, day
of week (0 for sunday).
Detailed UNIX-commandlist
To get detailed information about every UNIX-command available and lots of articles,
see site
AIX: www.rs6000.ibm.com/cgi-bin/ds_rslt
3.3 NT
at Schedule anything.
hostname Shows the hostname
ipconfig /all Show all ip-addresses of the system
ipcs –m Show all IPC-processes
ipcrm –m Kill ipc-process <process>
<process>
regedit / Edit the registry. (for instance HKLM, software, SAP)
regedt32
sapntchk Checks the system, its ip-adresses, running processes etc.
ntenv2reg Copy the environmentsettings to the registry to secure them
ntreg2env Copy the registry to the environmentsettings
4 General issues
4.1.1 dpmon
This tool allows you to check SAP’s processes and to find out which one is killing the
performance. Especially useful when it is not possible anymore to log on to your system.
4.1.2 gwmon
This tool allows you to check if the gateway is running. It is an addition to transaction
SMGW.
4.1.3 R3load
4.1.4 R3setup
4.1.5 R3trans
Sapdba is run to collect the data for the optimizer. This is done in two steps: First
‘SAPDBA –checkopt PSAP%’ checks which optimizerdata needs to be updated, then
‘SAPDBA –analyze DBSTATCO’ gathers the data of the objects to be updated.
Request the license for the system by sending the fax included in the installation-kit to
SAP.
4.1.8 saprouter
As of version 4.0 there is no more need for us to go down to the os-level. Everything can
be done with transaction STMS. Nevertheless the tp-commands are still be useful and
needed in some cases (yet). for detailed information on tp-command, see OSS-note
309711.
4 Warning
8 Error.
>1000 Returncode with extra information, but only the last three digits are relevant
The file TP_<DOMAIN>.PFL (used to be TPPARAM) in this directory holds the tp-
parameter-settings
filesplit=yes|true|on Export will be split into files of size 2147483647 (2GB-1). Useful
(default=no) for OS’s that can not handle files larger then 2GB.
SAP Directory structure is a files and folder locations in a computer after installation of sap system. we have to understand
this directory structure to understand the concept of TMS, PATCH Management and System profiles. There are 3 folders
resides in 4.7 system are sapinst, usr and oracle. sapinst always will be located in c:\sapinst and oracle and usr directories
will be located in either D: or E: according to the selection of drives while installation. There are some important
directories to understand in sap system to do basis administration in cool manner. The directories and it’s importance
are…
1. C:\sapinst (4.7) or C:\Program Files\sapinst_instdir (ECC 6.0): This directory stores all installation logs along
2. \usr\sap: usr stands for unix system resource and the shared names of SAP are sapmnt and saploc. sapmnt is
used to by sap server to access system specific information and saploc is used by sap server to access local
information
4. /usr/sap/trans/bin: This directory stores all the configuration of TMS in the form of TP_DOMAIN_SID.PFL
5. /usr/sap/trans/cofiles: This directory is used by profile to store the information about released or exported
6. /usr/sap/trans/data: Data folder stores the physical program or table in the form of r<no>sid once the
7. /usr/sap/trans/EPS/in: EPS stands for Electronic Parcel Service and in stores all the uncared or unzipped
9. /usr/sap/sid/sys/exe/run: RUN directory stores all the executables through which sap functions and it is called
as kernel directory
10. /usr/sap/sid/sys/profile: These are called system profiles. There are 3 system profiles. They are start, default
and instance profiles and are in the form of DEFAULT.PFL, START_DVEBMGS00_Hostname and
DVEBMGS00_Hostname