Skip to Content
0
Former Member
Aug 18, 2005 at 09:55 AM

System copy and SAP SID issues (WAS 6.20)

89 Views

Hi all,

We have a BW 3.1 development and production system running on a WAS 6.20, Win 2000/MSSQL, and need to upgrade this to BW 3.5. We also need to create a test system on a new server.

Our initial idea was to do a system copy of the production system onto the new server to establish the test system, but after checking with a few experts, we were told that changing the SID during the system copy process does not work for WAS 6.20. Can anyone else confirm this?

We now have a situation where we want to ghost/mirror the production system (instead of doing a system copy) to create a new test system. Our concern is the we will end up with both a test AND a prodution system with the same SAP SID. We suspect that it is not enough just to change the Logical System Name using transaction BDLS in order to uniquely identify the two systems. We will have to establish a transport path like this: DEV -> TST -> PRD. Will this be possible when TST and PRD have the same SAP SID?

Can anyone think of other issues we might run into with the "ghost" approach.

Any feedback is greatly appreciated.

Kind Regards,

Thomas Kjelsrud