BW 3.1 Cont migration from IA32 to x64 (AMD 64)

[Former Member]

We are currently running BW 3.1 Cont on IA32 (32 bit). In our current

project, we need to migrate this to 64 bit x64 (AMD 64 bit) and

subsequently do an upgrade to BI 7.0. Below are my questions:

1. Is BW 3.1 Cont compatible with x64 on a Windows 2003 64 bit OS? If

so, what are the migration steps. We are currently on MS SQL Server

2000 and we would subsequently upgrade to MS SQL Server 2005 in the x64

box.

2. We don't have the BW 3.1 Cont DVDs. How do we get the same?

As we are on a time constrained project, your support at the earliest

is highly appreciated.

Thank you.

[yuezhi_zhao · Accepted solution]

Hello,

BW cont is a plug in. The BASIS decides the OP platform. What is the BASIS release of the BW system? 46C or 620, or something else?

For the database upgrade to SQL 2005, you do not need the DVDs, since this is not considered as a homogenous system copy. The note 799058 give the detailed steps how to upgrade SQL 2000 to SQL 2005. Again, you need to make sure the BW3.1 system can run on SQL 2005.

Regards,

Joe

[Former Member · Accepted solution]

Hi Joe,

Thank you for the prompt response.

Yes, the BASIS version of the BW 3.1 system is 6.20. Does this mean I should be able to install BW 3.1 on the AMD64 box and do the migration from IA32 to x64?

How can I find out if BW 3.1 can run on SQL 2005?

Thank you.

[markus_doehr2 · Accepted solution]

BW 3.1 is in customer maintenance since 01.01.2007, means, there will be no more fixes, no more extensions (see note 52505).

You can copy the BW over to a 64bit system, check 777024 for the copy procedure (you need special CDs for that).

--

Markus

[yuezhi_zhao · Accepted solution]

Hello,

The best place to find this information http://service.sap.com/pam

If you enter 'SAP Netweaver' -> 'SAP Netweaver before SAP NW04 -> SAP web AS

-> SAP WEB AS 6.20

Then click on 'database platforms' tab, you can see that the 620/640 kernel only supports SQL2000, but not SQL 2005. But for hardware, it can run on 64 bit Windows.

You might need to reconsider the upgrade path. You can try:

1. Upgrade BW 3.1 to BW 70,

2. Upgrade the OP and DB.

BW 70 can run on both SQL 2000 and SQL 2005.

Regards,

Joe

[markus_doehr2 · Accepted solution]

> Then click on 'database platforms' tab, you can see

> that the 620/640 kernel only supports SQL2000, but

> not SQL 2005. But for hardware, it can run on 64 bit

> Windows.

This is in contrary what note 799058 tells:

[...]

You have the following options to introduce SQL Server 2005 in the SAP environment:

• You install a new SAP system that is based on NetWeaver 2004s (basis release 7.00), which supports SQL Server 2005.

In addition, there are installation master DVDs supporting SQL Server 2005 available for all products with basis releases 6.20 or 6.40. Refer to SAP note 905634 for information about these new installation master DVDs.

You should not use older installations of SAP products based on 6.20 or 6.40 with SQL Server 2005.

[...]

So I'd say YES, it's possible to run a 64bit BW 3.1 against an MSSQL2005 on X64.

Since the note is updated more often than the PAM I'd believe that one

--

Markus

[yuezhi_zhao · Accepted solution]

Hello Markus,

Very good point. I believe the notes are more updated.

Just one more thing, as in note 905634:

Supported SAP products based on SAP_BASIS 6.20 and SAP_BASIS 6.40

Product Windows platforms

BW 3.10 x86, IA-64

It seems that BW 310 can't run on x64, and SAP007 has AMD64. this might invalidate the upgrade path SAP007 has planned.

Regards,

Joe

[markus_doehr2 · Accepted solution]

Oh yeah - isn't that all a big mess? We have three statements:

1. PAM says NO

2. Note 799058 says YES

3. Note 905634 says NO

I'm sure if we go on searching we will find even more notes, that contradict.

I'd suggest opening an OSS call and ask SAP themselves, maybe they will know

I really wonder, what are the reasons why supporting one APPLICATION running on top of the kernel and not supporting another running on the same kernel when the basis is downported to 4.6c (4.6D_EXT)...

--

Markus

[yuezhi_zhao · Accepted solution]

It is kind of hard to consolidate all the information here. Sure SAP007 can open an OSS mesasge and wait maybe 3 months to get a reply

