Oracle Net8 Release Notes
Release 8.0.4
*******************************************
Copyright (C) 1997 Oracle Corporation
This software/documentation contains proprietary information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited.
If this software/documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights and the following legend is applicable:
RESTRICTED RIGHTS LEGEND:
Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, Rights in Technical Data and Computer Software (October 1988).
If this software/documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with "Restricted Rights," as defined in FAR 52.227-14, Rights in Data - General, including Alternate III (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.
Oracle and SQL*Net are registered trademarks of Oracle
Corporation, Redwood City, California. Oracle Security Server,
Oracle Enterprise Manager, Net8, and Oracle8 are trademarks of
Oracle Corporation, Redwood City, California.
Oracle Net8 Assistant requires the Java(TM) Runtime
Environment. The Java(TM) Runtime Environment, Version 1.1.1 ("The
Software") is developed by Sun Microsystems, Inc. 2550 Garcia
Avenue, Mountain View, California 94043. Copyright (c) 1997 Sun
Microsystems, Inc. The Software and documentation are the confidential
and proprietary information of Sun Microsystems, Inc. ("Confidential
Information"). You shall not disclose such Confidential Information
and shall use it only in accordance with the terms of the license
agreement provided with The Software.
All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
*********************************************
Overview
======
Net8 provides the networking component of Oracle8.
Net8 provides transparent client-server and server-server connectivity
across all major transport protocols and platforms. Net8 also
provides connectivity with Rdb, Oracle Gateways, and other network
services.
This Read Me file supplements information found in
the Oracle Net8 Administrator's Guide.
Contents of this Read Me File
=============================
- Backward Compatibility
- New and Enhanced Features
- Migration Notes
- Known Restrictions
- Documentation Corrections for Oracle Names
- Oracle Net8 Assistant Usage Notes
- Oracle Net8 Assistant Known Problems
Backward Compatibility
================
Net8 is the successor to SQL*Net version 2. Net8
is fully backward compatible, over the wire, with all currently
supported production releases of SQL*Net version 2 (2.1, 2.2 and
2.3). Net8 clients can interact with either SQL*Net v2 or Net8
services, and SQL*Net v2 clients can interact Net8 services.
The Net8 listener supports both Oracle7 and Oracle8 databases
allowing for only one listener per node.
New and Enhanced Features
==================
Net8 includes the following significant new or enhanced
features. They are listed here for your convenience, and are described
in detail in the Oracle Net8 Administrator's Guide.
Oracle Connection Manager
-----------------------
The Oracle Connection Manager (available with the
Oracle8 Enterprise Edition) provides three capabilities for Oracle8:
- Connection Concentration
Allows you to multiplex multiple logical client
sessions through a single transport connection to an Oracle server
destination. This permits large numbers of users to access a single
database which is running in multi-threaded server (MTS) mode,
and thus increases the server's scalability.
- Network Access Control
Provides a proxy for denying or allowing access
to a database server. This feature, implemented only over the
TCP/IP protocol, provides network filtering similar to that offered
with a firewall.
- Multi-Protocol Support
Replaces the Multi-Protocol Interchange. Allows client and database servers operating on different protocol stacks to communicate with each other.
Net8 Connection Pooling
--------------------
Connection pooling is another scalability feature
that allows you to maximize the number of physical network connections
to a multi-threaded server. With connection pooling enabled, the
server will release idle physical network connections for new
incoming sessions, in the event that no additional connections
are available. This essentially "recycles" server resources
that would otherwise be unavailable for use.
Oracle Net8 Assistant
-------------------
Net8 release 8.0 introduces the Oracle Net8 Assistant,
a tool that is both integrated with the Oracle Enterprise Manager
and provided stand-alone. By providing a graphical interface that
is easy to use, the Oracle Net8 Assistant eases the burden of
configuring and administering a distributed network. This tool
is implemented in Java and as such is available on any platform
where Net8 and Java version 1.1.1 are available. The Oracle Net8
Assistant configures the following:
- Service Names
The tool enables the user to create or edit the
local naming file (TNSNAMES.ORA).
- Profile
The tool enables the user to create or edit the
local configuration file (SQLNET.ORA) on the local machine.
- Oracle Names Servers
The tool enables the user to configure and control
a Names Server from the local machine, and to control other Names
Servers on remote machines.
This release of Oracle Net8 Assistant only supports
configuration of network listeners (LISTENER.ORA) on the Windows
NT platform. It does not provide configuration for Oracle Connection
Managers (CMAN.ORA), nor does it support configuration of local
service names for load balancing or Oracle Parallel Server access.
These capabilities may be provided in subsequent releases.
Host Naming
-----------
This feature enables users in simple networks to
access a database with minimal use of configuration files. It
enables users to contact a remote server by using the name of
the host on which it resides. Oracle recommends that NIS, DNS,
or a TCP/IP hosts file entries be used to map the name of the
database to the name of the machine.
At installation a LISTENER.ORA file is automatically
generated which will allow Net8 client workstations to make connections
using Host Naming to the initial database without additional Net8
configuration steps. However, this automatic configuration depends
upon getting accurate information from the operating system about
the host and domain name for the machine the server is installed
on. If you cannot make a connection to the initial database using
Host Naming over a TCP/IP network please verify that the GLOBAL_DBNAME
parameter in the LISTENER.ORA file specifies a complete name,
including domain, for the server machine such as mycomputer.acme.com.
Also for database location transparancy you may want to define
a host name alias for this computer in your NIS, NDS or other
TCP/IP host name resolution system which refers to this database
and change the GLOBAL_DBNAME parameter to use this alias rather
than the canonical host name.
Trace Assistant
---------------
Trace Assistant is a tool that formats level 16 (SUPPORT)
traces into paragraphs that are easier to read than unformatted
trace files.
Oracle Names Discovery Features
-------------------------------
In this release, Oracle Net8 clients use a mechanism
to locate and access Oracle Names Servers without the need for
extensive configuration files. Clients and servers may 'discover'
Names Servers by issuing a command from the Oracle Net8 Assistant
or from the Oracle Names Control Utility (NAMESCTL). The discovery
process will result in the creation of a list of Names Servers
sorted in order of response time on the client or server.
Oracle Names Client Cache
-------------------------
Clients using Oracle Names Version 8.0 will forward
their queries through a daemon process allowing the results of
their queries to be stored in its local cache. This helps to
save the time and resources required to make subsequent requests
to a Names Server for the same service name information.
Enhanced Listener Load Balancing
----------------------------
The Net8 network listener allows new classes of service
such as Multiple Parallel Processing (MPP) servers to use load
balancing methods.
External Naming (Native Naming Adapters)
--------------------
Native naming adapters for the Network Information
Service (NIS) and NetWare Directory Service (NDS) are included
with Net8 on selected platforms. These adapters were formerly
available only through the Oracle Advanced Networking Option.
Migration Notes
===============
Although Net8 is fully backward compatible with SQL*Net
v2, there are some migration considerations. In addition to those
listed here, see the Oracle Net8 Administrator's Guide.
Note: Previous releases of SQL*Net included several
documents. In this release of Net8, however, all generic documentation
for the product is included in the Oracle Net8 Administrator's
Guide. Net8 error messages are included in the Oracle8 Server
Error Messages document.
Oracle TRACE
------------
For customers who are migrating from the 8.0.2 Beta release, the tracing mechanism has reverted back to the ASCII file-based method from SQL*Net v2. Oracle Trace, which was made temporarily the default in 8.0.2, is still available, but is no longer the default, and can only be turned on via a special configuration parameter. To enable Oracle Trace- based tracing, add the following in the appropriate component configuration file (e.g., cman.ora, sqlnet.ora, or listener.ora):
USE_OTRACE=YES|ON|TRUE
"YES" or "ON" or "TRUE" will suffice. This is a toggle that will turn on Oracle Trace-based tracing, turning the default tracing mechanism off.
This tracing change in no way changes the usability
of the Net8 Trace Assistant. It functions normally as before,
providing details and analysis of Oracle networking traffic.
Oracle MultiProtocol Interchange Replaced
-----------------------------------
The Oracle MultiProtocol Interchange product has been superseded by the Oracle Connection Manager. While the MultiProtocol Interchange
can continue to function as a middle tier in a Net8-Net8, or SQL*Net-Net8 multiprotocol environment, if you are upgrading your software to Oracle8 and Net8, Oracle recommends that you replace the MultiProtocol Interchange with the Connection Manager. The Connection Manager is simpler to use and configure, needs fewer system resources, and has other useful features, such as concentration and network access control. Connection Manager supports SQL*Net clients and Oracle7 servers. However, you must replace the Oracle MultiProtocol Interchange configuration files and must change the connect descriptors to support routing. See the Oracle Net8 Administrator's Guide for details.
Note that the executable names for the Connection
Manager have changed to use the prefix "cm", and not
"sfp". This is mostly visible to customers who have
used the Connection Manager Control Utility, previously called
"sfpctl"; it is now "cmctl".
SQL*Net 7.1.6 Issues
------------------
Between 7.1.6 and later revisions of SQL*Net, including
Net8, there are two configuration issues:
1) For the IPC protocol adapter, the location of the UNIX Domain Socket (IPC) file on UNIX systems changed after 7.1. Thus, if you have 7.1 installed on the same machine as 8.0, and you attempt to make an IPC connection between the two instances, the connection may fail. The solution to this problem is to make a symbolic link between the directory where the IPC file used to be (/tmp/o, or /var/tmp/o on SVR4) to where it now resides (/tmp/.oracle or /var/tmp/.oracle on SVR4).
2) Any Oracle 7.1.6 product (for example, SQL*Plus
version 7.1.6) using SQL*Net services should verify that the following
parameter is not in the SQLNET.ORA file:
sqlnet.authentication_services=(<any entries>)
Remove the entire parameter if it exists in SQLNET.ORA.
If it remains, an ORA-12633 error may occur. This error indicates
a connection cannot be made because the client and server do not
both support the same authentication service.
Change to AUTOMATIC_IPC
------------------------
The AUTOMATIC_IPC feature has been switched OFF by
default. In past releases of SQL*Net, the service name was used
to construct an IPC address which the client code tried first
to connect to. This feature is superseded by the host naming feature.
Additional Connection Manager Parameter Descriptions
----------------------------------------------------
The following descriptions of parameters supported
in the Connection Manager configuration file supplement those
documented in the Oracle Net8 Administrator's Guide:
- MAXIMUM_CONNECT_DATA specifies a maximum limit
to the connect data string. It defaults to 1024.
- ANSWER_TIMEOUT indicates the number of seconds
that the Connection Manager will use to timeout the protocol handshake
associated with an incoming connect request. It defaults to 0
(meaning no timeout).
MTS_DISPATCHERS Parameter Correction
------------------------------------
The MTS_DISPATCHERS parameter referenced in Section
7.3.2 of the Oracle Net8 Administrator's Guide is incorrect.
It should read as follows:
MTS_DISPATCHERS = (PROTOCOL=TCP) (MULT=ON)
Known Restrictions
==================
Connection Manager:
--------------------
Multiplexing to multi-threaded servers with the Connection Manager is currently supported only for TCP/IP connections, end to end.
Oracle Net8 Assistant does not support Connection
Manager routing and listener failover. They must be configured
with a text editor.
Connection Pooling:
----------------
Multiplexing and connection pooling should not both be configured within INIT.ORA, as explained above. This will cause undefined behavior in the client.
Connection Pooling to multi-threaded servers is only
supported for TCP/IP and IPC connections for client/server.
TNS2NIS Name Conversion Note
============================
If you are using the TNS2NIS utility to convert local
names configuration files (TNSNAMES.ORA) to NIS map files, verify
that the format of the file conforms to that expected as if it
were generated by Oracle Network Manager and ensure that the name
"tnsnames.ora" appears in the second line of the file.
Oracle Net8 Assistant Usage Notes
=================================
Oracle recommends that you follow standard practice and make backup copies of your current SQL*Net version 2 configuration files before you begin updating them using the Oracle Net8 Assistant.
When opening a network configuration or doing a Save As operation, specify the directory in which the network configuration files are stored, not a specific configuration file. However, if you choose the browse button to find the directory you want to specify, you must select or enter a file name. The name you enter can be the name of a file that exists or does not exist; it does not matter.
Note: if you are running the Oracle Net8 Assistant in a language other than English, Net8 keywords will appear in English. Keywords have not been translated.
Oracle Net8 Assistant Known Problems
====================================
This section lists known problems, ways to avoid them, and bug numbers logged because of them.
1. The Oracle Net8 Assistant and the Oracle Net8
Easy Configuration Tool do not support configuring local service
names in a TNSNAMES.ORA file for load balancing or Oracle Parallel
Server access. In other words, they do not support description
lists. However, you can create service names with description
lists by editing the TNSNAMES.ORA file directly. Service names
with description lists will not be displayed by the Net8 Assistant
but they will be preserved if you use the Net8 Assistant to create
or change other service names. (484298)
2. The Oracle Net8 Assistant does basic validity
checking of the information you enter and where possible will
warn you of invalid entries. However, some fields are not validated.
Currently there is no validity checking on directory paths and
some file names. (499699, 500058, 500827)
3. If two instances of Net8 Assistant are running, one can overwrite the other's network configuration changes. At this time it is not possible to lock the configuration so that only one instance can modify the configuration. We recommend that you avoid running more than one instance of Oracle Net8 Assistant on any one set of network configuration files. (484369)
4. In the Oracle Net8 Assistant you cannot modify the name of a Service Name. On Windows NT/95, if you wish to modify the name of a Service Name, use the Oracle Net8 Easy Configuration Tool. Otherwise, do this directly by editing the TNSNAMES.ORA file with an editor of your choice. (484350)
5. The Oracle Net8 Assistant cannot create a Service Name having the same name as one which has just been deleted without first saving the network configuration. (484473)
6. In the Oracle Net8 Assistant you cannot explicitly specify a dedicated or a dispatched server on a specific Service Name. If you want to configure this we recommend that you configure this directly into the TNSNAMES.ORA file by using an editor of your choice. (493676)
7. In the network configuration files generated by the Oracle Net8 Assistant there may be an unprintable character at the end of each line in the files. Some editors may display this character as a box. This character can be ignored. It causes no ill effects. (459718)
8. When you save a file, the Oracle Net8 Assistant does not warn you if you are about to overwrite an existing file. Be sure that you want to overwrite any previous version of a file before you save it, or save it to a different location.(484373)
9. Oracle Net8 Assistant fails to display the new Names Server name in the tree structure after it has been changed. You can verify that the name has been changed by checking the NAMES.ORA file, and if necessary, edit the file with a text editor. (500176)
10. If you use the Net8 Assistant to manage a Names
Server, and make a change (such as changing the trace level or
trace file name), the Net8 Assistant requests that the Names Server
also write this change into the NAMES.ORA file. However, if the
Net8 Assistant is on the same machine as the Names Server, subsequently
saving the network configuration will overwrite the changes which
the Names Server made to NAMES.ORA. To avoid this problem, after
making changes in the Manage Server panels which you want to make
permanent, exit and restart the Net8 Assistant before saving the
configuration.(500798)
11. The Japanese version of Net8 Assistant displays
some Names Server messages as unreadable characters. These error
messages indicate that the Names Server cannot be contacted.(501430)
12. If more than seven addresses are specified for
a service name, not all Address tab panels can be viewed even
though they can be added. To view any Address tab, click on any
tab in the Tab panel and use the keyboard right and left arrow
keys to move to any other Address panel. (484316)
13. The Net8 Assistant on Solaris may not display
on an X terminal if the font being used by the Java Virtual Machine
is not a font which is displayable by the X terminal. To fix
this change the default font used by the Java Virtual Machine
(font.properties file) to a font which can be displayed by your
X terminal. (506114).