CATEGORII DOCUMENTE |
Bulgara | Ceha slovaca | Croata | Engleza | Estona | Finlandeza | Franceza |
Germana | Italiana | Letona | Lituaniana | Maghiara | Olandeza | Poloneza |
Sarba | Slovena | Spaniola | Suedeza | Turca | Ucraineana |
DOCUMENTE SIMILARE |
|
TERMENI importanti pentru acest document |
|
SAP Basis Training
SAP Architecture
R/2 vs R/3 Architecture:
R/3 Landscape Reebok:
PRD Layout:
SAP Application Layer
SAP Communication:
SAP Basis
System Monitoring From SAP:
AL08
DB01
SM12
SM21
SM36
SM37
SM50
SM51
SM66
ST04
System Monitoring From Unix:
Glance Plus
Onstat
Sar
Reporting Performance Issues:
Issues Affecting The Whole System:
Issues Affecting Only One User:
Heads Up:
Daily Status Report:
Informix
Informix Architecture:
Informix Information
Onstat:
SAPdba:
Onmode & Oninit:
Informix Information From SAP:
SAP Users And Security
Security Overview
Transaction Codes
SU01
SU53
System Support Menu (unknown transaction code)
ZAUT
Correction In Transport System (CTS)
Transport Layout
Transports From SAP
Manual Transports
R/2 (host based) R/3
(client/server 3 tier)
This transaction code shows a list off all user currently logged on to the SAP system (all app servers).
This transaction codes will display table locks.
This transaction code will display the enqueue locks.
Fill in the selection criteria as you want them and hit the list button at the top.
This transaction code is used to see the system log files.
After you have filled in your selection make sure to choose system log, choose, all remote system logs before you hit the read log button.
This transaction is used to schedule a background job.
This transaction code is used to display background (or batch) jobs submitted by users.
After making your selection hit enter.
This transaction code is used to display all the work
processes on the current apps server.
This transaction code is used to display a list off all the
running apps servers. There should be 12 apps servers running at all times.
By double clicking on one off the servers in the list you will
then see a listing off all the workprocesses on that server (same as using
sm50). Note: you will also connect to that server.
This transaction code will display a list off all current running work processes on all the apps servers. It doesnt refresh itself automatically so hit <enter> or select the refresh button located at the top.
The list can be sorted by selecting a colum and hitting the sort button located at the top.
This transaction code will bring up the Informix database overview. It displays information about the current use of the database
If you select the detail
analysis menu using the button in the top bar you will see the screen shown
below.
Here the button informix session is very usefull because the screen it brings up will help you map the PID to the SID.
Glance is an unix command used to show system usage. It must be run as root or superuser.
Onstat is an informix status command. It must be run on the informix database server as user informix. There are a few possible options:
$ onstat -l
$ onstat m (shows the tail off the informix log)
$ onstat g sql SID
$ onstat u r |grep SID
Sar is used to display disk activity on the unix box.
#sar g 5 5
If there are system wide problems makes
screenshots off the following transactions and send them to SAP Basis in the
sm66
al08
sm12
db01
sm51
# glance
# sar d 5 5
# onstat -l
If there are user specific problems make captures off the following transactions:
sm50
st04
sm37
# onstat u r |grep SID
If you do find anything in the list below pass on a general heads up to the Basis team so they have an idea where to look.
sm21
st22
sm13
ST11
Informix log (onstat m)
For the daily report send a mail message with:
Short dumps (st22)
System Log (sm21)
Update errors (sm13)
Reported user problems
A database is made up off database records. These are made up
of chunks (of raw disk space) which comprise pages of data. A data page will be
loaded into RAM. At that time an entry will be made in the physical log.
Changes are then made to the page in RAM and an entry added to the logical log.
If the database should crash, the physical and logical logs can be used to
restore database integraty.
All informix commands are run on the database server as user informix.
Onstat is used for a number off things.
onstat - : will show if informix is up and running
onstat m : tail of the informix message log (located in: /informix/<SID>/online.<machinename>.<sid>.log). Checkpoint shold be 7 secs
onstat -- |more : help on onstat
This displays information about the database for SAP. More than you can get from SAP but without the SAP protection of itself!
onmode -- : help on onmode
onmode yuck : SHUTDOWN informix db
oninit : start informix db
db02
st04
dpspace should be < 95%
There are 2 levels of security in SAP
Transaction Code
Authorisation
This lets you lock and unlock users.
This transaction code is used for displaying authorisation problems. If a user has an authorisation issue this screen can tell you why.
This is a handy menu that has a few off the essentials close
at hand, such as locking/unlocking users, assigning PSA accounts (temporary
accounts for testing purposes should not be active for more than 5 days, 3 is
prefferable to 5), printers, etc.
This is the tools for user maintenance. Requesting new users, changing authorisation, etc.
Use transaction ztms to view the transports and if they have been approved. If you need to do transports look at the cheat sheet Bill made.
For a few systems you have to do manual transports (like ARC). To do this:
rlogin to the box
su <sid>adm
cd /usr/sap/trans/bin
tp addtobuffer RET<transportnumber> SID
tp import RET<transportnumber> SID client050
Politica de confidentialitate | Termeni si conditii de utilizare |
Vizualizari: 1264
Importanta:
Termeni si conditii de utilizare | Contact
© SCRIGROUP 2024 . All rights reserved