Release 8.0.3
A51576_01
 Library |
 Product |
 Contents |
 Index |
| Net8(TM)
Administrator's Guide Release 8.0.3 A51576_01 |
|
Net8 release 8.0.3 provides you with a new tool called the Oracle Net8 Assistant to help you configure and manage your network clients efficiently and easily. Use the Oracle Net8 Assistant to configure local naming methods as well as profiles which define parameters for using Net8 features.
This chapter includes the following sections:
By default, Net8 will enable the following features on the client:
Net8 will attempt to resolve a name to a network address using the following three naming methods in the order that they appear by default:
The Host Naming option provides a way to establish a connection to a database with minimal configuration. For more information, refer to the section titled, "Configuring Host Naming".
Logging refers to the process by which network components note and append error-specific information to a log file. For more information, refer to the section titled, "Logging Error Information" in Chapter 8, "Troubleshooting Net8".
To change or to specify additional preferences for these and other Net8 features, you will need to configure a profile.
| Note:
If you use the default settings, Net8 will behave accordingly without a client profile (SQLNET.ORA file). |
To assist you in configuring a profile, local naming methods, and Oracle Names Servers, Net8 introduces the Oracle Net8 Assistant.
Oracle Net8 Assistant is a new configuration and management tool allowing you to set up and administer the following network features and components through a graphical user interface:
Profiles are collections of parameters that allow a client or server to specify preferences for the use of certain Net8 features.
Service names are simple, easy to remember names commonly used to specify the identity and address of database services on a network. Service names are mapped to connect descriptors which may be stored either locally with the client or in a names service such as Oracle Names. Connect descriptors contain information about the network address of each database service including their system identifier, global database name, and location of the database executable.
Oracle Names Servers provide a distributed naming service to help simplify the set up and administration of your Oracle network.
Figure 4-1 depicts a tree directory of the features and components that you may configure and manage using Oracle Net8 Assistant.
The Oracle Net8 Assistant is implemented in Java and is packaged with the Java Runtime Environment. Therefore, you may run the Oracle Net8 Assistant on any platform where Net8 is installed. The Oracle Net8 Assistant replaces most of the functionality previously provided by Oracle Network Manager and the Easy Configuration Tool which were supported only on Windows platforms.
On-line Help is available for the Oracle Net8 Assistant. If you have any questions regarding how to use the Oracle Net8 Assistant, or if you are unclear about what you can do within a certain component, click on any HELP button.
You may use the Oracle Net8 Assistant to create a profile to define preferences for using Net8 features on a client or server node. The Oracle Net8 Assistant saves these preferences to a configuration file called SQLNET.ORA.
Figure 4-2 depicts the graphical user interface used in the Oracle Net8 Assistant to configure a profile.
For a complete list of all available parameters that may be configured in a profile, refer to "Profile Parameters (SQLNET.ORA)" in Appendix B, "Configuration Parameters".
To change the default directory and file names to which log information is written, use the Oracle Net8 Assistant to specify new names.
Enter any valid directory name to specify the directory to which log files will be written on a client or server. For more information about the "LOG_DIRECTORY_CLIENT" and "LOG_DIRECTORY_SERVER" parameters, refer to Appendix B, "Configuration Parameters".
Enter any valid file name to specify the name of the client log file. For more information about the "LOG_FILE_CLIENT" parameter, refer to in Appendix B, "Configuration Parameters".
Tracing is a feature that enables you to obtain more information about the internal operations of Net8 than is provided in a log file. This feature is set to OFF by default.
Use the Oracle Net8 Assistant to enable tracing and to specify the level of the trace. You can also use the Oracle Net8 Assistant to specify the directory and file name to which trace information is written.
Set the trace level to one of the following values to specify the level of tracing on a client or server:
For more information about the "TRACE_LEVEL_CLIENT" and "TRACE_LEVEL_SERVER" parameters, refer to Appendix B, "Configuration Parameters".
Enter any valid file name to specify the name of the log file on the client or server. For more information about the "TRACE_FILE_CLIENT"and "TRACE_FILE_SERVER" parameters, refer to Appendix B, "Configuration Parameters".
Enter any valid directory name to specify the directory to which trace files will be written on a client or server. For more information about the "TRACE_DIRECTORY_CLIENT" and "TRACE_DIRECTORY_SERVER" parameters, refer to Appendix B, "Configuration Parameters".
Use the Oracle Net8 Assistant to route connect requests to specific processes.
To specify that a network listener spawn dedicated server process for connection requests, set the USE_DEDICATED_SERVER parameter to ON. Net8 sets the USE_DEDICATED_SERVER to OFF by default. For more information about the "USE_DEDICATED_SERVER" parameter, refer to Appendix B, "Configuration Parameters".
To force the network listener to route sessions to interprocess communication (IPC) addresses, set the AUTOMATIC_IPC parameter to ON. Net8 sets AUTOMATIC_IPC to OFF by default. For more information about the "AUTOMATIC_IPC" parameter, refer to Appendix B, "Configuration Parameters".
To route connections through Oracle Connection Manager, set the USE_CMAN parameter to TRUE. Net8 sets the USE_CMAN to OFF by default. For more information about the "USE_CMAN" parameter, refer to Appendix B, "Configuration Parameters".
Use the Oracle Net8 Assistant to configure advanced Net8 functionality.
Net8 sends a probe periodically to verify that a client-server connection is still active. This is done to ensure that connections are not left open indefinitely, due to an abnormal client termination. If the probe finds a dead connection, or a connection that is no longer in use, it returns an error, causing the server process to exit.
To enable dead connection detection, enter a time value in minutes specifying the SQLNET.EXPIRE_TIME. Net8 sets the SQLNET-EXPIRE_TIME to 0 by default. For more information about the SQLNET.EXPIRE_TIME parameter, refer to Appendix B, "Configuration Parameters".
Limitations on using the dead connection detection feature are as follows:
Some protocols may already include a native mechanism to perform the same functionality as dead connection detection. For more information, refer to Oracle operating system specific documentation for your platform.
To register a unique client identifier with the listener during a connection request and to include it in an Audit Trail, enter any alphanumeric string up to 128 characters long to specify the SQLNET.CLIENT_REGISTRATION. Net8 sets the SQLNET.CLIENT_REGISTRATION to OFF by default. For more information, about the "SQLNET.CLIENT_REGISTRATION" parameter, refer to Appendix B, "Configuration Parameters".
To turn signal handling off on UNIX systems, set the BEQUEATH_DETACH parameter to YES. Net8 sets the BEQUEATH_DETACH to NO by default. For more information, about the "BEQUEATH_DETACH" parameter, refer to Appendix B, "Configuration Parameters".
To disable out of band breaks, set the DISABLE_OOB parameter to ON. Net8 sets the DISABLE_OOB to OFF by default. For more information about the "DISABLE_OOB" parameter, refer to Appendix B, "Configuration Parameters".
Use the Oracle Net8 Assistant to specify the use and order of naming methods in your profile. Net8 provides several naming options.
Net8 attempts each naming method in the order specified until it establishes a connection. Net8 will attempt the first three naming methods listed above by default:
For example, if a user attempted to establish a connection to a database service called "sales.acme.com" by typing the following connect string:
SQLPLUS> scott/tiger@sales.acme.com
Net8 would proceed as follows:
For more information, refer to Appendix B, "Configuration Parameters".
To configure centralized naming using Oracle Names, take the following steps:
For more information about the "Oracle Names Control Utility (NAMESCTL)" command, refer to Appendix A, "Control Utility Reference".
For more information about the client cache daemon process, refer to "Client Cache Daemon Process"in Chapter 2, "Understanding Net8". For more information about the START_CLIENT_CACHE command, refer to the "Oracle Names Control Utility (NAMESCTL)" in Appendix A, "Control Utility Reference".
Host Naming requires minimal configuration. You may use the host name of the machine on which a database resides to connect to that database if:
For example, you could connect to a database named "host1.acme.com" by issuing the following connect string:
SQLPLUS> scott/tiger@host1.acme.com
if you configured a database existing on a host machine named "host1.acme.com", with the global_dbname="host1", and the global_dbdomain="acme.com".
You could also connect using the following connect string:
SQLPLUS> scott/tiger@salesdb1.acme.com
if you configured the global_dbdomain to "acme.com", and you aliased the host, "host1.acme.com" to "salesdb1".
To configure external naming:
The following is an example of how the parameter would appear in your client profile (SQLNET.ORA file) with the NIS native naming service and local naming configured:
NAMES.DIRECTORY_PATH = (NIS, TNSNAMES)
NAMES.NDS.NAME_CONTEXT =(<nds_name>)
For more information about this parameter, refer to Appendix B, "Configuration Parameters". For more information regarding native naming adapters, refer to Appendix D, "Native Naming Adapters".
By using the Oracle Names Server component of the Oracle Net8 Assistant, you can monitor, control, and operate Names Servers. For more information, refer to Chapter 5, "Configuring Network Services".
When using database links to initiate connections to other servers, the server needs all of the same configuration information as a client. This includes access to a local names configuration file (TNSNAMES.ORA) as well as a client profile (SQLNET.ORA).
By using the Service Names component of the Oracle Net8 Assistant, you can create or modify an existing local names configuration file (TNSNAMES.ORA). This file contains information about service names, source route addresses, and the session data unit.
Figure 4-3 depicts the graphical user interface used in the Oracle Net8 Assistant to configure service names.
To create or modify an existing local names configuration file (TNSNAMES.ORA), add the following keyword values for each service name:
To modify the size of the session data unit (SDU), enter a value for the SDU keyword in either the DESCRIPTION parameter of your service name in the TNSNAMES.ORA file, or in the SID_DESC parameter of your LISTENER.ORA file. By default, the SDU size is 2048. You may use the Oracle Net8 Assistant to configure the SDU in a local names configuration file as an ADVANCED Address feature. The SDU size should be a multiple of the normal transport frame size. Since the normal Ethernet frame size is 1064, the most efficient SDU size over an Ethernet protocol should be a multiple of 1064, but not more than four times the amount of 1064.
The source route address is a path of network addresses used to route a connection through Oracle Connection Manager. This usually consists of the Oracle Connection Manager's listening address followed by the server's listening address.
To specify an address list as a source route address, specify YES for the SOURCE_ROUTE keyword at the end of any ADDRESS list in the DESCRIPTION parameter in your local names configuration file. You may use the Oracle Net8 Assistant to configure a source route address in a local names configuration file as an ADVANCED Address feature.
The following is how a source route address would appear in your local names (TNSNAMES.ORA) configuration file:
sales = (description=
(address_list=
(address=(protocol=tcp)(port=1610)(host=spcstn))
(address=(protocol=tcp)(port=1580)(host=spcstn)))
(connect_data=(sid=db1))
(source_route=yes)
)
|
 Copyright © 1997 Oracle Corporation. All Rights Reserved. |
|