Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

SAP Migration to Windows Question

We are in need of some technical direction in performing a SAP migration from UNIX to Windows. We are running SAP ECC 5.0 (ABAP only) on Sun Solaris UNIX with an Oracle 10g database. The UNIX database server contains both the SAP Central Instance and the Oracle database. Our production environment also contains three separate UNIX servers that contain secondary SAP ECC 5.0 Application Server Instances. We must move all of the SAP Instances, including the Central Instance, to new Windows servers. But, the Oracle 10g database will remain in its current location on the UNIX server and will not be migrated. This is not a straight forward migration since the database is not being moved. We cannot find any official SAP documentation that covers this particular situation.

As a side note, we will be performing a SAP upgrade from ECC 5.0 to ECC 6.0 in conjunction with the migration of our SAP instances. This can be viewed as two separate projects, but we must perform the downtime portion of both tasks during the same weekend. The ECC 6.0 upgrade will be performed using a u201CSystem Switch Upgradeu201D strategy (Downtime minimized) that utilizes a shadow instance and repository switch. Therefore, a large portion of the upgrade will be performed while the system is available during the week and then the downtime part will be performed on the weekend.

Does anyone have any recommendations on how best to approach migrating just the SAP instances from UNIX to Windows (keeping in mind that the database is not moving and we are also performing an upgrade to ECC 6.0 along with the migration)?

Here are some specific scenarios that we have been discussing:

Scenario 1 (New Installation of SAP Windows Instances pointing to Existing Oracle/UNIX database)

Shutdown all SAP instances on UNIX. Perform a new distributed SAP installation on Windows, but skip the database instance portion of the procedure. We would need to identify and manually perform any items (such as profile modifications and kernel extractions) that would have been performed during the database instance installation. How is the best way to identify the manual steps that we would need to perform (in place of running the database instance installation step)?

Scenario 2 (System Copy)

We cannot find a SAP procedure that covers the combination of performing a Heterogeneous System Copy with the Database-Specific method. The SAP System Copy guide only discusses Heterogeneous System Copy with the Database-Independent method. Is it possible to perform a System Copy for this particular situation without unloading/loading the database?

Also, we are wondering if it would be best to migrate the SAP Instances to Windows before or after the upgrade to ECC 6.0 (given the fact that both will need to be done on the same weekend)?

Thanks in advance for any thoughts and/or recommendations that can be provided.

Former Member
Not what you were looking for? View more on this topic or Ask a question