DIY 3: Upgrade SAP R/3 to SAP ERP6

A step-by-step guide to upgrading from SAP R/3 to SAP ERP 6.0 (collage: grasundsterne)
A step-by-step guide to upgrading from SAP R/3 to SAP ERP 6.0 (collage: grasundsterne)

Carrying out an ERP upgrade is complicated, unpredictable, and takes months. Such projects are often the cause of long faces in IT departments and – contrary to a commonly held perception – do involve risks in transferring data and switching between hardware. However, even a complex transition from SAP R/3 to the current SAP ERP 6.0 can go off without a hitch in your IT department.

Many new functions, a significantly improved process structure, and a reasonable price – the latest version of SAP ERP certainly isn’t short on qualities both large companies and smaller businesses in the up-and-coming midmarket can appreciate. For more, also check out “EHP: Keeping SAP Up to Date” and “Preview: EHP 5.

Having attracted a number of attentive readers since its debut some days ago, this article series now turns its focus to the incremental progression of the software upgrade itself. Our aim is to allay any fears those interested might have about the transition and go through each of the primary steps in a practical setting. In case you missed them, here are the first two parts already published in this series:

  1. DIY: Upgrade SAP R/3 to SAP ERP 6.0
  2. DIY 2: Upgrade SAP R/3 to SAP ERP 6.0

The initial installment offers a rough overview of the complete software upgrade, and in the second we demonstrate how to install updates in an older SAP system and upgrade a SQL collation (database) – all while switching from a 32- to a 64-bit configuration.

In part three, we begin with the installation of SAP R/3 on a new server that will eventually become a productive system. We then import file backups from the previous SAP system before proceeding with the database upgrade from Microsoft SQL 2000 to 2005. The links directly below offer a quick run-through of these steps:

Next page: Installing SAP R/3 on a new server

Exemplarisch für frische R/3-Installation: HP Proliant DL 380
Perfect for a fresh SAP /R/3 installation: HP Proliant DL 380

Installing SAP R/3 4.7×200 on a new server

Höchstleistung auf kleinem Raum: Neuer Server für zukünftiges ERP 6.0
Maximum performance, minimal footprint: a new server for a future SAP ERP 6.0 system

In the second part of this series, we first installed Windows Server 2003 x64 on a new server and configured of the initial settings. Even though we’re going to install SAP ERP 6.0 in a later step, the new system must first run the same software version as the old – in our case, SAP R/3 4.7×200. The initial step in doing so involves entering the transhost for the system with the following command:


For the x64 installation, the system variable JAVA_HOME should be set to JS2E, which is available for download on Sun’s Web site (direct link to download Java SDK: j2sdk1.4.2_17-x64)


In switching from a 32-bit Intel Xeon server to a 64-bit hardware system, it is crucial to install the x86-64 (AMD64) files; these can be found on the SAP master CD – which is available on a network drive at this point – in the following directory:


While the old server runs the 32-bit version of SAP R/3 and the 32-bit 6.40 NUC kernel, the new installation is based around the kernel’s 64-bit variant. The screenshot below displays the “sapinst.exe” file (located in the directory specified above) needed to begin the installation.


The installation process creates a login for the user (SAPServiceECP) and assigns it the permissions of the sysadmin role. The software installed can be checked by starting the program. Assuming everything works correctly, the data can then be mirrored from the old SAP system to the new server using the homogeneous system copy (HSC) method. The existing database is overwritten in the process!

Next page: importing a server backup

Everything old is new again: importing a server backup

Erstellen der Users und Schemas
Creating users and schemas
Kontrolle der Einstellungen
Checking the settings
Überprüfen der Collation: BIN2 auf dem alten Server
Checking the BIN2 collation on the old server
Kommandos: use ECP und exec sap_droproc
Commands: “use ECP” and “exec sap_droproc”
Überprüfen der Logins, Zugriffsrechte und Regeln für ecpadm und SAPServiceECP
Checking the users, access permissions, and rules for ecpadm and SAPServiceECP
Anzeige der Datenbank-Version: MS SQL2000
Displayed database version: MS SQL 2000
Query Analyzer: Gelöschte Tabellen aus der Datenbank
Query Analyzer: tables truncated from the database

Next page: upgrading a database from MS SQL 2000 to 2005

Upgrading a database from MS SQL 2000 to 2005

Herunterladen der SAP-Tools für MS SQL Server aus dem Marketplace
Downloading the SAP tools for MS SQL Server from SAP Service Marketplace
Aufruf von sapinst.exe zur Datenbank-Copy
Running “sapinst.exe” to copy the database
Auswahl: Komplette Datenbank-Kopie
Selecting the database copy option
Eingabe der Login-Daten
Entering login information
Angabe der Datenbank-Verbindung
Specifying the target database for the connection
Konvertierung zum neuen User Schema
Converting to the new user schema


Fertig: Kopie der Datenbank mit SAP Tools für SQL Server
Finished copying the database with SAP Tools for MS SQL Server
Ändern des Kernels von 640_NUC_32Bit auf 640_NUC_64Bit
Upgrading the kernel from 640_NUC_32Bit to 640_NUC_64Bit