| Oracle® Database Release Notes 11g Release 2 (11.2) for Microsoft Windows Part Number E10842-02 |
|
| View PDF |
| Oracle® Database Release Notes 11g Release 2 (11.2) for Microsoft Windows Part Number E10842-02 |
|
| View PDF |
Release Notes
11g Release 2 (11.2) for Microsoft Windows
E10842-02
March 2010
This document contains important information that was not included in the platform-specific or product-specific documentation for this release. This document supplements Oracle Database Readme.
This document may be updated after it is released. To check for updates to this document and to view other Oracle documentation, refer to the Documentation section on the Oracle Technology Network (OTN) Web site:
http://www.oracle.com/technology/documentation/
This document contains the following topics:
The latest certification information for Oracle Database 11g Release 2 (11.2) is available on My Oracle Support (formerly OracleMetaLink) at:
In addition to the items listed in Section 2, "Features Not Available or Restricted in This Release," in Oracle Database Readme the following products or features are not supported:
Windows Automatic Storage Management-based and Oracle Notification Service-based Fast Application Notifications for IPv6.
Oracle RAC, Oracle Clusterware, Oracle Restart, and Oracle ASM are not supported on Windows 32-bit.
Pro*COBOL is not supported on Windows 7 and Windows Server 2008 R2 x64 operating systems. It will be certified when a supported COBOL Compiler is available on these operating systems.
Database Smart Flash Cache Support
Database Smart Flash Cache is supported on Solaris and Oracle Enterprise Linux only.
Oracle Automatic Storage Management Cluster File System and Oracle Automatic Storage Management Dynamic Volume Manager Support
Oracle Automatic Storage Management Cluster File System and Oracle Automatic Storage Management Dynamic Volume Manager are supported only on Oracle Enterprise Linux 5.0 and Red Hat Enterprise Linux 5.0 on Linux x86 and Linux x86-64. On Windows x64, Oracle ACFS and Oracle ADVM are only supported on Windows Server 2003 x64 and Windows Server 2003 R2 x64.
Oracle SQL Developer Support
Oracle SQL Developer 1.5.5 that ships with Oracle Database 11g Release 2 (11.2) is not supported on Windows x64.
Workaround:
Download Oracle SQL Developer 2.1 or later from the Oracle Technology Network (OTN) Web site:
http://www.oracle.com/technology/products/database/sql_developer/index.html
This issue is tracked with Oracle bug 9181397.
Refer to the installation guides for additional preinstallation requirements.
Review the following sections for information about issues that affect Oracle Database installation, configuration, and upgrade:
Upgrading Windows 32-Bit to Windows 64-Bit Using Oracle OLAP
Enabling Oracle Automatic Storage Management Dynamic Volume Manager Volumes
Automatic Storage Management Service Is Disabled After System Restart
Oracle MTS Recovery Service Issue When Installing Oracle RAC
Root Script Status Not Displayed with Oracle Grid Infrastructure
For late-breaking updates and best practices about preupgrade, postupgrade, compatibility, and interoperability discussions, refer to Note 785351.1 on My Oracle Support (formerly OracleMetaLink) (https://support.oracle.com/) that links to "Oracle 11gR2 Upgrade Companion" page.
The Microsoft Visual C++ 2005 SP1 Redistributable Package is automatically installed with the Oracle Database 11g Release 2 (11.2) software. Do not remove this package from the Add or Remove Programs interface in the Control Panel.
To upgrade Windows 32-bit to Windows 64-bit using the Oracle Online Analytical Processing (OLAP) option, refer to Note 352306.1 on My Oracle Support (formerly OracleMetaLink) at:
Oracle Database 11.2 supports Oracle SID having an underscore but it is not compatible with the earlier client releases with a bequeath connection. The issue affects any Oracle Database Client 11.1.0.7 or earlier client, when connecting to the database over a bequeath connection. This includes all OCI clients and Oracle Enterprise Manager agents that monitor the database.
Workaround:
Use only alphanumeric characters including hyphens for Oracle SID or connect to the database using TCP connection.
This issue is tracked with Oracle bug 7611024.
Oracle Automatic Storage Management Dynamic Volume Manager volumes are typically enabled automatically. Disk groups that are listed in the init.ora file for Oracle Automatic Storage Management (Oracle ASM) have all volumes automatically enabled during disk mount.
For volumes in disk groups that are mounted manually, you must also manually enable the volumes in that disk group before using them.
In Oracle Restart, to load Oracle Automatic Storage Management Cluster File System drivers during system initialization as an Administrator, you must manually reload the three drivers associated with Oracle ACFS: Oracle OKS, Oracle ADVM and Oracle ACFS.
This issue is tracked with Oracle bug 7700977.
After an installation, the Automatic Storage Management Startup Type is set to Manual. Hence, Automatic Storage Management does not start when you restart the system.
Workaround:
In Services Control Manager, change the Startup Type to Automatic.
A new Oracle Database release does not update OCI Instant Client version.
Solution:
Use the OCIClientVersion feature to determine the client version instead of checking the dll version number.
This issue is tracked with Oracle bug 8372062.
When you upgrade from Oracle database release 9.2 to release 10.2, and then upgrade to release 11.2, the database upgrade fails with an ORA-00600 error.
This issue is tracked with Oracle bug 8668823.
When you use Oracle Universal Installer to upgrade Oracle Clusterware 11g Release 1 (11.1.0.6), or Oracle Clusterware 11g Release 1 (11.1.0.7) to Oracle Clusterware 11g Release 2 (11.2), you may receive the following error:
[INS-40406] There is no previous version of grid software detected on the system.
Workaround:
While upgrading a node, for instance a remote node, other than the one on which Oracle Clusterware 11g Release 1 (11.1.0.6) was installed, the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\inst_loc may not be set correctly.
Ensure that you manually set the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\inst_loc to the location of the Oracle Inventory directory of the node on which you are performing the upgrade installation.
This issue is tracked with Oracle bugs 9210861 and 6527941.
If the EMVLOGGER.EXE process is terminated at the operating system level, it fails to restart automatically because of an existing log file.
Workaround:
Remove the emvlogger log file at Grid_home\evm\log\*_evmlogger.log, where Grid_home is the location of your Oracle grid infrastructure installation. The EVMLOGGER.EXE process should automatically restart after approximately one minute.
This issue is tracked with Oracle bug 9260650.
Manually shutting down an Oracle database or stopping an Oracle ASM instance using CRSCTL utility or SQL*Plus does not stop its associated Windows service.
Workaround:
Using the Services management console, manually stop the Windows service associated with the Oracle instance. You can access the Services management console through the Control Panel, or you can stop the Oracle database service, or Oracle ASM service directly using the following commands:
net stop OracleServiceSID net stop oracleASMServiceSID
This issue is tracked with Oracle bug 9178097.
When attempting to upgrade CRS or Oracle ASM to 11.2 release using the Automatic Storage Management Configuration Assistant (ASMCA), the upgrade succeeds, but the configuration changes made to the Agents on a remote host fail to reload. As a result, Oracle Enterprise Manager Grid Control and Database Control cannot monitor the Oracle ASM and CRS targets.
Workaround:
Manually reload the remote agents after the upgrade using the following command:
emctl reload agent
This issue is tracked with Oracle bug 9398380.
In an Oracle RAC database installation, Oracle MTS Recovery Service on the remote nodes does not have the correct host name registered for string variable HOST under registry key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Protid_0. This variable contains the name of the host from where the installation was performed instead of the name of the local host. This registry variable is used by COM+ applications to pass information to Oracle databases so that they can connect back to the Windows computer if the database needs to resolve in-doubt COM+ transactions. The incorrect host name that is registered can cause transaction recovery issues.
Workaround:
To fix this, use Registry Editor (regedit) on the remote Windows system and look under the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Protid_0
The string-type values for the following key must be set correctly:
Name: *Host* Type: REG_SZ Data: << the name of the host-machine e.g. myhost@example.com <mailto:myhost@example.com>>>
This key must contain the host name of the system on which the registry key exists.
This issue is tracked with Oracle bug 9483665.
When running rootcrs.pl or roothas.pl to configure, upgrade, or deconfigure Oracle grid infrastructure, the script does not display the success or failure status in the command window.
Workaround:
None. Check the log file generated at the following location to know the status of the script:
Grid_home/cfgtoollogs/rootcrs_host_name.log
This issue is tracked with Oracle bug 9473262.
While installing or upgrading Oracle grid infrastructure for a cluster, you might encounter an issue if non-ASCII characters are used in network connection names for some languages, such as French.
Workaround:
Do not use non-ASCII characters in network connection names.
This issue is tracked with Oracle bug 9472214.
The following sections contain information about issues related to Oracle Database 11g and associated products:
The Oracle Wallet Manager screen images and icons do not display clearly, and Oracle Wallet Manager help does not work.
Workaround:
Add owm-images.jar and owm_help.jar to the CLASSPATH variable in the owm.cl file so that the screen is displayed clearly and the Oracle Wallet Manager help works correctly.
Perform the following steps:
In the Start menu, right-click the OWM icon and select Properties. This gives you the location of the owm.cl file.
Open the owm.cl file using a text editor.
Add the owm-images.jar and owm_help.jar files to the CLASSPATH variable in the owm.cl file.
Note:
The path of the.jar should be same as of owm-3_0.jar. Typically, the owm-images.jar and owm_help.jar files are located in C:\app\user-name\product\11.2.0\ORACLE_HOME\owm\jlib\.Save the changes to the owm.cl file.
This issue is tracked with Oracle bug 7506415.
Deleting nodes using Oracle Enterprise Manager Database Control is currently not supported. However, you can manually delete the nodes. See the following for more information:
Chapter 3, "Cloning Oracle Clusterware to Create a Cluster" and Chapter 4, "Adding and Deleting Cluster Nodes on Windows Systems" in the Oracle Clusterware Administration and Deployment Guide
Chapter 10, "Adding and Deleting Nodes and Instances on Windows Systems" in the Oracle Real Application Clusters Administration and Deployment Guide
.NET Stored Procedures run fine with .NET Framework 2.0 and with .NET Framework 2.0 SP1. Running a .NET Stored Procedure with .NET Framework 2.0 SP2 causes an access violation in extproc.exe.
Workaround:
Install Microsoft hotfix KB974168.
Oracle RAC patch from Oracle Enterprise Manager Database Control is not supported.
Workaround:
Run OPatch to apply patches to Oracle RAC databases.
This issue is tracked with Oracle bug 9128255.
Oracle Management Service provides incorrect reverse ping command with Oracle Enterprise Manager Database Control. The emoms.properties file shows:
emdrep.ping.pingCommand=ping <hostname>
Workaround:
Change the property in the emoms.properties file to:
ping -n 3 -w 30000 <hostname>
Note:
On all the computers using IPv6, you must specifyping6 command (or an equivalent IPv6 command) instead of ping command.This issue is tracked with Oracle bug 9211800.
The Opatch tool shipped with Oracle Database 11g Release 2 fails while applying online patches on Windows systems.
Workaround:
Opatch tool version 11.2.0.1.1 is available on My Oracle Support as Patch 6880880 for Oracle Database 11g Release 2. Download and install Opatch Tool version 11.2.0.1.1 before applying online patches on Windows systems.
To list the database instances patched by an online patch, run the opatch lsinventory -details command. Ensure that you run the opatch rollback command instead of opatch disableOnlinepatch command to disable and remove an online patch from the final database instance in a node. The disableOnlinepatch command disables the online patch, but does not remove it. To remove the online patch in a disabled state, use -no_sysmod flag with Opatch rollback command only when opatch lsinv -details show no instances patched with it. For example, use opatch rollback -id 1234 -no_sysmod only when opatch lsinv -details show no instances patched for 1234.
This issue is tracked with Oracle bugs 8843060 and 9440270.
When the Oracle ACFS mount registry resource or the Oracle ACFS individual file system resource mounts an Oracle ADVM volume on a drive letter, the drive is not visible in Windows Explorer. This only affects the visibility of the drive letter in Windows Explorer; the volume is mounted and fully accessible using the command line, and is visible using the acfsutil.exe utility.
Workaround:
You must log out and log back in to view the driver letter in Windows Explorer.
This issue is tracked with Oracle bug 9343876.
The Microsoft handle utility is required for proper operation of Oracle ACFS High Availability resources managed by Oracle Clusterware. Oracle Clusterware resources may not shut down properly if this command is not included.
Workaround:
Download the Microsoft Handle utility from:
http://technet.microsoft.com/en-us/sysinternals/bb896655.aspx
After downloading, place the Handle utility in the BIN directory of your Clusterware Home.
Note:
Ensure that the grid home is included in the PATH environment variable for your current session.This issue is tracked with Oracle bug 9349433.
Using the node name instead of an IP address is supported when adding GNS to a cluster, but may fail because the name cannot be resolved.
Workaround:
Ensure that the node name is entered correctly. You can also use the IP address assigned to the node instead of the node name.
This issue is tracked with Oracle bug 9391290.
After installing Oracle grid infrastructure, the default listener does not listen on public addresses. As a result, even though the listener is available, the listener does not service the database or Oracle ASM instances.
Workaround 1:
If you are not using GNS with DHCP, then perform the following steps:
Add the local IP address and host name information to Systemroot%\System32\Drivers\Etc\Hosts.
For example, IP address host name such as 192.0.2.254 dbhost.
Restart the Oracle grid infrastructure listener.
This issue is tracked with Oracle bug 9382523.
Workaround 2:
If you have configured GNS and use DHCP to assign the addresses for the cluster nodes, then configure DHCP so that the IP address assigned to the host name for each cluster node (the public IP address) has a smaller numeric value than the IP addresses assigned for the Virtual IP (VIP) address, GNS VIP address, or SCAN VIP address for a node.
For example, you could use IP addresses in the range of xxx.xxx.xxx.0 – xxx.xxx.xxx.099 for only host IP addresses, and all other IP address assignments must use a value of xxx.xxx.xxx.100 or higher.
This issue is tracked with Oracle bug 9441288.
Starting Oracle tools such as Net Configuration Assistant, Database Configuration Assistant, Database Upgrade Assistant, Net Manager, Oracle Universal Installer, and so on, from shared Oracle home shortcut gives the following error:
Missing shortcut: windows is searching launch.exe
The shortcuts exit following the error.
Workaround:
Start the tools with Administrator privileges.
This issue is tracked with Oracle bug 7525053.
When running the addnode.bat script to add one or more nodes to your cluster, if there was a failure during any installation on any of the new nodes, they are removed from the list of nodes to be adding to the cluster. As a result the updatenodelist command called at the end of the node addition process returns a status of success even if there was a failure in adding a node.
Workaround:
None. Verify that the new nodes are correctly added to the nodelist at the end of addnode procedure. If not, check the addnode logs for any error messages. Correct the problem and repeat the addnode procedure.
This issue is tracked with Oracle bug 9481472.
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.
Oracle Database Release Notes, 11g Release 2 (11.2) for Microsoft Windows
E10842-02
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|