Release 8.0.3
A54896_01
 Library |
 Product |
| Oracle8
for Windows NT Release Notes Release 8.0.3 A54896_01 |
|
This Release Note documents important last minute features and limitations not included in the HyperText Markup Language (HTML) Release Note on the Oracle8 for Windows NT CD-ROM disc. It also includes corrections regarding information in the HTML Release Notes.
The following topics are included:
Before starting installation, ensure that the Taskbar is located at the bottom of the screen.
This section includes the following topics:
| Note:
If you use Oracle Data Migration Assistant to migrate data, the following procedure is not required. |
Before using MIG80 to migrate your Oracle7 database to an Oracle8 database, you must first check the character set of your Oracle7 database, and compare it with the character set in the NLS_LANG environment variable, or in the registry (if the character set does not exist as an environment variable.) If the character sets are identical, then you can proceed to run MIG80.
If the character sets are different, before you run MIG80, you must set the NLS_LANG environment variable as follows:
American_America.database character set
where database character set should be substituted with the character set of your Oracle7 database. For example, if the character set of your Oracle7 database is JA16EUC, set the NLS_LANG environment variable as follows:
C:\ SET NLS_LANG=AMERICAN_AMERICA.JA16EUC
Messages output from MIG80 will now be in English. After MIG80 finishes, you should reset the NLS_LANG environment variable to its original value.
When migrating from Oracle7 Server release 7.3.x to Oracle8 release 8.0.3, install the appropriate version of SQL*Net for the server before using Oracle Data Migration Assistant.
| Important:
Migration will be unsuccessful if you do not install the appropriate versions of SQL*Net. |
| Additional
Information:
See the Net8 README and the Oracle Security Server README for additional information that is not included in the printed documentation. |
This section includes the following topics:
If you select Custom installation and only choose Net8 Client, the Net8 Assistant and Net8 Easy Config tools are not installed. You need to choose Net8 Assistant if you need any of the configuration tools.
If you would like Oracle7 and Oracle8 server to co-exist on the same system, do not set TNS_ADMIN on the server system, since there will be port and service conflicts if both the listeners try to use the same LISTENER.ORA configuration file.
If you are using Dynamic Discover Option (DDO) and migrating to Oracle Names Version 8, you may need to add the domain name in GLOBAL_DBNAME field in LISTENER.ORA.
When a client connects to an Oracle8 server in dedicated server mode, WINSOCK2 Shared Sockets feature is used so that the client connection is routed from the listener to the database server. This feature improves the connection time, because the client does not need to close the socket connection with the listener and establish a new connection with the database server.
With the use of Shared Sockets, database server threads also use the same port as the listener. If you shut down the listener and try to start it up again for the same port, the listener does not start up if the port is in use due to any open connections with the database. Ensure that no client is connected to the database before starting up the listener. Note that if you are using a listener with a different port number you will be able to start it up.
Oracle Corporation attempted to overcome the restriction by using the WINSOCK2 option to allow the re-use of a port, but the option does not work reliably. Oracle Corporation is currently working with Microsoft Corporation to resolve this issue.
| Additional
Information:
See Net8 Administrator's Guide for more details about the reload command. |
An error was made in Oracle Networking Products Getting Started for Windows Platforms. The table on page 2-8 which lists the components included with Oracle Networking Products contains a typographical error. The Oracle Protocol Adapters are titled "Supported Protocol Stack Vendors", rather than "Oracle Protocol Adapters".
Oracle Net8 Assistant does not support Named Pipes configuration. Configure Named Pipes manually by editing the configuration files using an ASCII text editor such as Notepad.
Net8 and SQL*Net 2.3.3 support the Oracle APPC/LU6.2 Protocol Adapter on Windows NT, but both versions do not support the Oracle APPC/LU6.2 Protocol Adapter on Windows 95.
Net8 does not support the Oracle DECnet Protocol Adapter, though SQL*Net 2.3.3 supports the Oracle DECnet Protocol Adapter on Windows NT 3.51.
An error was made in Oracle Networking Products Getting Started for Windows Platforms. The section on page 5-9 describing loopback testing mistakenly describes performing loopback testing on a client machine. Loopback testing can only be performed on a server machine.
Note the following corrections for Chapter 4, "Configuring the Network" in Oracle Networking Products Getting Started for Windows Platforms.
All the host names, computer names and service names described in the table should be in lower case. See your operating system documentation for more information on how to set up the system names for different protocols.
If you want to keep the default settings, go to Step 24 (instead of Step 23).
You may get a warning about no Preferred Names Server. Ignore the warning. To avoid the warning:
You may get the error Names Error30, if the Names Server is not yet started. Ignore the error, or start the Names Server.
Oracle Net8 Assistant does not support Named Pipes configuration for Oracle Names Server. If you are using Named Pipes, configure it manually, as described in Net8 Administrator's Guide.
You can use the default No Region Database. In that case, you do not need to define the various parameters of Step 19.
Include the domain name (specified in the configuration file SQLNET.ORA as NAME.DEFAULT_DOMAIN, which is WORLD by default) in the parameter GLOBAL_DBNAME. For example, if the domain name is WORLD and you want to use a database name of TESTDB, specify GLOBAL_DBNAME as TESTDB.WORLD.
Ignore these steps.
This release of Oracle Networking Products for Windows Platforms does not support Network Information Service (NIS).
The connect string used by an Oracle8 client or Oracle8 server connecting to an Oracle8 Security Server, needs to include the parameter (in bold typeface):
...
(CONNECT_DATA=
(SID=ORCL)
(SECURITY=(AUTHENTICATION SERVICES=NONE))
When defining a global user, the user CN=user in X.509 syntax must match the global user name.
A typographical error was made in Oracle Networking Products Getting Started for Windows Platforms. The section "Defining for Multiple Protocol Interchange" should read "Defining for Multiple Protocol Support". The networking feature formerly known as Multi-Protocol Interchange (MPI) is now called Multiple Protocol Support. Multiple Protocol Support is available as part of the Oracle Connection Manager.
| Additional
Information:
See the Oracle Net8 README file installed in the Networking product group and Net8 Administrator's Guide for details. |
If you are using the parameter DESCRIPTIONLIST in the TNSNAMES.ORA configuration file, do not invoke Oracle Net8 Assistant, as it will modify your TNSNAMES.ORA file in a Parallel Server environment. Currently, you must manually edit the configuration files for an OPS environment.
The TRCROUTE application is not supported on Windows platforms.
Specify NTS in the SQLNET.ORA configuration file for both clients and servers to use the Windows NT Authentication Adapter:
SQLNET_AUTHENTICATION_SERVICES=(NTS)
Set OSAUTH_PREFIX_DOMAIN in the registry to TRUE if you require the database user name to include the Microsoft domain name. For example:
CREATE USER "DOMAIN\USERID" IDENTIFIED EXTERNALLY;/
Oracle Networking Products release 8.0.3.0.0 does not support 16-bit clients, but you can connect to an Oracle8 server from a 16-bit client using 16-bit SQL*Net releases 2.2.x, 2.3.2, and 2.3.3. The configuration files for 16-bit clients must be configured using either Oracle Network Manager or SQL*Net Easy Configuration Tool. Oracle8 features are not available for 16-bit clients. The Bequeath Adapter is not available for connecting a 2.2.x, 2.3.2, and 2.3.3 clients to an Oracle8 server.
On Windows NT and Windows 95, please use $ORACLE_HOME\NET80\LIB\TNSAPI.LIB and the include file $ORACLE_HOME\NET80\INCLUDE\TNSAPI.H.
Connection Manager is not included in Oracle8; it is only included in Oracle8 Enterprise Edition.
An error was made in Oracle Networking Products Getting Started for Windows Platforms. In Appendix C, "Troubleshooting", an erroneous reference to Understanding SQL*Net, Oracle Network Products Messages Manual and Oracle Network Products Troubleshooting Guide was made. See Oracle8 Server Error Messages for more information on Net8 error messages.
Do not exit the Oracle Enterprise Manager Toolbar using the keyboard combination Alt-F4.
All Oracle online documentation is provided in HTML and PDF formats. This section includes the following topics:
| Note:
The Oracle Information Navigator and its HTML files cannot be viewed on Windows 3.1. Please use a 32-bit Microsoft operating system such as Windows NT and Windows 95 to view this information. |
Use the included Oracle Information Navigator to view, navigate, and perform advanced text search on your HTML documentation set. You need a Java and frames enabled browser in order to use Oracle Information Navigator.
A bug has been reported in the Oracle Information Navigator that occurs when you attempt to click on entries found by the search facility. When you click these entries, an error message may appear indicating that the file was not found (for example in Oracle8 Messages and some Video Server manuals). This information is available.
To obtain this information:
Some documents in the Oracle Information Navigator may be missing graphics. If a graphic is missing, go to the Portable Document Format (PDF) version of the document to view the graphic.
Recent changes to Microsoft's Internet Explorer release 3.02 to address security issues may prevent the Oracle Information Navigator from starting and displaying properly. This does not affect your access to the Oracle online documentation.
Use the included Adobe Acrobat Reader to view, navigate, and print your PDF documentation set.
| Note:
You must use Adobe Acrobat version 3.0 to view your PDF documentation set. |
Oracle Enterprise Manager documents in HTML are available as an installation option in the Software Asset Manager window. The same documents are also available in HTML in the Oracle Documentation folder, and as PDF in the \PDFDOC directory on the CD-ROM disc.
Please refer to the README.WRI file located in the \SMS directory at the root of the CD-ROM disc for information on the de-installation options available for all installable products.
Three Beta version JDBC drivers are included in the \JDBC directory on the CD-ROM disc:
| Additional
Information:
See the README in the \JDBC directory and the HTML document Oracle JDBC Drivers in the \JDBC\DOC\CONTENTS.HTM directory for further information. |
Chapter 3, "Starter Database Contents" of Oracle8 Getting Started for Windows NT describes the users that are included in the starter database. Note that the Typical starter database always includes the CTXSYS and DRSYS users no matter what cartridges are selected. Their passwords are CTXSYS and DRSYS respectively and are required only for Oracle8 ConText Cartridge.
Easy-to-use Oracle Assistants are new to this release. This section includes the following topics:
In Chapter 5, "Database Co-existence and Migration", the second bullet paragraph in the section "Using Oracle Migration Assistant for Microsoft Access" is erroneous. Please refer to the following text.
The option that enables your unmodified Microsoft Access forms and reports to work with the newly created Oracle8 database through an Oracle Open Database Connectivity Driver (ODBC) connection does not work correctly with this version of the assistant. To have your Microsoft Access forms work with the newly created Oracle8 database, please use the Oracle ODBC driver after migration has finished.
The keyboard combination Alt F4 does not work for Oracle Migration Assistant for Microsoft Access. Please use the Cancel button of this wizard to exit.
Note that the migration of the replication option renders packages and views invalid.
If you migrate an Oracle7 database which has a different database character set from NLS_LANG environment variable, the text in the log file is written in English.
When trying to start your database with Server Manager after migrating from a 7.1.3.3.6 database, ensure that you use the PFILE option to identify the correct INITSID.ORA file. For example:
SVRMGR> STARTUP PFILE=C:\ORANT\RDBMS71\INITSID.ORA
where SID is the system identifier (SID) for the database you want to start.
If you create a new database using Oracle Database Assistant and would like to allow users from other systems to access the database, you need to:
and
This will ensure that the listener will listen for connections for the database, and remote users will be able to connect to the database.
When you exit from Oracle Database Assistant, you may sometimes receive a Dr. Watson for Windows error message. Please ignore this error message.
The online help for the page where you can select to include the Oracle8 ConText Option in your Oracle8 database describes several products/features that are not available with Oracle8.
Oracle Web Publishing Assistant will not create a web page (though the query will appear in the file listing) if the query includes columns that contain non-textual data, such as columns of datatype LONG RAW, RAW, or BLOB. A query that includes columns of those datatypes can be identified by a Modified date of "Not Available" in the file listing and a message "Could not execute database cursor, due to Oracle error #-932" in the Event Viewer Application log for that query. Delete the query to remove it from the file listing.
Currently, this feature cannot find a Japanese text string of more than one character. That is, if you enter one Japanese character to search, the search feature will work normally; it will find the character, provided it exists in the help text. If you enter more than one Japanese character, or one Japanese character mixed with other characters such as English characters, the search facility will fail to find the string even if it does exist in the help text. Searching for English and other European languages text strings does not have this limitation.
For information on OCI, read the information supplied in the README in the program group after installation.
Re-install Required Support Files version 8.0.3 if:
These problems occur if after installing version 8.0 products, you subsequently install a product that installs Required Support Files version 7.3.2 or version 7.2. Oracle Web Server version 2.1 is an example of such a product.
To re-install Required Support Files version 8.0.3:
The Software Asset Manager window appears
A window appears showing the progress of the installation. After installation is complete, a message appears confirming the installation.
For information on ODBC, read the information supplied in the README in the program group after installation.
For information on Oracle Objects for OLE, read the information supplied in the release note in the program group after installation.
This Release Note contains important information about SQL*Plus that is not included in the SQL*Plus documentation. This section includes the following topics:
In this release of SQL*Plus, the SET NEWPAGE 0 command does not clear the screen between pages; instead, a black box appears. This occurs because the text printing APIs do not support the formfeed character "/f" on these platforms.
Installation of SQL*Plus version 8.0.3 does not overwrite previous versions of SQL*Plus. Therefore, multiple versions of SQL*Plus can exist on the same computer. You may de-install older versions of the software if you choose.
The SQL*Plus User's Guide and Reference incorrectly states that the DEMOBLD file creates a LOGIN file in your current directory. The LOGIN file is not created when you run DEMOBLD; Oracle Installer copies LOGIN.SQL to the \DBS subdirectory of your Oracle home directory when you install SQL*Plus.
Oracle Installer also copies GLOGIN.SQL, a global LOGIN file, to your SQL*Plus directory. The GLOGIN.SQL file is similar to the LOGIN.SQL file, except that GLOGIN.SQL can be used to set preferences that all SQL*Plus sessions can use.
The following SQL*Plus documentation is included in the Oracle documentation set.
| Note:
SQL*Plus does not include online help |
Setting DBA_AUTHORIZATION=BYPASS is not supported in this release. If you install both Oracle7 and Oracle8 in the same Oracle home directory, you must enter a password when you log on, unless you:
Chapter 13 of Oracle8 Getting Started for Windows NT contains an incorrect entry in both the LISTENER.ORA and TNSNAMES.ORA file for using external procedures. Use the following syntax in your LISTENER.ORA file and TNSNAMES.ORA file to enable external procedures to work:
LISTENER =
(ADDRESS_LIST =
(ADDRESS=
(PROTOCOL= IPC)
(KEY= oracle.world)
)
(ADDRESS=
(PROTOCOL= IPC)
(KEY= ORCL)
)
(ADDRESS=
(COMMUNITY= TCP.world)
(PROTOCOL= TCP)
(Host= inventory.us.company.com)
(Port= 1521)
)
)
STARTUP_WAIT_TIME_LISTENER = 0
CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = ADMIN
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = ORCL)
)
(SID_DESC =
(SID_NAME = extproc)
(PROGRAM=extproc)
)
)
PASSWORDS_LISTENER = (oracle)
extproc_connection_data.world =
(DESCRIPTION =
(ADDRESS =
(PROTOCOL=ipc) (KEY=ORCL)
)
(CONNECT_DATA=(SID=extproc))
)
 Copyright © 1997 Oracle Corporation. All Rights Reserved. |
|