SUM Having mainly 6 steps,
- Extraction
- Configuration
- Checks
- Preprocessing
- Execution
- Postprocessing
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
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)
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
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
5. Execution
- Merging of shadow and Real Instance
- system upgrade
- Table conversion
- Downtime Complete
6. Post-processing
- SPAU change
- Backup
- Create folder in trans directory (EHPi)
No comments:
Post a Comment