Storing the network configuration in a local filesystem
Objective
Store the overall topology.
Storing Network configuration in local filesystem
Two parameter files control the overall Oracle Names environment.
Each Oracle Names server contains a names.ora file, while clients have a Names entry in their sqlnet.ora file.
For all Oracle clients that reference the Names server, some sqlnet.ora parameters need to be included:
names.preferred_servers =
This parameter indicates the name, addresses, and order of Names servers that will be used for a client's name requests. In the example below, the dilbert server will contain the Names server.
Indicates the domain from which the client most often requests names. When this parameter is set, the default domain name will be automatically appended to any unqualified service name.
Now let us look at the Names server parameter file. Just like the listener.ora, the names.ora file should reside in your $ORACLE_HOME/network/admin directory.
And like the Oracle listener, the Names server will create a server process that will poll for incoming requests.
Click the names-ora-file link below to look at a sample names.ora file. In the new window, roll your cursor over the areas outlined in red to learn about the most important values of the file.
Names orafile
names.addresses = This specifies the service name of the database containing the Names server data.
names.admin_region = This is used when you want the Names server to store transparent network substrate (TNS) and link information.
names.authority_required = Determines whether system queries require Authoritative answers.
names.server_name = Each Names server is uniquely identified by a name. All configuration references to a particular Names server use this name.
The next lesson discusses how to use the Names control utility.
Oracle Names Concepts - Quiz
Before moving on to the next lesson, click the Quiz link below to check your understanding of Oracle Names concepts. Oracle Names Concepts - Quiz