Oracle8i
Enterprise Edition for Windows NT Getting Started
Release 8.1.5 for Windows NT A68694-01 |
|
This chapter describes configuration for the Windows NT, Windows 95 or 98 platforms. For an overview of Net8 configuration in general, see the Net8 Administrator's Guide.
Specific topics discussed:
Net8 contains the registry entries Net8 Parameters and Net8 Service Subkeys. To successfully add or modify Net8 configuration parameters, you must understand where they are located and the rules that apply to them.
The location of the Oracle Net8 directory is
KEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID
where ID is incremented for each additional Oracle home directory on your computer (for example, HOME0 is for a first directory, HOME1 is for a second directory, and so forth).
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES contains subkeys that correspond to services. Depending on what is installed, your Net8 services will consist of all or a subset of the following:
Each service subkey contains the following parameters:
You can use the following parameters on Windows NT and Windows 95/98:
Net8 first checks for the parameters as environment variables, and uses the values defined. If environment variables are not defined, it searches for these parameters in the registry.
Additional Information: See "Appendix C-Oracle 8i Configuration Parameters and the Registry " for instructions on editing Windows registry keys. |
You can add the LOCAL parameter to make a connection without specifying a connect string service name. The value for LOCAL is the service name in the TNSNAMES.ORA file located in the ORACLE_HOME\NETWORK\ADMIN directory.
For example, if the LOCAL parameter is specified as finance, you connect to a database from Server Manager with the following command:
SVRMGRL> CONNECT SCOTT/TIGER
Net8 checks if LOCAL is defined as an environment variable or as a parameter in the registry, and uses finance as the service name. If it exists, Net8 connects.
You can add the TNS_ADMIN parameter to change the directory name for configuration files from the default location. For example, if you set TNS_ADMIN to ORACLE_HOME\TEST\ADMIN, the configuration files are used from ORACLE_HOME\TEST\ADMIN.
You can set the USE_SHARED_SOCKET parameter to TRUE to enable the use of shared sockets. If this parameter is set to TRUE, the network listener passes the socket descriptor for client connections to the database thread. As a result, the client does not need to establish a new connection to the database thread and database connection time improves. Also, all database connections share the port number used by the network listener, which can be useful if you are setting up third-party proxy servers.
On Windows NT 4.0 Service Pack3 or earlier, enabling this option precludes bringing the network listener up or down in a case where a database connection spawned by the network listener is active. Therefore, you may need to shut down all of the databases serviced by a network listener before you can bring down and restart a network listener. This results from the way shared sockets have been implemented in WINSOCK2. WINSOCK2 does not allow a reliable thread to a network listener on any port on which other connections are also active. This is not an issue on Windows NT 4.0 Service Pack 4 or later. Oracle recommends that you upgrade to Windows NT 4.0 Service Pack 4 if you intend to set this parameter.
This parameter only works in dedicated server mode in a TCP/IP environment. If this parameter is set, you cannot use the 8.1.5 listener to spawn Oracle 7.x databases. To spawn an Oracle 8.0.x database from an 8.1.5 listener with the shared socket enabled, you must also set the variable USE_SHARED_SOCKET for the 8.0.x Oracle home.
The following sections describe advanced configuration procedures specifically for Net8 on the Windows NT and Windows 95/98 platforms.
Net8 provides two authentication methods for Windows NT and for Windows 95/98, respectively:
The automatically installed Netware Directory Service (NDS) authentication method allows client applications and users to access a NetWare server running Oracle through NDS. Following NDS authentication, a user logged into an NDS directory tree can use an Oracle database on a NetWare server in the same tree. This avoids the user having to enter an additional user name and password.
Note: To connect from a client using the NDS authentication method, the server must be running the NetWare operating system. |
If you also use NDS External Naming, you can view the entire network under a single NDS directory tree.
Additional Information: |
To configure the server:
To configure a client:
The Windows NT Native authentication method (automatically installed with Net8 Server and Net8 Client) enables database user authentication through Windows NT. This ensures that client machines make secure connections to an Oracle8 database on a Windows NT server.
A secure connection is made when a Windows NT client user name is retrieved on a Windows NT server through the Windows NT Native authentication method. The Windows NT server then permits the user to perform the database actions on the server.
For both clients and server, the following authentication method is already set up by default in the SQLNET.ORA file:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
In addition, follow the instructions in "Connecting as INTERNAL with a Password File" in Chapter 10, "Authenticating Database Users with Windows NT" of this guide.
NDS naming refers to the resolution of a service name by
using a supported third-party naming service. The NDS Native Naming Adapters
resolve service names stored in a native naming service.
Note: To connect from a client using the NDS Native Naming Adapter, the server must be running the NetWare operating system. |
The NDS Native Naming Adapter for Windows NT and Windows 95/98 clients uses the NDS naming environment to store service names and addresses of Oracle8 NetWare Servers. This lets an NDS user view the entire network under a single NDS directory tree. You can use native name services in addition to, or instead of, Oracle Names or the TNSNAMES.ORA file.
If the NDS Authentication Adapter is used as well, a single
log on can access a multi-server and multi-database network.
Additional
Information:
See: |
To configure the NetWare Server:
To configure the client:
To connect from a client with the NDS Native Naming Adapter, enter the following command to access an Oracle8 database for NetWare database:
SVRMGR30 SVRMGR> CONNECT USERNAME/PASSWORD@DATABASE_OBJECT_NAME
If you are using Named Pipes protocol with Oracle Names, the network listener may not be able to connect to the Oracle Names server.
Oracle Names creates a "named pipe" at startup time. The network listener tries to open the Named Pipe at startup. If it cannot, the network listener uses the default system account "Local System."
The network listener service may not be able to open the Named Pipe created by Oracle Names unless the OracleHOME_NAMETNSListener(LSNR) service has a valid user ID and password associated.
To set up the network listener permissions:
The Service dialog box appears.
The Add User dialog box appears.
The user ID appears in the Add Name text
box.
This subsection describes the services and port numbers used by Net8.