64-Migration / Systemcopy / fastest way

[Former Member]

Hello,

we need to migrate a ERP 2005 / BI from 32 to 64 Bit.

Sourcesystem:

- Windows 2003 32 Bit
- Oracle 10.2
- SAP SID: DR1
- Oracle SID: DR1

Targetsystem:

- Windows 2003 64 Bit (maybe Windows 2008 64 Bit)
- Oracle 10.2
- SAP SID: P10
- Oracle SID: P10 

I've a very small time frame... max 3 days. A system copy with export / import will running longer than 3 days... I think 5 days with post system copy tasks.

Is there a other method to copy the system faster? What is the fastet way?

Best regards

Thomas

[markus_doehr2]

> I've a very small time frame... max 3 days. A system copy with export / import will running longer than 3 days... I think 5 days with post system copy tasks.

Use backup/restore - this is supported for a 32bit --> 64bit migration.

See also Note 960769 - Windows: Migration from 32-bit to 64-bit (x86_64)

If you want to use Windows 2008 you MUST use the Oracle 10.2.0.4 installler - which is not yet available (Hinweis 1303262 - Windows Server 2008 and Oracle).

Markus

[Former Member]

Use backup/restore - this is supported for a 32bit --> 64bit migration.

In former times I've only made systemcopies with export / import (r3load).

Can I change the SID with backup / restore method? What are the required steps?

If you want to use Windows 2008 you MUST use the Oracle 10.2.0.4 installler - which is not yet available (Hinweis 1303262 - Windows Server 2008 and Oracle).

There is no problem... I've access to the new Windows 2008 compatible installation set.

[markus_doehr2]

> In former times I've only made systemcopies with export / import (r3load).

> Can I change the SID with backup / restore method? What are the required steps?

Yes - it's possible - read the system copy guides

http://service.sap.com/systemcopy

> If you want to use Windows 2008 you MUST use the Oracle 10.2.0.4 installler - which is not yet available (Hinweis 1303262 - Windows Server 2008 and Oracle).

>

>

> There is no problem... I've access to the new Windows 2008 compatible installation set.

Be aware that a SAP compliant database is not installed using the Oracle standard provided "setup.exe" but through a script (sapserver.cmd) that uses a response file to activate certain necessary functionality already during installation and also set environment variables for sapinst.

Also there are differences in Windows 2008 concerning user security (UAC).

Markus

[Former Member]

Well I've read the guide. The described way is:

- create offline backup

- install new system via sapinst and using the backup

- post systemcopy tasks

With this procedure I get also a problem with my time frame.

Is the following way possible?

- install a new system completly

- create a db-backup of old system

- restore the db-backup on new system

... I think this will be the same as a "testsystem-refresh". Can I change the DB and SAP SID on this way?

Edited by: Thomas Rudolph on May 6, 2009 12:26 PM

[markus_doehr2]

>

> Well I've read the guide. The described way is:

> - create offline backup

> - install new system via sapinst and using the backup

> - post systemcopy tasks

>

> With this procedure I get also a problem with my time frame.

Why that?

>

> Is the following way possible?

>

> - install a new system completly

> - create a db-backup of old system

> - restore the db-backup on new system

This will take even longer than the first step. There is no need to install the system and then throw it away/overwriting it with the backup but you can use the backup directly will save you the time for the installation.

> ... I think this will be the same as a "testsystem-refresh". Can I change the DB and SAP SID on this way?

Yes.

Markus

Markus

[Former Member]

I need to minimize the required downtime. The total installation time is secondarily.

I think with the second way I can reduce the downtime. But can I change the DB SID and SAP SID?

[markus_doehr2]

The procedure will be like

- you install Oracle + patches on the new server (same version, patchlevel and interim patch)

- you start sapinst

- a few minutes later after the kernel has been unpacked you can restore the backup with the NEW SID

- you continue with sapinst to finish the installation

- you adapt the profile parameters according to the source system and the new 64bit system (mainly memory related)

- preferably update to latest Oracle patch (10.2.0.4) plus the latest interim patch

- you create a full backup

> But can I change the DB SID and SAP SID?

yes - as already wrote a few times But: the SCHEMA name will be the same as the source system.

Markus

[Former Member]

Ok. I'm understanding procedure for backup / restore.

Do you have a link to procedure like a "testsystem refresh"?

[markus_doehr2]

no.

What is not clear in the system copy guide?

Markus

[former_member204746]

I did this migration with less than 1 hour. Here's what I did.

I pre-installed new server with 64-bit binaries. I copied the SAP profiles and Oracle initSID.ora file and adapted them for the server name change. in your case, adapt them for the new SID also.

then, when ready, I stopped DB on source server. asked my SAN admin to move database partitions on the new server, change the SID by manipulatinf the control file and by changing path names to new SID.

when DB is up, run this:

sqlplus / as sysdba

startup upgrade;

@?/rdbms/admin/utlirp.sql

shutdown immediate;

startup

@?/rdbms/admin/utlrp.sql

also run:

sqlplus /nolog @D:\usr\sap\[SID]\SYS\exe\run\sapdba_role R3

start SAP and run SGEN

adapt SM37 jobs that have hard coded the servername.

adapt these tocdes too:

RZ10

SPAD

RZ12

AL11

SMLG

RZ03/RZ04

good luck.

[Former Member]

@Eric:

Are no more actions needed? Is the SAP SID and the old server namen not in many database tables?

[former_member204746]

you should refer to the homogeneous system copy guide for the SID change.

The steps I provided were the notes I kept for changing hostname. for changing SId, the SAP guide will help you.

[markus_doehr2]

You may refer to the logical system name - which usually contains the SID (transaction BD54).

It is not supported to change that name in production system. So leave it as it is. The SID is independent of that.

Markus