SAP Migration from AIX to Windows 2008 R2-ECC 6.0

[Former Member]

Hi Expert,

Our organization going to do migration from AIX machine to Windows 2008R2 64bit.

What are the step involed this migration project.

Any one guide to give great start for my work.

Thanks,

Vasan

[Former Member · Accepted solution]

Hi Vasan,

Also bear in mind that SAP will only support this migration of the production systems when an OS/DB certified consultant prepares the project plan and is active in the project.  Otherwise they will not support you if the production migration has issues under the support contract arrangement, rather they will charge you large amounts of money for support.

Regards,

Graham

[Former Member · Accepted solution]

Hi Vasan,

This field is huge and is very difficult to cover in a discussion.

In the Link http://service.sap.com/osdbmigration you can find a lot of information about the migrations.

Also you have the OS/DB Migration training and certificatio where is reviewed all the the important aspects.

To determine the method to use the first think that you have to verify is the source and target OS and DB. If you changing one of them you usually cannot use the standard DB methods (Backup/Restore) above all if you change the endian.

In case of changing OS and/od DB first bear in mind that to migrate productions environment is mandatory to Order the SAP OS/DB migration check and to have a certified in OS/DB migration that sign the project. Also you should leave some time (3 months) between an upgrade and a migration.

There are several methods standard and advanced. The most common is use the SAP Migration tools (R3Load and JLoad) and whitin there advanced techniques like Package Splitting, Table Splitting, Parallel Export/import, Usorted Export, Incremental Migration. Sometime you have to use your "imagination" to improve the process. Is very important to know how is your current environment, how is the strcture of your database and how will be your future system.

Also you can apply some feature during the migration like apply compression or patitioning for Oracle and Db2.

For some DB managers there are also method out of the SAP Export/import. E.g. Oracle has the O2O - Triple O method in order to migrate DB from Oracle/non-Oracle  to Oracle.

IBM have also software to do the migration of DB2 DB almost online.  Here you have a redbook about DB2 migration for SAP: http://www.redbooks.ibm.com/redbooks/pdfs/sg247774.pdf

There are also additional paid services (Zero DownTime) in case of reduced downtime windows or big databases.

The migration time depends on a lot of factors:

- Hardware capacity in Source and Target systems. As bigger the HW capacity is higher the parallelization and lower the time will be.

- Network Bandwidth.

- DB size. Before Migration consider seriously to reduce your DB space. E.g archive data is a good approach. Bear in mind that after the migration your database will be reorganized so it is a perfect moment.

- DB Structure: Is not the same to have a big database with the most of size concentrate in few tables than a big DB very distributed.

- Data fragmentation.

The only way to estimate the downtime is to test the migration before, and the most of times you need more than one test to find the good way to do it.

Also after the test migration you have to test your functionality.

In summary, this is a huge topic and I'm sure that I have forgot a lo of things.

Hopefully my comments help to you.

Cheers.

Jose

[Former Member · Accepted solution]

This message was moderated.

[Former Member]

Dear Mr. S Vasan,

Windows is little endian whereas AIX is big endian. Consider impact on Hardware and other resource.

Following link have information related to SAP migration. 

http://service.sap.com/systemcopy

http://service.sap.com/osdbmigration

Kind rgds,

Ashwin Mane

[former_member45419]

Dear Vasan

a)pls check necessary prerequisite before performing migration from AIX to Win

b)Import the target system(WIN) from Source system(AIX) with some Command

c)Install the target system and run the application sapint what ever you import from source system

d)install the database

e)export from AIX Machine to Wintel Machine

f)install the post installation activity by using system copy method.

Note :Go through this document

SYSCOPY_2004sSR2_ABAP.pdf

For further clarififcation pl check below link

https://service.sap.com/instguides

https://sdn.sap.com/irj/sdn/systemcopy

https://service.sap.com/osdbmigration.

Hope this will help you.

[former_member188883]

Hi Vasan,

For preparation work you need to read through the SAP hetergenous system copy guide.

This will help you in planning the migration work.

Below I provide you an overview of the work that shall be required

1) Preparation of Target system in terms of H/w , S/w and system resources

2) Perform Installation of Target system in Windows

3) Perform database export of source AIX system

4) Copy the export dump to Windows Target machine

5) Using this dump perform import into database on target windows system

6) Perform post migration activities as per system copy guide

Note: Please check the compatiblity of your SAP release with Windows 2008 R2 as a part of planning activity.

Hope this helps

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

Thanks for your reply.

Kindly explain technically with examples.

Which tool need to use for export soruce system, table splitting or package, what are you inputs need for export the database.

How we can copy from AIX machine to Windows machine?

Is there any setting and pre-request in Source system ..like Tablespace extention, SAPTEMP tablespace change, Disk space requirement 10% of current database size.

Where need to start in target system?

what are the known issue...?

If possible try to help this for before start my project ..we prepare prevent..

your previous reply only the outline idea.

Thanks,

Vasan

[Reagan]

Hello

Read this

http://scn.sap.com/docs/DOC-8324

The basic requirement for Heterogeneous system copies is a certified OS/DB migration consultant.

Check PAM for the OS and DB compatibility

You need to use the SWPM tool for the migration.

There is no need to set up the target system before the import. You can perform the import and target system creation in one run.

Regards

RB