ST03N: Workload Monitor [Monitoring]

ST03N: Workload Monitor [Monitoring]

ST03N is used to analyze statistical data for the ABAP kernel and monitor the performance of a system. You can display the total values for all instances, and compare the performance of particular instances over a period of time.

The workload overview provides system administrators with various detailed information about the most important workload data, such as the CPU time, the number of database changes, the response times, and so on. You can display the workload overview for all task types (Dialog, Background, RFC, ALE, and Update), or only for one particular task type.

Workload Overview :-

Processing time – This is equivalent to response time minus the sum of wait time, database request time, load time, roll time, and enqueue time
Hint: > 2x of CPU time
Probs: Hardware

CPU time – A work process uses the CPU.
Hint: 40% of response time]
Probs: CPU bottleneck
Solution:
In ST06,
Go to Detail Analysis Menu -> Top CPU , check existence of Non-SAP (external) programs by sorting by CPU time. Try to run these external programs in offline hours.
In ST02,
Check for any swapping happening in all the buffers. If there is high swapping for any buffer, increase the size of the buffer.

Response time – The time when a dialog process sends a request to a dispatcher work process, and the dialog is complete and the data is transferred to the presentation layer. The response time does not include the time for transferring the data from the SAP front end to the application server.

Hint: 1 second (dialog), <1 second (update)

Wait time – The time when a user request sits in the dispatcher queue. It starts when user request is entered in the dispatcher queue; and ends when the request starts being processed.

Hint: < 10% of response time
Probs: long running tasks, locked tasks, not enough work process
Solution:
In SM50,
Look for all the configured work processes are in Waiting or Running state. If all the wotk processes are running state, then increase the number of Dialog work processes.
In SM66,
This monitor will help to analyse the total work processes configured in all the servers and instances.

DB calls – Number of parsed accesses to the database.
Hint: DB calls/requests good ratio is 1:10 = efficiency table buffering

DB requests/DB Time – The time when a database request is put through to the database interface & when the database interface has delivered the result.
Hint: 40% of response time
Probs: CPU/memory bottleneck on DB server, expensive SQL statement, missing indexes, small buffer, missing statistics
Solution:
In ST04,
- Database buffer quality (> 95%), if <, increase database buffer cache size.
- Reads/User Calls (< 30), if >, the expensive SQL statements need to be tune. Some of expensive SQLs statement problems:
i) incorrect index access (Solution = create new index or reorganize the index)
ii) high table size (Solution = archive the old entries)

Average load & generation – The time needed to load and generate objects.
Hint: < 10% of response time, < 50ms
Probs: Program buffer, CUA buffer, screen buffer too small

GUI time – Response time between the dispatcher and the GUI during the roundtrips (roundtrips are communication steps between the SAP system and the front end during a transaction step).

Hint: < 200ms
Probs: network between GUI & SAP]
Solution:
In ST06,
Go to Detail Analysis Menu -> LAN Check by PING. If there is high Avg. time or Loss time for any presentation servers, means there are some settings need to be change for the presentation server.
In SE38,
Execute PROFGEN_CORR_REPORT_5 report. From the output check if any user assigned with > 1000 user menu nodes.

Roll in time -  The time needed to roll user context information into the work process.
Hint: < 20ms
Probs: SAP memory configuration (extended memory, roll buffer)

Roll wait time – Queue time in the roll area.
Hint: < 200ms

Probs: network between GUI & SAP

Post Installation Steps

Post Installation Steps :-

After Installing R/3 into a new system, Basis has to perform some post Installation steps before handing over to end users for operation. Post Installation steps make sure that System is ready, properly configured, Tuned and take load of user requests.

Below are some standard steps which has to perform immediately after the installation is finished.

PART 1:-

1. Login to SAP system using DDIC/000

2. Execute SE06 , Select Standard Installation and click on execute Perform Post Installation Steps. Click yes on each next screen.

3. Execute STMS , to configure TMS configuration system. If there is no Domain controller in organization then configure this new system as DC.

4. Execute SICK to check for any Installation error , If anything is reported then trouble shoot those errors.

5. Execute sapdba or brtools to check/increase tablespace size if any is >90%

6. IF sapdba then check the tablespace utilization by selecting c. Tablespace Adminitration - c. Free space fragmentation of Tablespaces

7. List out all the tablespaces filled above 90%

8. Add datafiles to corresponding tablespaces to increase the tablespace size and bring the utilization of tablespaces below 80%

9. Login as SAP*/000

10. Execute SCC4 -> Click on change button -> Confirm the warning and click on new entries to create a new client.

11. Execute RZ10 -> Utilities -> Import profiles -> Of Active Servers

12. check the system log in SM21

13. Check any dumps in ST22

