cancel
Showing results for 
Search instead for 
Did you mean: 

Same SAP System ID's in two systems

Former Member
0 Kudos

Hello,

We are planning for upgrade of our SAP system from EHP5 to EHP7.

The scope of this upgrade includes DB, OS, and Hardware Upgrade as well.

Considering that we have around 5-6 systems in the landscape and this

whole exercise will take around 8 months, can you let us know the best

practice approach for the SID naming as we will be running the systems

in parallel. Is it alright to have two systems using the same SID's in same

environment or we should have different SID's.

Thanks.

Kind Regards

Anand

Accepted Solutions (1)

Accepted Solutions (1)

Reagan
Advisor
Advisor
0 Kudos

Hello

You cannot have 2 systems with same SID in a landscape. You will need to use different SID if you are planning to have a parallel landscape. Also SAP recommends not to use the same SID when setting up a new system.

Regards

RB

Former Member
0 Kudos

Hello Reagan,

Thanks for the response.

We are going to run this parralel landscape only till the upgrade.

This new setup wont be having any real transaction and it will be used only for the testing purpose.

So technically we can have two SID's without any issue. Once we are done with whole testing we will be decommisning the old servers and stay with the new servers and copying the data . I want to know that if it is going to cause any issue in future?

Kind Regards

Anand


Reagan
Advisor
Advisor
0 Kudos

Hello Anand

Technically it is possible to have a system with same SID on a different machine as long as it does not have any connection with the main landscape.

SAP suggests not to use the same SID in the organization. I am not sure about the exact reason behind this. As this is only for a temporary period then this shouldn't be an issue.

Regards

RB

Answers (4)

Answers (4)

divyanshu_srivastava3
Active Contributor
0 Kudos

Hi Anand,

You can invest more and go for something like SAN replication. Where you can divert the users to a copied systems during a process of update. In this way system which are not going currently under update will be synced with the copied system. On the other hand, these two systems should have different hostname in same landscape with same SIDs.

Regards,

Divyanshu

Sriram2009
Active Contributor
0 Kudos

Hi Anand

You can have same SAP Sid on two different systems, but both systems should be in different network (Private network which is not communicating any other SAP or Non SAP systems)

                                                                                                           

1. For OS/DB migration. First take the Production system copy (Heterogeneous system copy method) export, do the import in new hardware with New OS / DB different SID or your SID = SBX SAP version EHP5, because all other system you may have some many pending transports / Development are there in different stages. Once you are migration in to new OS /DB you can check the basic function level testing as same amount of production system

2. Once the system imported then starts the upgrade from EHP 5 to 6 or 7, before that check the PAM & SAP Notes for interoperability with other systems

1388258 - Version Interoperability within the SAP Business Suite

1737650 - EHP7 for SAP ERP 6.0 SP Stacks - Release & Information Note

3. Once you are competed the upgrade process then you can starting upgrading from DEV, if possible keep the old DEV system till you are going to upgrade the live production system. In case if you want to do any development during the upgrade period you can use the old Dev system and transport the requests to production system

Regards

SS

former_member188883
Active Contributor
0 Kudos

Hi Anand,


Is it alright to have two systems using the same SID's in same environment or we should have different SID's.

Technically it is possible to have 2 systems with same SIDs but having different hostname.

Looking at your scenario as you plan for an upgrade ideally we prepare project landscape with different SID and hostname and perform the upgrade . All business functionalites are testing on this environment .Project landscape will exist in parallel with mainstream landscape.

Once testing is performed on project landscape, upgrade for mainstream landscape is taken into considered.

For your 5 - 6 systems ( SBX, DEV, QAS,TST, STG,PRD etc) you can first upgrade SBX then create a parallel landscape for DEV. Later upgrade QAS and then followed by PRD.

Once PRD is upgraded, you can re-created STG , TST and SBX again from backup of PRD.

Hope this helps.

Regards,

Deepak Kori

Former Member
0 Kudos

Thanks Deepak,

This is trhe exact secnario/plan we are having but I want to make sure it is the best possible way or we can have two SID's runnign altogether as well to avoid the work of renaming in later stage or just go for the new SID's.

Anand

former_member188883
Active Contributor
0 Kudos

Hi Anand,

As your scenario matches to what I have explained, You need to follow the approach as suggested.

In such a case you may need to have a parallel system for Development environment only which is used for dual maintenance until Production is upgraded.

New development will have TRs from old development which are imported manually and adjusted.

Refer information in link below

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70720cc8-b890-2c10-99a7-b51ae6c5b...

New Development system can have same SID with different hostname and it should be out of mainstream SAP landscape.

Rest other systems should be upgraded or built as suggested in my response earlier.

Hope this helps.

Regards,

Deepak Kori

Former Member
0 Kudos

Better to lock this query in SAP Basis forum as below:

http://scn.sap.com/community/netweaver-as