Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: GLOBAL_NAME change
Ref: GLOBAL_NAMES
It's nothing systematic. Our 'corporate' policy was to set TRUE on all databases. I tested many of my instances and found the settings were usually FALSE. No big suprise that people would not follow their own guidance. :-)
I discovered the TNS alias problem by curiosity and luck. There were a few new TNS entries among our hundreds of databases in the tnsnames.ora file, one or two I was actually using at the time, where I noticed it would be impossible to keep the TNS alias and convert the database to TRUE. I remember thinking to verify GLOBAL_NAMES=TRUE when testing new TNS configurations at this client site.
Unfortunately, I can't remember the exact reason. At the time, I double checked to confirm it would cause a problem, and made a couple test cases as proof, because it seemed so unlikely. Normally, you can setup tnsnames.ora at the server to be almost anything and fix this type of problem, but these guys used the same file for client and server. I know the developers would have been upset if we had to change the client TNS aliases.
Sorry. I wish I could remember the exact reasons. Frustrating for me too. I might simply suggest verifying the TNS entries after setting it TRUE.
HTH Regards,
Mike Thomas
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------Received on Thu Jul 22 2004 - 20:57:28 CDT
![]() |
![]() |