|Oracle® Database Net Services Reference
11g Release 2 (11.2)
Part Number E10835-04
This appendix describes coexistence and upgrade issues for Oracle Net Services. This appendix covers the following topics:
Typical users of directory naming (LDAP) require anonymous access to the Oracle Internet Directory for name lookup. If your Oracle Internet Directory software is upgraded to Oracle Internet Directory 11g, then it should be noted that the default setting for Oracle Internet Directory has changed. The default now is to disallow anonymous access to the directory. The directory administrator will need to configure the directory to enable anonymous binds after upgrading the directory to release 11g. In addition, the way anonymous binds are configured in Oracle Internet Directory has changed between Oracle Database 10g and Oracle Database 11g.
See Also:Oracle Internet Directory Administrator's Guide for additional information about anonymous binds
When migrating Oracle Database 11g Release 1 (184.108.40.206) to Oracle Database 11g Release 2 (11.2) in an Oracle Real Application Clusters environment, non-default listeners are not migrated by Oracle Net Services Configuration Assistant. To migrate the non-default listeners, use the following procedure:
Use Oracle Database 11g Release 1 (220.127.116.11) Oracle Net Services Configuration Assistant to remove the non-default listeners.
Use Oracle Database 11g Release 2 (11.2) Oracle Net Services Configuration Assistant to create the non-default listeners.
In Oracle Database 11g Release 2 (11.2), the password feature is being deprecated. This does not cause a loss of security because authentication is enforced through local operating system authentication. To migrate a listener that has a set password, do the following:
Remove all PASSWORDS_listener_name entries from the
Reload the listener using the following command:
lsnrctl reload listener_name
If remote administration of a listener is required, then use one of the following methods to connect to and administer the listener.
Connect to the host where listener is running using SSH or other secure method, and then perform local administration. Local administration is enforced by the operating system authentication.
Use Oracle Enterprise Manager to administer the listener. Oracle Enterprise Manager uses HTTPS, which ensures security.
See Also:Oracle Database Net Services Administrator's Guide for more information about managing the listener
Clients and database servers require compatible releases of Oracle Net Services. For example, an Oracle9i client requires an installation of Oracle Net Services, and an Oracle9i database requires an installation of Oracle Net Services with the Oracle Net Listener.
Consider the following client-to-database connection issues before you decide if upgrading is appropriate for your environment:
sales= (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=sales-server)(PORT=1521)) (CONNECT_DATA= (SERVICE_NAME=sales.us.example.com)))
Connect descriptors that are currently configured with the
SID parameter can remain. However, to take advantage of new features, such as client load balancing and connect-time failover, Oracle recommends replacing
To modify a connect descriptor to use
SERVICE_NAME, use the Oracle Net Manager's compatibility mode.
See Also:Oracle Database Net Services Administrator's Guide for additional information about database identification by
Oracle Names is not supported as a centralized naming method. Because no new enhancements are being added to Oracle Names, consider using directory naming or upgrading an existing Oracle Names configuration to directory naming, as described in the Oracle Database Net Services Administrator's Guide.