End users do not necessarily know or care about the physical location of the databases that comprise the system.
Data is retrieved without any specific reference to the physical sites.
Oracle Net8 accomplishes this through the use of transparent service names that hide the IP address, protocol, and remote database name.
In its most basic form, SQL*Net is a software tool that enables a network of Oracle clients and servers to communicate transparently on top of
any underlying network topology or protocol via SQL.
Although SQL*Net is a very robust and sophisticated tool, you must appreciate the inherent complexity that accompanies its flexibility.
This article provides a no-nonsense overview of the SQL*Net architecture.
All of the examples are based on Unix.
SQL*Net is not easy to install.
You need the following files on the server side in order to operate SQL*Net 2.0 on a Unix system:
Location transparency, or location independence, means that neither applications nor users need to know the actual location of the
- views, or
- stored procedures
they are accessing. Oracle provides support for location transparency
by means of database links and synonyms.
Suppose that the fictitious Bigwheel Bicycle company wants to make its PRODUCTS table visible to its sales site,
while the actual table resides at the headquarters site.
We can configure the sales sites so that a reference to PRODUCTS maps to the table in the headquarters site by creating a database link from
PSLS.BIGWHEEL.COM to PHQS.BIGWHEEL.COM and creating a synonym for the remote object: