Interesting question. Why should it be mandatory to have distinct global names ?
For convenience, manageability etc, yes. But mandatory for operations ?
AFAIK, the only place where GLOBAL_NAMES is enforced is in Replication.
I've inherited a site where the DBA created a database image and duplicated
it to 7 servers [7 servers running the same database schema but used in
different "areas" of manufacturing]. This is then replicated across multiple
production facilities -- thus I have about 30 databases with the same GLOBAL_NAME,
the same SID, the same DatabaseSchemaName and Password etc etc [all, of
course, on the same platform Tru64].
Whenever I duplicate my Oracle Apps production environment to one of the
Test/Development/Conversion I sometimes forget to change the GLOBAL_NAME
for weeks.
Another issue is that all the database default to a .WORLD domain as no
DB_DOMAIN has been set !
Hemant
At 05:48 AM 23-01-03 -0800, you wrote:
Sorry, no, I can't find it. Maybe someone else knows?Jared On Wednesday 22 January 2003 21:03, Justin Cave wrote: > At 12:07 PM 1/22/2003, [EMAIL PROTECTED] wrote: > > > It recently came to my attention that the DBA's where I work have > > > >adopted a > > > > > convention where the global_name of a database is the same for the > > > production, test, and development instance of that database (obviously, > > > they've turned off global naming in the init.ora). They've also set up > > > >the > > > >Oracle has stated for some time that global_names=true will be required > >in future versions of Oracle, and recommend that that be done now. > > Do you happen to have a link to an Oracle document to that effect? I've > searched tahiti and metalink, but haven't come up with anything other than > documentation that says Oracle recommends global_names=true. > > > > Our DBA argues that this configuration is strongly preferred by the > > > >majority > > > > > of developers since they don't have to make any changes to their code > > > >when they > > > > > move from development to QA and to test. > > > >Junior developers? If the changing the database name requires code > >changes, then > >the duhvelopers need some remedial education. > > I fully agree. Unfortunately, my project can't really tell other projects > to educate their developers. > > Thanks! > Justin Cave > Distributed Database Consulting -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Jared Still INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Hemant K Chitale My web site page is : http://hkchital.tripod.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Hemant K Chitale INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
