| Oracle® Database Net Services Reference 11g Release 1 (11.1) Part Number B28317-01 |
|
|
View PDF |
| Oracle® Database Net Services Reference 11g Release 1 (11.1) Part Number B28317-01 |
|
|
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:
Oracle Names is not supported as a naming method in Oracle Database 11g. You must migrate to directory naming.
See Also:
Oracle Net Services Administrator's Guide for information about migrating to directory namingIdentix and SecurID Authentication Methods
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:
RADIUS
Kerberos
SSL
Novell Directory Services (NDS) External Naming and NDS Authentication
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:
See Also:
Chapter 5, "Profile Parameters (sqlnet.ora)" for a description of these parametersIf 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:
TCP/IP
TCP/IP with SSL
Named Pipes
SDP
See Also:
"Protocol Parameters" for protocol parameter configurationTable A-1 describes the networking parameters no longer supported.
Table A-1 Unsupported Networking Parameters
| File | Parameter | 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 used to be included in profiles as slight variants of the NAMES.DEFAULT_DOMAIN parameter. |
8.0 |
|
|
|
This parameter was used to configure naming contexts for NDS external naming. |
8.1 |
|
|
|
This parameter's name has changed to WALLET_LOCATION. |
8.1 |
|
|
|
This parameter was used to seed a random number generator for Oracle Advanced Security. In 10i, Oracle Advanced Security uses a random number generator that does not to require a user-supplied seed value. |
9.2 |
|
|
|
|
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. Use the INBOUND_CONNECT_TIMEOUT_listener_name parameter. |
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. |
8.1 |
|
|
|
All parameters |
Oracle Names is no longer supported. |
9.2 |
Table A-2 describes the control utility commands not supported in release 9.0.
Table A-2 Unsupported Network Control Utility Commands
| Control Utility | Commands | Description | Last Supported Release |
|---|---|---|---|
|
Oracle Names Control Utility |
All commands |
Oracle Names is no longer supported. |
9.2 |
|
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. |
8.1 |
|
|
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. |
8.1 |
|
|
Listener Control Utility |
These commands instructed the listener to register database information with an Oracle Names server. |
8.1 |
