SM50

to check the status of wp of an instance.

DIA, BTC, UPD,SPO,UPD2 & ENQ
2 background process are required because to continously monitor two tables TRBAT &
TRJOB.

SM66 - Global Process overview

SM51 - Server status

TR
format as: <SID>K<Number>
Cofile : having the attributes of data file. Co-file is created “K”, Co Files
contains the controlling data
Data file : having the data file is created “R”, Data files contain the database
details.

SM21:
--------------------------------
Problems Only
Problems and warnings
All message

Time Stamp
Type of work process
System Number
Client Number
User id (who executed the transaction)
Tcode executed
Priority
Text related to the issue

if additional details are required related to dumps, they can check in ST22
transaction.

Action we take depends on the type of issue we encounter in system log.

For eg: If spool overflow error, we may need to run spool cleanup related work
If update deactivated, you may need to activate the update
If communication problems, you may need to check network for any connectivity
issues
If license expired, you may need to apply new license etc

Parameters - used to configure

RZ10 - Static Parameter
rdisp/wp_no_dia
rdisp/wp_no_btc
rdisp/wp_no_vb
rdisp/wp_no_vb2
rdisp/wp_no_enq
rdisp/wp_no_spo

RZ11 - Dynamic Parameter(TPFYPROPTY)

rdisp/max_wprun_time
rdisp/TRACE
rdisp/gui_auto_logout
rdisp/j2ee_start
rdisp/keepalive
rdisp/max_priv_time
rdisp/max_alt_modes
rdisp/wppriv_max_no

PRIV Mode:
if the particular open transaction process has taken up all the memory in the
extended memory, and then finally it starts taking up memory from Heap memory.
When a work process starts using Heap memory, it goes into PRIV mode.
rdisp/max_priv_time
rdisp/wppriv_max_no
ABAP/heaplimit
em/initial_size_mb

SM37 - long running job troubleshooting

Using ST05 or ST12, a trace can be taken for background job to figure out where
exactly time is being consumed
and to identify various cpu/memory bottlenecks or any buffer issues.
STAT/STAD transcation can be used to figure out what is the reason for high
response time and actions can be taken accordingly

STAD: Business transaction analysis

sap*
----------
login/no_automatic_user_sapstar=0, we can login with default password - PASS
login/no_automatic_user_sapstar=1, logon not possible with default password - PASS
Afterwards,
sqlplus “/ as sysdba”
Delete from SAPSR3.USR02 where MANDT=’000’ and BNAME=’SAP*’;

Extraction and Compress:

----------------------------------------
SAPCAR -xvf <filename.SAR> - Extract
SAPCAR -cvf <filename.SAR> - Compress
SAPCAR -tvf <filename.SAR> - list of files

Long running Transport issue:

-----------------------------------------
File system or tablespace full issue
no free background wp
RDD* jobs not running
Update got deactivated

system performance slow, users not able to connect

Oracle Architecture - Db instances/Processes(Pmon,Smon,DBWR,LGWR/DB system

STMS
Creating Domain controller
Adding systems to controller(can be approved from Doamin controller)
Transport route creation

Source:
30.201.0.33
30.201.0.34
Destination:
172.28.234.22
Port:
139, 445
Long Running Job
1. identify the wp details like server/pid on where the job is running.
2. identify the status of the job is it onhold/running.
3. identify what action being performed with the job like sequential
read/rollin/rollout/insert/delete/update.
4. if it is sequential read identify the table

Activate SAP*
login/no_automatic_user_sapstar to 0
Delete from SAPSR3.USR02 where MANDT=’000’ and BNAME=’SAP*’;

Schedule Standard Jobs

SM36 - standard jobs - default scheduling
These jobs will perform housekeeping in our system.
deleting old spool requests, deleting old background jobs/logs/updates/batch input
sessions/ABAP short dumps,
collecting operating system/database level statistics.

Spool Overflow
Spool request that got generated are stored in a temporary sequential file called
Temse
The default size of Temse is 32,000 and it can be increased till 2 billion.
SPAD - Delete old spool requests with minimum age setup
RS00041 or RS00043 reports.
RZ20 - sap ccms monitor template - spool system
spool number range can be setup using SNRO and object SPO_NUM

In a situation where My SAP system is down (Users unable to login to SAP system),
how to analyze the problem?
Check the Database status
SAP services
SAP management console ( Dispatcher, IGS and Message Server)
You need to find out trace root on the basis of point at serial no ( c ).
Check network connectivity if everything is ok

SAP note: to update single transaction/program

Kernel: to update the .exe files
Support Package: to update the bulk no.of things

STMS:
Creating Domain if not exist
DOMAIN.CFG file in user/sap/trans/bin directory
Adding systems to domain
Configure the transport routes

KT - client-specific data
KO - cross-client data
KX - client specific texts and forms

Refresh:
Update BTC parameter and start system
Clear the old logs from global directory
Update the license from os/sap
run the BTCTRNS1 report to suspend the prod jobs
Delete the old jobs using RSBTCDEL2 report
Reinitialize TMS and import the required TRs to update the configurations.
SCOT - revert back the same settings
run the report RDDNEWPP - schedules the transport dispatcher RDDIMPDP.
SAP Profile Parameter - Delete the all versions of a profile - related to
Production entries and import new profiles.
Operation modes - Delete all the production entries/ add the new entries in RZ04.
SMLG - logon groups and RZ12 - RFC server groups
User master import - SCC7 Post client import before importing open client in SCC4.
Printer import - SPAD, SP01, SP02 - to check if any stuck spool
BDLS - Conversion of Logical System Names, SLG1 with the object CALE and the
subobject LOGSYSNAME
Queue Registration - SMQR/SMQ2 - inbound and SMQS/SMQ1 - outbound
Partner Profiles - WE20, IDOC ports - WE21

SPAM for Support packages/SAINT for Add on's

ST-PI and ST-A/PI are SAP add-ons that contain application-specific data collectors
which contribute to Service Data Control Center (SDCCN). ST-PI basically provides
various function modules and SAP reports which assist in the data collection
process. Whereas ST-A/PI contains standard tools like ST14, ST12, and RTCCTOOL. So
we need to keep these add-ons up to date on all the ABAP systems.
Pre-requisite, Import abap queue - phases in spam/saint - Preperation Module,
Import Module1,2,3. - DDIC_Activate, DDIC_Import,Import_Proper
tp system log
types of logs in spam/saint
QueueCalculation/Import log/Action log

Kernel: The Kernel is a central program which acts as an interface between SAP
application and operating system.
The Kernel is the heart of the operating system. It contains those files which are
used to run every event in SAP.

Types of RFC,
sRFC - when acknowledgment is necessary - both systems needs to be available
AsRFC - acknowledgement not necessary - target system not needs to be available -
data loss may happen as target system sometimes not available.
tRFC - Extension of Asynchronous RFC, secure communication, it holds rfc dest and
data in the TID.
qRFC - Extension of TRFC, individual steps are processed in sequence

Performance issues troubleshooting:

SAP EarlyWatch Alert reports SAP Solution Manager Diagnostics Transaction ST03N for
workload analysis SQL Trace and SAP Performance traces System monitoring tools like
SAP Solution Manager or third-party monitoring tools