A typical implementation of this type involves corporate headquarters servers that
communicate with departmental servers in various locations. Each server supports client applications,
but it also has the ability to communicate with other servers in the network. This architecture is
shown in Figure 15-3.
514 Oracle Database 11g DBA Handbook
When one of the servers sends a database request to another server, the sending server acts
like a client. The receiving server executes the SQL statement passed to it and returns the results
plus error conditions to the sender.
When run on the clients and the servers, Oracle Net allows database requests made from one
database (or application) to be passed to another database on a separate server. In most cases,
machines can function both as clients and servers; the only exceptions are operating systems with
single-user architectures, such as network appliances. In such cases, those machines can only
function as clients.
The end result of an Oracle Net implementation is the ability to communicate with all databases
that are accessible via the network. You can then create synonyms that give applications true
FIGURE 15-2 Thin-client architecture
Chapter 15: Oracle Net 515
FIGURE 15-3 Server/server architecture
network transparency: The user who submits the query will not know the location of the data that
is used to resolve it. In this chapter, you will see the main configuration methods and files used to
manage inter-database communications, along with usage examples.
Pages:
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773