Part 2: Upgrade SAP R/3 to SAP ERP 6.0

August 25, 2010 | SAP News | David Velez | 0 Comment

Thinking of upgrading your SAP software? We show you how to import updates, select the right SQL collation, and transfer from 32 bits to 64 bits. Read on for the details in part two of our series.

DIY part 2: updating an old system and preparing new servers (collage: grasundsterne)

How does transferring from SAP R/3 to SAP ERP 6.0 work in principle? What updates do you need? How is data exported from the old system and imported to the new? What do you need to think about when switching from 32 bits to 64 bits? Such questions are on the minds of CIOs at companies that are currently planning a software upgrade to SAP ERP. Upgrades are often triggered when a company undergoes modernization or gets new server hardware, because more powerful processors with several computational kernels, larger working memory, and faster hard disks become available.

However, it is often the case that the old system works as it always did, and with its known weaknesses, such as a process chain that isn’t digital from end to end and custom-built modifications. In such cases, companies should be aware of the fact that the end of SAP R/3 maintenance is on the horizon. Furthermore, an upgrade brings with it very many of the benefits that companies need to remain future-proof.

In part one of our series – see the article DIY: Upgrade SAP R/3 to SAP ERP 6.0 – we had a look at the software upgrade process in general. In part two, we’ll now take a closer look at the following steps:

1. Old 32-bit system: Setting collation *BIN2 for SQL Server 2000
2. Old 32-bit system: Applying SAP Support Packages and 1:1 backup copy
3. New 64-bit system: Installing Microsoft Windows Server 2003 x64 Edition
4. New 64-bit system: Settings for the network and paging file
5. New 64-bit system: ECC 6.0 upgrade CDs and installing SQL Server 2005

Again, we’re showing you all the updates and settings using the example of the ITU in Geneva, which was one of the first companies in Switzerland to switch to the latest ERP software, including enhancement packages.

**Setting collation *BIN2 and 1:1 system copy**

First, we change the collation *BIN2 for Microsoft SQL Server 2000 on the existing SAP system with Microsoft Windows Server 2003 SE (x86, 32 bit, Service Pack 2). The current database collation is called “SQL_Latin1_General_CP850_BIN” (build 8.00.2040, HF2040, see also SAP Note 624951). The reason for this is that an upgrade to SAP ERP ECC 6.0 is not possible with the existing collation *BIN. If all the system data is already mirrored on the new server (HSC = homogenous system copy), it will not be possible to install the new SAP software at a later date.

Ready to change the collation: the file instcoll.exe to change to *BIN2

Please note: To change the collation to *BIN2 (see also SAP Note 600027), the fileinstcoll.zip (instcoll.exe) must be downloaded and then copied to the old server. The command line looks like this:

instcoll.exe –S<SERVER> –D<DB> where <SERVER> = SAPPRDITU and <DB> = P13 case

The following prompt then appears: “SQL_Latin1_General_CP850_BIN2” Continue? (Y/N): Y. The message is displayed as shown below.

Changing the database collation to *BIN2

The server can now be restarted and the new collation can be checked using the SQL Analyzer. As a result, the collation version SQL_Latin1_General_CP850_BIN2 is displayed. This is performed using the following commands:

select serverproperty(‘collation’)

select databasepropertyex(‘P13’, ‘collation’)

Importing SAP Support Packages

SAP Support Packages increase system reliability, program compatibility, and security. Several updates are combined to form a Support Package, which makes downloading them easier. Once all the components have been updated, a one-to-one system copycan be made. This is then created for the new server by homogenous system copy (HSC). A complete backup also includes backing up the database (P13, DB13), and in our case the backup file is P13DAT1.BAK. This file is copied to a dedicated drive on the new server. Here, it is important that you check the file size and the “created on” date. The file is needed for the HSC process.

Support Packages update the SAP components

Installing Windows Server 2003 x64 Edition

Operating system: transferring from a 32-bit to a 64-bit Microsoft Server 2003

So that the ERP upgrade can be performed later on the new server, the settings for using the working memory and the size of the paging file must be adjusted after the Microsoft Windows Server 2003 has been installed.