How to use STAD to show historical data

What is STAD

The Business Transaction Analysis (Transaction STAD) delivers workload statistics across business transactions (that is, a user's transaction that starts when a transaction is called [/n....] and that ends with an update call or when the user leaves the transaction) and jobs.

 

STAD Alternative Way

 

My attempt to show you to view historical data which are taken from the STAD transaction for a long time.

The default time period is 48hrs for STAD transaction. We only can analyze data for this time frame. The alternative way to save earlier STAD reports will be discuss here. I think this will be helpful for the administrators to analyse varies issues in their systems.

 

Method

Run STAD in Background with scheduled  in periodically.

The STAD program is RSSTAT26 which is run in background when we run the STAD transaction.

 

 

Step By Step Guide

 

• Transaction SE38 and provide the program name RSSTAT26 as in screen. Then execute

    

 

• Then select Program -> Execute in Background

 

      

 

       

 

 

• Then Select the data time and finally click on periodic values.

 

 

• Then Select the period.

 

 

• Then click on save button on above screen to save the background job.
• you can see the message for successful background job.

 

 

Now creating background job is completed. ++++++++++++++++++++++++

 

Next step is to check the report which the background job is created.

 

Then Goto SM37 for background jobs.

 

 

Then click on pool icon show on the image.

 

Click on the icon mentioned under type column.

 

 

 

Then you can see the report for given period.

 

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

 

The report can be customized for user, transaction and more parameter fields. Then the report can be create for specific requirements and historical statistic data.

How to create Trust/Trusted RFC relationship

1.Create a RFC destination to the system you want to trust(for example Y57->Y58)

 

 

2. Create a trusted system in Y57 using the RFC destination you just created.

 

3. Go to SMT2, you will see trusting system is here.

 

4. Create a RFC destination without user and password but using "Trust Relationshiop" and "Current user" instaed.

Now you can use this RFC destination logon to Y57 without enter user and password

How to find SQL Traces in ST05

When i was working with Performance issues on BEx queries we face so many issues.

While coming  we created BEx reports for dashboard requirement and always users want run the dash board they want immediately.

We made aggregates on cube but again some performance issue came. How do you which object is using frequently then we trace the Dash board BEx queries.

How to find the SQL Trace

1.enter the T- code- STO5

Below screen appear then check the SQL Trace and RFC Trace then select the activate trace with filter – give user name -> USER1.

Select continue

Now see trace activated.

2.Enter the T-code- RSRT

Run the query and it took 8 minutes time

Go to again T-code- ST05

Deactivate the Trace now trace are switched off

Then select the display trace

Then next screen will appear

Filter the object name was Info cube E face table

Double click on the SQL select statement

Below screen will appear

In SELECT statement how many object are using we find easily (for information i am erasing the using all info object) then we made aggregates based on the SQL script.

After making aggregates on cube our dash board report came within 2 minutes.

SAP 7.20 Kernel Patch Upgrade in MSCS setup

Introduction:

 

This document is intended to outline the steps to upgrade SAP 7.20 kernel patch on MSCS set up. There may be confusion on the MSCS set up as to what exactly needs to be done and after successfully carrying out this activity recently I feel this document will benefit other fellow members. I will try to put the screens wherever necessary to explain the step.

 

Overview:

 

This document contains steps to upgrade SAP Kernel 7.20 from Patch level 105 to Patch level 201

 

Technical Information:

 

Kernel 7.20

Windows 2008 Enterprise Editon Service Pack 2

Oracle 11g

 

 

Pre-requistes:

 

a. Download the latest Kernel Patch from http: service.sap.com/swdc->Support Packages and Patches -> A - Z Index -> E -> SAP ERP -> SAP ERP ENHANCEMENT PACKAGE -> Choose your Version -> Entry by Component -> ABAP Technology for ERP EHP 5 -> SAP Kernel 7.20 64-Bit Unicode

you need to download the following files:

SAPEXE_201-10007272.SAR (this file is available under 'database independent' title)

ntclust_2-10007272.sar (this file is also available under 'database independent' title)

SAPEXEDB_201-10007270.SAR

 

b. Take backup of your existing Kernel directory: ie: \usr\sap\SID\SYS\exe\uc\<os platform>

you can also find this directory by checking in RZ11 the value of parameter DIR_CT_RUN

 

c. It will also be better if you take an image backup of your C: drive

 

d. Always perform the Kernel Upgrade first in your test system to check for any errors. Once its verfied only then Upgrade in Production.

 

Procedure::

 

1. Take backup of your existing kernel directory:  \usr\sap\SID\SYS\exe\uc\<os platform>

 

2. Take backup of C:\windows\sapcluster on all MSCS nodes

 

3. Take backup of C:\Windows\system32\SapClus.dll on all MSCS nodes

 

4. Unpack the latest kernel (201) using the following command

SAPCAR -xvf SAPEXE_201-10007272.SAR

SAPCAR -xvf SAPEXEDB_201-10007270.SAR

SAPCAR -xvf ntclust_2-10007272.sar

 

same way you need to extract SAPEXE & ntclust.sar

 

5. Shutdown SAP System

 

6. Take SAP Service offline (from Failover Cluster Management)

 

 

7. Shutdown database (from Oracle Failsafe Manager)

 

8. Now, start copying the latest kernel files(kernel 201) to your existing kernel directory

 

Select 'Copy and Replace' option

 

6. Now Update the files on all cluster nodes in the Windows\SAPCLUSTER directory with the corresponding files in the central kernel staging directory.

 

7. Next, we have to update SapClus.dll file

when you run SAPCAR on ntclust.sar file, following folders will be available

 

 

In the NTCLUSTER sub-folder, you will find 'SapClus.dll' file

 

We need to copy 'SapClus.dll' to C:\Windows\System32 on all MSCS nodes

 

NOTE: Although on some scn threads it is said to update 'Saprc.dll' & 'Saprcex.dll' also but we only copied 'SapClus.dll' and our Kernel Upgrade went fine. We performed both the switchover & failover test for our MSCS nodes and it was successful.

 

8. Now restart the database and bring the SAP services online

 

9. Next, Re-start SAP system

NOTE: The instance restart will take 5 - 10 mins and if you have one or more dialog instances then you do not need to update them separately.

 

10. Finally, Perform the MSCS Switchover/Failover test to confirm the successful upgrade of the kernel patch.

 

Result:

 

Your have upgraded your kernel patch on MSCS setup.

 

Sapnotes:

 

sapnote 1636252 - Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11

 

If you have any comments or feedback please feel to update.