Sapdatabase for all sap modules

sapdatabase provides you all sap modules information,latest updates

Sapdatabase for sap education

sapdatabase provides you all sap modules material,interview needs

Sapdatabase for all sap information

Sapdatabase makes you as a sap professional

Sapdatabase for outsourcing and online training

Sapdatabase provides you online training,outsource services for all sap modules in econamic fee

Sapdatabase for sap jobs

Sapdatabase makes job searching for you

Showing posts with label SAP DATA. Show all posts
Showing posts with label SAP DATA. Show all posts

Thursday, February 2, 2012

apply support packs & errors faced while deployed support packs

  1. To fix the bugs.
  2. To get the functional enhancements.
  3. To upgrade the system to next level.
  4. To support third party tool such as solution manager, charms (change request management), mopz(maintenance optimizer).
1)      Ensure that STMS  is configured in client 000.
2)      Patches are applied only through client 000 with user like ddic(most of the patches are at repository level So they are applicable to all clients) and some of the patches like CIN(country India version)  or baseline packages are client specific. In this case the client copy has to be performed from 000 again. If customizing is performed client comparison and adjustments using Tx SCMP.
3)      Ensure that TP,R4Trans,SAP CAR are upgraded to the latest version (these 3 are hot patches does not requires system shut down).
4)      Ensure that 2 free back ground process (work) are available (at least).
5)      Ensure that the SPAM (support package manager)/SAINT(sap add-on installation tool) is upgraded to latest.
6)      Sap packages are incremental i.e the reason why sequence is required i.e jumping between packages is not allowed i.e after applying 12 then only 13 can be applied
7)      Support packages cannot be reverted back so read the composite note provided by SAP (note 22379) and read for the following reasons
a.       Check the dependencies b/w the packages.
b.      To identify the known problems related to that specific package.
c.       To identify the support packages queue which can be blinded together to avoid known problem.
                       Eg :support package 10,11 and 12 should be applied together or SP recommends not to                                                               include 12 and 13 in one queue.
8)      Ensure that you have enough space in the database. Execute DB02 to check the size of each tables space and ensure that each one below 90% or (click on critical space objects).
9)      Ensure that we have enough space in usr/sap/trans directory.
10)   Patches should be applied in the sequence of support packages SAP-BASIS,SAP-ABAP,SAP-BW,SAP-AP,SAP-APPL,SAP-HR.   
11)   Ensure that valid backup is taken before applying support packages using BRTOOLS,DB13 or third party tools.
12)   Based on the support package size apply either through front end or application server.
If support packages size >10MB use application server
                                                <10MB use front end. But it is always recommended to apply through application server(to reduce network blockage).
13)   Ensure that RDDIMPDP, RDDNEWPP background jobs are scheduled in 000 client to apply support packages.(execute Tx SA38 -> specify job name and execute jobs).
14)   While applying (patches) support packages related to functional areas like APPL and HR ensure that functional consultants are available to adopt the modifications.
Ex: the changes at repository level may effect a program. customization (these changes might be developed which needs to be adjusted after deploying a package). 
15)   Apply the support packages in the landscape (follow sequence) development, quality, pre-production and finally production.
16)   Support packages are hot packages and applied when the system is up and running. To ensure that the objects are not locked by the users, it also consumes CPU and memory resources. So apply packages during off peak hours.
17)   Ensure that the router is configured to open the system for SAP remote support incase if the patches are chocked/aborted.
18)   Ensure that there are no aborted packages in the system.
19)   Ensure that the objects are not locked/unconfirmed/modified state in SE01(i.e the change req need to be released).
20)   Ensure that SPDD/SPAU phases are run to adopt the modifications related to data objects and the repository objects.
Note: SPAM/SAINT patches can be applied in any order. They are cumulative and move from lowest to highest number.
1)      Download the packages from market place using url packages and patches.
2)      Copy the packages into trans directory. Ensure that they have permissions for <sid>ADM 775 (not root).
3)      Uncar the patches using command sapcar –xvf KB70018.sar. it will generate .att and .pat files in the EPS/In directory. If executed on trans directory ig will geberate files in eps/in directory and generate .att and .pat files in that directory.
EPS- electronic parcel service is used to host the packages, add-ons, languages etc.
4)      Execute SPAM use load packages from application server.
5)      The support package in now available in the sap database and ready for deployment.
6)      Check the pre-requisities(select all support packages display).
7)      Define the queue (select one or more packages in display and define button). Click on import queue (truck).
8)      Schedule the package to run in the background mode.
9)      Start the package application.
10)   Monitor the tp logs,sm50,sm66 and sm37.
11)   Monitor the temp directory and check for file size movement.agter completion click on confirm queue.
12)   Support packages are applied to the system because of the following reasons.
a)      When there is a bug/security issue sap releases a note \patch\support stack.
b)      Note or patch is small correction to the programs with any keys which is applied through Tx. SNOTE
c)       Notes/patches are grouped s package patches are grouped as support-stack patches  Are  grouped as support –stack patches. and can be applied during an os/db/r3 upgrade.
d)      These also can be applied for maintain the system as per sap standards/maintenance scheldule.
13)   While applying support packages suspend all the released or active jobs(background) using BTCTRNS1 and after completion resume using             BTCTRANS2.
14)   All phases of the SPAM we can see by executing the report RSSPAM10 in sa38/se38.
15)   Due to any constraint if the support package is trapped or terminated restart the spam and import again. it will start from the point where it has been stopped by reading from logs/temp.
·         This is the phase where technical/functional consultants need to take decision.
Eg: there was a but in the system which was fixed by applying a note. This note is also available in support package. (notes are small correction to programs and where as support packages contains all the notes and enhancements). During the support package application SPDD/SPAU phase occurs to take a decision
                                            I.            Whether to roll back to old code.
                                          II.            Remain the same as it is.
                                        III.            Adopt the changes provided by support package.
