Oracle9i Net Services Reference Guide Release 2 (9.2) Part Number A96581-02 |
|
|
View PDF |
This appendix describes features no longer supported by Oracle Net Services.
This appendix contains these topics:
In an effort to streamline configuration decisions for the Internet, the following subsections describe the features and the configuration file that are no longer being supported:
If you are using Identix or SecurID authentication methods, provided by Oracle Advanced Security, Oracle Corporation recommends migrating to one of the following authentication methods:
Support for NDS as an authentication method and as an external naming method is no longer supported. If you are using NDS as an external naming method, Oracle Corporation recommends using directory naming instead.
Net8 OPEN, which provided an application program interface (API) that enabled programmers to develop both database and non-database applications, is no longer supported.
The protocol.ora
file is no longer supported.
Parameters in the protocol.ora
file have been merged into the sqlnet.ora
file. These parameters enable you to configure access control to the database, as well as no delays in TCP/IP buffer flushing. These parameters include:
TCP.EXCLUDED_NODES
TCP.INVITED_NODES
TCP.NODELAY
TCP.VALIDNODE_CHECKING
See Also:
Chapter 6, "Profile Parameters (sqlnet.ora)" for a description of these parameters |
If you have a protocol.ora
file in the $ORACLE_HOME/network/admin
directory on UNIX, and the ORACLE_HOME
\network\admin
directory on Windows operating systems, Oracle Net Manager, when first started, automatically merges the protocol.ora
parameters into the sqlnet.ora
file.
There may be operating system-specific parameters in protocol.ora
that are node specific. For this reason, Oracle Corporation recommends not sharing sqlnet.ora
with other nodes after merging or adding these parameters.
Prespawned dedicated server processes are no longer supported. Instead, configure shared server to improve scalability and system resource usage.
Protocol addresses using the SPX or LU6.2 protocol must be replaced. Oracle Net provides support for the following network protocols:
See Also:
"Protocol Parameters" for protocol parameter configuration |
Table B-1 describes the networking parameters no longer supported.
Parameter | File | Description | Last Supported Release |
---|---|---|---|
|
|
The parameter was a required part of all network service addresses. Thus, it appears anywhere you might find an address (for example, local naming and listener configuration files). |
8.0 |
|
|
This parameter was used to force sessions through IPC addresses. Due to performance issues, this parameter has been removed. Configure an IPC address instead. |
8.0 |
|
|
This parameter was used to be included in profiles as slight variants of the |
8.0 |
|
|
This parameter was used to configure naming contexts for NDS external naming. |
8.1 |
|
|
This parameter's name has changed to |
8.1 |
|
|
These parameters supported the Identix authentication method. |
8.1 |
|
|
This parameter specified the amount of time that the listener waited for a client's request after the transport connection had been established. |
8.1 |
|
|
These parameters were used for prespawned dedicated server configuration. Prespawned dedicated servers are no longer supported. Use shared server instead. |
8.1 |
|
|
This parameter instructed the listener to register database information with an Oracle Names server during startup. Use the Oracle Names Control utility |
8.1 |
|
|
This parameter enabled/disabled the Dynamic Discovery Option. Use the Oracle Names Control utility |
2.3 |
Table B-2 describes the control utility commands not supported in release 9.0.
Commands | Control Utility | Description |
---|---|---|
|
Oracle Names Control Utility |
This command created a domain hint. Configure the |
|
Listener Control Utility |
These commands controlled the Oracle Intelligent Agent for use with Oracle Enterprise Manager. You can now control the Oracle Intelligent Agent through the Oracle Enterprise Manager Console. |
|
Listener Control Utility |
These commands specified the amount of time that the listener waited for a client's request after the transport connection had been established. |
|
Listener Control Utility |
These commands instructed the listener to register database information with an Oracle Names server. Use the Oracle Names Control utility |