cancel
Showing results for 
Search instead for 
Did you mean: 

System Landscape

Former Member
0 Kudos

Hi Alll,

Currently we have system ladnscape as below .

DEV - > QAS - > PRD ( Support ) - > PRD .

The production support has same SID as Production .This was setuip using flashcopy from PRD . hence did not change the SID.

So we have two systems with same SID .

I am being asked to change the SID of PRD ( Support ) to a different SID .

I would like to evaluate the issues with or without same SIDs.

Please advice if anybody has faced any issue because of identical SID .

Thanks,

Chirag.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

Yes this sytem will b e used as staging system.

Would like to weigh the risks of same SID or I should chnage it .

Hence need some advise on issues with same SID from your experiences.

Thanks,

Chirag

JPReyes
Active Contributor
0 Kudos

Please follow the advice given a change the SID.

You cannot have 2 systems with the same SID in TMS

Regards

Juan

Former Member
0 Kudos

Hi Juan,

We are using TMS between PRD ( UAT ) and PRD ( Production ) by manually copying the data files and co-files using AIX script .

Why we are preferring the same SID in these two systems is because we can quickly refresh production data in UAT using IBM flashcopy .

Apart from this TMS thing , any other risks ?

I would like to weigh in the risks to decide whether to change the SID .

Thanks,

Chirag

JPReyes
Active Contributor
0 Kudos

Theres is specific procedures to have a stand-by or copy of production for disaster recovery scenarios.

We are using TMS between PRD ( UAT ) and PRD ( Production ) by manually copying the data files and co-files using AIX script .

That can be easily done by creating a transport route to your new SID when you change it.

Apart from this TMS thing , any other risks ?

Sure... lots, Logical systems, RFC's... etc.

You need to change your Production support system SID

Regards

Juan

Former Member
0 Kudos

Hi All,

We are using PRD-Support as UAT environement .

Hence change cycle is

DEV -> QAS - > PRD (UAT) - > PRD.

I would like to understand what are the risks with this kind of setup .

Thanks,

Chirag

Former Member
0 Kudos

I am particularly interested to know what is the current role of PRD(support) and after system copy.

Even if you switch the SID, there should be clear difference between the PRD and the new SID interms of usage.

In any typical landscape, no one will have two production systems unless there is valid reason.

Please explain why you have two productions for the benfit of the community.

JPReyes
Active Contributor
0 Kudos

@Vijay: Is quite normal to see a 4 tier landscape

I would like to understand what are the risks with this kind of setup .

I don't see any "risks" as long as they don't have the same SID.

Regards

Juan

Former Member
0 Kudos

Thanks Juan.

We do maintain 6 system landscapes.

I refered to using two production in a landscape, which is typically not anywhere.

Thats the reason why i asked whats the role of it and chirag clarified as UAT.

Chirag,

I second fiddle Juan on the risk category.

After UAT, do you have any plan to make the system as staging system.

JPReyes
Active Contributor
0 Kudos

Simply you shouldn't have 2 systems with the same SID in your landscape (specially with the same SID as PRD)... then implications are evident.

You can change the SID by doing a homogeneous system copy.

Regards

Juan

Former Member
0 Kudos

As recommeneded by Juan, you can go for homogenious system copy. After the restoration phase, you can change the SID of PRD Support system.

Thanks and Regards,

Kedar