Support Packs installations

Support Packs
Support pack installations are mini-upgrades, the purpose of a Support Pack is to provide a bundle of fixes that have all been tested together. A Support Package corrects errors in the SAP System or makes necessary adjustments, for example, due to legal changes. The objects affected are replaced in your system.Each Support Package is valid for only one release (but for all databases and operating systems) and requires an exactly defined number of predecessors.

The following types of Support Packages are available:

• SPAM/SAINT Update: A SPAM/SAINT Update (PAT) contains updates and improvements to the SAP Patch Manager and the SAP Add-On Installation Tool.
• FCS Support Package: An FCS Support Package (FFD) updates an FCS system to its General Availability release so that other Support Packages can be imported.
• Component Support Package: This type of Support Package (COP) is valid for one software component (SAP_BASIS, SAP_HR, SAP_APPL) and contains corrections to errors in the Repository and Dictionary in this software component only.
• BW Support Package: A BW Support Package (BWP) is a Support Package for the software component SAP Business Information Warehouse (SAP_BW) and only contains corrections for this component.
• Add-On Support Package: An Add-On Support Package (AOP) is valid for an add-on with a particular release and contains corrections for this add-on.
• Conflict Resolution Transport: A Conflict Resolution Transport CRT is exclusively used for add-ons, for example, IS-IS or IS-OIL. It resolves conflicts that can occur between Support Packages and an add-on.

Before going to applying support packages you should follow the some prerequisites:

1. SPAM/SAINT should be latest version( always apply support packages to the level n-1)
2. No aborted packages in your system
3. Minimum two background work process are available
4. Free space in EPS directory
5. Must read the note for following sequence of support packs
6. Latest Kernel version (Upgrade "Kernel")

Update Saint Tool:

1. Download required version
2. Uncar and keep in eps/in
3. Go to SPAM
4. Go to Support Package
5. Click import saint/spam update
6. This step will take some time and then  click on green ok button
7. Some time it will throw error ….no need to worry just go to spam steps 5 again and the version will change  
8. http://www.sapbasistuts.com/home/abap-stack/abap-stack-wiki/sap-spam-saint-update

SPAM Steps 
The SAP Patch Manager informs you of the status of the step currently being executed in the status bar. If you want to know which steps are executed for which scenario, run the program RSSPAM10.
The following list explains the steps executed by SPAM in the order in which they are performed.
1.PROLOGUE: In this step, the system checks if you are authorized to import Support Packages.
2.CHECK_REQUIREMENTS: In this step, various requirements are checked for importing a Support Package, for example, the transport control program tp logging on to your system.
3.DISASSEMBLE: In this step, files from the corresponding EPS parcels are disassembled, or unpacked, and stored in the directory.
4.ADD_TO_BUFFER: In this step, the queue is put into the transport buffer of your system.
5.TEST_IMPORT: In this step, the system checks if there are still objects in tasks that have not yet been released and are overwritten when the Support Package is imported.
6.IMPORT_OBJECT_LIST: In this step, the object lists for the Support Packages in the queue are imported into the system.
7.OBJECTS_LOCKED_?: In this step, the system checks if there are still objects in tasks that have not yet been released and are overwritten when the Support Package is imported.
8.SCHEDULE_RDDIMPDP: In this step, the transport daemon (program RDDIMPDP) is scheduled.
9.ADDON_CONFLICTS_: In this step, the system checks if there are conflicts between objects in the queue and installed add-ons.
10.SPDD_SPAU_CHECK: In this step, the system checks if a modification adjustment is necessary (Transactions SPDD/SPAU).
11.DDIC_IMPORT: In this step, all the ABAP Dictionary objects of the queue are imported.
12.AUTO_MOD_SPDD: In this step, the system checks if modifications to the ABAP Dictionary objects can be adjusted automatically.
13.RUN_SPDD_: In this step, you are asked to adjust your modifications to the ABAP Dictionary objects by calling Transaction SPDD.
14.IMPORT_PROPER: In this step, all the Repository objects and table entries are imported. Then actions such as distribution, conversion, activation and generation occur.
15.AUTO_MOD_SPAU: In this step, the system checks if modifications can be adjusted automatically.
16.RUN_SPAU_: In this step, you are asked to adjust your modifications to the Repository objects by calling Transaction SPAU.
17.EPILOGUE: In this step, the import of the Support Package is ended. The system checks if the queue has been completely processed.

• Log files will be under /usr/sap/trans/log. Log files are not created for all the phases.
• If you want to know which steps are executed for which scenario, run the program RSSPAM10 

