23 Administration

SAP Administrator Daily Activities

SAP DAILY ACTIVITIES
1] Check that all the application servers are up:
sm51
SAP Servers
sm04/al08 Logon Users
2] Check that daily backup are executed without errors
db12 Backup logs: overview
3] SAP standard background jobs are running successfully. Review for cancelled and critical jobs.
sm37 Background jobs--- Check for successful completion of jobs. Enter * in user-id field and verify
that all critical successful jobs and review any cancelled jobs.
4] Operating system Monitoring
st06
5] Extents monitoring
db02 Database monitoring--Check for max-extents reached
6] Check work-processes(started from sm51)
sm50 Process overview-- All work processes with a running or waiting status.
7] Check system log
sm21 System log-- Set date and time to before the last log review. Check for errors ,warning, security,
message-bends, database events.
8] Review workload statistics
st03 Workload analysis of <sid>
sto2 tune summary instance
9] Look for any failed updates
sm13 update records
10] check for old locks
sm12 lock entry list
11] Check for spool problems
sp01 spool request screen-- check for spool that are in request for over an hour.
12] Review and resolve dumps
st22 ABAP Dump analysis
13] Checking .trc file in SAP trace directory for block corruption on daily basis.
C:\ORacle\sid\saptrace
14] Archive backup
brarchive -f force -cds -c
Insert the archive backup tape
15] Review NT system logs for problem
-> NT system log- look 4 errors or failures
-> NT security log- failed logon 2 sap servers
-> NT Application log -look 4 errors or failures

Tcodes used for Daily System Monitoring

After running daily system monitoring transaction, what should we check for:
In st22 look for the core dumps if any and report to the respective consultants and try to know why it
happened.
In sm21 try to check for errors.
In sp01 try to see if any spool jobs have failed.
In st02 look if any swaps are happening, swaps are not good for performance.
In st04 look for Database alert logs and Performance.

In st03 look for ratio hits.

In sm59 look for connectivety tesing if there are other systems also connected to your SAP R/3 system
In db13 look if the jobs have run successfully.
In sm37 look for any cancelled scheduled job and take action appropriately.
In sm12 look for any pending locks from the previous days.
In sm13 look for any hanged updates, or updates pending for long or updates in PRIV mode.

Monitor and Administrate 4 SAP Systems

If there are 4 systems installed SAP, how should I connect all of them in one network so that I can
administrate the 4 systems with one among them as main server.
This should help you:
After installing an R/3 System, you can use transaction RZ20 to monitor the system. To monitor
all systems of your system landscape centrally from one system, first customize the alert monitor by
choosing Tools > CCMS > Configuration > Alert monitor or calling transaction RZ21.
Then, to specify the remote systems by System ID and RFC destination (which must have been
created beforehand), choose Technical infrastructure > Create remote monitoring entry.
Next, to change your monitor definitions (you can only change your own monitors), choose Tools >
CCMS > Control/Monitoring > Alert monitor or call transaction RZ20.
Activate the maintenance function by choosing Extras > Activate maintenance function.
Then,
double
click
on
the
monitor
and
choose
Monitoring
change.
Parameter R3system defines which systems can be monitored by an alert monitor. Change parameter
R3system from <CURRENT> (only the current R/3 System can be monitored) to <ALL> (all R/3
Systems defined in RZ21 can be monitored). Save the changes.
It will help you monitor & use spome other activities centrally.

Things To Check When SAP System Down

How to troubleshoot my sap system when it was down? What are the things I have to check?
A Basic Technical Troubleshooting:
Perform initial analysis.
Identify if something has changed (software or hardware installation, scripts, profile parameters,
database structure).
System (hardware) is down:
- Check console messages.
- Reboot and keep important system log files.
- Check hardware components.
- Analyze with diagnosis tools.
- Escalation procedure: call hardware support.
- Check main log files.
- Analyze with diagnostic tools.
- Start up/shut down log files.
- Check operating system log files.
- Identify other problems (startup/shutdown, disks and operating systems, database, operational R/3,
performance).
Startup and shutdown problems (R/3 and application servers):
1. Check processes or services at operating system level.
2. Check whether database is up.
3. Check connection with database (i.e., tnsping, R3trans).
4. Check whether file systems are full.
5. Check for network problems in the server network.
6. Check backup log for problems after backup.

