Global in Oracle

Welcome to the Oracle community forum and interact with 2 million technical staff. 1. YouconnecttoSALES. US. EXAMPLE. COMandquerytheGLOBAL_NAMEdatadictionaryviewtodeterminethecurrentdatabaseglobalname: CONNECTSYSTEM@sales.us.example.comSELECT * FROMG

Welcome to the Oracle community forum and interact with 2 million technical staff> enter 1. you connect to SALES. US. EXAMPLE. COM and query the GLOBAL_NAME data dictionary view to determine the current database global name: CONNECT SYSTEM@sales.us.example.com SELECT * FROM G

Welcome to the Oracle community forum and interact with 2 million technical staff> enter

1. You connect to SALES. US. EXAMPLE. COM and query the GLOBAL_NAME data dictionary view to determine the current database global name:

CONNECT SYSTEM@sales.us.example.com

SELECT * FROM GLOBAL_NAME;

GLOBAL_NAME

----------------------------------------------------------------------------

SALES. US. EXAMPLE. COM

2. You query the V $ PARAMETER view to determine the current setting for the DB_DOMAIN initialization parameter:

Select name, value from v $ parameter where name = 'db _ domain ';

NAME VALUE

--------------------

Db_domain US. EXAMPLE. COM

3. You then create a database link to a database called hq, using only a partially-specified global name:

Create database link hq USING 'sales ';

The database expands the global database name for this link by appending the domain part of the global database name of the local database to the name of the database specified in the link.

4. You query USER_DB_LINKS to determine which domain name the database uses to resolve the partially specified global database name:

SELECT DB_LINK FROM USER_DB_LINKS;

DB_LINK

------------------

HQ. US. EXAMPLE. COM

This result indicates that the domain part of the global database name of the local database is us.example.com. The database uses this domain in resolving partial database link names when the database link is created.

5. Because you have already ed word that the sales database will move to Japan, you rename the sales database to sales.jp.example.com:

Alter database rename GLOBAL_NAME TO sales.jp.example.com;

SELECT * FROM GLOBAL_NAME;

GLOBAL_NAME

----------------------------------------------------------------------------

SALES. JP. EXAMPLE. COM

6. You query V $ PARAMETER again and discover that the value of DB_DOMAIN is not changed, although you renamed the domain part of the global database name:

Select name, value from v $ PARAMETER

Where name = 'db _ domain ';

NAME VALUE

--------------------

Db_domain US. EXAMPLE. COM

This result indicates that the value of the DB_DOMAIN initialization parameter is independent of the alter database rename GLOBAL_NAME statement. the alter database statement determines the domain of the global database name, not the DB_DOMAIN initialization parameter (although it is good practice to alter DB_DOMAIN to reflect the new domain name ).

7. You create another database link to database supply, and then query USER_DB_LINKS to see how the database resolves the domain part of the global database name of supply:

Create database link supply USING 'supply ';

SELECT DB_LINK FROM USER_DB_LINKS;

DB_LINK

------------------

HQ. US. EXAMPLE. COM

SUPPLY. JP. EXAMPLE. COM

This result indicates that the database resolves the partially specified link name by using the domain jp.example.com. this domain is used when the link is created because it is the domain part of the global database name of the local database. the database does not use the DB_DOMAIN initialization parameter setting when resolving the partial link name.

8. you then receive word that your previous information was faulty: sales will be in the ASIA. JP. EXAMPLE. COM domain, not the JP. EXAMPLE. COM domain. consequently, you rename the global database name as follows:

Alter database rename GLOBAL_NAME TO sales.asia.jp.example.com;

SELECT * FROM GLOBAL_NAME;

GLOBAL_NAME

----------------------------------------------------------------------------

SALES. ASIA. JP. EXAMPLE. COM

You query V $ PARAMETER to again check the setting for the parameter DB_DOMAIN:

Select name, value from v $ PARAMETER

Where name = 'db _ domain ';

NAME VALUE

---------------------

Db_domain US. EXAMPLE. COM

The result indicates that the domain setting in the parameter file is the same as it was before you issued either of the alter database rename statements.

9. Finally, you create a link to the warehouse database and again query USER_DB_LINKS to determine how the database resolves the partially-specified global name:

Create database link warehouse USING 'warehouse ';

SELECT DB_LINK FROM USER_DB_LINKS;

DB_LINK

------------------

HQ. US. EXAMPLE. COM

SUPPLY. JP. EXAMPLE. COM

WAREHOUSE. ASIA. JP. EXAMPLE. COM

Again, you see that the database uses the domain part of the global database name of the local database to expand the partial link name during link creation.

Therefore, alter database rename global_name to xx does not affect the db_domain parameter, but uses global_name instead of db_domain when creating the db link.