.jpg){kind=small}
SUM Having mainly 6 steps,
- Extraction
- Configuration
- Checks
- Preprocessing
- Execution
- Postprocessing
Step 1.Extraction
- DDIC username and password
- Identify database & SAP version
- Checks the stack xml file
- Scanning of download directory where all the patches are placed
- Extract files to move to EPS/in
- Check SPAM version. Skip this if SPAM is already in latest version
- <SID>ADM credentials
- Pre-upgrade S-note list implementation
- Checks if the source and target system is valid for update
- Checks SAP system release
- Checks the system profiles
Step 2. Configuration
- Input parameters for type of upgrade (downtime optimizes, higher complexity, high resource assignment)
- Keep database archiving on
- Execution strategy for transaction SGEN
- Maximum number of processes to be used for load generation. SGEN Processes
- Batch Process(Uptime) & Batch Process(Downtime)
- Maximum number of DDL processes (Uptime and Downtime)
- Number of parallel import processes (R3trans -Uptime and Downtime)
- Parallel Phases (Uptime and downtime)
- Update Instances
- Enhancement package inclusion
- Add-On selection
- Modification Adjustment (SPDD transport request and SPAU transport request)
Step 3. Checks
- Space check in database, if space is Insufficient then extend tablespaces with script
- BW checks and phases
- Activation and conversion checks
- Modification support
- Preliminary upgrade processing
- List Locked SAP objects
Step 4. Preprocessing
- Check for locked objects
- ABAP Workbench locking
- Run shadow system for preparation of new release (ACT_UPG, PARDIST, SGEN)
- SPDD Adjustments
- Downtime Starts
Step 5. Execution
- Merging of shadow and Real Instance
- system upgrade
- Table conversion
- Downtime Complete
Step 6. Post-processing
- SPAU change
- Backup
- Create folder in trans directory (EHPi)
To know the exact downtime taken for this upgrade, Please find UPGANA.XML file for detailed information from the below mentioned path:
Location of the file as below
./SUM/abap/htdoc/UPGANA.XML for SUM 1.0
../SUM/abap/doc/analysis/UPGANA.XML for SUM 2.0
Phase name |
Brief details |
CHECK4NOTES_TOOL phase: |
SUM asks to implement some necessary SAP Notes |
CHECKPROF_INI phase: |
SUM checks the system profiles for problems |
CHECKSYSSTATUS phase: |
SUM reads the profiles and checks the state of the running instances |
CONFCHK_IMP phase: |
In this phase SUM checks the Operating System and Database Version |
DBCHK_PRE phase: |
SUM Determines database version and SAP release |
DBCONNCHK_INI phase: |
SUM tests if new tools can connect to the database |
DBQUERY_PRE phase: |
SUM checks the database state and asks database dependent questions |
DETMAINMODE phase: |
SUM checks the stack xml file and decides about the main program mode |
EXTRACTKRN_PRE phase: |
SUM tests a kernel DVD to install SUM in /usr/sap/<dir>/SUM/abap/exe |
INITPUT_PRE phase: |
SUM reads profiles and initializes knowledge about the system |
INSTANCELIST_PRE phase: |
SUM will gather information about the instances of the system |
JOB_RSUPDTEC phase: |
In this phase a batch job RSUPDTEC will be started. This job resolves inconsistencies in TABART-TABSPACE mapping. Log files: PSUPDTEC.LOG PSUPDTEC.ELG |
KX_CPYORG phase: |
SUM Copies the original kernel to $(PUTPATH)/exe |
PROFREAD phase: |
SUM reads the profiles and prompts for required passwords |
READCVERS_DUMP phase: |
SUM reads the CVERS table content |
READDATA_EXP phase: |
SUM tests a kernel DVD to install SUM in /usr/sap/<dir>/SUM/abap/exe |
SCAN_DOWNLOADDIR phase: |
SUM scans the download directory and extracts the packages |
TOOLCHECKXML_INI phase: |
SUM determines and checks the tool versions in SYS (the active SAP kernel directory) |
TOOLIMPD phase: |
SUM prepares the ABAP dictionary for importing upgrade tools on the standard instance |
TOOLVERSXML_UNI phase: |
SUM checks the tool versions if the system is UNICODE |
VALCHK_INI phase: |
SUM checks if the source and target system is valid for update |
VERSCHK_INI phase: |
SUM checks if the SAP system release |