Wednesday, January 30, 2013

SAP Basis (Daily)

SAP IDES – the "Internet Demonstration and Evaluation System" in the R/3 System, represents a model company. It consists of an international group with subsidiaries in several countries. IDES contains application data for various business scenarios that can be run in the SAP System. The business processes in the IDES system are designed to reflect real-life business requirements, and have access to many realistic characteristics. IDES uses easy-to-follow business scenarios to show you the comprehensive functions of the R/3 System. The focal point of IDES, however, is not the functionality itself, but  the business processes and their integration.

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
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

c:\sqlplus   "/as   sysdba"
SQL> alter database backup controlfile to trace;

One “.trc” file will be created under “ /oracle/PRD/saptrace/usertrace”  Folder
check ".trc" file with today's date.

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
------------------------------------------------------------------------------------------------------------------------
1.SU01 User Maintainence
2. SCC4 Client Overview ( Create , Quick Delete , Modify )
3. SCC5 Deletes a client completely with tables & other factors
4. SCCL Local Client Copy
5. SCC9 Remote Client Copy
6. SCC3 Client Copy log Analysis
7. DB02 Storage Management & Database Performance
8. DB12 SAP Backup Logs
9. DB14 Database Monitor
10. SM12 Lock Entries
11. SM21 System Logs
12. SM36 Background Job Scheduling
13. SM37 Background Job Monitoring
14. SM31 Table Maintenance
15. SM50 Process Overview
16. ST22 ABAP Dumps
17. ST02 Buffer Analysis
18. ST03 Workflow Analysis
19. RZ04 Operation Mode
20. SE09 Transport Organizer
21. SCC1 Copy as per Transport Request
22. STMS Transport Management System  


--------------------------------------------------------------------
you can stop the saprouter process (saprouter -s) and restart it
temporarily using the following options:

saprouter -r -V 2 -K "p:CN=depix, OU=0000345622, OU=SAProuter, O=SAP, C=DE"

Try to test the RFC connection to SAPOSS (SM59 -> R/3 Connections ->
SAPOSS) and send us the following information, in order for us to
troubleshoot the connection problem:

o Output of the command 'sapgenpse'
o Output of the command 'sapgenpse get_my_name -n all'
o Output of the command 'sapgenpse seclogin -l'
o Files dev_rout (after the test access to SAPOSS) and saprouttab
o Technical settings in Tcd OSS1 (Parameter -> Techn. Settings)

----------------------------------------------------------------------------------

- On your SAProuter, delete your existing PSE file and old certificate
file (local.pse, cred_v2)
- Go to the http://service.sap.com/saprouter-sncadd
- Click on "Apply Now!"
- Follow the steps detailed in the following documentation
http://service.sap.com/saprouter-sncdoc
--------------------------------------------------------------------


1. You need to remove the old generated files(certreq, cred_v2, local.pse, srcert) from previous certificate request. To do this you can either rename these files or create a new folder and move these files into it.

2. Login to http://service.sap.com/saprouter-sncadd and click the “Apply now” button. From the list of SAProuters registered to your installation, choose the relevant “Distinguished Name”.

3. Generate the certificate Request. To do this go to your SAProuter server and run this command on the saprouter directory.

sapgenpse get_pse -v -r certreq -p local.pse “
Example:  sapgenpse get_pse -v -r certreq -p local.pse “CN=example, OU=0000123456, OU=SAProuter, O=SAP, C=DE”

You will be asked twice for a PIN here. Please choose a PIN and document it, you have to enter it identically both times. Then you will have to enter the same PIN every time you want to use this PSE.

4. Display the output file “certreq” and with copy&paste (including the BEGIN and END statement) insert the certificate request into the text area of the same form on the SAP Service Marketplace from which you copied the Distinguished Name.

5. In response you will receive the certificate signed by the CA in the Service Marketplace. Copy&paste the text to a new local file named “srcert”, which must be created in the same directory as the sapgenpse executable.

6. With this in turn you can install the certificate in your saprouter by calling: sapgenpse import_own_cert -c srcert -p local.pse

7. Now you will have to create the credentials for the SAProuter with the same program (if you omit -O , the credentials are created for the logged in user account).
sapgenpse seclogin -p local.pse -O
Note: The account of the service user should always be entered in full

8. This will create a file called “cred_v2″ in the same directory as “local.pse”

9. To check if the certificate has been imported successfully, run the following command: sapgenpse get_my_name -v -n Issuer
The name of the Issuer should be: CN=SAProuter CA, OU=SAProuter, O=SAP, C=DE

No comments:

Quote of the Day