Skip to Content

Migration of DUAL stack High availability ON premise to Distributed AWS

Jul 19, 2017 at 08:22 AM


avatar image


We are in process of migrating DUAL stack High availability ON premise (4 nodes -- 2 apps and 2 db nodes) to Distributed AWS system with 2 nodes. For standalone systems we have copied file system and migrated database using DB tools and they are working fine.

But we are bit confused with dual stack migration by copying file systems as we believe we may encounter issues with JAVA stack.

As of now DB on AWS is built and my DB team has converted RAC to standalone. As of now database part is ready.

Can anyone suggest what will be the best approach to accomplish this?

Do export central system and import central system will work using SWPM? Without exporting database instance?

Any other suggestions?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Reagan Benjamin
Jul 19, 2017 at 01:13 PM

You should follow the standard system copy procedure to move the system to the new host. The database can be restored to the new server as long as the source and the target OS and DB versions are same. Once the database has been restored you then do an export of the Java stack on the source and import it to the new server. If the systems are on Linux and if the hostname and SID remains the same it is possible to move the systems by copying the filesystems. You just need to install a new license after the move. If there is a change in hostname and SID then system copy with Java stack export import procedure is required.

Show 7 Share
10 |10000 characters needed characters left characters exceeded

Reagan, Thank you. Is is sufficient to export Java stack alone and Import the same? Don't we need ABAP stack?

Also the DB(Oracle) and OS(Linux) level versions are same in target machine. Hostname and IP are different.

Can you please brief in this case.


For Java stack you need to perform export and import. During the export phase you should select the option "Use database specific tools" in the database export section. This means you will perform a back and restore on the target and sapinst will only export the file system content.


Hi Reagan,

Based on SWPM options

Export preparation

Table Splitting Preparation

Database Instance Export

Central Instance Export

as of now we are choosing ""Central Instance Export"" alone. Do we need to execute ""database instance export"" as well?

Is it possible to export and import JAVA alone in a dual stack system?

Please guide me.


In the past the database and central instance export was a single option. I would try the database instance export and see if I get the "use database specific tools" or not. If the tool is exporting the full database then I would cancel it and go for the central instance export. I don't have a system here to test and confirm but you way try. In case first perform a test export and see how it goes.


Thank you Reagan,

This may help us. We will try out what you suggest and let you know.




Hello Amarnath,

for Dual Stack system it's mandatory to copy both stacks. You must also not skip one of the steps of
the system copy service in SWPM (unless it's mentioned in the guide, e.g. the Table Splitting Preparation can
be left out). Since the source is an High availability system, choose the appropriate services in SWPM.

Check system copy guides, it's all explained in there:




Thank you Hendrik,

We do have a different scenario than the guide describes and we are looking for option that will discard database and export non database files.

Please help on how best we can achieve this.