Release 3 (8.1.7) for Windows NT
November 16, 2000
Part No. A85305-01
These Release Notes contain important last minute information not included on the Oracle8i documentation CD-ROM. They may also contain information regarding products not on your CD-ROM.
This document contains these topics:
This section contains these topics:
Legato Storage Manager (LSM) release 5.7 is certified on Windows 2000.
Oracle Internet File System (iFS) release 1.1 now ships as part of both the:
This section contains these topics:
Additional product README files are located in the product subdirectories under the ORACLE_BASE\ORACLE_HOME directory or in the \RELNOTES directory.
The Oracle8i installation guide and release notes are not included on the Oracle8i documentation CD-ROM. These documents are available on the software CD-ROM and are selectively installable through the Custom installation type and automatically installable through all other installation types. Access these documents after installation from the Start Menu or by clicking INSTALL.HTM in the \DOC directory on your hard drive. You can also access these documents on the software CD-ROM by going to the \DOC directory and clicking INDEX.HTM.
Oracle documentation is also available at these Web sites:
http://docs.oracle.com/ http://technet.oracle.com
The Oracle8i documentation CD-ROM contains guides listed as release 8.1.5, 8.1.6 and 8.1.7. Only guides listed as release 8.1.7 have been updated since release 8.1.6. Guides listed as release 8.1.5 and 8.1.6 have not been revised. However, updates to some of these 8.1.5 and 8.1.6 guides may be included in:
The following section lists the Oracle8i for Windows guides that have been revised, are new, or have been obsoleted in the Oracle8i for Windows documentation set. Other generic guides not listed here have also been updated for release 8.1.7. For information on the particular generic guides that have been revised, are new, or have been obsoleted, see Oracle8i Documentation Addendum.
The following guides have been revised for this release.
The following guides are new for this release and are specific to Legato for Windows.
Read these guides instead of the generic Legato Storage Manager Administrator's Guide, which is also on the Oracle8i documentation CD-ROM.
The following guides that were included on the release 8.1.6 documentation CD-ROM are not included on the Oracle8i for Windows documentation library CD-ROM.
(Bug 1349024) Contains an error regarding the installation of interMedia support. This error is located in chapter 5, "Post-Installation Configuration Tasks", section "To create the CTXSYS user name and the interMedia Text data dictionary tables:", task 4.
4. Run the DR0INST.SQL script to create and populate the Oracle interMedia data dictionary tables:
SQL> @ORACLE_BASE\ORACLE_HOME\CTX\ADMIN\DR0INST.SQL ORACLE_BASE\ORACLE_HOME\CTX\LIB\ORACTXX8.DLL;
The directory path to the DLL should be:
ORACLE_BASE\ORACLE_HOME\BIN\ORACTXX8.DLL
The section "Products Supporting a Single Oracle Home" on page 3-7 of either guide contains a list of products that can be installed only one time per computer This list is not up-to-date. See Chapter 3 of the installation guide for Windows located in the \DOC directory of your component CD-ROM for an up-to-date list of single Oracle home products.
(Bug 1411720) Contains an error regarding support for multi-threaded external callouts. The following bullet point on page 1-7 should have been removed because multi-threaded external callouts are desupported.
EXTPROC operates as an NT process that is capable of spawning multiple threads. When multiple sessions are connected to an Oracle database, only one EXTPROC process is spawned by Oracle instead of spawning separate EXTPROC processes to handle each database session. This one EXTPROC process in turn spawns one thread per database session.
This section contains these topics:
Oracle8i Release 3 (8.1.7) on Windows NT is certified on Windows 2000 with the following exceptions:
These tools do not perform on Windows 2000 and do not report errors when they run. Use the Microsoft Computer Management tools to partition the disks.
Additionally, creating a large number of logical partitions may cause a significant increase in the time needed to reboot and launch the disk administration tools.
If a Windows 2000 computer is not identified with a DNS domain name, you receive the following error message:
Calling query w32RegQueries1.7.0.17.0 RegGetValue Key = HKEY_LOCAL_MACHINE SubKey = SYSTEM\CurrentControlSet\Services\Tcpip\Parameters Value = Domain Query Exception: GetValueKeyNotFoundException Query Exception Class: class oracle.sysman.oii.oiil.OiilQueryException ...
Perform the following steps:
Oracle8i software is supported on the Windows 2000 Multi-language Edition.
On some Windows 95 systems, the Data Control for Oracle Objects for OLE is not registered properly with the operating system. This occurs on systems where an older version of the MFC Runtime Module (MFC42.DLL) is installed. While this module is upgraded by Oracle Universal Installer, if the module is in use, it is not upgraded until after rebooting.
If an older version of the MFC Runtime Module than the one required by Oracle Objects for OLE (required version is 6.00.8447.0) is installed, register the Oracle Objects for OLE Data Control with the operating system after rebooting, using the upgraded MFC Runtime Module.
To do this, enter the following at the command prompt:
REGSVR32ORACLE_BASE\ORACLE_HOME\BIN\ORADC.OCX
where ORACLE_BASE is the Oracle base directory and ORACLE_HOME is the Oracle home directory specified when Oracle Objects for OLE was installed.
This section contains these topics:
If your operating system locale is one of those listed above on your Windows 2000 computer, temporarily change it to English by following the steps described below before installing Oracle8i Release 3 (8.1.7). You can change your operating system locale back to the original value after you finish installing Oracle8i Release 3 (8.1.7) or finish using Oracle's Java-based tools.
In order to change the operating system locale on Windows 2000, perform these steps:
Note that this problem also exists on Oracle8i Release 3 (8.1.7) for Windows NT, but these locales are not supported on this operating system, so the problem does not occur.
The Java Runtime Environment was not found at <location> hence the Oracle Universal Installer cannot be run.
As the Novell server does not support long filenames, the directory path for JRE_LOCATION is not recognized (some of the directory names have more than eight characters). Therefore, this configuration is not supported. Try mounting the CD-ROM locally or on a Windows NT Server.
You can avoid this by performing the following steps:
You cannot deinstall Oracle JServer separately from other products installed with Oracle8i Release 3 (8.1.7).
Deinstalling Oracle JServer causes Oracle Universal Installer to remove Oracle8i and other products dependent on Oracle JServer from your system.
With release 8.1.7, users can select individual Oracle Intelligent Agent extensions such as Oracle Application Extensions, Oracle HTTP Server Extensions, Oracle eBusiness Management Extensions, Oracle Forms Extensions, Microsoft SQL Server Extensions for installation, separately from the basic Oracle Intelligent Agent. Installing an extension will also install the basic Oracle Intelligent Agent since, the extensions depend on the Oracle Intelligent Agent.
Oracle Intelligent Agent and Data Gatherer services are automatically started after installation provided existing Oracle Intelligent Agent and Data Gatherer services are not running. Therefore, Oracle Intelligent Agent discovers existing services such as databases and listeners upon startup. Any service like a database or listener that is installed after Oracle Intelligent Agent is discovered by stopping and restarting the Oracle Intelligent Agent service.
Oracle8i installation may attempt to install several redistributable system files that are required for Oracle software to function correctly. These files are shared by other applications and most likely are in use on the computer.
If the version of a given system file is less than the version required by Oracle, Oracle Universal Installer attempts to upgrade it. Errors may occur during upgrade if the system file Oracle Universal Installer is trying to upgrade already exists on the computer and has been designated as read-only.
In this case, Oracle Universal Installer indicates that it encountered difficulties in copying the appropriate file to the system. If such an error occurs, check to see if the system file in question is writable or if a similar file of the name SYSTEMFILE.OLD exists on the computer.
If the system file that Oracle Universal Installer is trying to replace is read-only, change its attribute so that the file is writable, and click "Retry" in the Oracle Universal Installer window to upgrade the system file.
In some instances, the Oracle Home Selector fails to switch the entries in the PATH environment variable as desired. This occurs in cases where the PATH is defined in multiple places in the file AUTOEXEC.BAT. For example, if the following lines exist in AUTOEXEC.BAT:
PATH C:\windowsPATH D:\oracle\ora817;D:\oracle\ora816;%PATH%
then an attempt to switch the order of D:\ORACLE\ORA817 with D:\ORACLE\ORA816 in the PATH using Oracle Home Selector fails.
To work around this limitation, modify AUTOEXEC.BAT so that the PATH is defined in one location in the file. Using the above example, if you modify AUTOEXEC.BAT to read:
PATH D:\oracle\ora817;D:\oracle\ora816;C:\windows
then attempt to use Oracle Home Selector to switch, the order of Oracle Homes in the PATH succeeds.
It is not possible to install and configure Oracle Internet Directory (OiD) and Oracle Workflow in the same installation session during a custom installation of Oracle8i Management and Integration. If you perform such an installation and choose to install both OiD and Oracle Workflow, the OiD Configuration Assistant is launched during post-installation to configure OiD in the database, and Oracle Workflow is not automatically configured.
To configure Oracle Workflow manually after the installation session is complete.
D:\ORACLE_BASE\ORACLE_HOME\wf\install> inst252.bat wf_acct wf_pwd wf_home sys_pwd system_pwd INSTALL
where:
wf_acct = workflow account. Use OWF_MGR.
wf_pwd = password@db for workflow account. Use OWF_MGR.
wf_home = workflow top level directory, for example, ORACLE_BASE\ORACLE_HOME\wf
sys_pwd = password@db for the SYS account, for example, change_on_install@wfdb
system_pwd = password@db for SYSTEM account, for example, manager@wfdb
It is possible to install Oracle8i Release 3 (8.1.7) using HTTP. To do this:
http://acme.us.oracle.com/817/stage/products.jar
When performing such a Web-based installation on a computer in which no Oracle products have previously been installed, you may experience two errors during installation. These errors occur when installing the Oracle Administration Assistant for Windows NT and Oracle Intelligent Agent. Both errors occur when Oracle Universal Installer attempts to download a library from the indicated URL. The error messages are as follows:
Error Occurred
There was an error during loading library : NtServicesQueries.
To work around these two errors, do the following:
The installation of these two components now proceeds normally.
When installing Oracle Workflow Mailer, the file WFMLR.EXE is incorrectly installed into the directory ORACLE_BASE\ORACLE_HOME. Copy this file into the directory ORACLE_BASE\ORACLE_HOME\BIN before using the mailer.
This section contains these topics:
In Oracle8i Release 3 (8.1.7), Oracle is supporting drop-in compatibility of the 8.1.7 client-side libraries on top of the 8.1.6 client-side libraries. This means that applications and tools running in the same Oracle home as these 8.1.6 client-side libraries do not encounter runtime errors if the libraries are upgraded to 8.1.7 during installation. However, drop-in compatibility is not supported for client-side libraries being used by a database or listener. If an attempt to upgrade the 8.1.6 client-side libraries is made in the same Oracle home as an Oracle8i Release 2 (8.1.6) database or listener, and the database or listener is not also upgraded to 8.1.7, the 8.1.6 versions of the database or listener will break. If you want to keep the older versions of the database or listener intact, you must install Oracle8i Release 3 (8.1.7) in a new Oracle home.
Before performing either a manual database upgrade or an automated database upgrade using Oracle Data Migration Assistant, you must first set _SYSTEM_TRIG_ENABLED = FALSE in the initialization parameter file. After completing the database portion of the upgrade, you must either remove _SYSTEM_TRIG_ENABLED from the initialization parameter file or explicitly set it to TRUE before attempting any other upgrade steps, such as upgrading Oracle JServer.
The Heterogeneous Services Agent Control Utility (AGTCTL.EXE) incorrectly reports its version as 8.1.0.0.0. The version of this utility is 8.1.7.0.0.
Ignore the following error when upgrading from release 8.0.x to 8.1.7. Despite the error message, the upgrade has completed successfully. Note that the error does not occur during upgrade from 8.1.x to 8.1.7.
ORA-00604: error occurred at recursive SQL level 1
If you performed an upgrade of your Oracle8i release 8.1.5 software to Oracle8i Release 2 (8.1.6) in the same Oracle home and now want to upgrade the 8.1.6 software to Oracle8i Release 3 (8.1.7), you will experience an installation runtime error that occurs during the deinstallation of the 8.1.6 software that you can ignore. Oracle Universal Installer treats a software upgrade as a deinstallation of the old software followed by an installation of the new software. While deinstalling the release 8.1.6 software, an attempt to unregister the release 8.1.6 DLL OraOLEDB.DLL fails. An error message is displayed indicating:
A dynamic link library initialization routine failed.
This error occurs because during the upgrade from release 8.1.5 to release 8.1.6, the file OCI.DLL in ORACLE_BASE\ORACLE_HOME\BIN was not upgraded properly to release 8.1.6. Since this occurs during the deinstallation of the release 8.1.6 software, and since both OCI.DLL and OraOLEDB.dll are upgraded successfully to release 8.1.7, the error can be ignored.
In certain situations, an attempt to upgrade some but not all Oracle8i release 8.1.5 or Oracle8i Release 2 (8.1.6) software to Oracle8i Release 3 (8.1.7) may result in the deinstallation of all of the older software, even though you did not choose to upgrade that software during the current session. Pay careful attention to the Oracle Universal Installer Summary window to make sure that this does not happen. For example, if you have performed a release 8.1.6 Oracle8i Enterprise Edition (Oracle8i Standard Edition or Oracle8i Personal Edition) Typical installation, and you want to upgrade only Oracle Intelligent Agent to release 8.1.7, then all of the 8.1.6 components will be deinstalled.
|
Note: Oracle Corporation discourages such partial server-side upgrades, especially if an older Oracle8i database or listener is installed in the same Oracle home. See "Required Support Files Drop-In Compatibility" for more information. |
If you want to retain the basic functionality that was present in the Oracle home with the older software, choose to upgrade all components that are installed in the Oracle home.
It is possible to perform a partial upgrade of some of the software in a particular Oracle home without running into the problems described here. To do this, you must select a different top-level component in the new installation session than was originally chosen when installing the older software. For example, using the same scenario as above, if you performed a release 8.1.6 Oracle8i Enterprise Edition (Oracle8i Standard Edition or Oracle8i Personal Edition) Typical installation, and you want to upgrade only some of the components to release 8.1.7, you should select one of the installation types for Oracle8i Client and upgrade the software as usual. Performing the upgrade in this way will not result in the deinstallation of all your older software, and only those components you have selected for installation will be upgraded.
This section contains these topics:
When you use Oracle Database Configuration Assistant to create a custom database that includes Oracle JServer, be aware that it can take over an hour to finish loading Oracle JServer into the database, depending on your system's hardware configuration.
The OEM _MONITOR role can be granted to any database user being used as a preferred credential when registering advanced (database) events available with the Oracle Enterprise Manager Diagnostics Pack.
This role is defined in ORACLE_BASE\ORACLE_HOME\RDBMS\ADMIN\CATSNMP.SQL, which is called by the catalog scripts at database creation time. In addition to the OEM_MONITOR role, the database user requires space on their default tablespace within the monitored database, in order to have some of the advanced events evaluated. Failure to do so results in an insufficient privilege message.
(Bug 1501788) The Oracle Parallel Server extensions to the Enterprise Manager Console have been left out. This causes parallel servers not to display under the Databases folder. The symptoms of this problem are the existence of oracle_sysman_ops and ops_sysman_opsinst folders under the Network node of console following the discovery of a node that contains a parallel server.
The workaround for this problem is to append the contents of the file OPSCLIENT.PROPERTIES (available as a patch) to the Oracle Enterprise Manager properties file ORACLE_BASE\ORACLE HOME\SYSMAN\CONFIG\OEMCLIENT.PROPERTIES.
This section contains these topics:
If the same IP address and port are used for different Net8 listeners, then instead of the second and the consecutive listeners failing to bind as expected, it allows them to go ahead and listen on this IP address and port. This results in unexpected behavior of the Net8 listeners. This is a suspected Windows NT operating system problem with TCP/IP and has been reported to Microsoft.
nnl-6, nnl-10, nnc-406
The workaround for this problem is to use namesctl at the command prompt with the command load_tnsnames.
ldifde -p OneLevel -d cn=DisplaySpecifiers,cn=Configuration,domain context -f temp file
where:
domain context is the domain context for this Active Directory server. For example dc=acme,dc=com
temp file is a file where you want to put the output.
If the command reports that less than 24 entries were found, you can still use the Net8 Configuration Assistant. However, it will only report that Oracle schema creation failed when all that failed was that display specifiers for some languages were not created.
For all other users (local users, Windows NT 4.0 domain users, Windows 2000 domain users, Windows 95 users, and Windows 98 users), NTLM is the authentication mechanism used by the NTS adapter. So, if the authentication is set to NTS, on a standalone Windows 2000 or Windows NT 4.0 computer, ensure that the Windows Service "NT LM Security Support Provider" is started. If this service is not started on a standalone Windows 2000 or Windows NT 4.0 computer, NTS authentication fails. This issue is applicable only if you are running Windows 2000 or Windows NT 4.0 in standalone mode.
This section contains these topics:
When using Oracle features that support Active Directory using LDAP, ensure that the Active Directory computer can be successfully reached using all of the TCP/IP hostname forms possible to reach the domain controller. For example, if the hostname of the domain controller is server1 in the domain acme.com, then you can ping that computer using:
server1.acme.com acme.com and server1
Active Directory often issues referrals back to itself in one or more of these forms, depending upon the operation being performed. If all of the forms cannot be used to reach the Active Directory computer, then some LDAP operations may fail.
If you are using Active Directory with Oracle on Windows 2000 or Windows NT, then ping the DNS domain name of your Windows 2000 domain. If this does not work, perform either of the following tasks:
For example, your Windows 2000 domain is SALES, the DNS domain name for this domain is SALES.ORACLE.COM, the IP address of the domain controller is 255.255.255.0. On the Windows 2000 computer, either 255.255.255.0 can be set as the DNS, or 255.255.255.0 SALES.ORACLE.COM can be added to the HOSTS or LMHOSTS file.
If this step is not performed, then errors such as the following are returned when using Active Directory.
Cannot Chase Referrals
You must license Oracle Advanced Security to use Active Directory to manage enterprise roles.
On Windows NT and Windows 2000, the Oracle database service runs in the security context of the LocalSystem or a specific local or domain user. When using Oracle8i release 8.1.7 with Active Directory, if the database service runs in the security context of LocalSystem, manually add the computer name in which the database service is running. This enables you to access control entries on the OracleDBSecurity container object in the Active Directory with read permissions on the OracleDBSecurity container object. For example, if the database service OracleServiceORCL is running in the security context of LocalSystem in the computer MYPC1, then add MYPC1 with READ permissions ON OracleDBSecurity object to the access control entries on the OracleDBSecurity container object.
Several products included with Oracle8i Release 3 (8.1.7) are now directory-enabled and can take advantage of an LDAP version 3 directory server such as Oracle Internet Directory. Purchase of Oracle8i Release 3 (8.1.7) includes a restricted use version of Oracle Internet Directory release 2.1.1 for Windows NT that may only be used in conjunction with Oracle's directory-enabled components and products such as Net8, Oracle Advanced Security, Oracle8i, and all future directory-enabled Oracle products.
To enable SSL when connecting to an Oracle database, do not use the default user account in the Windows NT Services dialog box when starting the Oracle service and the listener service. Start these services in the same user account as the wallet created in Oracle Wallet Manager. If the Oracle service and the listener service are started in the default user accounts, SSL does not work and the listener does not start.
Support for SSL, except for HTTPS, is an Oracle Advanced Security feature. Oracle Wallet Manager is also an Oracle Advanced Security feature.
Oracle TCP/IP support for Windows 95/98 uses Windows Sockets 2 interfaces. Therefore, you must install Windows Socket 2 Update for Windows 95 before installing Oracle8i Release 3 (8.1.7). Download it from the following Microsoft Web site:
http://www.microsoft.com/windows95/downloads
Windows Socket 2 Update for Windows 95 can also be installed by double-clicking on the file WS2SETUP.EXE located in the \WINSOCK2 directory at the root of your distribution media.
The Common Object Request Broker Architecture (CORBA) oneway call messages may not be delivered reliably to the server if a client writes several oneway messages and then immediately closes the connection and exits. This is due to a Windows Sockets API bug on Windows NT 4.0 SP6 and SP6a with the Lotus security patch.
Do not exit immediately after invoking oneway calls, for example, by putting a call to Thread.sleep ( ). Additionally, the CORBA specification describes oneway call semantics as best-effort, at-most-once and does not guarantee delivery of the message. The Aurora Object Request Broker (ORB) guarantees delivery of even oneway calls, but because of this bug on Windows NT, it may not guarantee it on Windows NT.
(Bug 993548) When Net8 operating system native authentication is not enabled for the database, users are unable to view the database thread information using Oracle Administration Assistant for Windows NT. If this is the case, and users want to view the database thread information using Oracle Administration Assistant for Windows NT, they need to run a utility called OCFGUTIL.EXE with the arguments username and password. This utility stores the user name and password in the registry location \\HKEY_LOCALMACHINE\SYSTEM\CurrentControlSet\Services\
Oracle8Oraconfig which is read by the Oracle Remote Configuration Agent to log into the database.
This section contains these topics:
Microsoft Windows Terminal Server is a Windows thin-client terminal server, a product that adds support for multiple, simultaneous client sessions on the Windows NT Server. Windows Terminal Server provides an operating system graphical user interface (GUI) to users of Oracle8i for Windows NT databases, release 8.1.7.
Oracle8i installations are supported on the following Windows Terminal Servers:
(Bug 1458669) The LSNRCTL START command does not return a prompt and hangs when run from the Terminal Services Client. The listener service is started but is unusable. A workaround is to start the listener service by using the NET START command at the command prompt if the listener service is already created. Note that the LSNRCTL START command works when run from the Terminal Server console.
Net8 Configuration Assistant hangs when trying to start the Net8 listener on Microsoft Terminal Server. If this hang occurs during installation, exit Net8 Configuration Assistant and start the listener service by using the NET START command if the listener service is already created.
This section contains these topics:
When creating a database for use with Oracle Parallel Server, you must set the SYSTEM tablespace size to 274 MB. If you are creating a custom database with the Oracle Database Configuration Assistant, you need to change the SYSTEM tablespace size from the default of 260 MB to 274 MB before creating the database. In addition, the size of the raw device that you create for the SYSTEM tablespace must also be at least 275 MB. This requirement supersedes the corresponding file size requirement listed in the Oracle8i Parallel Server Setup and Configuration Guide.
When Oracle Database Configuration Assistant creates Parallel Server databases, the Windows NT service, OracleServiceSID, is created. This service must be started after the OracleCMService. However, the OracleServiceSID is not created by Oracle Database Configuration Assistant with a dependency on the OracleCMService. Thus, when the node is rebooted, the OracleServiceSID fails to start up because the OracleCMService has not started. In this case, the Windows NT Event Log contains Application Log entries such as the following:
error 203; LoadOpsOsd 2, OPS: Startup routine failed: 0 2 3
To start OracleServiceSID after OracleCMService starts, a dependency must be added. Enter the following command:
C:\> CreatDep /s OracleServiceSID /d OracleCMService
For example, if Oracle Database Configuration Assistant creates a parallel server named OP with two instances named OP1 and OP2, enter the following on the node where OP1 runs:
C:\> CreatDep /s OracleServiceOP1 /d OracleCMService
On the node where OP2 runs, enter:
C:\> CreatDep /s OracleServiceOP2 /d OracleCMService
This adds the dependencies on OracleCMService to each of the OracleServiceSID services, ensuring the correct service startup order.
This section contains these topics:
(Bug 599321) Although all Windows operating systems allow spaces in file names and directory names, the Oracle Pro*C/C++ and Oracle Pro*COBOL precompilers will not precompile files that include spaces in the file name or directory name. For example, do not use the following formats:
proc iname=test one.pc
or
proc iname=d:\dir1\second dir\sample1.pc
When adding a registry variable for all sessions, the correct registry key is HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID, not HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE, as incorrectly stated in Oracle Call Interface Getting Started for Windows, release 8.1.6.
ORACLE_BASE\ORACLE_HOME\PRECOMP\DEMO\PROC
The header file XA.H is installed in the ORACLE_BASE\ORACLE_HOME\RDBMS\DEMO directory. It is incorrectly stated in the Oracle Call Interface Getting Started for Windows and Pro*C/C++ Precompiler Getting Started for Windows release 8.1.6 that the file is located in the ORACLE_BASE\ORACLE_HOME\RDBMS\XA directory. Also, the correct name for the library file is ORAXA8.LIB, not ORAXA.LIB. The current URL for general information about XA and TP monitors is:
http://www.opengroup.org/publications/catalog/tp.htm
This section contains these topics:
Using Microsoft Transaction Server With Oracle8 states that Microsoft Transaction Server is currently available as part of the Microsoft Windows NT 4.0 Option Pack. However, Microsoft Management Console version 1.0 is the version installed. This version works with Oracle Services for Microsoft Transaction Server release 8.1.6, and not with release 8.1.7. To use Oracle Services for Microsoft Transaction Server release 8.1.7, you must use Microsoft Management Console version 1.2. Microsoft Management Console is automatically installed with Microsoft Transaction Server.
Certain Chinese language versions of the Oracle Service for Microsoft Transaction Server resource DLLs are not consistent with Oracle8i Release 3 (8.1.7). These include:
To obtain the latest releases of these files, contact Oracle Support Services.
Oracle Performance Monitor for Windows NT is not installed in the Typical installation option. If you install Oracle Performance Monitor for Windows NT using the Custom installation option, you must disable the OracleHOME_NAMEDataGatherer service in the Windows NT Services dialog box. Oracle Performance Monitor for Windows NT cannot co-exist with Oracle Data Gatherer (a component of Oracle Intelligent Agent) on the same computer.
The following instruction on how to delete services using ORADIM was omitted from Oracle8i Administrator's Guide for Windows NT.
To delete an instance using ORADIM, use the following commands:
ORADIM -DELETE -SID SIDA,SIDB,SIDC, ... ORADIM -DELETE -SVRC SVRCA, SVRCB, SVRC, ...
where:
The following initialization parameters have been introduced on Windows NT for release 8.1.7. These parameters already exist on UNIX platforms.
A new feature in Oracle8i for Windows NT is support for Very Large Memory (VLM) configurations, which allows Oracle8i to access more than the 4 gigabyte (GB) of RAM traditionally available to Windows NT applications.
Specifically, Oracle8i Enterprise Edition on Windows NT 4.0 (in conjunction with Intel's PSE36 driver) can now allocate substantially more database buffers than previous releases. Further details are posted at:
http://www.intel.com/ebusiness/server/resources/pentiumii/xeon/esma.pdf
On Windows 2000, Oracle8i uses the Address Windowing Extensions (AWE) built into the operating system to access more than 4 GB of RAM. For more information, see the Microsoft Web site:
http://www.microsoft.com/WINDOWS2000/news/fromms/intelpae.asp
To take advantage of this support, you must do the following:
For example, assume that the Oracle8i database is running on an Windows NT 4.0 computer with 8 GB of RAM, which means that the PSE36 driver has control of 4 GB of RAM. If DB_BLOCK_BUFFERS=2500000 and DB_BLOCK_SIZE=2048, then a total of 5 GB of database buffers needs to be allocated. If VLM_BUFFER_MEMORY is set to 1 GB, then 1 GB of buffers come from the Oracle8i virtual address space and 4 GB come from the PSE36 driver. If you set VLM_BUFFER_MEMORY to 500 MB, an error occurs at startup because there is not 4.5 GB of memory available to the PSE36 driver for database buffers. Likewise, if you set VLM_BUFFER_MEMORY to 3 GB, an error occurs because the Oracle8i address space is limited to 3 GB on Windows NT, and this address space must also hold Oracle8i code, shared pool, PGA memory, and other structures.
In general, the higher the VLM_BUFFER_MEMORY or AWE_WINDOW_MEMORY is set, the fewer connections and memory allocations are possible for Oracle8i. The lower VLM_BUFFER_MEMORY or AWE_WINDOW_MEMORY is set, the lower the performance.
Currently, there is a limitation in SQL*Plus for Windows NT whereby the amount of database buffers displayed during database startup is incorrect if more than 4 GB of buffers are in use. For instance, if 5 GB of buffers are used, SQL*Plus incorrectly reports that 1 GB is being used. This limitation will be fixed in the next release of Oracle8i.
Oracle HTTP Server is automatically started at installation with the Secure Socket Layer (SSL) enabled. The server binary name is APACHE.EXE, and is located in ORACLE_BASE\ORACLE_HOME\APACHE\APACHE.
This section contains these topics:
Oracle HTTP Server can be started or stopped in either of two ways:
To start or stop from the Start menu:
Start > Programs > Oracle - HOME_NAME > Oracle HTTP Server > Start | Stop
To start or stop from the Services window of the Control Panel:
Start > Settings > Control Panel > Services > OracleHOME_NAMEHTTP_Server > Start | Stop
Start the Task Manager and check for two APACHE.EXE processes. If you do not see any APACHE.EXE processes, Oracle HTTP Server is not running.
The initial static page contains links to documentation and demos for each of the server components. The ServerName is identified in the configuration file \ORACLE_BASE\ORACLE_HOME\APACHE\APACHE\CONF\HTTPD.CONF. Load this URL to view documentation and demos for the components in the server:
http://ServerName/
The server-status URL gives specific information regarding the current activity of the server:
http://ServerName/server-status/
For security reasons, the following status pages are disabled in the default configuration files:
http://ServerName/perl-status/
Location: \ORACLE_BASE\ORACLE_HOME\APACHE\APACHE\CONF\HTTPD.CONF
http://ServerName/jserv/
Location: \ORACLE_BASE\ORACLE_HOME\APACHE\JSERV\CONF\JSERV.CONF
To enable them, modify the appropriate configuration file and restart the server.
Any server problems are reported to several log files. Log level directives in the configuration files control the amount of information written to the log files.
\ORACLE_BASE\ORACLE_HOME\APACHE\APACHE\LOGS\ERROR_LOG \ORACLE_BASE\ORACLE_HOME\APACHE\APACHE\LOGS\SSL_ENGINE_LOG \ORACLE_BASE\ORACLE_HOME\APACHE\JSERV\LOGS\JSERV.LOG \ORACLE_BASE\ORACLE_HOME\APACHE\JSERV\LOGS\MOD_JSERV.LOG
At the end of an Oracle8i server installation, the Oracle HTTP Server is started as a standalone process in its own Windows NT Console window. If you close this window, the HTTP Server stops. It is possible to start the Oracle HTTP Server as a background Windows NT service; however, you must reboot your system to successfully complete this operation. If you attempt to start the Oracle HTTP Server service prior to rebooting your system, you receive an error and the service does not start. To start the Oracle HTTP Server as a Windows NT service after installation, perform the following steps:
ORACLE_BASE\ORACLE_HOME\Apache\Apache
C:\> apache -k shutdown
The Oracle HTTP Server service automatically starts upon reboot. Do not perform any additional steps.
(Bug 1503745) When performing silent installations, the Oracle HTTP Server fails to start at the end of installation. Start the Oracle HTTP Server after the silent installation is complete as follows:
ORACLE_BASE\ORACLE_HOME\Apache\Apache
C:\> apache -k start
In Oracle8i Release 3 (8.1.7), the default behavior for the ResultSet::getXXXStream() APIs have been modified to comply with the JDBC specification so that they return null values for database null LONG/LONG RAW values. In earlier versions of the 8.1.x JDBC drivers, the default behavior was to return the empty stream for database null values. To restore the earlier JDBC default behavior when using the 8.1.7 drivers, you must use the Java property jdbc.backward_compatible_to_8.1.6. For example, if this Java property is set at the virtual machine runtime, the command:
java -Djdbc.backward_compatible_to_8.1.6 myJavaProgram
causes the 8.1.7 JDBC drivers to return empty streams from calls to ResultSet::getXXXStream().
The jdbc.backward_compatible_to_8.1.6 Java property applies to 8.1.7 JDBC Thin driver and OCI driver.
This section contains these topics:
To migrate successfully, consider the following:
Since release 1.3.0.0.0 of the Migration Workbench includes 8.1.7 dependencies, you can only install it into an 8.1.7 Oracle home or its own home directory. If you have a previous release of Oracle installed on your system, you must install this release of the Migration Workbench into a separate Oracle home. You then need to switch your default Oracle home to point to your previous Oracle installation so that you do not pick up the new Windows NT client dependencies for other applications you may use on the system. Do this using Oracle Home Selector from the Oracle Installation Products program group. In this case, Oracle Universal Installer displays the error message:
Oracle Migration Workbench can only be installed into a new ORACLE_HOME or an existing 8.1.7 ORACLE_HOME.
While launching the Migration Workbench from Windows 95/98, you may obtain the Finished - Shortcut To dialog box containing the following error messages:
Out of environment space Out of environment space Bad command or file name
If you obtain these error messages, do the following as a workaround:
There is a known bug with Java Runtime Environment (JRE) within the JDK 1.1.7 shipped within Oracle. It can cause Oracle Migration Workbench to hang when you are loading the source master database from Sybase. Therefore, upgrade to Sun Microsystems Java Development Kit (JDK) 1.1.8, and relaunch Oracle Migration Workbench. Download JDK 1.1.8 from:
http://java.sun.com/j2se
From the Web site, select the following links and follow the download instructions:
Install the application into the C:\JDK DIRECTORY. Modify the OMWB.BAT file from the %OMWB_HOME%\OMWB\BIN directory by replacing the following section of the path:
%NT_START% %JRE% -classpath "C:\Program Files\Oracle\jre\1.1.7\lib\rt.jar;C:\Program Files\Oracle\jre\1.1.7\lib\i18n.jar;
with
c:\jdk\bin\java -classpath "c:\jdk\lib\classes.zip;
You can install Oracle Migration Workbench by using Oracle Universal Installer included with Oracle8i (Release 3) 8.1.7.
If you are running Windows 95 or Windows 98, restart your system before running Oracle Migration Workbench. Rebooting your system resets the path for the JRE.
To launch Migration Workbench, choose Start > Programs > Oracle - HOME_NAME > Migration Utilities > Migration Workbench.
You can obtain the release notes for Oracle Migration Workbench release 1.3.0 by choosing Help > Release Notes from within the product.
(Bug 1346516) In certain situations when you invoke help within a modal dialog, such as the Capture Wizard, you are unable to navigate or scroll through the help. A workaround is to obtain the help by choosing Help > Contents. You can also cancel out of the wizard or modal dialog to navigate successfully through the help.
This section contains these topics:
(Bug 1417713) The VOLSIZE parameter for the Export utility is not supported on Windows NT. If you attempt to use the Export utility with the VOLSIZE parameter, error LRM-00101 occurs. For example:
D:\> exp system/manager full=y volsize=100m; LRM-00101: unknown parameter name 'volsize' EXP-00019: failed to process parameters, type 'EXP HELP=Y' for help EXP-00000: Export terminated unsuccessfully
(Bug 1321952) Depending on the products that you have installed, a number of Oracle services are started automatically when you restart your Windows NT computer. A user with a non-system account must have local administrative rights to run services on a Windows NT computer.
(Bug 1383522) If you are using Windows NT 4.0 (service pack) SP6a on a Dell GX110, the computer automatically reboots during database creation, either using Oracle Database Creation Assistant or SQL scripts. This problem does not occur on any other type of computer or service pack. This bug has been reported to both Dell and Microsoft.
(Bug 1397927) If you have installed an Oracle database service on Windows 2000, when logging in as SYSTEM user (Local System), with startup mode set to Automatic, it is possible that the Oracle database service starts but the database does not start automatically. The following error message is written to the ORADIM.LOG file in the ORACLE_BASE\ORACLE_HOME\DATABASE directory.
ORA-12640: Authentication adapter initialization failed
It has also been observed that the services like Oracle Enterprise Management Agent, Oracle Enterprise Manager Management Server and Oracle Internet Directory may also fail for the same reason because they cannot connect to the database.
The workarounds for this problem are:
|
|