·         During he adoption i.e modification or adjustment a change request is generated in DEV which subsequently included in the QAS and PRD.
·         RDDIMPDP                 triggers all the remaining RDD* jobs.
·         System is crashed aborted during patch application.
Sap system is started and GUI logon is not possible as the programs are modified.
The background jobs which was stopped will resume and continue to run (if not get the command from ULog and trigger manually at os level). Sometimes there will be a lock that is held in tmp directory which can be resumed manually by deleting the lock.
·         As the GUI logo  is not possible use MMC on windows (dpmon on unix along with monitoring of tmp directory, till it  is emptied).
·         Support packages uses tables PAT01 and PAT03. Do not empty these tables unless SAP recommends to do.
All the pre-requisites turn into error if they have not handled properly.
1.       Database space issues.
2.       File system space issues.
3.       Patch chokes due to inter dependencies.
4.       Objects are locked in change request.
5.       Background processes are not available.
6.       RDDIMPDP job not scheduled.
7.       Tmp directory is full/cannot write into directory.
8.       Add-on conflicts.
            (CRT: conflict resolution transports are provided by sap to resolve the conflicts b/w sap basis/abap support package and add-ons like insurance banking etc. these CRT’s need to be apply manually through TP).
9.       Outdated kernel (update tp,r3trans & sap car).

  See Related posts

Wednesday, February 1, 2012

What are the most important OS level Commands in sap? Sap Os level commands

dpmon d
Dispatcher queue monitor
Sapdba (up to SAP R/3 -4.7)/ brtools
database administration
Running work process
ps -eaf|grep dw
process overview
ps -eaf|grep ora
check oracle service is running
Ps –eaf | grep dw kill -9
Kill work process
msmon pf=profile path name=sid
to check the message server status
gwmon pf=profile path nr=num
to check the gateway status
Ps –eaf | grep lsnrctl
Listener status
Rslgview pf =-r –ft | pg
System logs
Disp + work –v
to check the version of r3 kernel
R3trans –d ,tnsping
Checking the connection with database
Df –k
File system monitor
Du –k
Display all directories and size of current directory
Connect internal//(old versions)
“/as sysdba” (new versions)
SQL prompt and database connection

SQL prompt and database connection

Saplicence  -get
to get hardware key
saplicense -install
to install license
sappfpar all pf=profile path
display all profile parameters
sappfpar check path=profile path
checks the required space for memory
to check the available space for heap and swap memory
Remote system login
telnet <ipaddress><dispatcherportnum>
to check the remote sap system is up and running
file transfer protocol
remote copy of files
Start/stop sap
Start / stop Sap instance
check destination host reachable
check connection between server and a client by transferring packets
check the configuration of system
Ps -aef
Processes status
lsps -a
Swap space

Tuesday, January 31, 2012

Maximum No. Of SAP Session Per User