But just in case it's urgent like he/she stated before, he can try the upgrade path proposed earlier and it seems to be safe.

Regards,

Joe

[Former Member]

James,

Did you get the problems resolved yet? If not, let me know. I can send the step by step method I used to get the BW 3.1 migrated from IA32 to x86_64.

Thank you.

[Former Member]

I know this is a stretch but I'm going through the exact process (4 years later than everyone in this post). This is directed to user SAP007 - Would you be able to send me the steps you took to migrate from BW 3.1 32-bit to BW 3.1 x64? My source is Windows 2000 OS, SQL 2000, BW 3.1, BASIS level 6.2, all on an ancient 32-bit Compaq hardware. My intended destination is Windows 2003 (or WIndows 2008, if possible) SQL 2005 (or SQL 2008), BW 3.1, BASIS level 6.2, on an HP blade (x64). Please include the media you needed from SAP's marketplace. Hopefully, you're still a member of this forum. Eventually, I aim to do an application upgrade to BI 7.3.

Thanks (if you're out there) .......

[Former Member]

Well, I would like to close this question because, I found the solution to this myself.

- Yes, x64 is compatible with BW 3.1

- I used the 51032143_13 to install the BW 3.1 on the x64 system. After this, the migration from x86 to x64 was easier.

- Then performed the upgrade using the newtweaver 2004s upgrade DVD along with the BI_CONT 7.03.

Since we are having problems to make SAP GUI 7.1 to work with the BI 7.0, we decided to use SAP GUI 6.40 with the latest Patch Level.

Thank you for all the support.

[Former Member]

Hello

I have a few question, I moved from 4.7 32bit to X86 64 bit and did it so

I installed a new 4.7 system on the X86 64bit with the Netweaver 7.0 CD and did a system copy from my 32 bit and and moved it over my system which worked fine and did this with Oracle and MSSQL. Started with oracle 9 and on the new system installed oracle 10 also with MSSQL started with 2000 and the new system I set up on 64bit was MSSQL2005 and copied the 32 bit database onto the 64 Central Instance I installed, also with no problem,

I can not find any Installation CD for BW 3.1 to install on X64 bit.

I want to install a new MSSQL 2005 database and a Central Instance for BW3.1 on my 64bit and take a System copy from my old Hardware and copy it onto my New Hardware which works fine for the 4.7 Installation ,

But I cant find and CD for 3.1 X64bit.

Any Ideas

[markus_doehr2]

> But I cant find and CD for 3.1 X64bit.

You should be able to use

51032143_15 Installation Master 6.20/6.40 Windows Server on x64 64bit

and install a BI 3.1 with that CD and the appropriate kernel.

--

Markus

[Former Member]

Thanks Markus

I tried this the problem here is that the following Path is looked for,

IM_WINDOWS_X86_64/SAPINST/NT/AMD64/PATCOL640/BW31/MSS/ABAP/NUC and if you notice after PATCOL640 the following folder is needed BW31 and on this CD this is missing , and that is where I get stuck ,.

<b>PATCOL640:</b>

CRM40

ECC50

R3E47X2

SCM41

SOLMAN32

SRM40

WEBAS630

any ideas

James

[markus_doehr2]

If you installation is just for setting up the target system, then you can install any of those, after finishing you can restore your "old" instance on the new box.

The only difference between all those is the different usage of export CDs (CRM vs. ERP vs. R3E etc.), the setup itself is always the same.

--

Markus

[Former Member]

All question Answered, Just install a 4.7 release since all the same Basis of 620?640 and the copy over with a system copy from the BW 3.1 System, seems the same way as I did my 4.7 system

James

[Former Member]

Hi Markus / Joe,

I am a little confused between which one is the migration tied to, the BASIS version or BW 3.1 ?

If it's the basis version, I am very sure, this would work on BASIS 6.20. Because, I just did a migration and an upgrade of SCM 4.0 to SCM 5.0 that had BASIS 6.20. And the upgrade is successful.

On the other hand, if it's BW 3.1 that is looked at for the migration then, I really am worried.

Thank you.

[markus_doehr2]

BW is VERY database tied; we did some performance tests comparing different databases (MaxDB, DB2, Oracle) and migrated off from MaxDB. BW is picky and is implemented based on the underlying database, specific to that database to gain maximum performance. It may be, that exactly THIS part avoiding the migration. Technically it might be possible and it will run for sure, but you won't get support of that combination. Additionally, BW 3.1 is out of general maintenance though and that may also be the reason why this combination isn't supported any more.

--

Markus