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
SAP_REORG_BATCH
SAP_REORG_ABAPD
SAP_REORG_JOBST
SAP_COLLECTOR_F
SAP_COLLECTOR_F
SAP_COLLECTOR_F
SAP_REORG_PRIPA
SAP_REORG_XMILO
SAP_CCMS_MONI_B
RSPO1043 RSPO1043 yes daily
RSTS0024 RSTS0024 yes daily
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/locke
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/developmen
6. Check workbench organizer settings
7. Refresh test system8. Simulate disaster recovery/failov
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
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.
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
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/shutdo
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/
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.
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/Monitor
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
It will help you monitor & use spome other activities centrally.
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.
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--Che
6] Check work-processes(
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
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\s
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
發表文章