7. Check for problems after system crash.

8. Check for problems with PDC file server.
9. Check files permissions and authorizations.
10. Manually start up or shut down database and then the application server.
11. Check hosts and services files.
Operating system problems:
1. Check operating system log and event viewers.
2. Check disks and file systems.
3. Check directories and permissions.
4. Check path names.
5. Check security.
Database problems:
- Starting and stopping database
- Refer to startup problems.
- Check database specific error log file.
- Database storage status
- Check database error numbers.
- Check database alerts.
R/3 application operational problems:
1. Check whether all users are affected.
2. Check whether there is no work at all, or whether work is just limited.
3. Check whether application servers are available (SM51). Check with standard monitoring transactions:
SM50, SM04, SM12, SM13, ST22, SM37, and SP01.
4. Check trace files on work directory (/usr/sap/<SID>/<instance>/work).
5. Check SAP systems alerts.
6. Analyze database problems.
Specific operational problems:Problems with printing:
A. Check network.
B. Check SP01/SPAD spool request logs.
C. Check system log.
Problems with batch input:
A. Check directories and files.
B. Check SM35 logs.
C. Check system log.
Problems with lock entries:
A. Check lock entries.
B. Check update process.
Problems with update process:
A. Check update process.
B. Check database.
C. Check network connections.
4. Problems with enqueue:
A. Check database.
B. Check instance parameters.
C. Check operating system processes.
5. Problems with message server:
A. Check processes.
B. Check network.
C. Check log files at work directory.
6. Problems with background processing:

A. Check job log.

B. Check background system consistency.
C. Check file systems.
D. Check system log.
7. Performance problems:
1. Perform workload analysis.
2. Perform debugging.
3. Perform runtime analysis.
4. Perform SQL trace.
5. Check for operating system problems.
6. Check disks for input/output bottlenecks.
Resolution process:
1. Search or SAPnet notes for hints, solutions, or workarounds.
2. Escalation: enter message on SAP hotline or SAPnet.
3. Enter problem on hardware partner hotline.
4. Follow problem actions and SAP indications.
5. Apply patches and corrections; test and verify results.

Brief Description About SAP Basis Implementation

Please give a brief description about implementation process carried out.
There is no standard Implementation process, it purely depends on which methodology person have
adopted for implementation. I will give you broad view of implementation project... I am just starting
from sizing of the servers ...
1. Identify the no of users and type of users
2. Design the technical system landscape of servers
3. Do the sizing based on users, documents created.
4. Convert your sizing requirement in to Hardware requiremnet
5. Consider the backup procedure also
6. Then start with the setup of development landscape
7. Define client strategy, transport strategy, User management.
8. Fix the support package levels.
9. Tune the system for performence
10. set up the QA systems
11. Define client copy strategy
12. Setup the PROD systems
13. Apply for Pre Golive report
14. Monitor system of db load
15. Apply post golive report

What Are The work responsibility for a BASIS person

By: Ahmed Mohamed
SAP Remote Basis Administration Service Task List
Recommended daily tasks
1. Check whether the systems are up
2. Check whether the backups finished without errors
3. Check for alerts in CCMS monitors
4. Check for hanging or stopped work processes
5. Check system log for errors/warnings
6. Check whether any background jobs got canceled for any reason
7. Check the lock entry list

8. Look for any failed updates