14. Login at command prompt using ora<sid> or <SID>adm

PART 2:-

1. login to new client to perform a client copy using SAP*/<new client number>/PASS

2. Perform local client copy procedure to copy new client from 000 client.

3. Once client copy is over , login to new client using SAP* and password of SAP* which was

 used in client 000

4. Execute RZ10 -> Select Instance Profile -> check Extended maint -> click on change.

5. Add parameter login/system_client parameter to make new <client_number> as default client to login.

6. Make changes to dialog process and background if you need to change than default one.

7. Save the profile and activate it.

8. Create one or two super users using SU01 with profiles SAP_ALL and SAP_NEW

9. Create some developer users if you can, else leave it.

10. Stop and Start SAP R/3 for profile parameter to be in effect.

11. Upgrade the kernel to the latest level

12. Upgrade the SPAM version to latest level

13. Apply latest support pack to components SAP_BASIS, SAP_ABAP, SAP_APPL and some other components if it is required.

14. Follow the kernel, SPAM and support pack application methods

15. Now system is ready to login and work for developers and administrator

16. Keep on changing the parameters , system configuration as per requirement later.

17. Run SGEN to regenerate the objects . In this process SAP keeps all the required objects access in SAP buffer. So that transaction accessing becomes faster.

Support Pack Upgrade Process

Support Pack Upgrade Process :-

Support Pack Application:-

1. Check the current patch in your system.

a. Check SPAM Version

b. Check SAP_BASIS patch level

c. check SAP_ABAP patch level

d. Check SAP_APPL Patch level.

To get all the above information follows the following steps:-

Execute SPAM - Check the SPAM level at the top.

Click on Package Level to display all the patches in the system

Note down SAP_BASIS, SAP_ABAP, SAP_APPL patch level in the display.

2. Find out what is the latest patch level available for above components.

Download -> Support Packages and Patches -> Entry by Application Group-> Application Components ->SAP R/3 Enterprise -> SAP R/3 Enterprise 47 X 110 -Entry by component -> SAP R/3 Enterprise Server-> SAP_BASIS620 ->

3. From the list select which component you want and click on it.

E.g.click on SAP BASIS 6.20 and select the patch level 25 you want comparing your current patchlevel. Select all the patches you are behind to current and add to download basket.

All the patches are in .CAR format.

Repeat the same step for all components you want to apply for your system.

4. Download all the patches you added to download basket by using SAP Download Manager.

5. Save all the .CAR files to your local hard drive say C:\supportpacks

6. now transfer all these .CAR files to Your Unix Server where your SAP is running using ftp.

ftp steps

go to command prompt

cd c:\supportpacks

c:\supportpacks\> ftp solsrv (solsrv is the unix servername)

username : SIDADM

password : (Password of SIDADM)

ftp> cd /downloads/supp_pack

ftp> bin

ftp> mput *.CAR (press y for all the confirmations)

ftp> bye

7. Now extract the .CAR files by using executable CAR.EXE

#cd /download/supp_pack

# CAR -xvf <Filename1>.CAR (files are extracted to .../EPS/in folder)

Repeat extraction for all .CAR files

You will get the files with extension .ATT and .PAT

8. Now go to /usr/sap/trans/EPS/in directory and remove the existing files out there.

login as <SID>adm and pasword

# cd /usr/sap/trans/EPS/in

# rm -rf *

9. Now Copy all .ATT and .PAT files to /usr/sap/trans/EPS/in directory

# cp /download/supp_pack/* /usr/sap/trans/EPS/in

# ls –l

10. Login to SAP using a superuser other than SAP* and DDIC to 000 client.

11. Execute SPAM in SAP command line

12. Click on Support Package -> Load Packages -> From Application Server.

Here all the .ATT and .PAT files are converted into proper Patch format and available on SAP level to apply suuport packs as per the requirement.

Click on Back button

13. Now Click on Display/define

14. Ask all the users to logoff from the system OR lock all the users in all business clients using customizing program or SAP tool.

15. Make sure you have full backup of system before applying the patch

and enough downtime to apply the patch

SPAM Update

16. Select support package ->Import SPAM update to update the SPAM version.

Applying Patch

Before Applying the Patch to system, we have to check if there are any objects under modification or any Transport Request in modification condition. IF any then we may have to adjust those prior to applying

the SAP Patch.

Execute SPAU and see if any objects are there to adjust

Execute SPDD to see if any dictionary objects are there to adjust.

Execute SPAM

Click on display/Define

Select the component (e.g. SAP_BASIS)

Select the Patch number (e.g. SAPKB62012)

Click on confirm Queue (\/)

Select Import queue by selecting truck button

Confirm it by clicking on (\/) mark

Patch application is started.

If you encounter error during patch application, start applying again.

Confirm the message

