Release 8.0.6 for Windows NT
A69516-01
 Library |
 Product |
| Oracle8 Enterprise Edition Release Notes Release 8.0.6 for Windows NT A69516-01 |
|
March 14, 2000
Part No. A69516-01
These Release Notes provide important last minute information not included in the documentation set. Topics include:
This section contains important last minute information not included in the online Release Notes. All other sections in this printed Release Note are available in the online Release Notes. Addendum topics include:
Oracle for Windows NT Performance Monitor is not installed in the Typical installation option. This product cannot co-exist with Oracle Data Gatherer (a component of Oracle Intelligent Agent) on the same computer. If this product is installed using the Custom installation option, please disable the Oracle Data Gatherer service in the Windows NT service control panel.
The 805.DLLs located on the release 8.0.6 CD-ROM are functionally different from the 805.DLLs on the release 8.0.5 CD-ROM. However, these two sets of similarly named .DLLs can co-exist in the same environment as long as they do not reside in the same Oracle home.
The 20th September 1999 virus definition update for Norton AntiVirus may categorize EMPMIX.EXE as a file infected with "Bloodhound.Unknown" virus. The executable is automatically moved into a quarantine area. This causes Oracle Installer to report that EMPMIX.EXE is not found during installation. This is an error on the part of Symantec. The Symantec AntiVirus Research Center has confirmed this is a false positive.
Oracle Corporation recommends that you contact Symantec to obtain the latest version of Norton AntiVirus to avoid this problem.
The Oracle SNMP Agent is not installed if the Windows NT SNMP service is running. If the Windows NT SNMP service is running, you must stop it, configure it for manual startup, and then install Oracle SNMP Agent through the Custom installation option.
The STRTORCL.ORA file contains the Oracle8 database INTERNAL password in plain text. It is critical that the permissions on this file are set appropriately so that it can only be accessed by authorized database system administrators. This file is used to automatically start up the database when Windows NT boots, and it is possible that one of these files will exist for each database instance created on the computer.
The Oracle Installer help files that are accessed from the Software Asset Manager do not specifically provide information for installation on an Windows 98 operating system. For example, the Oracle home help screen does not mention that the default directory for Windows 98 products is \ORAWIN98. Nonetheless, this product is certified for use on Windows 98 and you should follow the help instructions provided for Windows 95 users to the extent these instructions are relevant.
In the online Release Notes in the section "Installing on a Cluster Drive" in the second paragraph it states, "Advanced users using Oracle on cluster drives must refer to their Oracle Fail Safe or Oracle Parallel Server documentation before attempting installation".
The above statement is incorrect regarding Oracle Fail Safe. Oracle Fail Safe does not support any installation of Oracle on a cluster drive.
The Oracle8 database has been tested against Windows 2000 Release Candidate 1, but because the operating system is a Beta version there may be unexpected problems. Oracle Corporation does not recommend that production databases be deployed on this operating system version.
Install Oracle8 Enterprise Edition or Oracle8 only on a disk that is private to and exclusively owned by the installation system (for example, the system disk). Unless you have specific reasons to do so and understand the risks involved, do not install Oracle on a disk that could be owned or mounted by more than one system.
Advanced users using Oracle on cluster drives must refer to their Oracle Fail Safe or Oracle Parallel Server documentation before attempting installation.
Installation events are not logged to ORACLE_HOME\ORAINST\ORAINST.LOG by default in the version of Oracle Installer that ships with release 8.0.6. Installation events are only logged to ORAINST.LOG if this option is turned on during Custom installation.
To enable logging of installation events:
The Software Asset Manager window appears.
The Option dialog box appears.
Once Log Installer Actions is enabled, installation events are logged to ORAINST.LOG during all subsequent Custom installations until the option is explicitly turned off.
Installation events are not recorded for Typical installations.
The SPAWN command is not supported on Windows Platforms.
In Chapter 2, "Building Pro*COBOL Applications" of Pro*COBOL Precompiler Getting Started for Windows NT and Windows 95/98 replace the sections "Fujitsu Compiler", "MERANT Micro Focus Compiler", and "The PROCOB_DFLT Configuration Parameter" with the following sections.
Also, replace the "Using Fujitsu COBOL PROGRAMMING-STAFF" section with "Using Fujitsu COBOL Project Manager" in these Release Notes.
The sample directories for release 8.0.6 and release 1.8.28 contain a batch file called FJMAKEIT.BAT.
For release 8.0.6, this batch file does the following:
procob80 iname=%1.pco ireclen=132 maxliteral=160 comp5=yes cobol32 -M %1.cbl link %1.obj f3bicimp.lib libc.lib kernel32.lib user32.lib /out:%1.exe ORACLE_HOME\pro80\lib\sqllib80.lib
For release 1.8.28, this batch file does the following:
procob18 iname=%1.pco ireclen=132 maxliteral=160 comp5=yes cobol32 -M %1.cbl link %1.obj f3bicimp.lib libc.lib kernel32.lib user32.lib /out:%1.exe ORACLE_HOME\pro18\lib\sqllib80.lib
To build the sample programs, run this batch file with any sample file. Do not provide the file extension. For example:
FJMAKEIT sample1
The sample directories for release 8.0.6 and release 1.8.28 contain a batch file called MAKEIT.BAT. For release 8.0.6, this batch file does the following:
procob80 iname=%1.pco ireclen=132 cobol %1 /anim /litlink makesyn "COMP-5" = "COMP"; cbllink %1 /M%1 ORACLE_HOME\pro80\lib\sqllib80.lib
For release 1.8.28, this batch file does the following:
procob18 iname=%1.pco ireclen=132 cobol %1 /ganim /litlink makesyn "COMP-5" = "COMP"; cbllink %1 /M%1 ORACLE_HOME\pro18\lib\sqllib80.lib
To build the sample programs, run this batch file with any sample file. Do not provide the file extension. For example:
MAKEIT sample1
The PROCOB_DFLT configuration parameter indicates which release of Pro*COBOL is started when you use the PROCOB command. There are two valid values: PROCOB80 and PROCOB18.
The value of PROCOB_DFLT depends upon which installation of Pro*COBOL is the most recently installed.
Programs generated by Pro*COBOL can be compiled and executed from within Fujitsu COBOL Project Manager.
To avoid potential inconsistencies when calling routines in the Oracle libraries, use the "COMP5=YES" option. This step is required because binary numbers for COBOL BINARY/COMP data are stored in Big Endian format. Oracle libraries expect binary numbers to be stored in Little Endian format (machine format).
To debug the application using the Interactive Debugger "WINSVD" when the COBOL application is compiled, the compiler option "TEST" must be selected.
When you click Build/Rebuild, COBOL Project Manager generates the executable and WINSVD debug information.
After building the application, you can debug the application using the Interactive Debugger "WINSVD". To start "WINSVD", choose Debug from the Tools menu of COBOL Project Manager.
When using SQL*Loader to direct load an Index-Organized Table, you may receive an internal error if the table has an Overflow segment.
Specific topics discussed are:
The Legato documentation is included on the CD-ROM in the LEGATO\DOCS directory. The Legato Storage Manager Administrator's Guide is not included in the Oracle online documentation library. It is included in a file named README.TXT in the LEGATO\DOCS directory of the CD-ROM.
In the Japanese version of LSM 5.5, the following log files are written in UTF8 format:
C:\win32app\nsr\applogs\dmo.messages C:\win32app\nsr\logs\daemon.log C:\win32app\nsr\logs\messages
On a Japanese version of Windows NT running Japanese LSM 5.5, you must run the following command at the command prompt to read one of these UTF8 log files:
nsrcat -n < file_name
Here, file_name is the appropriate pathname for the specific log file, such as:
C:\win32app\nsr\applogs\dmo.messages
If you use Legato Storage Manager, and have more than one tape device on your system (Legato Storage Manager supports a maximum of 4), ensure that the following settings are made in the LSM Administrator GUI:
Specific topics discussed are:
To update to a newer version of the LSM Administrator GUI on your Windows NT client system:
To remove the LSM Administrator GUI from your Windows NT client system:
If you plan to use Legato Storage Manager on the server to back up to tape, and want to administer the Legato Storage Manager server from a Windows NT client system, you need to install the LSM Administrator GUI software on the Windows NT client system.
To install the LSM Administrator GUI on your Windows NT client system:
For more information on using the LSM Administrator GUI, refer to the Legato Storage Manager README for Windows NT in the LEGATO\DOCS\README.TXT file.
Do not store database files on a compressed drive.
Doing this can result in write errors, as well as decreased performance.
You will find several README files included with your products. Other important or interesting information is contained in these README files.
README files may be included for products you did not purchase or license. Their presence does not mean that you can install and use those products.
At the top level of the CD-ROM directory there is a file called READMES.HTM. This file contains links to all of the READMES on the CD-ROM. This is a convenient point from which to review READMES before you install products.
If you want to view the online documentation on your product CD-ROM, you can read the documentation in HTML format. Go to the \DOC directory and select the INDEX.HTM FILE or PRODUCTS.HTM file to view the online documentation. If you select the INDEX.HTM file, Oracle Information Navigator is launched along with the documentation.
The PDF (Adobe Acrobat) version of the documentation included on your product CD-ROM is compressed to save space. To view the PDF documentation, save the compressed PDF file located in the \PDFDOCS directory to a separate directory on your hard drive. Oracle Corporation recommends that you save the file in the ORACLE_HOME\PDFDOCS directory. Launch the self-extracting compressed file to extract the PDF files. You can access the individual PDF guides through the INDEX.PDF file.
If you decide to install Oracle documentation using Oracle Installer, only the HTML documentation is installed to ORACLE_HOME\DOCS.
If you have also installed the PDF documentation to ORACLE_HOME\PDFDOCS, you can access the PDF documentation from the HTML documentation libraries.
Net8 Assistant, Net8 Easy Config, and Oracle Intype File Assistant (and Oracle Database Assistant and Oracle Data Migration Assistant for servers) require monitors displaying at least 16 colors.
Oracle Corporation recommends that you configure Oracle8 database files, directories, and registry settings to allow only authorized database administrators to have full control. The following sections describe how to perform these tasks:
The Oracle8 database uses files to store database data, backup data, log information, and so on. To do this, the Oracle8 database process runs under a security account. This security account (the Windows NT LocalSystem account called SYSTEM) includes the ability to create and access these files. The security account is assigned to the service that the Oracle8 database uses (in the Control Panel). This account requires full file system permissions to create, read, write, delete, and execute files.
To ensure that only authorized users have full file system permissions:
Oracle Corporation recommends that you remove write permissions from users who are not Oracle8 database system administrators in the HKEY_LOCAL_MACHINE\SOFTWARE\Oracle key of the Windows NT registry.
To remove write permissions:
The Registry Key Permissions dialog box appears.
In release 8.0.5, NT Backup Manager and NT Recovery Manager were Oracle tools that enabled you to perform database backups to disk or tape. Both tools were automatically installed with the Oracle8 Utilities.
These tools are not available on the 8.0.6 CD-ROM. They are no longer supported. Oracle Corporation recommends that you use third-party backup and recovery tools.
Your CD-ROM includes Oracle8 Context Cartridge Workbench release 2.4.5. However, in Oracle8i release 8.1.5, an improved version of ConText is included in the interMedia product. The new version is more deeply integrated in the Oracle database, providing better performance, scalability, and ease-of-use.
Oracle Corporation recommends that potential Context customers use the new interMedia Text 8.1.5 product.
In particular, the Workbench has been replaced by Oracle interMedia Text Manager, which is a Java application integrated with Oracle Enterprise Manager. Contact Oracle Client Relations to order interMedia and Oracle8i release 8.1.5.
Once you have installed the Oracle8 database and the ConText Cartridge using either the Typical or Custom database creation option during installation, you must subsequently enable the ConText Cartridge demo using Oracle Database Assistant.
While the Custom option offers you the opportunity to enable the demo during installation, the Enable demo check box is disabled. This is a bug. The workaround is to enable the demo by using Oracle Database Assistant after you have completed installation as described below.
To enable the ConText Cartridge demo:
Oracle Database Assistant appears.
"Oracle Data Migration Assistant migrates from release 7.1.3.3.6 or later to release 8.0.6."
This statement is incorrect. The correct statement is:
"Oracle Data Migration Assistant migrates from release 7.3.4 or later to release 8.0.6."
The last page of the Oracle Database Assistant does not contain a help screen. This is the correct implementation of the product.
After Oracle Migration Assistant for Microsoft Access completes migration, you should check that the migration was successful. To check that the migration was successful, look at the Summary information. You can choose to view reports describing specific migration information.
Do not use the following sequence of commands in Oracle Migration Assistant for Microsoft Access. If you do, the assistant crashes.
Some servers, such as Novell, do not support long file names. If the Oracle software CD-ROM is mounted on a drive of a Novell server, some of the directory paths on the CD-ROM, such as the JRE location, may not be recognized and the installation will fail. You need to mount the CD-ROM on a system that supports long file names, such as a Windows NT workstation.
Your documentation library contains guides with version numbers of 8.0.4, 8.0.5, and 8.0.6. This is because some guides did not require updating for releases subsequent to 8.0.4 (for example, the generic documentation set did not require updates since 8.0.4). Please be assured that the latest documentation is on your CD-ROM.
In Oracle8 Enterprise Edition Getting Started for Windows NT in the chapter "Creating a Database", in the section "Using ORADIM80 to Administer the Oracle Instance" it is stated that ORADIM80 can be used to start and stop services and/or instances from the MS-DOS command prompt. This is incorrect. ORADIM80 can only be used to start and stop services from the MS-DOS command prompt. This is a fix for bugs 986272 and 986261.
This section indicates any sections in the online documentation libraries that are incorrect.
For example, to access the file SYSTEM01.DBF in the directory C:\ORACLE\ORA81\ORADATA\ORCL on the shared server ARGON, you reference the file as:
\\ARGON\ORACLE\ORA81\ORADATA\ORCL\SYSTEM01.DBF
should be corrected to:
For example, to access the file SYSTEM01.DBF in the directory C:\ORANT\DATABASE on the shared server ARGON, you reference the file as:
\\ARGON\ORANT\DATABASE\SYSTEM01.DBF
|
|
 Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|