9. Check for users logins from unknown terminals/locked users
10. Analyze program dumps
11. Check for excessive swaps and buffer statistics
12. Review Database performance
13. Check database for space critical objects
14. Check the average response times
15. Check for OS level alerts
16. Check CPU load and memory usage
17. Review SAPDBA calendar job logs
18. Check archive directory status
Recommended weekly tasks
1. Check database for free space
2. Monitor tablespace growth
3. Monitor total DB growth
4. Clean up Spool
5. Clean up transport buffers
6. Run TemSe consistency check
7. Review security audit log
8. Check for adequate file system space
9. Analyze Early Watch reports
Recommended monthly tasks
1. Cycle the R/3 system to defragment memory
2. Analyze the database growth and plan for storage
3. Review directory structure and need to move data files
4. Cleanup old logs
Recommended quarterly tasks
1. User security overview
2. Review SAP profile parameters
3. Review the standard scheduled jobs
4. Test the backup by restoring
5. Archive the old transport files
6. Maintain SAPDBA and database parameter files
7. Review maintenance contracts for all hardware / software
8. Check for usage versus licensing
Recommended annual tasks
1. Audit user security
2. Audit profiles and authorizations
3. Review user roles
4. Maintain activity groups/profiles
5. Cleanup clients in test/development systems
6. Check workbench organizer settings
7. Refresh test system8. Simulate disaster recovery/failover testing
Software maintenance (as needed) 1. Applying support packages
2. Applying database patches
3. Upgrading kernel
4. Change Management /applying notes
Additional services (as needed) 1. User Maintenance / Profiles creation and maintenance
2. Printer definition maintenance
3. Data archiving
4. Technical Upgrades

5. Server Migration

Administrator House Keeping Jobs List

What are the list of housekeeping jobs based on Daily, Weekly, Monthly Reports?
Job name
Program
Variant Freq
SAP_REORG_JOBS
RSBTCDEL
yes
daily
SAP_REORG_SPOOL
RSPO0041/1041
yes
daily
SAP_REORG_BATCHINPUT
RSBDCREO
yes
daily
SAP_REORG_ABAPDUMPS
RSSNAPDL
yes
daily
SAP_REORG_JOBSTATISTIC
RSBPSTDE
yes
monthly
SAP_COLLECTOR_FOR_JOBSTATISTIC
RSBPCOLL
no
daily
SAP_COLLECTOR_FOR_PERFMONITOR RSCOLL00
no
hourly
SAP_COLLECTOR_FOR_NONE_R3_STAT RSN3_STAT_ COLLECTOR no
hourly
SAP_REORG_PRIPARAMS
RSBTCPRIDEL
no
monthly
SAP_REORG_XMILOG
RSXMILOGREORG
yes
weekly
SAP_CCMS_MONI_BATCH_DP
RSAL_BATCH_ TOOL_DISPATCHING no
RSPO1043
RSPO1043
yes
daily
RSTS0024
RSTS0024
yes
daily

hourly

Common Abap Dumps And Their Meaning

You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is
to look up in ST22. Here you can see a descrition of what happened. You can further look up OSS notes for the
Error code, or for any programs, table or FM mentioned in the dump.
Dumps happen when an ABAP program that is running in a background generally causes an immediate termination
of the background job.
ABAP short dumps are something which trouble any SAP user (sometimes help the user to understand the system
needs better). We normally do a search for SAP notes or contact SAP to solve these dumps. But hardly takes any
chance to understand the meaning of the dumps. Here I am listing some 'famous' ABAP dumps and trying to explain
what are they. Please note that the solutions provided here may different from case to case. These should be used
just as a 'first aid'.
1) STORAGE_PARAMETERS_WRONG_SET
The problems with the dump STORAGE_PARAMETERS_WRONG_SET are mainly related to the general
restrictions of the 32bit OS. You can address up to 4GB of virtual memory. Each process in OS is running in its own
context and can address max. 4GB. The parameters which are related to heap memory' ie abap/heap_area_dia,
abap/heap_area_nondia, abap/heap_area_total are should be set to 2 GB. Common approaches which we can take
for this dump are:
a) Please use in the 'boot.ini' file the switch '/3GB' and restart your whole computer as described in the below SAP
Notes:
SAP Note 552209 - Maximum memory utilization for processes on NT/Win 2000
SAP Note 313347 - Windows NT, 2000, 2003: Editions and memory usage.
b) Another way to avoid this problem is to try to add more criteria to your report/program/transaction so that there
will be fewer entries that need to be retrieved from your database or buffers. This way, the system would not need to
use up much resource to complete the transaction. The query may have been quite big already and the load cannot
be accommodated. So please do add more criteria or options so that there will less data to fetch.
c) To decrease the value of the parameters: rdisp/ROLL_SHM, rdisp/PG_SHM
d) Migrate to 64-bit OS (as per SAP Note 931024 and SAP Note 996600)
2) TSV_TNEW_PAGE_ALLOC_FAILED
The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested by the system because the
program needed to expand an internal table, but not is available. When Extended Memory is completely used up, the
process will go into PRIV mode and it will starts using Heap Memory in case of Windows or vice versa in case of
Unix. Once this enters into PRIV mode, no other user will be able to use the corresponding work process. If there is
enough memory for it to finish, you will not see the error.