You set this Parameter : rdisp/max_alt_modes in transaction RZ10.
Add in the above parameter in the Instance Profile - Options Extended Maintenance.
Restart the R/3 instance.
The default maximum no. of sessions in 4.6x is set as 6 session per user.
Most company will reduced the number of session per user but not increase it. 

See Related posts

Friday, January 20, 2012


SA     fsap performance tuning activities   

Ø  If  single user or single transaction getting this (large response time) performance problem, we need to tune the program which is causing large response time
·         From ST03, The average response time for dialog-step should not be more than 1000 ms
ü  We can Check for the top programs which are causing high data base request time and programs with high CPU time, mainly we concentrate on customized programs
   If the average DB request time is more than 500 ms
§  It can problem with missing indexes on tables and expensive SQL statements
ü  We can check for missing indexes in DB02 (detail analysis-missing indexes), if we find any missing indexes .., we can raise the ticket to ABAPers to re-create the indexes for proper fields.
ü   And also Check the expensive SQL statements in St04,which are taking High disk reads(> 5% of total physical reads), High buffer gets/misses(> 5% of total reads) monitoring  (detailed analysis menu-SQL request tab),if we got any expensive SQL statement ,we need to optimize that SQl statement by ABAP’ers
 If the CPU time is greater than 400 ms
§  It can problem with wrong logic of the ABAP program
ü  We can analyze the time consuming transaction using STAT and raise the ticket to ABAPers to make correction of  wrong logic or reprogram
Ø  If all transactions are getting the (large response time) performance problem we need to analyze the programs which are causing large Wait Time, large roll- wait time, and large load time, large DB request time, large CPU time and large processing time.
     If the average Wait time is more than 50 ms
§  It can problem with long running jobs.
ü  We can identify the long running jobs by using SM50 or SM66 and tune that long running job or terminate them.
ü  Work processes are blocked by long running reports, this problem occurring frequently we need to increase the work processes.
ü  The average number of free work processes available in the system should be sufficiently to ensure that user’s queries are processed with out delay 
ü  //-----(if user start programs such as reports with very long response times, the affected work processes may be occupied for several minutes. This may mean that number of remaining work processes is not sufficient to process the queries of other users, which could cause wait times.)--
Þ      If the average DB request time is more than 500 ms
§  It can problem with missing indexes on tables and expensive SQL statements
ü  We can check for missing indexes in DB02, if we find any missing indexes .., raise the ticket to ABAPers to create the indexes for proper fields.
ü  And also Check the expensive SQL statements in St04,which are taking High disk reads, High buffer gets/misses monitoring  (detailed analysis menu-SQL request tab),if we got any expensive SQL statement ,we need to optimize that SQL statement by ABAP’ers
ü  Check and update CBO statistics (DB21)
     If the CPU time is greater than 400 ms
§  It can problem with wrong logic of the ABAP program
ü  We can analyze the time consuming transaction using STAT. Than raise the ticket to ABAPers to make correction of  wrong logic or reprogram
Þ      If the Load time is greater than 10 ms
§  It can problem with Program (PXA) and Screen (CUA) buffers are too small
ü  From ST02, We can check for the Buffer quality ,it should  be more than 90%,If it is less than 90%
ü  We can check for Swaps on buffer, swaps should be in red color and not more than 5000 swaps day, if we getting more swaps on buffers
ü  We need to increase program and screen buffer sizes
 //----- (Program (PXA) buffer: This buffer stores the compiled executable version of the ABAP programs, also known as program loads. abap/buffersize
Screen (CUA) buffer: This buffer stores menu data, buttons and related SAPGui functionality-rsdb/cua/buffersize) ---//
   If the Roll wait time is greater than 200 ms
§  Can problem with RFC connections or network communication
ü  From ST03 -We can check the average RFC + CPIC time this time indicates the time for establishing an RFC connection.
ü  This average RFC time should be less than 10 ms.

    If the Processing time is greater than CPU time
§  Can problem with CPU bottle necks and network problems
§  From ST06, we can check the CPU idle %, if high CPU loads (the CPU Idle average per hour is less than 40%, if it is more than 40% can be problem with logic of the current executing program.
ü  Then we can analyze the program which is causing top CPU TIME by using STAT
§  And also we can analyze the Top CPU processes( ST06)
ü  If work processes causing high CPU load, We can analyze the time consuming transaction using STAT .If external processes causing high CPU load, we need to terminate the external processes
§  We can check the LAN communication from ST06(detail analysis menu –check by ping tab)