Skip to Content
avatar image
Former Member

ECC 6 EHP6 to EHP8 (OS/DB Upgrade) Same SID Windows Domain Installation

Hi Experts,

I have a requirement for my existing customer to Upgrade Ecc 6 EHP6 to EHP 8 .As per the guides & PAM , the current OS & DB is not supported on exisiting hardware and has to be upgrade/migrated to new hardware with new OS & DB .Below are my source and traget details to have better idea,

Source System
OS : Windows 2008 R2
DB : Sybase ASE 15.7
SAP: ECC EHP 6 NW 7.31

Target System
OS : Windows 2012 R2
DB : Sybase ASE 16

Sap Components Involved in landscape ECC , PI , SRM , SUS/ROS , EP ,BI/BO .

I have planned to go with parallel landscape strategy for this upgrade project so that I can minimize the downtime and code freeze to lesser extent as much as possible.Definitely , I will be using the Homogeneous System Copy Export/Import approach during this project but I was wondering on SID Strategy to be used during System Copy on new server.
Please note all my non production & production systems are domain installations and I want to use the same SID on new server with domain installation and also the old productive landscape will be up running till go live .

Will there be any impact using the same SID .I know technically its possible but will there be any impact because in current landscape PI system plays major role for us in PO replications from ECC & SRM System. My main intention to use same SID to avoid the other efforts in re-configuration on Sap Systems.

Will there not be any consequences on Windows Active Directory as same SIDADM & SAPServiceSID already available adn during installation conflicts at user creation phase.Lastly , we have to follow sap best practice .

Your expert suggestion will help me in taking right decision and approach for using same SID or different.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers