Hi Gerry,
I think the question of having duplicate SID names vs. distinct SID
names depends on your environment. In both my last job and my current job
the DBA group is responsible for installing and maintaining Oracle
installations in multiple sites. Since each installation has the same
database structure, stored procedures, etc. it is easier to use the same SID
names on each system. The benefits are:
Use standard scripts for monitoring and modifying databases
Instant identification (ORCL is production, TEST is test).
regards
Jerry Gitomer
Gerry Sinkiewicz wrote in message <372658AD.81059A84_at_snet.net>...
>It seems to me that you would want to have distinct SID names within
>the same region. But even then it is the service names that need to
>be different (as in tnsnames.ora).
>
>When moving instances around we often have duplicate SIDs on different
>servers. As long as the tnsnames "alias" is different there is no problem.
>Of course on the same server SIDs must be distinct.
>
>The best reason I can come up with for different SID names is just
>maintenance. Keeping everything strait. It is better to have an
>internal and external name the same so that even the DBA's will not
>be too confused.
>
>
>
>James Lewthwaite wrote:
>>
>> Hello,
>> In a WAN environment how important is the database SID. Should
>> the SID
>> be different for all databases or just for multiple databases on the
>> same box?? I will have several databases on my WAN and I don't want any
>> SIDs to cause conflicts. Is the Global database name more important on
>> the WAN ??
>>
>> Thanks,
>> Jimmy
>
>--
>Gerry Sinkiewicz
>sinkiege_at_snet.net
Received on Thu Apr 29 1999 - 08:44:09 CDT