cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade SQL SERVER 2005 to 2008 with STM

Former Member
0 Kudos

Hello,

I want to install a new Windows 2008R2 server / SQL Server 2008R2 and make homogeneous system copy to bring my database on this new server.

Source server : W2003 server / SQL server 2005 / SAP 4.7

Target server : W2008R2 server / SQL server 2008R2 / SAP 4.7 (temporary before ECC6 upgrade)

The database upgrade will be done normaly with the system copy step as OSS note 683447 - SAP Tools for MS SQL Server explains (detach/attach method).

Have you ever done this operation ? STM is it enough to upgrade from 2005 to 2008R2 ?

Thank you for your advice.

F.M

Accepted Solutions (0)

Answers (1)

Answers (1)

Sriram2009
Active Contributor
0 Kudos

Hi

Kindly go thru the below links, I thing windows 2008 R2 will not support Ecc4.7 its require minimum requirements

windows Support link

system copy https://websmp208.sap-ag.de/installnw70

Regards

S

Former Member
0 Kudos

Hello,

W2008R2 / SAP 4.7 is just a step before ECC6 upgrade, not for a productive usage.

(Note 1476928 - System copy of SAP systems on Windows 2008 R2 SQL Server explains this case).

BR.

petra_writz
Participant
0 Kudos

Hi,

did you make this systemcopy?

I tried the same, but it doesn't work.

First I wanted to install a 4.7 instance on W2K8 R2/SQL 2008 R2 to make afterwards to the copy with attach/detach (and later on the upgrade to ECC 6.0)

But the installation stops with error at the point of database load.

The error in the logs:

J:\usr\sap\MDE\SYS\exe\run/R3load.exe: START OF LOG: 20110804133123

J:\usr\sap\MDE\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP

J:\usr\sap\MDE\SYS\exe\run/R3load.exe: version R6.40/V1.4

Compiled May 29 2011 23:33:44

J:\usr\sap\MDE\SYS\exe\run/R3load.exe -ctf I D:/SAP_Incoming/6.20/51019635_3/DATA/SAPSLOAD.STR D:/SAP_Incoming/6.20/51019635_3/DB/DDLMSS.TPL C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB/SAPSLOAD.TSK MSS -l C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB/SAPSLOAD.log

J:\usr\sap\MDE\SYS\exe\run/R3load.exe: job completed

J:\usr\sap\MDE\SYS\exe\run/R3load.exe: END OF LOG: 20110804133123

J:\usr\sap\MDE\SYS\exe\run/R3load.exe: START OF LOG: 20110804133527

J:\usr\sap\MDE\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP

J:\usr\sap\MDE\SYS\exe\run/R3load.exe: version R6.40/V1.4

Compiled May 29 2011 23:33:44

J:\usr\sap\MDE\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB/SAPSLOAD.cmd -l C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\MSS\NUC\DB/SAPSLOAD.log -loadprocedure fast

(DB) ERROR: db_connect rc = 256

(DB) ERROR: DbSlErrorMsg rc = 99

J:\usr\sap\MDE\SYS\exe\run/R3load.exe: job finished with 1 error(s)

J:\usr\sap\MDE\SYS\exe\run/R3load.exe: END OF LOG: 20110804133527

I used note 1476928 and 899111 to prepare the CDs for installation.

Does anyone hav an idea to solve this problem.

Best regards

Petra Wu00F6ritz

markus_doehr2
Active Contributor
0 Kudos

> First I wanted to install a 4.7 instance on W2K8 R2/SQL 2008 R2 to make afterwards to the copy with attach/detach (and later on the upgrade to ECC 6.0)

Why do you install an instance to then deleted it? You can use the system copy section of sapinst to do this all in one step.

Markus

Former Member
0 Kudos

Hello,

I've not realized yet (September).

Why did you use R3load ?

I'll restore a database backup . Using STM Tools to upgrade the Database to SQL-2008R2.

Best regards.

xymanuel
Active Participant
0 Kudos

Hi Frederic,

we often use the STM Tools.

We used them for homogeneous system copies (Q system refresh)

or for upgrading DB from MSQL 2000 --> 2005 --> 2008 --> 2008 R2.

We did all of these steps.

From 2000->2005 we did schema change from dbo. to sid. with the STM.

Never had some problems with the tools.

We are currently also in an release change from 4.7 MDMP to 6.0 EHP 5.0 Unicode.

For the unicodeupgradepart we have to use r3load export / import.

Export from SQL 2005 Nonunicode and import into SQL 2008R2.

But we do the upgrade on SQL 2005! (CU&UC)

Which means, first upgrade to 6.0, second export with r3load, third load into SQL 2008R2 with now unicode.

By default ROW compression is enabled which is very nice!

Kind regards

Manuel

Edited by: Manuel Herr on Aug 5, 2011 3:14 PM