Homgeneouos system copy - Import/Export

[ganesh_borase2]

Hello everybody,

I have successfully upgrade system( ECC 5.0) m from windows 2003 (32)+ SQL 2000 to windows 2003 (64-bit) + SQL 2005. using attach /detach method, in post processing execute STM tool, update stats etc.

But we found performance is not much of improve previous system with only 4 GB RAM, new one with 32 GB RAM.

I have remove the parameter PHYS_MEMSIZE parameter from the profile so it is under ZERO MEMORY MGT.

This above said in testing environment till.

For testing, I planning for the same using export/import

Plan :

Source system

1. Now, Export the database by executing sapinst.exe and then

select ABAP system-->MS SQL server -->Unicode -->ABAP Database content export

and continue with the Export procedure.

On the Target system

1. Create a directory EXPORT and copied all the exported data.

2. Start the SAP installation(only start database instance installation), enter the required parameters up to the

window selecting the database instance installation method, on this

I will choose System copy/migration(R3load based)

3. provide the path of the Export directory.

4. Specify the order in which the package are loaded - I select alphabetical order

5. No other option will select on this screen.

So for testing, I simply database export from source system and on target system I execute only Database instance installation, all process successfully done.

We have not any BW client so I am generate the DDL statement

Pleas suggest above plan is correct or anything missing?

will improve performance of system?

Thanks

Ganesh

[Former Member]

Hello,

Above procedure is correct, but during target system installation please continue with SAPinst to install SAP instance as well.

As far as performance is concerned, the EXPORT/IMPORT procedure re-organizes the database so you might get some improvement in performance and 64 bit platform might add up to it.

If you do not have BW client, even then please execute SMIGR_CREATE _DDL report. If it doesn't generate any SQL statements then it is OK but let's not skip this report.

Thanks

[ganesh_borase2]

HI!

As per suggested for DDL statement generation, we have no any productive BW client,

i tried on our Qaulity system by logging on regular using client, message display DDL statement

generated successfully,. but when I check in usr\sap\tmp folder there no file

1. is Unicode migration option selection is necessary?

in installation directory path is

[ganesh_borase2]

HI!

As per suggested for DDL statement generation, we have no any productive BW client,

i tried on our Qaulity system by logging on regular using client, message display DDL statement

generated successfully,. but when I check in usr\sap\tmp folder there no file

1. Unicode migration option selection is necessary?

in installation directory path is only /tmp so I checked in ( usr\sap\tmp) directory.

2.

Above procedure is correct, but during target system installation please continue with SAPinst to install SAP instance as well. 

As above statement, I started installation on Target system by SAPinst then from option

  mySAP EPR 2004 SR1
     System copy
          Target system
             ABAP system
                MS SQL Server
                    Unicode
                          Central instance installation
                          Database instance installation
                          MSCS Node A Configuration
                          MSCS Node B Configuration
                          Dialog instance installation
                          internet graphic server upgrad 

I select Database instance installation Database instance installation option. No any other process I have done.

3. is same procedure for system copy in clustering environment ( because our Production system in windows 2003 (64 -bit) clustering environment.

4. After installation complet, in post processing need to use STM tool, update static etc.

Please suggest.

Thanks

Ganesh

[Former Member]

Hello,

1. No, unicode migration option is not necessary and not be selected if you are not going for Unicode Migration.

Change the installation directory to something else and then run ddl statement report. Most probably the files will not be generated but still better to run the report. (/tmp is /tmp, not \usr\sap\tmp).

2. Database instance installation option is OK and you will get DB instanace installed for you. This option will just IMPORT the DB not the SAP application binaries. But if you need SAP/CI instance then you will have to run 'Central Instance Installation' Option as well.

3. I am not sure for clustering environment, please read the guide. Concept is same - db instance + sap instance installation but they way might be different.

4. Post installation steps as usual -

683447 SAP Tools for MS SQL Server

551915 - R/3 won't start after database restore or database copy

Note 151603 - Copying an SQL Server database

Thanks

[ganesh_borase2]

HI!

I have done homogeneous system copy using Export/import method

in following steps.

1. Install fresh QAS system.

2. Export data from source (Same SID - QAS) system

3. from SApinst, select Database instance installation option

4. import the database.

is it correct?

Thanks

Ganesh

[Former Member]

Correct !

Thanks

[ganesh_borase2]

Hi!

Thanks for support

Last question is

So no need to selection Central instance installation option?

thanks

Ganesh

[Former Member]

No need Ganesh.

Thanks