Please refer the following SAP notes:

SAP Note 649327 - Analysis of memory consumption.
SAP Note 20527 - Runtime error TSV_TNEW_PAGE_ALLOC_FAILED
SAP Note 185185 - Application: Analysis of memory bottlenecks
SAP Note 369726 - TSV_TNEW_PAGE_ALLOC_FAILED
3) TSV_TNEW_OCCURS_NO_ROLL_MEMORY
The dump TSV_TNEW_BLOCKS_NO_ROLL_MEMORY usually means that the roll buffer has been exhausted.
Please check the usage of your roll buffer with ST02->History->Page. Near the bottom of the screen you can see
ROLL BUFFER history. If the roll buffer has been exhausted, you can increase the size with parameter
rdisp/ROLL_MAXFS, but make sure you have sufficient disk space to handle the additional size of this buffer if it
writes to disk.
Please refer the following SAP note:
SAP Note 185185 - Application: Analysis of memory bottlenecks
4) LOAD_PROGRAM_LOST
The LOAD_PROGRAM_LOST error can occur when there are two or more versions of a given program loaded
into the buffer at any given time. This happens when the program is changed by one user while it is still in use by
another user. When a user gets to the program that is having this problem and R/3 attempts to load the generated
version from the buffer, it sees that the version is not the most current and tries to swap it out for the most current,
but the load was lost from the PXA buffer, hence it throws the dump of LOAD_PROGRAM_LOST.
LOAD_PROGRAM_LOST are the result of the combination of not enough PXA space + changes of programs
which are in use currently. A running program can't run with two different versions of one program. Ask the users
restart their transactions (/nST22). By the way, if the PXA would be big enough then the user who does not leave
their transaction for weeks will not see the changes to this application until they restart the transaction.
Other way to correct the error is you need to run transaction SAMT & regenerate the program(s) that are listed in
the dump. You can then do a $SYNC in the command field in the affected application server, but make sure that the
other application servers are not running at that time. After the $SYNC, the other app servers can be brought up and
the buffers should then be in sync.
Please refer the following SAP notes:
SAP Note 5451 - LOAD_PROGRAM_LOST
SAP Note 24824 - Inconsistencies in a Program Load
SAP Note 10367 - Termination LOAD_PROGRAM_LOST
5) CALL_FUNCTION_SIGNON_INCOMPL
The short dump CALL_FUNCTION_SIGNON_INCOMPL is typical of an RFC-Call with incorrect or missing
logon-data. So, we have to find out where the call is coming from.
Please refer the following SAP notes:
SAP Note 171805 - Determining RFC client when sign-on problems occur.
SAP Note 684788 - Possible reason for CALL_FUNCTION_SIGNON_INCOMPL.
SAP Note 901256 - Rabax "CALL_FUNCTION_SIGNON_INCOMPL".
6) RFC_NO_AUTHORITY
This error mostly appears with the user SAPSYS. The user SAPSYS is an internal user, it is not a personally used
ID in the R/3 system. However, all system errors and ABAP programs are run via this user id. As per note 93254,
since release 4.0 the parameter auth/rfc_authority_check is set on 1 per default. This means, as long as you did not
set it explicitly to value 0', any incoming RFC call is checked as described in the mentioned note.
The common approaches which we can take on this dump are:
1. Deactivate RFC authority Check: set auth/rfc_authority_check to value '0' (zero) in your profile and restart the
server. (This is the least secure option as any authorization checks are disabled for all RFC requests).
2. Assign full RFC authorities to the users who need to connect to your system via RFC.
Please also check the user id provided in RFC connection (check from SM59) which cause the dump

