Home » RDBMS Server » Server Administration » global_name parameter
global_name parameter [message #125584] Mon, 27 June 2005 17:44 Go to next message
vadlamani
Messages: 39
Registered: November 2003
Member
What does this command do ...?
alter database rename global_name to orcl;

why is its practical use..

Thanks
Satish
Re: global_name parameter [message #125586 is a reply to message #125584] Mon, 27 June 2005 17:58 Go to previous messageGo to next message
vadlamani
Messages: 39
Registered: November 2003
Member
vadlamani wrote on Mon, 27 June 2005 17:44

What does this command do ...?
alter database rename global_name to orcl;

why is its practical use..

Thanks
Satish



i know global database name is DB_NAME.DB_DOMAIN name.
So does the Alter command changes these values dynamically?

Thanks
Satish
Re: global_name parameter [message #128094 is a reply to message #125586] Fri, 15 July 2005 00:51 Go to previous messageGo to next message
vadlamani
Messages: 39
Registered: November 2003
Member
Any idea why we use this command
Re: global_name parameter [message #128199 is a reply to message #128094] Fri, 15 July 2005 11:57 Go to previous messageGo to next message
andrew again
Messages: 2577
Registered: March 2000
Senior Member
This came from Snapshots (MVs) and it was mainly created to make sure that database link names matched the actual target database name. The GLOBAL_NAME is also related to a startup parameter (you can change it as the session level too) GLOBAL_NAMES=true/false.

When GLOBAL_NAMES=true in your local database session, and you create a db_link called say DB_DEV, then GLOBAL_NAME of the remote database must match that, else you will get an error when you try to use the DB link. Depending on a bunch of other settings, it may or may not need the domain to match too.

you could create a db link called DB_DEV.world@scott and the remote database GLOBAL_NAME of DB_DEV or DB_DEV.WORLD should work.
Re: global_name parameter [message #128202 is a reply to message #128199] Fri, 15 July 2005 12:02 Go to previous message
andrew again
Messages: 2577
Registered: March 2000
Senior Member
Of course you don't change GLOBAL_NAME to suit the DB link name, you set the DB link name to "match" the remote GLOBAL_NAME. If you don't want this check performed when you use a DB link, then you should set GLOBAL_NAMES=false in your session(or database startup). Usually GLOBAL_NAME (excluding the domain info) matches the SID or database name.
Previous Topic: how to view packages bodies from other user?
Next Topic: Implementation of boolean types.
Goto Forum:
  


Current Time: Fri Jan 10 08:03:18 CST 2025