> 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. Which obviously won't work if you have databases with the same global name. I personally have global_names=false, though our databases all have different global names. Having databases with the same global name is rather confusing. I can't say I've really thought through the ramifications other than that. > 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. my $0.02 Jared -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: 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).
