Thursday, February 2, 2012

apply support packs & errors faced while deployed support packs


SUPPORT PACKAGES AND PATCHES
  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).
PRE-REQUISITES OF SUPPORT-PACKAGES
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.
PROCESS
1)      Download the packages from market place using url www.service.sap.com/swdc-support 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.
SPDD/SPAU PHASE:
·         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.
ISSUES
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
26.DISABLE SAP USERS TO LOGON MULTIPLE TIMES27.SUPPRESS SAP MULTI LOGIN MESSAGE28.ADDING TEXT TO THE SAP LOGON/LOGIN SCREEN



Reactions:

0 comments:

Post a Comment