For example, if the database is in the
HQ.MYCORP.COM domain, and the database link is named LOC, the database link will resolve
to LOC.HQ.MYCORP.COM whenever it is referenced.
Using global database names establishes a link between the database name, database domain,
and database link names. This, in turn, may make it easier to identify and manage database links.
For example, you can create a public database link (with no connect string, as shown in the
preceding example) in each database that points to every other database. Users within a database
no longer need to guess at the proper database link to use; if they know the global database name,
they know the database link name. If a table is moved from one database to another, or if a
database is moved from one host to another, it is easy to determine which of the old database
links must be dropped and re-created. Using global database names is part of migrating from
standalone databases to true networks of databases.
Using Shared Database Links
If you use a shared server configuration for your database connections and your application will
employ many concurrent database link connections, you may benefit from using shared database
links. A shared database link uses shared server connections to support the database link connections.
If you have multiple concurrent database link accesses into a remote database, you can use
shared database links to reduce the number of server connections required.
Pages:
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893