RFC_NO_AUTHORITY. Make sure that this user has sufficient authorizations.

Please refer the following SAP notes:
SAP Note 171805 - Determining RFC client when sign-on problems
SAP Note 93254 - RFC short dump RFC_NO_AUTHORITY
SAP Note 91980 - Missing output of RFC short dump after login errors
7) SYSTEM_NO_TASK_STORAGE
For this error, please go to service market to download the latest patch for your SAP Application release and apply
the patch. The latest patch would be useful for the problem. The SYSTEM_NO_TASK_STORAGE is a known
problem and related to limitation of 32bit OS. Please see notes 110172, 552209, 546361 for details. As long term
solution you have to use 64bit Windows (Note 996600).The cause for the dump SYSTEM_NO_TASK_STORAGE
could also be an old sap collector. SAP recommends using the updated collector version always.
The common approaches which we can take on this dump are:
1. Check your settings match the recommendations mentioned in SAP Note 146289.
2. Are ulimits set according to SAP Note 323816? (Referenced in SAP Note 146289)
3. If there is no additional instances on same host then it should be possible to increase EM/TOTAL_SIZE_MB
from 4096 MB towards the RAM and even higher so that ztta/roll_extension can be reached. Also the swap space
should be set according to SAP Note 153641 for this.
Please refer the following SAP notes:
SAP note 789477 - Large extended memory on AIX (64-bit) as of Kernel
SAP note 191801 - AIX 64-bit with a lot of Extended Memory
SAP note 445533 - Lots of extended memory on AIX (64-bit)
SAP note 581319 - Signal 33 on AIX (64-bit only)
SAP note 153641 - Swap space requirement for R/3 64-bit kernel
8) CALL_FUNCTION_NOT_FOUND
The error CALL_FUNCTION_NOT_FOUND is due to the fact that the program called the function which doesn't
exist in the library. Means the requested function module is not found in table TFDIR. Also you may get this error if
the buffered version of the TFDIR contains errors. The error needs to attention based on the function module. You
may take a general approach mentioned in the SAP Note 98458.
Please refer the following SAP note:
SAP Note 98458 - SAPMSSY1, CALL_FUNCTION_NOT_FOUND
9) CALL_FUNCTION_SINGLE_LOGIN_REJ
This error usually comes when you don't have sufficient authorization to login to the trusted system. This dump
accompanies with 4 different error codes:
0 - Incorrect logon data for valid security ID.
1 - Calling system is not a Trusted System or security ID is invalid.
2 - Either user does not have RFC authorization (authorization object S_RFCACL), or a logon was performed using
one of the protected users DDIC or SAP*.
3 - Time stamp of the logon data is invalid.
Please refer the following SAP notes:
Note 986707 - No authorization to log on as a trusted system (RC=1)
SAP Note 128447 - Trusted/Trusting Systems
SAP Note 204039 - Authorization check in trusted system
10) SYSTEM_CORE_DUMPED
Generally, SYSTEM_CORE_DUMPED is related to R/3 system kernel. Upgrade the kernel patch to the latest may
solve the issue. But without a detail analysis of the coredump at the Kernel, we cannot conclude the reason behind
the dump. I would recommend contacting SAP for this dump.
SAP Note 19466 - Downloading SAP kernel patches.