Oracle® Database Release Notes 11g Release 1 (11.1) for Microsoft Windows Part Number B32005-03 |
|
View PDF |
Release Notes
11g Release 1 (11.1) for Microsoft Windows
B32005-03
February 2008
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/
For additional information about this release, refer to the readme file located in the ORACLE_BASE
\
ORACLE_HOME
\relnotes
directory.
Note:
The Database Quick Installation Guides are no longer available in printed format. These documents are available with the media in the same location as the software and on Oracle Technology Network.This document contains the following topics:
The latest certification information for Oracle Database 11g Release 1 (11.1) is available on OracleMetaLink at:
A list of unavailable features and products is available in Section 2, "Features Not Available or Restricted in This Release", in Oracle Database Readme.
Refer to the installation guides for the preinstallation requirements. Following is the additional compiler requirement for Oracle Database:
Pro*C/C++ is also supported with the Microsoft Visual C++ .NET 2002 7.0 and Microsoft Visual C++ .NET 2003 7.1 compilers.
Review the following sections for information about issues that affect Oracle Database installation, configuration, and upgrade:
Adding or Deleting an Instance Using Oracle Enterprise Manager Displays an Error
Error When Installing Oracle Database 11g Enterprise Edition on Windows Vista
Oracle Universal Installer Displays Single Instance Install Option on Oracle RAC
The Prerequisite Checker Deployment Procedure Reports Incorrect Results
Upgrading Oracle Clusterware from Oracle Database 10g (10.x)
Warning Message is Displayed When ORACLE_HOME
Refers to a Non-Existent Directory
Installation, Configuration, and Upgrade Issues on Windows 32-Bit
Installation, Configuration, and Upgrade Issues on Windows x64
An error message is displayed if you add or delete an instance in the following scenarios:
You add or delete an instance using Oracle Enterprise Manager from a new cluster on which you have never installed Oracle
You start the process of adding or deleting an instance from a node other than the one where you initially started the process
The error message displayed is similar to the following error message:
Error -Error getting a return value: The inventory pointer location /var/opt/oracle/oraInst.loc is either not readable or does not exist Operation Failed. Refer logs at ...
Workaround: Complete one of the following procedures to address this issue:
On each node of the cluster, run commands similar to the following:
SYSTEM_DRIVE:> cd CRS_home\oui\bin SYSTEM_DRIVE:> attachhome -silent -local "CLUSTER_NODES={comma_separated_node_list_of_this_cluster}
On each node of the cluster:
Run a command similar to the following command:
SYSTEM_DRIVE:> cd CRS_home\oui\bin
Start Oracle Universal Installer by running the setup.exe
command.
On the Welcome page, click Next.
Exit from Oracle Universal Installer.
Note:
This issue is not observed if you already have an Oracle installation, such as Oracle Database, Oracle Management Agent, and so on, on the node.This issue is tracked with Oracle bug 6603930.
During Automatic Storage Management configuration, the Configure Automatic Storage Management dialog is displayed. The dialog prompts you to enter a new discovery path for discovering Automatic Storage Management disks by clicking Change Disk Discovery Path. On Windows Vista, you cannot use the asterisk (*
) wild card character for the new discovery path. For example, using the C:\\.\ORCLDISK*
path is not supported. You have to provide a comma separated list of disk paths, such as C:\\.\ORCLDISK0,C:\\.\ORCLDISK1,C:\\.\ORCLDISK2
. Additionally, ensure that there are no embedded spaces in the discovery path.
On other Windows operating systems, the asterisk (*
) wild card is supported and handled appropriately in Oracle Universal Installer, during Automatic Storage Management disk selection, and in passing the new discovery path to Oracle Database Configuration Assistant. However, due to a behavioral change in Windows Vista, the selection appears to succeed during Oracle Universal Installer disk selection, but Oracle Database Configuration Assistant fails and displays the Invalid command line argument
message. This is because the Windows Vista command processor (cmd
) expands the wild card character (*
), even when present within a double quoted string in a command line argument. The new discovery path is passed to Oracle Database Configuration Assistant as a double quoted string and as a result it fails.
This issue is tracked with Oracle bug 6373662.
When installing Oracle Database 11g Enterprise Edition on Windows Vista, if you fill in the Oracle home name and click Next, and then click Back because you want to change the Oracle home name, an error message is displayed. If you continue by clicking OK on the error dialog box, the installation will proceed but the prerequisite check will be skipped. This may lead to other errors.
Workaround: Exit the installation process and restart it instead of proceeding through the error dialog box.
This issue is tracked with Oracle bug 6449586.
Nmefwmi crashes on Windows Vista with the following popup message:
nmefwmi.exe has crashed.
or displays a metric collection error on the Network Interfaces metric and Windows Events Log metric with the following message:
Command exited abnormally without any output.
Workaround: Disable the Network metric and Windows Event Log metric temporarily by following these steps:
Network Metric:
Navigate to Host home page.
Click Metric and Policy Settings.
On the Metric Thresholds tab, select All metrics from the View list.
In the Network Interface Combined Utilization row, click the link in the Collection Schedule column.
Click Disable.
Click Continue and then click OK.
This will remove the metric collection error in 5 to 10 minutes.
Windows Events Log Metric:
Navigate to Host home page.
Click Metric and Policy Settings.
On the Metric Thresholds tab, select All metrics from the View list.
In the System row, click the link in the Collection Schedule column.
Click Disable.
Click Continue and then click OK.
This will remove the metric collection error in 5 to 10 minutes.
This issue is tracked with Oracle bug 6596234.
When you run the deployPackages -d
ORACLE_BASE
\
ORACLE_HOME
\ccr\inventory\core.jar
command to remove Oracle Configuration Manager, the following message is displayed:
The batch file cannot be found.
This message indicates that the Oracle Configuration Manager service has been removed. To complete the removal of Oracle Configuration Manager, run the following command
SYSTEM_DRIVE:> rmdir /s/q ORACLE_BASE\ORACLE_HOME\ccr
This issue is tracked with Oracle bug 5982610.
When you run the crssetup.add.bat
batch file to add another node, incorrect port number is registered for the new node.
Workaround: Complete the following procedure to resolve this issue:
After running the crssetup.add.bat batch file, ignore the error messages similar to the following error message:
Starting ONS application resource on (*) nodes1:CRS-0215: Could not start resource 'ora.*.ons'
Use the following command to stop the nodeapps
service on all the newly added nodes:
srvctl stop nodeapps -n node
Use the following command to delete the existing ONS port number registration:
racgons remove_config node:4948
Use the following command to add an ONS port number:
racgons add_config node:remote_port
Use the following command to start the nodeapps service on all the newly added nodes:
srcvtl start nodeapps -n node
This issue is tracked with Oracle bug 6410914.
Oracle Database supports multiple Oracle homes. This means that you can install this release or previous releases of the software more than once on the same system, in different Oracle home directories. This enables flexibility in deployment and maintenance of the database software. For example, it enables you to run different versions of the database simultaneously on the same system, or it enables you to upgrade specific database or Automatic Storage Management instances on a system without affecting other running databases.
You must install Oracle Database 11g into a new Oracle home directory. You cannot install products from one release of Oracle Database into an Oracle home directory of a different release. For example, you cannot install Oracle Database 11g Release 1 (11.1) software into an existing Oracle9i Oracle home directory. If you attempt to install this release into an Oracle home directory that contains software from an earlier Oracle release, the installation fails.
You can install this release more than once on the same system as long as each installation is installed in a separate Oracle home directory.
See Also:
OracleMetalink Note 460054.1 for more details about multiple Oracle home environment issuesIn Oracle Database 11g, the executables for USER_FILTER
should exist in the ORACLE_BASE
\
ORACLE_HOME
\ctx\bin
directory. Therefore, after upgrading an earlier version of Oracle Database to Oracle Database 11g, you need to run the following SQL commands as the SYS
, SYSTEM
, or CTXSYS
user to display the list of USER_FILTER
executables:
SQL> select ixv_value SQL> from ctxsys.ctx_index_values SQL> where ixv_class = 'FILTER' SQL> and ixv_object = 'USER_FILTER' SQL> and ixv_attribute = 'COMMAND';
Copy the displayed executables from the ORACLE_BASE
\
ORACLE_HOME
\bin
directory to the ORACLE_BASE
\
ORACLE_HOME
\ctx\bin
directory.
This issue is tracked with Oracle bug 6269811.
If Oracle Clusterware is installed on servers that have not had previous Oracle installations, and you start to install Oracle RAC on a cluster node other than the node on which you installed Oracle Clusterware, then Oracle Universal Installer displays a single-instance Oracle Database installation screen instead of an Oracle RAC installation screen.
This issue appears when you perform the following procedure, where node_1 is the node on which you install Oracle Clusterware, and node_n is another node in the cluster:
Install Oracle Clusterware from node_1.
After Oracle Clusterware install, start an Oracle RAC database install from node_n.
Oracle Universal Installer displays the Select a Product to Install screen. Select Oracle Database 11g, and click Next.
Oracle Universal Installer displays the Select Installation Method screen with Basic/Advanced Installation options. This is specific to single instance installation. For Oracle RAC installation, the Select Installation Type screen should have been displayed.
Workaround: Continue with the installation by selecting Advanced Installation and clicking Next. Oracle universal Installer displays the Select Installation Type screen. Proceed with the rest of the Oracle RAC installation, as usual.
This issue is tracked with Oracle bug 6527941.
When running Database Upgrade Assistant, registry and service for Oracle Database Enterprise Manager Database Control is not created on the remote node.
Workaround: You must close Service Control Manager window when installing Oracle Clusterware, Oracle Database, and running Database Upgrade Assistant.
This issue is tracked with Oracle bug 6499676.
When doing a rolling upgrade of Oracle Clusterware from earlier version to Oracle Database 11g, the Oracle Universal Installer prerequisite checks displays an error message when checking the status of Oracle Synchronization Service. This is an expected error message.
The message indicates that you must shutdown services on all the nodes. However, you only need to shutdown the services on the node(s) on which you are performing upgrade.
This issue is tracked with Oracle bug 6152450.
Oracle Enterprise Manager, Oracle Net Configuration Assistant, and Oracle Net Manager cannot be used on a Windows Vista computer to configure Oracle Net Naming with Active Directory. Use another version of Microsoft Windows to configure Oracle Net naming with Active Directory at this time.
Active Directory Authenticated Name Lookup does not work from Oracle database clients running on Windows Vista. In a typical Oracle installation, no client-side configuration change is required. However, if Active Directory is configured to disallow anonymous binds for Oracle Net name lookup, Net name lookups from Windows Vista clients fail.
See Also:
Note 459688.1 on OracleMetalink for more information.This issue is tracked with Oracle bug 6249895.
When you run the Prerequisite Checker Deployment procedure from Oracle Enterprise Manager Database Console, the procedure displays that the Check Active Files and Executables check has failed. However, on Windows Vista, the procedure reports that the check has passed.
Workaround: Ignore the result of this check and consider it as failed.
This issues is tracked with Oracle bug 6215909.
When you upgrade Oracle Clusterware from an Oracle Database 10g release (10.x), the OPMD
service is not created.
Workaround: After completing the upgrade process, run the following command from the CRS_home
\bin
directory on each node:
opmd -install
This issue is tracked with Oracle bug 6416092.
ORACLE_HOME
Refers to a Non-Existent DirectoryWhen the ORACLE_HOME
environment variable refers to a directory that does not exist, Oracle Universal Installer displays a warning message about a non-empty home directory when you click Next on the Install Location screen.
This is a benign message that you can ignore and continue with the install. This message is displayed when you have Oracle Database 11g Clusterware installed on the machine.
This issue is tracked with Oracle bug 6160525.
The following are the Windows 32-bit specific issues that affect Oracle Database installation, configuration, and upgrade:
Install Error: The Application Fails to Install Because the MSVCRTD.dll File is Missing
The runcluvfy.bat
File Fails to Run From the Root of the DVD Media
Note:
The issues mentioned in this section are not observed on Windows x64.When installing Oracle Provider for OLE DB on a computer with Oracle Services for Microsoft Transaction Server (OraMTS) version 9.2.0.1.0 installed, the installation process may display the following error message:
Install Error: The application fails to install because the MSVCRTD.dll file is missing. Re-installing the application may fix this problem.
Workaround: If reinstalling the application does not fix this issue, you can perform one of the following actions:
Install OraMTS 11g Release 1
Apply patch 2428356 on OraMTS 9.2.0.1.0
This issues is tracked with Oracle bug 2428356.
runcluvfy.bat
File Fails to Run From the Root of the DVD MediaIf you try to run the runcluvfy.bat
file from the root of the DVD media, it fails to run and displays the following error message(s):
The network path was not found. The system cannot find the path specified. The system cannot find the path specified. The system cannot find the path specified.
Workaround: Run the runcluvfy.bat
file from Oracle Clusterware source location under the DVD_driveletter
:\source\crs\Disk1
directory.
This issue is tracked with Oracle bug 6528709.
The srvctl
utility and Oracle Database Upgrade Assistant fail to start or stop Oracle9i RAC databases after installing or upgrading to Oracle Database 11g Release 1 Windows clusterware. The srvctl
utility displays the following error message:
PRKP-1006 : Failed to shut down cluster database database_name
ORA-01031: insufficient privileges
ORA-01005: null password given; logon denied
ORA-01031: insufficient privileges
ORA-01005: null password given; logon denied
Workaround: Complete the following procedure to resolve this issue:
Run the following commands on each node in Oracle Clusterware:
CRS_home\bin\crsuser add Oracle_92_user_domain\Oracle_92_username CRS_home\bin\crs_setperm ora.node_name.gsd -o Oracle_92_user_domain\Oracle_92_username
From any node, run the following commands for each node configured in the cluster:
CRS_home\bin\crs_stop -f ora.node_name.gsd CRS_home\bin\crs_start ora.node_name.gsd
Note:
To display a list of node names in the cluster, run the following command:CRS_home\bin\olsnodes
This issue is tracked with Oracle bug 4523043.
The following are the Windows x64 specific issues that affect Oracle Database installation, configuration, and upgrade:
Note:
The issues mentioned in this section are not observed on Windows 32-bit.When performing Oracle RAC add node, the following error may be displayed:
Error while copying directory C:\app\oracle\product\11.1.0\db_1 with exclude file ist'C:\DOCUME~1\oracle\LOCALS~1\Temp\1\OraInstall2007-04-01_08-00-09PM\installExcludeFile.lst' to nodes 'nodes_being_added'. [PRKC-1073 : Failed to transfer directory "C:\app\oracle\product\11.1.0\db_1" to any of the given nodes "nodes_being_added". Error on node nodes_being_added:Access denied] Refer to 'C:\Program Files\Oracle\Inventory\logs\addNodeActions2007-04-01_08-00-09PM.log' for details. You may fix the errors on the required remote nodes. Refer to the install guide for error recovery. Click 'Yes' if you want to proceed. Click 'No' to exit the install. Do you want to continue?
Workaround: This is a benign error. Click Yes to continue and perform the remaining steps in the add node procedure as documented.
This issue is tracked with Oracle bug 5967610.
When creating a DSN entry using the odbcad32.exe
application, the ODBC Driver Setup dialog box does not work as desired. This issue is specific to Oracle Instant Client Installation on Windows Vista.
Workaround: Copy the mfc42.dll
file from Microsoft Platform SDK for Windows Server 2003 redistributable to the Oracle Instant Client installation directory. This file is also available on the Oracle Technology Network page from where you can download instant client ODBC driver for Windows x64.
This issue is tracked with Oracle bug 6529492.
When installing Oracle Database 11g, the configuration step which installs and configures Oracle Configuration Manager (OCM) may fail on Windows 64-bit platforms. OCM attempts to create a service named Oracle
homeName
ConfigurationManager
, where homeName
is the user-specified name for the database install home. In some cases, OCM is unable to retrieve the home name from the Windows registry. This causes a premature exit from the OCM configuration procedure.
Workaround: If you encounter this issue, you can download the latest OCM kit from OracleMetaLink and install it following the instructions provided on the OracleMetaLink Web site.
This issue is tracked with Oracle bug 6172972.
oradim.exe
Application May Fail on Windows Vista When Deleting Non-Existing Oracle ServicesOn Windows Vista, when you use the oradim.exe
application to delete a non-existing service, the application may fail and display an operating system message box stating that the application was terminated.
Workaround: Click OK to terminate the application.
This issue is tracked with Oracle bug 6595601.
The following sections contain information about issues related to Oracle Database 11g and associated products:
When using Database Resident Connection Pooling on Windows, disable Windows native authentication for the clients that connect to pooled servers. Ensure that sqlnet.authentication_services
parameter does not have NTS set for these clients. Pooled servers do not support NTS authentication, so there is no loss in functionality for these clients.
This issue is tracked with Oracle bug 6183123.
If you export an encrypted table, an error message is displayed.
This issue is tracked with Oracle bug 6324760.
If you import an encrypted table, an error message is displayed.
This issue is tracked with Oracle bug 6326362.
The deployment script file pgmobj.sql
located in the Gateway_Home
\admin\deploy
directory contains incorrect database link and library names. These incorrect names result in the malfunctioning of the gateway. You can detect this issue if the ORA-28509
error message is displayed and no gateway trace files are generated.
Workaround: To resolve this issue, make the following changes to the pgmobj.sql script:
Replace all the database link names pg4mqdepdblink
with dg4mqdepdblink
.
Replace all the library names libpg4mq
with libdg4mq
.
Save the pgmobj.sql
script and follow the instruction available in the gateway manual to run the script. To run the script, use SYS
user as SYSDBA
in SQL*Plus on the Oracle database that needs access to the gateway.
This issues is tracked with Oracle bug 6448585.
When you upgrade Oracle9i or Oracle Database 10g to Oracle Database 11g on Windows Server 2003, Oracle VSS Writer Service is not available in the upgraded database. If you want to make a backup of an Oracle database using Windows VSS infrastructure, then you must start Oracle VSS Writer Service.
Workaround: Use the following command to create Oracle VSS Writer Service:
SYSTEM_DRIVE:> oravssw ORACLE_SID /i
When you run this command, Oracle VSS Writer Service is created under Local System account. Using the Services icon in the Control panel, you must change the service to be run as a user account that has SYSDBA
privilege using operating system authentication. This means that the user should be a member of ORA_DBA
group.
This issue is tracked with Oracle bug 6496376.
If you run Oracle Database Configuration Assistant to install Automatic Storage Management with shared Oracle base and non-shared Oracle home, an error message stating permission denied is displayed.
Workaround: This is a benign message. Click OK to continue and complete the installation process. The Automatic Storage Management is created successfully.
This issue is tracked with Oracle bug 6327383.
The OC4JADMIN
user is deactivated during the Oracle Database 11g installation process. After the installation is complete, you must modify the ORACLE_BASE
\
ORACLE_HOME
\oc4j\j2ee\OC4J_SEARCH\config\system-jazn-data.xml
file. Replace the following content of the file:
<user deactivated="true"> <name>oc4jadmin</name> <display-name>OC4J Administrator</display-name> <description>OC4J Administrator</description>
with:
<user> <name>oc4jadmin</name> <display-name>OC4J Administrator</display-name> <description>OC4J Administrator</description>
Use the following commands to restart the Oracle Ultra Search middle tier in the Oracle Database:
System_Drive:>ORACLE_BASE\ORACLE_HOME\bin\searchctl stop System_Drive:>ORACLE_BASE\ORACLE_HOME\bin\searchctl start
The following is the Windows 32-bit specific known issue related to Oracle Database 11g and associated products:
Note:
The issues mentioned in this section are not observed on Windows x64.If Visual C++ .Net 2003 7.1 or a later version is installed on the computer, you will not be able to compile the XDKCPP demonstrations.
Workaround: Visual C++ .Net 2003 7.1 has deprecated classic iostream
support. To compile the XDKCPP demonstrations with Visual C++ .Net 2003 7.1, update the code that uses classic iostream
(#include <iostream.h>
) to use the standard iostream
with the following code:
#include <iostream> using namespace std;
This issue is tracked with Oracle bug 5652607.
The following are the Windows x64 specific known issue related to Oracle Database 11g and associated products:
Note:
The issues mentioned in this section are not observed on Windows 32-bit.You must set the values of the InitialLongFetchSize
and InitialLobFetchSize
properties of the oracleCommand
class to a multiple of 4 on the 64-bit platforms.
64-bit platforms support only Microsoft .Net Framework 2.0. Therefore, this is the only Microsoft .Net Framework version supported by Oracle Database Extensions for 64-bit .Net.
You deploy a .Net stored procedure using Oracle Developer Tools for Visual Studio .NET (ODT.Net). In absence of the support for ODT.Net on 64-bit platforms, you can use ODT.Net for Visual Studio 2005 on a 32-bit computer to develop and deploy .Net stored procedures on 64-bit database server. You must select Any CPU as a Platform Target for such .Net stored procedures to ensure that these procedures can run on a 64-bit computer. ODT does not work with the Visual Studio Team System Edition.
These issues are tracked with Oracle bugs 5603810 and 5605769.
sqldveloper.exe
Application is not SupportedThe sqldveloper.exe
application is not supported on Windows x64. To use SQL Developer on Windows X64, set JAVA to be included in the path. For example, add C:\oracle\product\11.1.0\db_01\jdk\bin
to the path. Run the ORACLE_BASE
/
ORACLE_HOME
/sqldeveloper/sqldeveloper/bin/sqldeveloper.bat
command to start the application.
This issue is tracked with Oracle bugs 6142427 and 6114051.
This section lists the corrections and additions to the documentation for Oracle Database 11g on Windows platform:
The "Installing and Configuring the Scheduler Agent" section of Chapter 28, "Administering Oracle Scheduler" in Oracle Database Administrator's Guide states that you need to use the schagent -installagentservice
command to install the OracleSchedulerExecutionAgent
service before starting the Scheduler agent. However, the service is installed and started automatically during the installation process. Therefore, no additional step is required.
This issue is tracked with Oracle bug 6431812.
ocopy.exe
Utility is not Installed in CRS_Home
In Oracle Clusterware Installation Guide for Microsoft Windows, you are instructed to make a backup of the contents of the voting disk by using the ocopy.exe
utility after the Oracle Clusterware installation is complete. However, the ocopy.exe
utility is not installed in the CRS_home
. You should either use the ocopy.exe
utility available in the database ORACLE_HOME
, or use another utility to make the backup.
This issue is tracked with Oracle bug 6336685.
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. 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.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, 7 days a week. For TTY support, call 800.446.2398. Outside the United States, call +1.407.458.2479.
Oracle Database Release Notes, 11g Release 1 (11.1) for Microsoft Windows
B32005-03
Copyright © 2008, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States 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, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.