Steps to applying SAP Support packages

1. Login from DDIC and enter Tcode SPAM, Click on Package level to know the existing level of the support packs and the add-ons.
2. Go to transaction SPAM and Load the support packages from frontend if it is < 10 MB. The support packages which are in the form of .car will be decompressed into eps/in directory.  
3. If the size is > 10mb, copy the support packages to /trans directory and uncar the support packages using the below command 
4. cmd>cd usr\sap\trans
5. sapcar –xvf .car
6. The command SAPCAR will decompress the CAR file and put two files (with extensions .ATT and .PAT in the /usr/sap/trans/EPS/in directory.
7. Go to SPAM from DDIC and client 000 and click on Display/define A box will appear with the Support Package categories, Click on the category for the support packages that you uploaded and it will list them in order. You can apply them individually or the whole list at one time.
8. Go to support package click import queue (or) Click on truck icon.
9. Click on continue after importing in to the Queue.
10. Click Continue.

Note: - While applying support packages it triggers two phases SPAU and SPDD 

• SPDD

When the support packages contain any changes in the data dictionary then this phase is invoked.

• SPAU

When the support packages contain the changes related to repository objects SPAU phase is invoked.  it prompts whether to keep to existing changes modified by notes or adapt to changes.

Modification Adjustment during Import of Support Packages Use: - If SAP modified objects that have also been modified by the customer, a modification adjustment is executed in the transactions SPDD and SPAU during import of Support packages.

Procedure

• As far as the modification adjustment is concerned, you use the common procedure described below to import Support Packages:
• Create two change requests in the Workbench Organizer (transaction SE09), one for the modification adjustment with transaction SPDD and the other one for the modification adjustment in transaction SPAU.
• Create a task for each developer who is involved in the modification adjustment.
• The developers must use transactions SPDD and SPAU to determine whether to retain or delete the modifications.
• After modification adjustment is finished, the developers must release their tasks.
• Use transaction SPAM to access the SAP Patch Manager.
• Choose Patch -> Import Patch Queue. A confirmation dialog window appears.
• Choose Enter to finish the import process of the Support Package.
• Release the change requests that result from the modification adjustment using transactions SPAU and SPDD.

It prompts you the Queue is imported successfully and asks to confirm the queue.
Go to -> SPAM -> Support Package -> Confirm the Queue
This shows the support package has implemented for the one of the queue and you need to do the same as for the other queue (software components).

Post processing for support package 

1. Check if any alerts or error messages in SICK and SM21.
2. Release all the background jobs (BTCTRNS2).
3. Unlock all the users.
4. Run SGEN (SGEN compiles all programs.SGEN reduces abap load on the system).

ABAP Stack SP Upgrade:

1. Download required sp's from service marketplace.
2. Extract downloaded files to your "saptranshost"
3. Logon your system (client 000) with user that has "SAP-ALL" authorization.
4. Run transaction SPAM, define queue, and start import.

JAVA Stack SP Upgrade:

1. Download required sp's from marketplace.
2. Unpack the files or move them to the "saptranshost" depending of your release.
3. Run SAPINST or JSPM depending on your release.

ABAP+JAVA Dual Stack systems SP Upgrade:

• Patch ABAP Stack as described.
• Patch JAVA Stack as described.

Question and answer:
Q. When you will apply patches? Give short of examples the situation, where to troubleshoot you have applied patches!
Q.Why it`s required to shut down all SAP, Database instances & services during kernel up-gradation.
A. Because SAP system and database uses kernel service starsapsrv.exe for their functioning, if the service file to be updated is in use, kernel upgrade is not possible then. 
Q. Why it`s required to keep all instances up during the updating hot package?
A. Because SAP system process the system tables/object and modifying them during updating hot package besides hot packages are the most basis packages required for SAP system to work fine. 
Q. Can we apply higher version Patch Level using lower version of SPAM? 
A. NO
Q. What is importance of Import Queue?
Maintain the support packs selected. 
Check the dependency, actually queue can’t be defined unless the dependencies of selected components meet and let them apply in order. 
Q. Can we apply higher level of HR or other Financial Patch with lower version of ABAP/BASIS patch level?
A. Never. Because SAP Basis/ABAP are the most basic components that need to be updated before you can update any components. 
Q. Is there any sequence to apply hot packages?
A. Means, BASIS – ABAP – HR – FIN or HR – FIN – ABAP – BASIS vice versa Basis and ABAP should be at first then others. 
Q. BASIS and ABAP patch level should be same. So first which patch level should be updated ABAP or BASIS? If BASIS then why? If ABAP then why?
A. Not necessary for them to be at same patch level. Though standard says they should be at same level.  Generally we apply BASIS and ABAP together. If we have to apply one at first, it should be basis. 
Q. Why you update SPAM version before applying other patches? What is the logic behind this?
A. A SPAM/SAINT Update (PAT) contains updates and improvements to the SAP Patch Manager and the SAP Add-On Installation Tool. 
Q. How you will decompress the downloaded compressed patch files? After decompression what are the two files generated. State the names of that files & type of the files? 
A. SAPcar –xvf filename.sar
They will contain PTT and ATT files.
Q. Why we login as DDIC user at the time of patch administration? If we logged as different user, what will the problem?
A. Users are locked generally for SPAM upgrade. Hence use DDIC, its standard SAP user. 
Q. Updating the patch level means Updating of SAP system or Upgrading SAP system?
A. Updating the SAP system
Q. Why Support packages are required
A. A support packages is a quantity of corrected SAP objects.
Support packages are required to correct errors in various components. This is done by replacing erroneous objects with corrected versions of these objects.
Each software component has a separate sequence of Support Packages. 
Q. How from Client 000, all clients exists in SAP system get effected?  In which table these stored?
A. It updates standard table’s objects and data dictionary objects which are accessible by all the clients.

EHP UPGRADE

ASAP ROADMAP

The ASAP Roadmap provides the methodology for implementing and continuously optimizing your SAP System. ASAP Methodology for Implementation is the SAP roadmap for implementing SAP solutions in a cost-effective, speedy manner.

Standard ASAP 8 Methodology Phases-The Standard ASAP 8 Methodology is structured into the following phases.

1. Project preparation - During this phase the team goes through initial planning and preparation for SAP project.

2. Business blueprint - The purpose of this phase is to achieve a common understanding of how the company intends to run SAP to support their business. In Standard ASAP 8 Methodology the result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops

3. Realization - The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration in Standard ASAP 8 Methodology is done in two work packages: Baseline configuration (major scope); and Final configuration (remaining scope). During this phase the solution is also tested.

4. Final preparation - The purpose of this phase is to complete the final preparation (including technical testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System.

5. Go-live support - The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation.

6. Operate - During this phase the system is operated with the help of the central operation platform, SAP Solution Manager, with the documented solution based on the transferred project documentation.

Need of phases

These phases are the main milestones for your SAP System implementation project. Each phase has:

•Work packages, which consist of activities, for which project teams are responsible.

•Activities, which consist of tasks, which are processed by one or more team members.

•Tasks, which are carried out by a project team member. You can also access the How-to sections and accelerators at this level.

What is an SAP EHP Upgrade?

It's the installation of a new SAP ERP software version, together with the accumulation of all the relevant fixes in the form of a Support Package Stack.

Upgrade Tools

          •PANAYA

          •SUM

          •solution browser

          •SAPUp – SAP Upgrade

          •SAPEhpi - SAP enhancement package installer

          •SUM – Software Update Manager

SUM

Traditionally for applying SPS we use SPAM for ABAP & JSPM for Java

Some of the benefits of using SUM tool over these tools among others are

          •Two different tools are not required to apply SPS. One SUM tool is used.

          •No need to uncar the SAR files.

          •Minimum downtime (Single downtime for both ABAP & Java combined).

          •Simultaneously the SPS are applied to both the stacks.

Note:

          Before you start the SUM tool do ensure that

          •Latest Kernel is applied to the Source System

          •Latest SPAM patch is applied.

          Clone Mode: The Software Update Manager checks the tables in the database which will be cloned to the shadow system later on during the update. Here a shadow instance will be created with tables copied from source system.

          Next input screens will ask for SPAM update. The SPAM was already updated; we choose to ignore the SPAM update. As in case of other tools such as SAPup & EHPI tool, SUM tool will also prompt for any missing notes that should be applied

SUM STEPS:

          0. Administrator user and pass

          1. Welcome:

          2. Specify credential:

          3. Select target:

          4. Conform target:

          5. Execute process:

             5.1 Initialization
             5.2 Extraction
             5.3 Configuration
             5.4 Check
             5.5 Preprocessing
             5.6 Execution
             5.7 Post processing
             5.8 Finalization

          6. Summary: 

PRE STEPS:

1. Install maintenance license
2. Prepare stack.xml and download software.
3. Install SUM as adm
          STEPS:
          1. cd /sapcd/XXX702SPS08
          2. SAPCAR –xvf //.SAR -R /usr/sap/
          3. SAPCAR -xvf SUM10SP08_1-20006543.SAR -R /usr/sap/xxx
          4. Change ownership to sidadm:sapsys on /usr/sap/XXX/SUM
          5. Change permission to 777 on /usr/sap/XXX/SUM
4. Create and/or give Basis user in 000 and 300 client, assign SAP_ALL and SAP_NEW in system being upgrade.
5. Recommendation for Oracle 11.2: Apply latest Patch Set
6. Turn off backup
6. Database Passwords: Do not use the '@' character in your database passwords, as the                                            Software Update Manager cannot handle the passwords then.
7. Increase the OPEN_CURSORS Parameter:Alter system set open_cursors = 20000 scope=both;
8. UPDATE STATS
          brconnect -u / -c -f stats -t oradict_stats
          brconnect -u / -c -f stats -t system_stats
          brconnect -c -u / -f stats -t all -f collect -p 4
Note:
Oradict_stats: Collects statistics for Oracle dictionary objects using DBMS_STATS package. For more information, see SAP Note 863811.
system_stats: Collects system (CPU, I/O) statistics using the DBMS_STATS package. For more information, see SAP Note 601395
9. Calculate Space Statistics before the Upgrade/Update
    brconnect -u / -c -f stats -t all -m +I -s P1 -f allsel, collect, method, precision -p 4
10. Make copy of profiles.
11. SAPSR3 Tablespace free space should be more than 75GB free
12. Make sure there’s no lock objects – release all transports
13. Turn off archive mode (If you can’t, you’ll have a chance to do so before downtime)
14. Check disk space in the file systems, SUM and current SAP mounts need to have at least 200GB free or larger
15. Check DIR_TRANS, clean up /EPS/in directory
16. Add more data files to tablespaces
17. Check path and empty /usr/sap/trans/EPS/in

UPGRADE:

1. Start SUM as adm

          STEPS:

          1. cd /UPGRADE/SUM/SUM/

          2. ./STARTUP (It Will Start SL Controller)

          3. Run SUM GUI

          5. CD /UPGRADE/SUM/SUM/SDT/EXE

          6. ./DSUgui

                             OR from Browser

          4. http://:4239

2. Start phases

   SUM STEPS:

     0. It will ask for Administrator user and pass we can give any user name and pass but this person will be responsible for whole upgrade. The role should be Administrator.

  

     1. Welcome: In this phase we generally get the information of Detected SAP NetWeaver System. Like System technology: ABAP SYSTEM id: KUN, System Directory: /usr/sap/KUN It also recommended Reading note 1790828

     2. Specify credential: this Part Used to ask about SIDADM Password so Provide KUNADM as user and password as *******

     3. Select target: This part having two options one for Stack.xml file and manually prepared directory. We choose the location of Stack.XML File with XML name. EX-/usr/sap/KUN/ECCEHP6/SMSDXML_KUN_20130816212838.269.xml

     4. Conform target: target release is confirmed here it will show current version and ehp of system and the target version of the system where we are going also it will say to enter a keyword from a snote mention in the screen. 

     5. Execute process

            5.1Initialization: 

            5.2 Extraction: Once you click next to go to Extraction Phase, it will ask for DDIC user Password and also Database user SYSTEM password. The Extraction phase will extract the relevant files from the download directory.

Next input screens will ask for SPAM update. The SPAM was already updated; we choose to ignore the SPAM update. As in case of other tools such as SAPup & EHPI tool, SUM tool will also prompt for any missing notes that should be applied.

ERROR!!

Solution:

You’ll need to manually exchange R3trans & TP from /sapcd/sapcd/KUNUpgrade2013/KernelDuringKUNUpgrade***cp R3trans tp /usr/sap/KUN/SUM/abap/exe

Restart SUM step

          5.3 Configuration: Here we mainly choose standard option and don’t check the check boxes about archiving and expert mode. Here it will ask number of Processes during up time and during down time like Batch, DDL, R3Trans etc. Usually we keep default Value. After 2 Hours we will get another screen which will ask for Addons. The Java configuration steps also starts. With SUM tool you can choose to automatically update the additional dialog instances if any. In older times we had to manually uninstall and install dialog instances

           5.4 Check: It will check for the Spaces in database. If space is not available then create Tablespace for space

Solution:

          create tablespace PSAPSR3731 extent management local autoallocate segment space management auto datafile '/oracle/XXX/sapdata2/xx3731_1/xx3731.data1' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_2/xx3731.data2' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_3/xx3731.data3' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_4/xx3731.data4' size 10000M autoextend off, '/oracle/XXX/sapdata2/xx3731_5/xx3731.data5' size 10000M autoextend off

OR Send an email to the DB2 Team to add the space

        5.5 Preprocessing: In this phase SUM prepare the system for Upgrade.

Here we will have to move the SPDD TR#DR2K900020 into shadow system

Make sure the data & cofiles are available in /upgrade/SUM/SUM/abap/cofiles & /upgrade/SUM/SUM/abap/data with correct owner ship & permissions

Login to KUN shadow system with DDIC/000 client and create an dummy user (abapddic is created) user with su01 with an copy from DDIC

Goto SE06 ->System change option and check if it is modifiable

Import the SPDD TR into shadow system

Execute SE38-> UPGACTKORR

Give the SPDD TR(DR2K900020) in the Request name and execute. This will activate the request in the shadow system

Later on confirm with the Abap Team on SPDD TR and proceed further with the upgrade once everything is fine.

Error – “SQL10003C There are not enough system resources to process the request. The request cannot be processed. SQLSTATE=57011”.

Solution – Sent mail to DB2 DBA Team to increase the database buffer.

Possible Error: Batch job RSVBCHCK Failed with error code 8

                   SM13: Repeat or Delete all update records

                   1873772 - Last error code set: Single errors (code <= 8) found in logfile 'PSVBCHCK.ELG'

                   Transaction LBWQ; Delete all queues;

                   Transaction LBWG; Delete 06/13

        5.6 Execution: In this phase SUM perform actual update in the system and downtime begin this phase take a long time.

Error occurred during the XPRAS execution

Solution – Continued by selecting Accept on “Accept non-severe errors and repeat phase MAIN_NEWBAS/XPRAS_AIMMRG”.

Other Solution:

This is due to multiple active BADI implementations. READ 1835882 - Error in XPRAS_AIMMRG phase during EHP installation for BADI Multiple active implementations

Steps to recover:

• Unlock TP
  • Cd /usr/sap/trans/SRD/bintp unlocksys SID  pf=TP_DOMAIN_SRD.PFL
  • Login to client 000, unlock scc4 and se06SE18, Enhancement implementation àoverview, double click the new /LOCSRM/***, deactivate that new BADI implementation, create new transport and release it before continue.

When finish, repeat the phase

             Possible Error: Calling usr/sap/XXX/DVEBMG/tp failed with return code 8.

                   Solution: Note 912369 - FINB_TR_DEST, after import failures, transport errors

                   Transaction: /nFINB_TR_DEST at client 000

                   Create RFC FINBTR@XXXCLNT001 and FINBTR@XXCLNT300; Under RFC, input client with DDIC user/pwd.

                   1 .In the next Screen it will ask u to take Backup of ur database if you already done click action completed and hit Next.

                   2. End of downtime notification

          5.7 Post processing:

         In this phase system will unlock and downtime finished. In this phase some manual action required some of them are

                   1. we can reschedule the periodic job which has been DE schedule during downtime.to reschedule these job we can run a report BTSTRNS2 using DDIC user in transaction SE38.

                   2. Application specific post upgrade activity. Start ASU toolbox using transaction /ASU/UPGRADE

                   3. see the log of SUM from usr/sap/XXX/SUM/ABAP/log/LONGPOST.LOG and from message class and message number we and applied the relevant Snote.

           5.8 Finalization

   

          6. Summary: This phase will give the target version which completed and total time and system downtime.

POST UPGRADE

1. Implement note 1720495 before you start transaction SPAU (Note 1790828); Manual step is not needed. Make sure to implement SAP note 1720495 immediately after a Support Package import, an enhancement package installation, or an upgrade and before making any adjustments in transaction SPAU

2. If you have SAP Kernel 7.10 or higher:
  Execute the following commands:
  cd /abap/exe
  ./oraroot.sh
  If you have an MCOD system and/or the database name does not correspond to the SAP      system name, use the following command to run oraroot.sh:
  ./oraroot.sh
  If you have one kernel directory: cd /usr/sap//SYS/exe/run
  If you have two kernel directories: cd /sapmnt//exe/(n)uc/
  cp -p ./icmbnd.new ./icmbnd
  chown root:sapsys icmbnd
  chmod 4750 icmbnd
  exit
  cd $ORACLE_HOME/dbs
  cp /usr/sap//SYS/exe/run/sapdba_role.sql sapdba_role.sql
  sqlplus /nolog @sapdba_role.sql SR3

3. Call transaction STMS and choose OverviewSystems.
  Double-click the system that has been upgraded and switch to the Change mode.
  Do not change anything unless another action requires changes, and choose Save. Go back to the system overview.
4. Checking for Unused Indexes
  Call transaction DB02.
  Choose Missing Tables/Indexes.
  Choose Unknown objects in ABAP Dictionary.
  Check if there are unused indexes in the database. If this is the case, delete them manually.
  For more information, see SAP Note 1227270

5. Oracle: Deleting Tablespaces    
  Select table_name, tablespace_name from dba_tables where    TABLESPACE_NAME='PSAPSR3702';
  Select index_name from dba_indexes where tablespace_name='PSAPSR3702';
  Note 1819182 - Tables (TTREE*) remain in old exchange tablespace
  In transaction SE13 or SE11, change the data type SSEXC to APPL0 for the tables and activate your data. After you do this, you can use
          a) SE14
          b) ICNV
          c) DB tools
  to move the table to a different tablespace (for TABART APPL0).
  SE11-> Technical Setting -> change data class from SSEXC to APPL0
  Check TAORA for APP0
          1. Call transaction ICNV and read the online documentation ("I" button"). Converting a table using ICNV is a complex procedure during which, for example, changes to the table contents are made using a database trigger. It is important that you have a basic understanding of how the transaction works.
          2. Call transaction SE14, enter the name of the table that you want to move and select "Edit" and then "Storage Parameters".
          3. Select "For new creation" and use the "current database parameters" as a template (if required). Switch to "Change" mode.
          4. After "TABLESPACE" and "INDEXSPACE", enter the new tablespaces required for the tables or index data.(Change PSAPSR3702 to PSAPSR3)
          5. Save your entries.
          6. Call transaction ICNV.
          7. Select "Edit->Add table" and enter the name of the table that you want to move. Do not change the proposed scenario.
         8. Follow the steps proposed by the wizard (choose "Assistant" or perform the following steps manually using the "Control" menu).
            a) Initialization
            b) Data transfer
            c) Transfer
            d) Delete entry
  Shutdown Oracle;
  brspace –f tsdrop
  brspace -c force -o process, time -u / -f tbreorg -a reorg -tablespace PSAPSR3702 -t "*" -parallel 3 -degree 3 -newts PSAPSR3
  Problem:
  ZPPSFIF004
  But when I was trying to upload a file from application server to table using a z program found the below error.
  Solution:
  Fix RFC WEBMETHOD.
          #1859173 - Taking into account of external services in SU25, improved display in step 2b
          #1850378 - Handling of (historically created) defective modification flags in SU24 data by SU25
          #1878702 - Optimizing the navigation in step 2b and the transport connection

6. Make sure client 000 is locked in SCC4
7. Set SE06>System Change Option back to original
8. Shutdown SAP
  As root, run ./saproot.sh SID in /sapmnt/SID/exe
  Rename folder /oracle/netbackup_script.bak to netbackup_script.bak
  Create link for netbackup

IMPORTANT QUESTION:

     Q. How we will know that shadow instance has been created in preprocessing Phase?

     A. Pf – ef | grep shd Note: Shadow instance will +1 more than instance, 00 will 01

     Q. There is a report we need to run in preprocessing Phase during SPAU/SPAD?

     A. UPGACTKORR Its Activate Request in Shadow System.

     Q. How to unlock shadow system and why we use it?

     A. usr/sap/sid/upg/abap/bin

    ./sapup unlockSHD SSH

     Q. How many Minimum Background work processes needed in EHP Upgrade?

     A. 4

     Q. What used to happen during Downtime?

     A. 1. Kernel Switch from old kernel to new kernel

         2. Table conversion

         3. User will not able to login 

     Q. What is /ASU/upgrade?

• It use for Start ASU Toolbox in Upgrade Mode.
• It interacts with tables, function modules, methods, classes etc.
• It comes in Post processing phase of the UPGRADE

     ASU Toolbox

• It is SAP tool in ST-PI
• It generates client-specific task list
• Transaction /n/ASU/UPGRADE

     Q. Reset Administrator password of SUM.

• Stop SUM
• Rename two files .sdt_storage & .sdt_keystorage from \SUM\sdt\data OR
• Delete the file ".sdt_storage"
• Start SUM

Courtesy : Quicksap blog