Perform Kernel upgrade on source if required.
Cleanup Inbound/Outbound(SMQ1/SMQ2) queues.In case you are upgrading the second system in the landscape Import TR for SAP notes 001680583,0001678047,1609895,1861585 and can be imported before the upgrade and hence you can skip this step during the SUM checks, else you need to implement the above mentioned notes in DEV system and then generate a TR for the same.should not be present and removed from the location, See SAP note 1649026. Cleanup profile directory and only active and relevant profiles should be there, all the backup profiles etc.1639578,15479837 notes should be referred to setup the new DB connection before the issue arises( – Secure connection of AS ABAP to Oracle via SSFS for removal of OPS$ mechanism).OS level user: SIDADM and ORASID, SAP level user DDIC password in all the clients should be known prior to start and in 000 ,System user password is required for DB.Update SPAM/SAINT to latest version and in the EPS we have SPAM/SAINT 51 so do it in advance.Making Preparations in the Monitoring AreaĬhecking the Requirements for the Modification Adjustment Checking the Number of Background Processes Setting the Operation Mode for the Update Checking the Structural Requirements for ABAP
Checking the Software Delivery Manager Version Checking the Software Update Manager Version, Please try and ensure that we have latest Tool SUM 1.0 SP10 Upgrade of the Operating System and Database System if required Meeting the Operating System-Specific Requirements Checking the Source Release of the SAP System Below are the Source and Target Details during the ECC 6.0 EhP7 Upgrade for our System upgrade
0 kommentar(er)
