Re: (un) setting global names and db_domain

On 28 May 2003 19:02:15 -0700, wsgullickson_at_yahoo.com (william) wrote:

>Dear all -
>Let's say for hypothetical reasons, that a database just had a global
>name of PIG2 (no .WORLD or .ACME.COM extention) and was quite happy to
>be replicated by it's sister database PIG1, and everything was just
>fine. Until one day some joker issues a command:
>
>SQL> ALTER DATABASE RENAME GLOBAL_NAME TO BACON.PAN;
>
>database links blow up, and a good laugh was had by all. BUT, it turns
>out that the .PAN extention is seemingly impossible to remove as such:
>
>SQL> ALTER DATABASE RENAME GLOBAL_NAME TO PIG2;
>
>SQL> select * from global_name;
>
>GLOBAL_NAME
>--------------------------------------------------------------------------------
>PIG2.PAN
>
>hrm. That's strange.
>
>SQL> ALTER DATABASE RENAME GLOBAL_NAME TO PIG2.POT;
>
>Database altered.
>
>SQL> select * from global_name;
>
>GLOBAL_NAME
>--------------------------------------------------------------------------------
>PIG2.POT
>
>Aha! I can CHANGE the db_domain to anything else, except nothing,
>which is exactly what it needs to be. This is all the more confusing
>because in my spfile I have the line:
>
>*.db_domain=''
>
>I can turn global_names on and off until I'm blue in the face with
>
>SQL> alter system set global_names = false scope=both
>
>and watch the spfile change, but nothing changes the GLOBAL_NAME value
>to just PIG2.
>
>Am I missing something obvious? Thanks in advance -
>
>W

No. The global name is in the control file and db_domain is used only once to set it, and ignored afterwards

Sybrand Bakker, Senior Oracle DBA

To reply remove -verwijderdit from my e-mail address Received on Thu May 29 2003 - 00:13:10 CDT