| Oracle® Enterprise Data Quality for Product Data Oracle DataLens Server Upgrade Guide Release 5.6.2 Part Number E24164-04 |
|
|
View PDF |
| Oracle® Enterprise Data Quality for Product Data Oracle DataLens Server Upgrade Guide Release 5.6.2 Part Number E24164-04 |
|
|
View PDF |
Oracle DataLens Server Upgrade Guide
Release 5.6.2
E24164-04
April 2012
This document describes how to upgrade Oracle DataLens Server from Oracle Enterprise Data Quality for Product Data, formerly known as Oracle Product Data Quality, releases 5.0.01, 5.0.02, 5.1, 5.5.n, 5.6.0, and 5.6.1 to 5.6.2. This document contains the following:
The Enterprise DQ for Product (EDQP) upgrade methodology is to upgrade your Oracle DataLens Administration Server, while maintaining the ability to revert to your existing server. You should not uninstall your existing Oracle DataLens Administration Server until you have tested and verified that your new Oracle DataLens Administration Server operates correctly in your environment.
The following previous releases can be upgraded to the EDQP 5.6.0 release:
| Release | Default Server Directories | Notes |
|---|---|---|
| 5.0.01 | /opt/SCSData
or
|
MySQL databases are upgraded to Derby. EDQP directory structures are upgraded and earlier scs directories remain. |
| 5.0.02 and
5.1 |
/opt/silverCreek/server
or
|
MySQL databases are upgraded to Derby. EDQP directory structures are upgraded and earlier scs directories remain. |
| 5.5.x | /opt/datalens/server
or
|
Earlier internal Derby databases are upgraded to newer Derby version. EDQP directory structures are upgraded and earlier datalens directories remain. |
The following previous releases can be upgraded to the EDQP 5.6.2 release:
| Release | Default Server Directories | Notes |
|---|---|---|
| 5.6.0 and 5.6.1 | /opt/Oracle/Middleware/opdq
or
|
Your server must be upgraded to the 5.6.0 release before upgrading to either the 5.6.1 or 5.6.2 release. The EDQP Web application archive (WAR) file is upgraded. |
Oracle recommends that you always create a test environment for an upgrade before attempting to upgrade your production environment.
Note:
Assistance for upgrades can be obtained by contacting Oracle Consulting Services. Upgrades should be a planned migration to ensure the retention of your EDQP Server Group Topology, data repository, DSAs, data lenses, and data.You can identify which product release your existing Oracle DataLens Administration Server is running by logging into the Oracle DataLens Administration Web pages for the server you want to upgrade. The Home page displays the version of the Oracle DataLens Administration Server at the top of the page as in the following example:
Oracle DataLens Server Oracle DataLens Server 5.6.0.0, build 2,622, on Feb 14, 2011 at 4:21 PM Java JVM Version 1.6.0_21 from Sun Microsystems Inc. JSP Server Apache Tomcat/6.0.29
For more information, see Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide.
This section provides upgrade instructions for the following upgrade paths for your Oracle DataLens Administration Server:
This section describes how to upgrade the data repository directory structure of Oracle DataLens Servers running the EDQP 5.0.nn, 5.1.nn, and 5.5.nn releases to the 5.6.nn release configuration. This prepares your Oracle DataLens Server for the installation of the EDQP 5.6.2 release described in "Upgrading from Release 5.6.0 or 5.6.1 to Release 5.6.2". Use of this section is necessary only for the EDQP 5.0.nn, 5.1.nn, and 5.5.nn releases because the updated data repository structure began with the EDQP 5.6.nn release.
Throughout the following Oracle DataLens Server data repository directory structure upgrade process to the 5.6.nn release configuration, /server_directory is used to indicate the directory path to the existing Oracle DataLens Administration Server. For example, /opt/Oracle/Middleware/opdq on a Linux or UNIX server. Additionally, /opdq_home is used to indicate the directory path to the 5.6.2 Oracle DataLens Administration Server once installed. For example, /opt/Oracle/Middleware/opdq is the default directory created by the 5.6.2 EDQP installer on a Linux server. The following steps use the Linux server directory syntax though the directory structures are mirrored on Windows servers.
To upgrade your Oracle DataLens Server data repository:
Locate and download the 5.6.0 EDQP Upgrade Patch:
Browse to the My Oracle Support Web site:
Log in or register.
Click the Patches & Updates tab.
Click Product or Family (Advanced Search).
Search for Oracle Enterprise Data Quality for Product Data by beginning to enter the name in the Product field and then select it when it is displayed in the list.
Select the Release list, click the arrow adjacent to the Oracle Enterprise Data Quality for Product Data folder.
Select the EDQP 5.6 release and then click Close.
Click Search.
Select the UPGRADE FROM 5.0.X, 5.1.X, AND 5.5.X TO 5.6.0 patch from the list of patches, and then click Download.
Click the patch file name, and then save it to a temporary directory.
Change directories to the temporary directory.
Unzip the patch zip file into the temporary directory.
Ensure that you have a current backup you Oracle DataLens Server including the /server_directory/data/repository directory.
(Optional) Run a job to create a baseline regression set that is representative of your data set to validate upgrade results.
Check in all local copies of your DSAs and data lens to your Oracle DataLens Server. You may leave the lenses locked.
Shut down all existing Oracle DataLens Servers by stopping the Tomcat Application Server service; your MySQL database must continue to run in order to synchronize all your existing data during the upgrade process.
Create a new Oracle DataLens Administration Server by installing EDQP 5.6.2, and then verifying the installation. For more information, see Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Installation Guide.
Shutdown the 5.6.2 Oracle DataLens Administration Server by stopping its application server its application server in preparation to cleanly copy files.
Install the EDQP 5.6.2 Client Software. For more information, see Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Installation Guide.
Next, the internal database must be updated to the EDQP 5.6.nn Derby schema.
For upgrades from 5.5.nn, the update occurs automatically when the 5.6.nn Oracle DataLens Server is started.
For upgrades from 5.0.01, 5.0.02 or 5.1 only, you must transfer the existing MySQL data to the EDQP 5.6.nn Derby schema by executing the following additional steps:
Copy the 5.6.nn internal Derby database, which includes the preconfigured database connection:
Where temporary_location is the directory where you unzipped the EDQP Upgrade Patch file.
On Linux or UNIX:
cp -R /temporary_location/scsdata.migration /opt/Oracle /Middleware/opdq/data/repository/internal/scsdata
On Windows:
xcopy /temporary_location\scsdata.migration C:\Oracle \Middleware\opdq\data\repository\scsdata /E
Rename the ServerProfiles.xml.bak to ServerProfiles.xml; this file is located in the following directory:
On Linux or UNIX:
/opt/Oracle/Middleware/opdq/data/shared/config
On Windows:
C:\Oracle\Middleware\opdq\data\shared\config
Start your 5.6.2 Oracle DataLens Administration Server by starting its application server.
Note:
Your
admin user password is reset to the admin1 so you will be prompted to change it.Your server is automatically updated to the new Derby internal database schema.
Note:
If errors occur, restart your server. Ensure that you have correctly copied the Derby database files and that you renamed theServerProfiles.xml file.Run Application Studio.
Import and check in the appropriate database upgrade DSA from the temporary location created in Step 1, run it, and then check it in using one of the following:
Upgrading 5.0.01: Upgrade_5_0_01MySQL_to_5_6Derby.pmap
Upgrading 5.0.02: Upgrade_5_0_02MySQL_to_5_6Derby.pmap
Upgrading 5.1: Upgrade_5_1MySQL_to_5_6Derby.pmap
Exit Application Studio.
Login to the Oracle DataLens Administration Web pages.
Create and run scheduled a job to run immediately for the upgrade DSA, which migrates the data from the previous release internal database structure to the new EDQP internal database structure.
Review the DSA Job Status page for errors. If errors occurred, locate the failing step and the review the information provided for resolution.
Review the Oracle DataLens Log for errors relating to the DSA job and any failing steps.
If there are no errors, go to Step 10; otherwise continue with the next step.
Repeat Steps a through c, and then Steps h through k to resolve the errors.
If you need assistance in resolving errors, contact Oracle Support.
Shutdown the 5.6.2 Oracle DataLens Administration Server by stopping its application server in preparation to cleanly copy files.
Copy your data repository to the 5.6.2 Oracle DataLens Server location. These directories include your data repository and shared directory. To copy these directories, use the following copy commands:
Note:
There is nocommon directory in the EDQP release 5.6.2 directory structure.The internal database repository is also copied and it is automatically updated by the Oracle DataLens Server on restart.Note:
The upgrade process will not move any of the parameters defined in theserver.cfg file of your previous installation.On Linux or UNIX:
| From 5.0.01 |
|---|
cp -R /opt/SCSData/OR_DEV /opt/Oracle/Middleware/opdq/data/shared/ |
cp -R /opt/SCSData/OR_PROD /opt/Oracle/Middleware/opdq/data/shared/ |
cp -R /opt/SCSData/OR_QA /opt/Oracle/Middleware/opdq/data/shared/ |
cp -R /opt/SCSData/OR_SHARED/common/glossary /opt/Oracle/Middleware/opdq/data /shared/ |
cp -R /opt/SCSData/repository/project /opt/oracle/Middleware/opdq/data /repository/project/ |
cp -R /opt/SCSData/repository/workflow /opt/oracle/Middleware/opdq/data /repository/workflow/ |
| From 5.0.02 |
|---|
cp -R /opt/silvercreek/server/data/shared/qadata /opt/Oracle/Middleware/opdq/data /shared/ |
cp -R /opt/silvercreek/server/data/shared/proddata /opt/Oracle/Middleware/opdq /data/shared/ |
cp -R /opt/silvercreek/server/data/shared/devdata /opt/Oracle/Middleware/opdq /data/shared/ |
cp -R /opt/silvercreek/server/data/shared/common/glossary /opt/Oracle/Middleware /opdq/data/shared/ |
cp -R /opt/silvercreek/server/data/repository/project /opt/oracle/Middleware /opdq/data/repository/project/ |
cp -R /opt/silvercreek/server/data/repository/workflow /opt/oracle/Middleware /opdq/data/repository/workflow/ |
| From 5.1 |
|---|
cp -R /opt/silvercreek/server/data/shared/devdata /opt/Oracle /Middleware/opdq/data/shared/ |
cp -R /opt/silvercreek/server/data/shared/prodata /opt/Oracle /Middleware/opdq/data/shared/ |
cp -R /opt/silvercreek/server/data/shared/qadata /opt/Oracle /Middleware/opdq/data/shared/ |
cp -R /opt/silvercreek/server/data/shared/common/glossary /opt/Oracle /Middleware/opdq/data/shared/ |
cp -R /opt/silvercreek/server/data/repository/project /opt/Oracle/Middleware /opdq/data/repository/project |
cp -R /opt/silvercreek/server/data/repository/workflow /opt/Oracle/Middleware /opdq/data/repository/workflow |
| From 5.5.x |
|---|
cp -R /opt/datalens/server/shared/devdata /opt/Oracle/Middleware/opdq /data/shared/ |
cp -R /opt/datalens/server/shared/proddata /opt/Oracle/Middleware /opdq/data/shared/ |
cp -R /opt/datalens/server/shared/qadata /opt/Oracle/Middleware/opdq /data/shared/ |
cp -R /opt/datalens/server/shared/common/glossary /opt/Oracle /Middleware/opdq/data/shared/ |
cp -R /opt/datalens/server/data/repository/project /opt/Oracle/Middleware /opdq/data/repository/project/ |
cp -R /opt/datalens/server/data/repository/workflow /opt/Oracle/Middleware /opdq/data/repository/workflow/ |
On Windows:
At a command prompt as an Administrator user:
| From 5.0.01 or 5.0.02 |
|---|
xcopy C:\SCSData\OR_DEV C:\Oracle\Middleware\opdq\data\shared /E |
xcopy C:\SCSData\OR_PROD C:\Oracle\Middleware\opdq\data\shared /E |
xcopy C:\SCSData\OR_QA C:\Oracle\Middleware\opdq\data\shared /E |
xcopy C:\SCSData\OR_SHARED\common\glossary C:\Oracle\Middleware\opdq\data \shared /E |
xcopy C:\SCSData\repository\project C:\oracle\Middleware\opdq\data\repository \project /E |
xcopy C:\SCSData\repository\workflow C:\oracle\Middleware\opdq\data\repository \workflow /E |
| From 5.0.02 |
|---|
xcopy C:\silvercreek\server\data\shared\devdata C:\Oracle\Middleware \opdq\data\shared /E |
xcopy C:\silvercreek\server\data\shared\proddata C:\Oracle\Middleware \opdq\data\shared /E |
xcopy C:\silvercreek\server\data\shared\qadata C:\Oracle\Middleware \opdq\data\shared /E |
xcopy C:\silvercreek\server\data\shared\common\glossary C:\Oracle\Middleware \opdq\data\shared /E |
xcopy C:\silvercreek\server\data\repository\project C:\Oracle\Middleware\opdq \data\repository\project /E |
xcopy C:\silvercreek\server\data\repository\workflow C:\Oracle\Middleware\opdq \data\repository\workflow /E |
| From 5.1 |
|---|
xcopy C:\silvercreek\server\data\shared\devdata C:\Oracle\Middleware \opdq\data\shared /E |
xcopy C:\silvercreek\server\data\shared\proddata C:\Oracle\Middleware \opdq\data\shared /E |
xcopy C:\silvercreek\server\data\shared\qadata C:\Oracle\Middleware \opdq\data\shared /E |
xcopy C:\silvercreek\server\data\shared\common\glossary C:\Oracle\Middleware \opdq\data\shared /E |
xcopy C:\silvercreek\server\data\repository\project C:\Oracle\Middleware\opdq \data\repository\project /E |
xcopy C:\silvercreek\server\data\repository\workflow C:\Oracle\Middleware\opdq \data\repository\workflow /E |
| From 5.5.x |
|---|
xcopy C:\datalens\server\shared\devdata C:\Oracle\Middleware\opdq \data\shared /E |
xcopy C:\datalens\server\shared\proddata C:\Oracle\Middleware\opdq \data\shared /E |
xcopy C:\datalens\server\shared\qadata C:\Oracle\Middleware\opdq \data\shared /E |
xcopy C:\datalens\server\shared\common\glossary C:\Oracle\Middleware \opdq\data\shared /E |
xcopy C:\datalens\server\data\repository \project C:\Oracle\Middleware\opdq \data\repository\project /E |
xcopy C:\datalens\server\data\repository \workflow C:\Oracle\Middleware\opdq \data\repository\workflow /E |
Note:
The/E flag is used to copy all the subdirectories including the empty ones.Verify that you copied the directory structure correctly.
Start your 5.6.2 Oracle DataLens Administration Server by starting its application server.
Your server is automatically updated to the new Derby internal database schema.
Check out all server copies of your DSAs and data lens to your client machines.
(Optional) If you created a baseline regression data set on the previous release server, run a job on the 5.6.2 Oracle DataLens Server and compare the results of the data sets. Be aware that the upgrade itself results in progressions (positive changes) because of server fixes from the original baseline though the progressions should not be significant.
Note:
When the EDQP upgrade has successfully completed, MySQL is no longer used by EDQP. MySQL can be shut down if not used by other applications.Verify that all EDQP 5.6.2 files have been installed on your Oracle DataLens Server correctly by using the EDQP audit script. Based on the type of installation you selected, WebLogic or Tomcat, all directories and files are inspected to ensure that the structure is correct and that there are no missing files.
Note:
The audit script is designed to inspect the default installation paths so it may not operate correctly with alternate installation paths.The audit script uses the following two parameters to define the type of verification that will be executed:
tc
Used for Tomcat Application Server installations.
wls
Used for WebLogic Application Server installations.
Verify the EDQP file structure on your Oracle DataLens Server:
On Linux and UNIX: /opt/dls_install/install/audit/audit.sh parameter
On Windows: C:\dls_install\install\audit\audit.bat parameter
Where parameter indicates the verification type, tc or wls.
Upon completion, a successful verification is indicated by the Finished message. If errors are detailed, you should copy the files indicted into the proper directory, and then rerun the audit script until a successful verification is accomplished.
The upgrade from either the 5.6.0 or the 5.6.1 releases to the 5.6.2 release is performed by simply deploying the new WAR file. Use the following steps to upgrade your 5.6.0 Oracle DataLens Administration Server:
Ensure that your server is running either the 5.6.0 or 5.6.1 release as described in "Identifying Your Oracle DataLens Server Version".
Log in to the server as an administrator user.
Browse to the Oracle Software Delivery Cloud Web site at:
Click the Continue link or click a language.
Enter the required information and select a country from the list.
Click both check boxes to accept the License Agreement and Export Restrictions.
Click Continue.
From the Select a Product Pack list, select E-Business Suite.
From the Platform list, select your operating system.
Click Go.
Select the Oracle Enterprise Data Quality for Product Data 5.6.2 Media Pack option and click Continue.
Click the Download button.
Save the product zip file, Vnnnnn.nn, to a temporary directory.
Unzip Vnnnnn.nn in the same directory to extract oracle_datalens_server_5_n_n.zip.
Unzip oracle_datalens_server_5_n_n.zip in the same directory to extract all files including the datalens.war file.
Change directories to:
On Linux: /opt/Oracle/Middleware/opdq
On Windows: C:\Oracle\Middleware\opdq
Complete the upgrade using one of the following sections as appropriate for your application server:
Change directories to:
On Linux: /opt/Oracle/Middleware/opdq/tomcat/bin
On Windows: C:\Oracle\Middleware\opdq\tomcat\webapps
Stop your Tomcat Server.
On Linux: ./shutdown.sh
On Windows: % shutdown.bat
Change directories to:
On Linux: /opt/Oracle/Middleware/opdq/tomcat/webapps
On Windows: C:\Oracle\Middleware\opdq\tomcat\webapps
Delete the entire datalens directory from the webapps directory.
Rename the existing WAR file from datalens.war to datalens.backup.
Copy the EDQP 5.6.2 release WAR file, datalens.war, from the temporary directory you downloaded and unzipped it in, to the webapps directory.
Change directories to:
On Linux: /opt/Oracle/Middleware/opdq/tomcat/bin
On Windows: C:\Oracle\Middleware\opdq\tomcat\webapps
Start your Tomcat Server.
On Linux: ./startup.sh
On Windows: % startup.bat
The EDQP 5.6.2 release WAR file is now deployed.
Verify that the server is up and running correctly by browsing to the Oracle DataLens Server Administration Web site at:
http://server:2229/datalens
Where server is the name of the host where the Oracle DataLens Server was installed.
View the log files from the home page to ensure that no errors have been recorded.
Note:
The following steps only apply to the deployment of Development Servers.Change directories to:
On Linux: /opt/Oracle/Middleware/opdq
On Windows: C:\Oracle\Middleware\opdq
Rename the existing WAR file to datalens.backup.
Copy the EDQP 5.6.2 release WAR file, datalens.war, from the temporary directory you downloaded and unzipped it in, to the opdq directory.
Start the WebLogic Server Administration Console by browsing to:
http://server:2229/datalens
Where server is the name of the host where the Oracle DataLens Server was installed.
Enter the dls_domain user name and password, and then click Log In.
The Oracle WebLogic Server Administration Console home page is displayed.
Click Deployments from the Domain Structure tree.
The Summary of Deployments page is displayed.
Click the Update button.
Note:
You must set these EDQP internal database settings correctly for the Oracle DataLens Server to start.The Install Application Assistant screen is displayed.
Enter or locate the path to the EDQP WAR file.
Select the datalens.war option, and click Next.
Click Next to install the deployment as an application.
The optional settings are displayed in the Install Application Assistant screen.
Retain the page defaults, and click Finish.
The WAR file is deployed and confirmation message that the deployment was successful is displayed in the Summary of Deployments page, which can take several minutes.
The Summary of Deployments page is displayed.
Select the check box adjacent to datalens.
Click Start and select Servicing all requests to ensure that all requests are sent to the EDQP WAR deployment.
The EDQP 5.6.2 release WAR file is now deployed.
Verify that the server is up and running correctly by browsing to the Oracle DataLens Server Administration Web site at:
http://server:2229/datalens
Where server is the name of the host where the Oracle DataLens Server was installed.
View the log files from the home page to ensure that no errors have been recorded.
Upgrade all other Oracle DataLens Administration Servers using the preceding steps.
Since your data including data lenses and DSAs reside in the centrally managed repository on the Oracle DataLens Administration Server, to upgrade your Oracle DataLens Transform Servers you simply install the EDQP 5.6.2 release. Prior to installation, ensure that you have configured the server mount (Linux or UNIX) or the shared directory (Windows). For more information about configuring and installing Oracle DataLens Transform Servers, see Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Installation Guide.
Should it be necessary to revert to the previous release after executing an upgrade, use one of the following sections:
Reverting to a 5.n.n Oracle DataLens Administration Server from the EDQP Release 5.6.x, use the following steps:
Shut down the 5.6.2 Oracle DataLens Administration and Transform Servers.
Start the 5.n.n Oracle DataLens Administration Server.
Ensure that the 5.n.n Oracle DataLens Administration Servers started correctly by logging into the Oracle DataLens Administration Web page and reviewing the Oracle DataLens Log for errors.
Start the 5.n.n Oracle DataLens Transform Servers.
Log in to your Oracle DataLens Administration Server as an administrator user.
Change directories to:
On Linux: /opt/Oracle/Middleware/opdq
On Windows: C:\Oracle\Middleware\opdq
Rename the existing WAR file to datalens.newrelease
Rename the previous WAR file from datalens.backup to datalens.war.
Complete the reversion using one of the following sections as appropriate for your application server:
This section describes known issues with the Oracle DataLens Servers installation and configuration.
When upgrading 5.0.01, 5.0.02, or 5.1, existing job results are moved into an archive table rather than the Job Results web page. You can obtain the archived results by logging into the Oracle DataLens Administration Web page, clicking Operations, and then clicking Get Data. The archived data is displayed in a table including the job id, description, and status for your review.
For more information, see the following documents in the documentation set:
The Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Installation Guide provides detailed Oracle DataLens Server installation instructions.
The Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide provides information about installing and managing an Oracle DataLens Server.
The Oracle Enterprise Data Quality for Product Data COM Interface Guide provides information about installing and using the Oracle DataLens Server COM APIs.
The Oracle Enterprise Data Quality for Product Data Java Interface Guide provides information about installing and using the Oracle DataLens Server Java APIs.
The Oracle Enterprise Data Quality for Product Data Glossary provides definitions to commonly used Enterprise DQ for Product technology terms.
See the latest version of this and all documents listed at the Oracle Enterprise Data Quality for Product Data Documentation Web site at:
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Upgrade Guide, Release 5.6.2
E24164-04
Copyright © 2011, 2012, 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 is software or related documentation that 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 America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware 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 that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware 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 © 2011, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|