Can we re-use SAP export files built for other OS/DB combination?

[former_member204746]

Hi,

We exported an SAP system (using SAP tools) from AIX/DB2 to Linux/Oracle. Import is going well into the Linux/Oracle system.

We would like to use the same export files and import into a brand new AIX/DB2 system.

For technical reasons  the old and new AIX/DB2 systems do not use compatible backup systems. So, backup/restore is not an option. Also, we "lost" the source system and it would be complicated to rebuild the source system.

Question: Is it feasible to use the same export files to build the new AIX/DB2 systems even if the export files were "meant" to be used for AIX/DB2?

Will we have issue with code page and/or Endianness?

Thanks.

[Frank-Martin · Accepted solution]

Hi Eric,

The R3load data export files and the STR files are not database dependent. For example for a fresh SAP installation only one set of export files is shipped by SAP and used on all OS/DB combinations.

If your system is a BW system and you have generated .SQL files using SMIGR_CREATE_DDL those .SQL files contain database dependent DDL statements. In this case you need to rerun

SMIGR_CREATE_DDL on your source system. For example ORACLE uses range partitioning on BW while DB2 LUW uses MDC or BLU.

R3load will find out the endianess of the export files itself. During import SWPM will call R3load with a parameter giving the target endianess.

Regards

                Frank

[former_member204746 · Accepted solution]

Thanks Frank-Martin and Manu.

We will test this in the following weeks.

[manumohandas82]

Yes . You can use the same export to build the new systems in AIX/DB2

SWPM ( as export files are db independent )  will take care of this though Linux and Unix are different endians 

Thanks ,

Manu