本文主要是介绍dblink命名时需注意的地方和GLOBAL_NAMES的含义，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！
官方文档：
Typically, a database link has the same name as the global database name of the remote database that it references. For example, if the global database name of a database is sales.us.oracle.com, then the database link is also called sales.us.oracle.com.
If you set the initialization parameter GLOBAL_NAMES to FALSE, then you are not required to use global naming. You can then name the database link whatever you want. For example, you can name a database link to hq.acme.com as foo.
Note:
Oracle recommends that you use global naming because many useful features, including Replication, require global naming.
After you have enabled global naming, database links are essentially transparent to users of a distributed database because the name of a database link is the same as the global name of the database to which the link points. For example, the following statement creates a database link in the local database to remote database sales:
CREATE PUBLIC DATABASE LINK sales.division3.acme.com USING 'sales1';
See Also:
Oracle Database Reference for more information about specifying the initialization parameter GLOBAL_NAMES
GLOBAL_NAMES的含义：
| Property | Description |
| Parameter type | Boolean |
| Default value | false |
| Modifiable | ALTER SESSION, ALTER SYSTEM |
| Range of values | true | false |
| Basic | No |
GLOBAL_NAMES specifies whether a database link is required to have the same name as the database to which it connects.
If the value of GLOBAL_NAMES is false, then no check is performed. If you use or plan to use distributed processing, then Oracle recommends that you set this parameter to true to ensure the use of consistent naming conventions for databases and links in a networked environment.
这篇关于dblink命名时需注意的地方和GLOBAL_NAMES的含义的文章就介绍到这儿，希望我们推荐的文章对编程师们有所帮助！