SPAM status is in yellow

Click "confirm queue” button to confirm the queue.

Check the spam status. It should be green.

Support pack application is successful

Click on Package level to see the change.

KERNEL UPGRADE STEP BY STEP

KERNEL UPGRADE STEP BY STEP :-

Check the existing kernel level by logging into SAP level

SM51 ->Release notes

OR

Go to command level and execute disp+work (Login as <SID>ADM to perform this task)

Check the Kernel levels available in SAP service market place

Downloads-Download -> Support package and patches -> Entry by Application Group ->Additional components -> SAP Kernel-> SAP Kernel 64 bit->SAP Kernel 7.00 64 bit-SAPKERNEL 64 bit->Windows server on X64 bit->Database Independent

Select SAPEXE_ (latest patch number) _*.SAR and click on add to download basket from the bottom.

Repeat above step to down load Database Dependent kernel by selecting the database you have/want.

Select SAPEXEDB_<latest_patch_number>_*.SAR and click on Add to download basket.

Now launch download manager from your system and down load the SAPEXE* and

SAPEXEDB* to your local drive. (e.g. G:\Kernelupgrade)

Now extract the .SAR files from command prompt

cd G:\kernelupgrades

G:\Kernel upgrade>sapcar -xvf SAPEXE_1773-10001664.SAR

G:\kernelupgrades\>sapcar -xvf SAPEXEDB_1773-10001667.SAR

Now check the number of files in G:\kernelupgrade (e.g. 115 files)

Go to C:\usr\sap\S11\SYS\exe\run

Check the number of files (e.g. 124 files)

Stopsap on target system

login as <SID>adm

#stopsap (UNIX)

In Windows/NT: go to desktop > double click on SAP Management Console

Select the server

Click on stop

Wait for SAP to be stopped

Stop all sap service and database service from

Windows/NT: Programs->Administrative Tools ->services->

Stop TNSlistner server for oracle

stop oracleserviceS11 for oracle

stop SAPS11_00 for SAP

stop SAPOSCOL for SAP

stop if any other oracle service is running.

Select the service ->right click –Stop

Now take backup of your old kernel directory (use OS level copy command)

Copy run folder to G:\kernelbackup

Go to Kernel-upgrade folder

Copy all the contents from this folder and paste it into c:\usr\sap\<SID>\SYS\exe\run

Check the kernel patch by typing disp+work at command level

Start all sap and database services from Programs->Administrative Tools->services->

Start TNSlistner server for oracle

Start oracleserviceS11 for oracle

Start SAPS11_00 for SAP

Start SAPOSCOL for SAP

Select the service ->right click -Start

Start sap on Server now

Windows/NT: SAP Management Console (MMC) ->select Server->click on start button from top menu. Check for green light on servers

UNIX: startsap

Now login to sap from saplogon menu and see you are able to login successfully.

Double check the kernel patch level by executing SM51 -> Release Notes

Kernel upgrade is completed.

Start and Stop Sap System

Start and Stop Sap System :-

Start the SAP instances  by entering the command startsap. Start the central  instance first and then the dialog instances.

a) Start the SAP instances by entering the command startsap.

startsap 

syntax: startsap name=<sid> nr=<Instanz-Nr.>SAPDIAHOST=<Servername>

Start the central instance first and then the dialog instances.

Stopping the SAP System

It may be necessary to stop an SAP system for a variety of reasons, for example,

restarting after permanently changing profile parameters, before installing kernel

patches, or allowing hardware upgrades to be carried out.

Before you stop the system, you should check the status of the system.

 This involves, among other things:

. Active Users:

  Check which users are logged on using the User List (SM04).

. Background Processing :

  Check which jobs are active using the Job Overview (SM37). If jobs are

  terminated by the system stop, these jobs must be rescheduled. Jobs that are

  scheduled for the time when the system is stopped run automatically once

  the system restarts.

. Batch Input:

The transaction Batch Input: Session Overview (SM35) displays running

batch input jobs.

. Update:

Use the Update Overview (SM13) to check whether update processes are

terminated by the system stop. These update records are rolled back during

the stop, and these are set to the status .init.. These records are then updated

again during the restart.

Before you stop your system, you should inform users using a system message

(SM02).

Enter the command stopsap to stop an instance.

stopsap 

syntax:  stopsap name=<sid> nr=<Instanz-Nr.>SAPDIAHOST=<Servername>

Phases during sap patch deployment

Phases during sap patch deployment :-

In the status bar, Support Package Manager informs you of the status of the current phase. To find out which phases are executed for which scenario (test or standard scenario), run program RSSPAM10.

The following list provides an overview of all the modules and phases in the order in which Support Package Manager executes them:

Preparation Module:-

1. PROLOGUE

