Release Notes
A68803-01
Library |
| Oracle8i
Enterprise
Edition for Windows NT and Windows 95/98
Release Notes A68803-01 |
|
When you begin to install products a second time after initially
installing using Oracle Universal Installer, (if you choose to perform
a Custom installation) you will see that the products you previously installed
are selected. For example, if you previously installed Oracle Server and
SQL*Plus, those items will be selected in the list of installable products.
To install additional products, select those products, but
do not deselect the products you have already installed. If you
deselect the products you previously installed, they will be deinstalled.
If you reinstall products using Oracle Universal Installer,
reboot your machine after installation.
When deinstalling the database and Net8 server for 8.1.5, the corresponding services are not automatically removed. This will generate event viewer errors when rebooting your computer. To correct this, you must manually remove these entries in the registry. Before you attempt these steps, make sure you know which Oracle home and SID to deinstall. Deleting the wrong home and/or SID service entry could cause major problems with your Oracle environment. Below is an example of removing services. Follow similar steps for each service you want to remove.
1. Start regedit (you can start it at the command prompt by typing C:\regedit, or from the Start menu.)
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
3. Delete Oracle<HOME_NAME>TNSListener.
4. Delete OracleService<SID>.
<HOME_NAME> is the Oracle Home Name you just deinstalled from (such
as: OraHome81)
<SID> is the SID you just deinstalled (such as: ORCL)
1. You must install Microsoft Visual C++ before you
install Oracle AppWizard for Microsoft Visual C++.
See Chapter 1 of the Oracle AppWizard for
Microsoft Visual C++ User's Guide for more information.
2. If Oracle AppWizard for Microsoft Visual C/C++ cannot be loaded successfully, make sure that you have installed Oracle Objects for OLE (OO4O) and that the following directory has been created:
%ORACLE_HOME%\BIN
3. With Windows 95/98, you must reboot your computer after you have installed an Oracle product for the first time.
4. This release works with Microsoft Visual C++ 5.0 and should work with Microsoft Visual C++ 6.0 as well. However, when using version 6.0, selecting or deselecting the following options either has no effect or does not generate the code for that option.
| Option: | Result: |
|
What type of application would you like to create?
If you choose "Document/View
architecture support"
|
Default is selected. Deselect does not take effect because
the
generated MFC-based application must use this architecture.
|
|
What compound document support would you like to include?
If you choose
"Both container and server "
and "Active
document container "
|
You get MSVC 5.0 container and server support. |
|
What do you want your toolbars to look?
If you
choose "Internet Explorer ReBars"
|
Internet Explorer ReBars is not supported in this release. |
|
What style of project would you like?
If you choose
"Windows Explorer"
|
Windows Explorer is not supported in this release. |
You will find several README files included with your products.
Although these release notes contain vital information you
need, other important or interesting information is contained in the 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.
Use the HTML version of your documentation library to access
all of the release notes and README files.
By default the sample .PRE files search for their corresponding
.PC files in the C:\ORACLE\ORA81 directory (where C:\ is the drive that
you are using, and ORACLE\ORA81 represents the location of the Oracle home).
If the Oracle base and Oracle home directories are different on your computer,
you must change the directory path to the correct path.
To change the directory path for a sample .PRE file:
Networking components for releases 7.3 and 8.0 are not included
on the release 8.1.5 CD-ROM. If you need these components, obtain the 8.0.5
Client software (part number A65346 contains the 7.3.4 and 8.0.5 RSFs)
from Oracle Support Services.
Specific topics discussed are:
| Additional
Information:
See the README.NET8 file located in ORACLE_HOME\NETWORK\DOCS for additional information that is not included in the printed documentation. |
Once Oracle8i is installed, Oracle recommends that you use the new Net8 8.1 listener for all of your Oracle databases of Oracle8i release 8.1 and previous releases (such as an Oracle8 8.0 database). Even if you install Oracle 8i on multiple Oracle homes on the same computer, you should only use one listener for all your databases on the same computer.
Additionally, the new Net8 8.1 listener will be set to start automatically
at system reboot. If you intend to use only the Net8
8.1 listener for all of your databases, you should ensure that only
the Windows NT service for the Net8 8.1 listener, as listed in the Windows
NT services control panel, is set to start automatically.
If you must use multiple listeners (such as a Net8 8.0 listener and Net8 8.1 listener) on the same computer, please refer to the Net8 Administrators Guide and Oracle 8i Enterprise Edition Getting Started (Chapter 5) for more information.
If Net8 8.1 listener service is not created during Oracle 8i installation due to conflicts in listening endpoints, you should first resolve the conflicts by changing listener configurations and then start your Net8 8.1 listener by using the listener control program:
From a command prompt:
lsnrctl start <listener_name>
where <listener_name> is LISTENER for typical install or the listener name given during custom install.
This command also creates the NT service for the listener, if the service
does not already exist.
In 8.1.5 three networking tools are included:
When configuring Oracle Names servers with Net8 Assistant, consider the following:
For information on these products please refer to README.wri in
the
ORACLE_HOME\NETWORK\AGENT\DOC directory.
To work around this problem, you may do any of
the followings:
If the registry value is not found, then OLE DB Services is already
disabled.
1. Run Net8 Assistant on each remote node to create LISTENER.ORA on the remote nodes.
2. On each remote node, from the command prompt, issue this command:
A new feature in Oracle8i for Windows NT is support
for Intel ESMA, which allows Oracle8i to access more than the 4GB
of RAM traditionally available to Windows NT applications.
Note: This feature is only available on Intel Pentium II and Pentium
III Xeon 32-bit processors.
Specifically, Oracle8i (in conjunction with Intel's
PSE36 driver) can now allocate substantially more database buffers than
previous releases. Further details are posted at:
http://developer.intel.com/procs/servers/isv/oracle/esma.htm
To take advantage of this support, you must do the following:
1. More than 4GB of RAM must be present in the server on which Oracle8i will run.
2. Windows NT v4.0 Enterprise Edition, Service Pack 3 or later must be installed.
3. The Intel PSE36 driver must be installed and operational. See http://developer.intel.com/vtune/pse36/index.htm for further PSE36 system requirements and for download instructions.
4. USE_INDIRECT_DATA_BUFFERS=TRUE must be present in the INIT.ORA for the database instance that will use the PSE36 driver. If this parameter is not set, then Oracle8i behaves in exactly the same way as previous releases.
5. Set DB_BLOCK_BUFFERS and DB_BLOCK_SIZE as desired for the database. Note that the total number of bytes of database buffers (that is, DB_BLOCK_BUFFERS multiplied by DB_BLOCK_SIZE) is no longer limited to 3GB as was the case in previous releases.
6. The VLM_BUFFER_MEMORY registry parameter must be created and set in the appropriate key for your Oracle home in the Windows NT Registry. This parameter is specified in bytes and has a default of 1GB. When set, this parameter tells Oracle8i how much non-PSE36 memory to use for database buffers. This memory comes from Oracle8i's virtual address space as was the case in previous releases. Setting this parameter to a large value has the effect of using more of Oracle8i's address space for buffers and using less PSE36 memory for buffers. However, since accessing PSE36 buffers is somewhat slower than accessing virtual address space buffers, tune this parameter to be as large as possible without adversely limiting database operations.
For instance, assume that the Oracle8i database is running on a machine with 8GB of RAM, which means that the PSE36 driver has control of 4GB of RAM. If DB_BLOCK_BUFFERS=2500000 and DB_BLOCK_SIZE=2048, then a total of 5GB of database buffers needs to be allocated. If VLM_BUFFER_MEMORY is set to 1GB, then 1GB of buffers come from the Oracle8i virtual address space and 4GB come from the PSE36 driver. If you set VLM_BUFFER_MEMORY to 500MB, an error occurs at startup because there is not 4.5GB of memory available to the PSE36 driver for database buffers. Likewise, if you set VLM_BUFFER_MEMORY to 3GB, an error occurs because the Oracle8i address space is limited to 3GB 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 is set, the fewer connections and memory allocations will be possible for Oracle8i. The lower VLM_BUFFER_MEMORY is set, the slower the performance will be.
7. Once these parameters are set, the Oracle8i database can be started up and will function exactly the same as before except that more database buffers are available to the instance. In addition, disk I/O may be reduced since more Oracle data blocks can be cached in the SGA. If out of memory errors occur during the startup sequence, verify the following:
Net8 Assistant and Net8 Easy Config (and Oracle Database
Configuration Assistant and Oracle Data Migration Assistant for servers)
require monitors displaying at least 16 colors.
If your monitor displays less than 16 colors, these assistants
will not start.
An error occurred while upgrading your Oracle database. Check the log files to determine if the upgrade was successful.If you receive this message, do the following:
7. While migrating
or upgrading your Oracle database to release 8.1.5, if your rollback segments
are not large enough, you may receive one of the following errors:
ORA-01628; max # extents (number) reached for rollback segment segment_name
ORA-01562; failed to extend rollback segment number segment_number
If you receive one of these errors during migration, use
one of the following commands to increase your rollback segment size:
alter rollback segment segment_name storage(maxextents
number);
alter rollback segment segment_name storage(maxextents unlimited);
If you use Oracle Database Configuration Assistant to create
a new database in a new multiple Oracle home, the LISTENER.ORA file located
in ORACLE_HOME\NETWORK\ADMIN is updated with the SID information.
Also a new TNS entry is generated in the TNSNAMES.ORA file located in ORACLE_HOME\NETWORK\ADMIN.
Users must have NT administrative privileges in order to create an Oracle8i database. If the Oracle Database Configuration Assistant is run from an account that is not part of the Administrator group, then the tool exits without completing the operation.
Sometimes, when Oracle Universal Installer launches Oracle Database Configuration Assistant, the installer continues to wait even after migration is completed. In these instances, Oracle Database Configuration Assistant has finished, yet the buttons in Oracle Universal Installer remain grayed out. If this happens, select the tool from the list in the OUI, and then click the Stop button. OUI may indicate that the tool has failed, but if the tool completed successfully, you may ignore the display.
The following two errors are sometimes seen by users. They are both harmless, and DBCA works properly after these exceptions are noted:
1. java.lang.NullPointerExcetption: invalid peer
at
sun.awt.windows.WWindowPeer$FocusOnActivate.dispatch(WWindowPeer.java:100)
After release 8.1.5, all remaining Server Manager text and
examples will be replaced with SQL*Plus equivalents. Although Server Manager
will continue to be shipped with 8.1.x releases, Oracle Corporation
strongly recommends that you migrate from Server Manager to SQL*Plus as
soon as possible.
When migrating to SQL*Plus, be aware of the following syntax differences:
The preceding SQL*Plus commands and character usages are fully covered in the SQL*Plus User's Guide and Reference.
ub4 cb
with
unsigned long cb
ub4 cb;
if (db->GetImageStream(bl, buf, sizeof(buf), offset, &cb))
System.out.println("Enter column Name");System.in.read(byteArray);columnName = new String(byteArray);strBuffer = new
StringBuffer (columnName.substring(0,columnName.indexOf("\n")));
In: <ORACLE_HOME>\ord\aud\demo\demoProgram.javaReplace this line: audioObj.setBindParams (tableName, columnName, dataCondition);With: audioObj.setBindParams ("TAUD", "aud", "n=1");
Replace: videoObj.setBindParams (tableName, columnName, dataCondition);
With: videoObj.setBindParams ("tvid", "vid", "n=1");
When using SQL*Loader to direct load an Index-Organized Table,
you may receive an internal error if the table has an Overflow segment.
Select start->programs->networker group->networker administrator to start the LSM Administrator GUI.Click the set up server button, and set the parallelism field to the number of tape devices you have. Then, click the devices button. For each tape device listed, select it with the right mouse button, select edit, and set the target sessions field to 1.
C:\win32app\nsr\applogs\dmo.messages
C:\win32app\nsr\logs\daemon.log
C:\win32app\nsr\logs\messagesOn 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.
2. In 8.1.5, the rman DUPLICATE DATABASE command is not supported on Windows NT.
3. Backups to the LSM fail if the DB_DOMAIN INIT.ORA parameter is not set. To backup to the LSM, you must set the DB_DOMAIN INIT.ORA parameter.
4. On Windows NT, starting with version 8.1.6, Oracle will apply additional
transformations to filenames entered by the user. Such files include
control files, data files, online and archived redo logs used by the Oracle
server, and datafile copies and on-disk backup pieces used by Recovery
Manager. These transformations are collectively referred to as 'file
name normalization'.
In versions 8.1.5 and previous, the only transformation applied
to user-entered filenames was that they were converted to uppercase.
SQL commands that reference a filename, such as the 'alter database rename file' command may specify file names in any format, and they will be recognized.
If you use recovery manager, and use a recovery catalog database, then
the filenames stored in the recovery catalog must be changed. Oracle will
provide an upgrade mechanism for the recovery catalog.
Please note the following changes to Chapter 4 of the Oracle COM Automation Developer's Guide for Windows NT:
Do not store database files on a compressed drive.
Doing this can result in write errors, as well as decreased
performance.
In order to use this MMC-based tool, you must install Microsoft Management Console 1.0 or 1.1 (1.1 is recommended) and HTML Help 1.2. They are available for download from Microsoft Corporation's website.
Updated 8.1.5 ODBC drivers are available for download via
the web. Please check http://www.oracle.com (type ODBC in the search
field on Oracle's Home page, then choose the drivers you require) for the
latest version of the ODBC driver from Oracle.
(Bug 380655) If you insert new records into a form block,
and then attempt to access those rows to update them (internally by ROWID,
using the tool) before the rows have been requeried within the block, Oracle
attempts to lock the rows for update and fails with:
'FRM-40501: ORACLE error:
unable to reserve record for update or delete'.
The workaround is to requery the rows before attempting to
update them.
A patch for SQL*Forms and Developer/2000 is also available
to fix this bug. The patch is included in the 8.1.5 release for most common
platforms, and is also available from Oracle Support Services.
The patches for this issue are located at the top-level of
the server installation area in a directory called patches. In this
directory is a sub-directory named for the above bug number, within which
can be found platform-specific versions of the patch, and installation
instructions for each platform.
In rare situations, some users may want to correct serious system problems by completely removing Oracle products from their system. This is not recommended as an easy way to fix problems, especially common ones. Only create a Clean Machine as a last resort, and only if you want to remove all Oracle products from your system. Complete the following steps to create a Clean Machine.
Note: The following Clean Machine instructions assume an OFA (Optimal Flexible Architecture) structure.
Warning: This will remove all Oracle products, Oracle
services, and Oracle registry entries from your computer.
2. Using regedit (at the command prompt, type regedit), go to HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE and delete the ORACLE key.
3. Delete HKEY_LOCAL_MACHINE\SOFTWARE\odbc.
4 Open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services, and remove all keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services that begin with ORACLE.
7. From the Control Panel, open System.
8. If JRE was installed by Oracle, remove the %ORACLE_HOME%\BIN path and the JRE path. For example, you may see a path similar to this one: C: \ORACLE\ORA81\BIN;G: \Program Files\Oracle\jre\1.1.7\bin. Go to Start > Control Panel > System > Environment tab. Click on the system variable path and modify the path.
9. Delete Icons from <system_drive>: \Winnt\Profiles\All Users\Start Menu\Programs\Oracle - <HOME> and <system_drive>: \Winnt\Profiles\All Users\Start Menu\Programs\Oracle Installation Products. Where <HOME> is the previous HOME name.
10. Delete <system_drive>: \Program Files\Oracle (from the Windows NT Explorer or from the command prompt).
11. Reboot your computer.
12. Delete all ORACLE_BASE directories (You can find the Oracle homes listed in HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ORACLE_HOMES).
3. Delete HKEY_LOCAL_MACHINE\SOFTWARE\odbc.
4. Edit your AUTOEXEC.BAT file and remove your %ORACLE_HOME%\bin and JRE paths from the path setting.
5. From the Windows Explorer (or from the command prompt), delete the Oracle directory (Oracle Base).
6. Delete <system_drive>: \Program Files\Oracle (from the Windows NT Explorer or from the command prompt).
7. Delete Icons from <system_drive>: \Windows\Start Menu\Programs\Oracle - <HOME> and <system_drive>: \Windows\Start Menu\Programs\Oracle Installation Products. Where <HOME> is the previous HOME name.
|
Copyright © 1999 Oracle Corporation. All Rights Reserved. |
|