This phase checks whether you are authorized to import Support Packages.

2. CHECK_REQUIREMENTS

This phase checks various requirements for importing a Support Package, for example, whether transport control program tp can log on to your system.

3. DISASSEMBLE

This phase unpacks files from the appropriate EPS parcels and saves them to the transport directory.

4. ADD_TO_BUFFER

This phase adds the queue to your system’s transport buffer.

5. MODIFY_BUFFER

This phase prepares the transport buffer so that the following import phases can be processed correctly.

6. TEST_IMPORT

In this phase, a test import is run for the current queue with transport control program tp. The system checks for objects that are in open repairs and that are overwritten during the import, or for other factors that might prevent an object being imported.

7. IMPORT_OBJECT_LIST

This phase imports the object lists for the Support Packages in the queue into the system.

8. OBJECTS_LOCKED_?

This phase checks for objects that are overwritten by the import and are still in unreleased requests.

9. ADDON_CONFLICTS_?

This phase checks for conflicts between objects in the queue and installed add-ons.

10. SCHEDULE_RDDIMPDP

This phase schedules the transport daemon (program RDDIMPDP).

Module Import 1

11. CREATE_VERS_BEFORE

This phase generates versions of the objects that are contained in the Support Packages in the queue (if this option is set).

12.  SPDD_SPAU_CHECK

In this phase, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).

13.  DDIC_IMPORT

This phase imports all ABAP Dictionary objects in the queue.

14. AUTO_MOD_SPDD

This phase checks whether all modifications to ABAP Dictionary objects can be adjusted automatically.

15. RUN_SPDD_?

In this phase, you are asked to adjust your modifications to the ABAP Dictionary objects by calling transaction SPDD.

16. LOCK_EU (only for import mode downtime-minimized)

This phase locks the development environment.

17.  INACTIVE_IMPORT (only for import mode downtime-minimized)

This phase imports program code and program texts in an inactive state.

18. DDIC_ACTIVATION

This phase activates the imported ABAP Dictionary objects.

Module Import 2

19. IMPORT_PROPER

This phase imports all the Repository objects and table entries not already imported during the INACTIVE_IMPORT phase. This is preceded by actions such as table conversion and activation of the name tabs.

20. PREPARE_XPRA

This phase prepares the execution of the XPRAs and after-import methods.

21. UNLOCK_EU (only for import mode downtime-minimized)

This phase unlocks the development environment.

22. AUTO_MOD_SPAU

This phase checks whether modifications can be adjusted automatically.

23. XPRA_EXECUTION

This phase executes the XPRAs and after-import methods.

24. ABAP_GENERATION

This phase generates the runtime objects for the imported Repository objects (ABAP source code and screens).

Clean Up Module:-

25.  RUN_SPAU_?

This phase prompts you to adjust your modifications to Repository objects by calling transaction SPAU.

26. CLEAR_OLD_REPORTS (only for import mode downtime-minimized)

This phase deletes the obsolete versions of program code and program texts in the database.

27.  EPILOGUE

This phase completes the import. Among other things, it checks whether the queue has been processed completely.

How to trace user's activity

How to trace user's activity :-

Creating a User Audit Profile :-

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM19.

3. From the top-most menu bar on the Security Audit: Administer Audit Profile screen, click Profile
   -> Create.

4. On the Create new profile popup, type in a new Profile name and click the green √ picture-icon.

5. On the Filter 1 tab of the Security Audit: Administer Audit Profile screen, click the icon to the left of Filter active to place a √ in the box. In the Selection criteria section, select the Clients and User names to be traced. In the Audit classes section, click “on” all the auditing functions you need for this profile. In the Events section, click the radio button to the left of the level of auditing you need. Once you have entered all your trace information, click the Save picture-icon. You will receive an Audit profile saved in the status bar at the bottom of the screen.

6. Please note that while the user trace profile has been saved, it is not yet active. To activate the user trace, see the next section Activating a User Audit Profile.

7. You may now leave the SM19 transaction.

Activating a User Audit Profile :-

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM19.

3. On the Security Audit: Administer Audit Profile screen, select the audit profile to be activated from the Profile drop down. Click the lit match picture-icon to activate it. You will receive an Audit profile
activated for next system start in the status bar at the bottom of the screen. The audit will not begin
until after the SAP instance has been recycled.

4. You may now leave the SM19 transaction.

Viewing the Audit Analysis Report :-

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM20.

3. In the Selection, Audit classes, and Events to select sections of the Security Audit Log: Local Analysis screen, provide your information to filter the audit information. If you need to trace the activities of a specific user, be sure to include that user’s ID. Click the Re-read audit log button.

4. The resulting list is displayed. This list can be printed using the usual methods.

5. You may now leave the SM20 transaction.