Skip Headers
Oracle9i Release Notes
Release 2 (9.2.0.1.0) for IBM S/390 Based Linux
A97686-04
 

 

Oracle9i

Release Notes

Release 2 (9.2.0.1.0) for IBM S/390 Based Linux

A97686-04

February 2006

These release notes contain important information not included in the Oracle9i Installation Guide Release 2 (9.2.0.1.0) for UNIX Systems and the Oracle9i Administrator's Reference Release 2 (9.2.0.1.0) for UNIX Systems. This document contains the following topics:

1 Third-Party Software Notices

This program contains third party code from International Business Machines Corporation ("IBM"). Under the terms of the IBM license, Oracle is required to provide the following notice:

CONTAINS

IBM® zSeries Developer Kit for Linux®, Java™ 2 Technology Edition Runtime Modules © Copyright IBM Corporation 1997-2002 All Rights Reserved

Note that the Oracle program license that accompanied this product determines your right to use the Oracle program, including the IBM software. Notwithstanding anything to the contrary in the Oracle program license, the IBM software is provided by Oracle "AS IS" and without intellectual property indemnities, warranty or support of any kind from Oracle or IBM.

2 System Requirements

This section contains the following topics:

2.1 Hard Disk Space Requirements

The hard disk space requirements listed in the Available Products window of the Oracle Universal Installer apply to installations that include a database. If you select the Software Only configuration type, the installation requires 3 GB of available hard disk space.

2.2 Operating System Requirements

Oracle9i for IBM S/390 based Linux requires one of the following operating systems:

  • SuSE SLES-7 (s390) with following kernel version and compilers:

    • Kernel 2.4.7

    • glibc 2.2.4

    • GCC 2.95.3

  • SuSE SLES 8 with following kernel version and compilers:

    • Kernel 2.4.19-3suse-SMP

    • glibc 2.2.5

    • GCC 3.2

  • SuSE SLES 9 with following kernel version and compilers:

    • Kernel 2.6.5-7.139-s390x

    • glibc 2.3.3

    • GCC 3.3.3

2.3 Required GNU C Compiler

On SuSE SLES-7 (s390), Oracle9i for IBM S/390 based Linux is certified using the GNU C compiler gcc version 2.95.3. Therefore, you must use the GNU C compiler gcc version 2.95.3 (gcc_old) and not version 3.0 or higher to compile and run proc programs and to use some functions of the Oracle software.

The GNU C compiler gcc version 2.95.3 is installed in the /opt/gcc295/ directory. You can install both gcc 2.95.3 and gcc 3.0 or higher on the same system. Make sure that the gcc version that you want to use is listed first in the PATH environment varible.

2.4 Java Development Kit (JDK)

On SuSE SLES-7 (s390), download and install IBM JDK 1.3.1 from the following Web site before you install Oracle9i for IBM S/390 based Linux:

http://www.ibm.com/servers/eserver/zseries/software/java/

On SuSE SLES 9, download the IBM Java JDK 1.3.1 sr8 by completing the following steps:

  1. Go to http://www-128.ibm.com/developerworks/java/jdk/linux140/download.html

  2. Select 31-bit zSeries (S/390) Java 1.3.1 sr8

    The login page for the site opens. If you do not have the login ID, follow the instructions available on the page to create an ID for you.

  3. Login and follow instructions to download the JDK. You can download the software as either an rpm or a tqz file.

  4. Select your preferred method, as this will determine how you install the SDK.

2.5 Kernel Parameters

The following information supplements the information on kernel parameters in the Oracle9i Installation Guide Release 2 (9.2.0.1.0) for UNIX Systems:

  • SHMSEG: This kernel parameter is no longer supported in current kernel distributions.

  • SHMALL: Leave this kernel parameter set to the default value. This supersedes instructions in the installation guide to change the value.

  • SHMMAX: Set this kernel parameter to half the size of the physical random access memory (RAM) available on your system. Do not exceed a value of 2,147,483,647 bytes.

2.6 Tuning the System Global Area (SGA) Size

The default maximum SGA size on IBM S/390 based Linux is 750 MB. You can increase the maximum SGA size to 1 GB by changing the SGA base address as follows:

  1. Log in as the oracle user.

  2. Enter the following commands from the $ORACLE_HOME/rdbms/lib directory:

    genksms -s 0x45000000 > ksms.s
    make -f ins_rdbms.mk ksms.o
    make -f ins_rdbms.mk ioracle
    
    
  3. Start Oracle9i.

2.7 Extended Buffer Cache

Extended Buffer Cache is not supported with this release.

2.8 Asynchronous I/O

Asynchronous I/O is not supported with this release.

2.9 Oracle Universal Installer Release Update

Oracle9i release 2 (9.2.0.1.0) uses Oracle Universal Installer release 2.2.0.12.0. This release number supersedes the number listed in the Oracle9i Installation Guide Release 2 (9.2.0.1.0) for UNIX Systems.

3 Documentation

This section contains the following topics:

3.1 Updated Release Notes

These release notes are correct at the time of release. Oracle updates these release notes online at:

http://www.oracle.com/technology/documentation/

3.2 Certify Web Pages

The Certify Web pages section on OracleMetaLink provides information about certified configurations for Oracle and third-party products. To access the Certify Web pages:

  1. Log on to OracleMetaLink at the following Web address:

    http://metalink.oracle.com
    
    

    Note:

    If you do not have an OracleMetaLink username and password, you must register with OracleMetaLink before you log on.

  2. Select Certify and Availability from the OracleMetalink navigation bar.

    The Certify Web page appears.

  3. Select Certifications in the Product Lifecycle window navigation bar.

  4. Select Certifications by Product.

    The Certify - Product Group Selection page appears.

  5. Select a product group from the Product Groups list and click Submit.

    The Certify - Platform Selection page appears.

  6. Select a platform from the Platform Selection list and click Submit.

3.3 Readme Files

Additional product README files are located in the respective product subdirectories of the Oracle home directory and in the $ORACLE_HOME/relnotes directory.

3.4 Documentation Errata

This section corrections for errors in the Oracle9i Installation Guide Release 2 (9.2.0.1.0) for UNIX Systems.

3.4.1 PL/SQL Gateway

Appendix A, Oracle9i Components, lists PL/SQL Gateway as a supported product. PL/SQL Gateway is not supported in this release.

3.4.2 Pre-installation Requirements

On page 2-3, in the table in the Random Access Memory section, the Linux and HP commands are swapped. The following commands are correct:

  • Linux:

    $ grep MemTotal /proc/meminfo
    
    
  • HP:

    $ /usr/sbin/dmesg | grep "Physical:"
    

3.4.3 Oracle Real Application Clusters

On page 2-43, in Step 2 replace ismod with insmod.

4 Preinstallation Tasks

Ensure that the following requirements are met before you start with the installation process on SuSE SLES 9:

5 Downloading Required Software

Ensire that you have the required software on your computer. Check the following software before you proceed with the installation process on SuSE SLES 9:

6 Installing of Oracle9i on SuSE SLES9

Complete the follwoing steps to install Oracle9i on SuSE SLES 9:

  1. Ensure that the following rpms are installed on the computer:

    • compat-2002.8.15-20.s390.rpm

    • gcc_old-2.95.3-4.s390.rpm

  2. Use the following command to change the value of the PATH variable:

    export PATH=/opt/gcc295/bin:$PATH
    
    
  3. To install the JDK 1.3.1 sr8 that was downloaded:

    • Install JDK as rpm using the rmp command

    • Use the tar command with -zxvf options if the downloaded file has the tgz extension.

    If the rpm command is used, root owns the SDK and put in the /opt directory. You should the grant 755 permissions, which allows oracle access to the SDK.

    You must remember the location where SDK is installed as this location is needed later. This locations is the JAVA_HOME.

  4. Unarchive the Oracle9i CDs by using the tar command followed by the cpio command on the lnx390_db_9201_Disk1.cpio.tgz and lnx390_db_9201_Disk2.cpio.tgz files you downloaded.

  5. Replace the SDK on Disk1 with the SDK you downloaded earlier.

    • To make it possible, you need to set some system variables for this process. Use a command similar to the following to set the JAVA_HOME and CD_LOC variables (Disk1 for Oracle9i installation CDs):

      export JAVA_HOME=/oracle/IBMJava2-s390-131
      export CD_LOC=/oracle/images //location for Disk1 and Disk2 directories
      
      
    • Replace the SDK that is in the OUI that shipped with the CDs by using the following commands similar to the following set of commands:

      cd /$CD_LOC/Disk1/stage/Components/oracle.swd.jre /1.3.1.0.0/1/DataFiles/Expanded/lnx390/IBMJava2-s390-131/
      mv jre oracle.jre //to back up the existing SDK
      ln -s $JAVA_HOME/jre jre //create links to the JDK you installed
      export LD_ASSUME_KERNEL=2.4.19
      
      
  6. Apply the 3287374 patch for Oracle 9.2.0.1 base product. This patch is applied to the OUI code in the file system where CD-ROM is placed.

  7. Install the 9.2.0.1 base Oracle binaries by using the ./runInstaller command in the Disk1 directory.

  8. Edit the patch.sh file, which is supplied with the 3287377 patch. Change all occurances of 9.2.0.4 to 9.2.0.5. Run the patch.sh script and make appropriate changes to directories as noted in header of the patch.sh shell script.

  9. Refer to step 5 and replace the SDK on the Disk1 of the 9.2.0.5 patch CD. The new SDK needs to be installed on this CD.

  10. Follow the procedure in the 9.2.0.5 Read Me file to install new Oracle Universal installer 2.2.0.18.0. Be sure to exit Oracle Universal installer after installing the new Oracle Universal installer.

  11. Start Oracle Universal installer and install Patchset 9.2.0.5. a. When installing the patch, oracle will be re-linked and you will get the following error messages:

    Exception String: Error in invoking target install of makefile /oracle/O9i/network/lib/ins_oemagent.mk
    Exception String: Error in invoking target install of makefile /oracle/O9i/rdbms/lib/ins_rdbms.mk
    
    

    The next step shows how to fix these errors.

  12. Two make files must be changed and re-run to resolve problems with oem and external procedures. Ensure ORACLE_HOME is set appropriately.

    To fix problem with make of ins_oemagent.mk, use the following command:

    vi $ORACLE_HOME/network/lib/ins_oemagent.mk
    
    

    Replace:

    LDFLAGS   = $(STDMODE) -L$(LIBHOME) -L$(ORACLE_HOME)/rdbms/lib  -L$(ORACLE_HOME)/network/lib
    
    

    with:

    LDFLAGS   = $(STDMODE) -L$(LIBHOME)/stubs -L$(LIBHOME) -L$(ORACLE_HOME)/rdbms/lib  -L$(ORACLE_HOME)/network/lib
    
    

    Change to the following directory:

    cd $ORACLE_HOME/network/lib
    
    

    Run the following command:

    /usr/bin/make -f ins_oemagent.mk install ORACLE_HOME=$ORACLE_HOME
    

    To fix problem with linking of extproc during make of ins_rdbms.mk, use the following command:

    vi $ORACLE_HOME/bin/genagtsh 
    
    

    Replace:

    # Linker command and options
    LD="gcc -m31 -shared  -L${ORACLE_HOME}/lib"
    
    

    with:

    # Linker command and options
    LD="gcc -m31 -shared  -L${ORACLE_HOME}/lib/stubs -L${ORACLE_HOME}/lib"
    
    

    Change to the following directory:

    cd $ORACLE_HOME/rdbms/lib
    
    

    Run the following commands:

    $ORACLE_HOME /bin/genagtsh $ORACLE_HOME /lib/libagtsh.so 1 0
    /usr/bin/make -f ins_rdbms.mk install ORACLE_HOME=$ORACLE_HOME
    
    
  13. To enable the DBCA, you need to copy libcore.so from the IBM SDK 1.3.1 to $ORACLE_HOME/JRE/bin. The $ORACLE_HOME/JRE directory is a link that is created by the Oracle Universal Installer. In the $ORACLE_HOME, if you run the ls -la command, the following output is displayed:

    lrwxrwxrwx   1 oracle oinstall   39 2005-10-12 15:32 JRE -> /oracle/jre/1.3.1/IBMJava2-s390-131/jre
    
    

    To copy the libcore.so, use the following command:

    cp $JAVA_HOME/jre/bin/classic/libcore.so $ORACLE_HOME/JRE/1.3.1/IBMJava2-s390-131/jre/bin/libcore
    
    
  14. At this point you have made all the necessary corrections to complete the installation of Oracle9i. To create a database, use either the DBCA or manually create a database by using scripts with the create database command.

7 Installation Issues

This section contains the following topics:

7.1 Installing Oracle9i From a Disk Drive

The IBM S/390 based Linux platform does not support direct attachment of CD-ROM devices. To install Oracle9i, mount the CD-ROM on another system and copy the files to the IBM S/390 based Linux system from the other system.


See Also:

Oracle9i Installation Guide Release 2 (9.2.0.1.0) for UNIX Systems for information on mounting the CD-ROM.

7.2 Creating Databases with the Database Configuration Assistant

If you use the Database Configuration Assistant (DBCA) to create a database, you must change the passwords of the SYS and SYSTEM groups at the end of the configuration process. This is a new security requirement designed to protect access to data.

7.3 Installing Oracle9i Using Response Files

To install Oracle9i using a response file, specify the full path of the response file when starting the Installer in silent mode. If you use a relative path, the Oracle Universal Installer fails.

7.4 Unzip Utility for Uncompressing Oracle Patches

The unzip utility is provided with Oracle9i release 2 (9.2.0.1.0) for uncompressing Oracle patches downloaded from the OracleMetaLink Web site. The unzip utility is located in the following directory:

$ORACLE_HOME/bin/

8 Post-installation Issues

This section describes issues that can occur after installation. It contains the following topics:

8.1 Control File Size Limits

In addition to the database, a number of other Oracle features use control files to record metadata. The maximum size of control files is limited by the minimum data block size that your operating system permits. On HP-UX, the minimum data block size is 4096 bytes, and the maximum size of control files is 20000 database blocks.

8.2 Database Management

The following sections provide additional information on database management.

8.2.1 Segments and Compression Settings

To determine which database segments are using compression, log in to the database as the SYS user and enter the following command to create the ALL_SEGS view:

SQL> CREATE OR REPLACE VIEW ALL_SEGS
     (owner, segment_name,
       partition_name, spare1)
AS
SELECT u.name, o.name, o.subname, s.spare1
FROM SYS.USER$ u, SYS.OBJ$ o, SYS.TS$ ts, SYS.SYS_OBJECTS so,
     SYS.SEG$ s, SYS.FILE$ f
WHERE s.file# = so.header_file
   AND s.block# = so.header_block
   AND s.ts# = so.ts_number
   AND s.ts# = ts.ts#
   AND s.ts# = so.object_id
   AND o.owner# = u.user#
   AND s.type# = so.object_type_id
   AND s.ts# = f.ts#
   AND s.file# = f.relfile#
UNION ALL
SELECT u.name, un.name, NULLL, NULL
FROM SYS.USER$ u, SYS.TS$ TS, SYS.UNDO$ un, SYS.SEG$ s, SYS.FILE$ f
WHERE s.file# = un.file#
   AND s.block# = un.block
   AND s.ts# = un.ts#
   AND s.ts# = ts.ts#
   AND s.user# = u.user#
   AND s.type# IN (1, 10)
   AND un.status$ != 1
   AND un.ts# = f.ts#
   AND un.file# = f.relfile#
UNION ALL
SELECT u.name, TO_CHAR(f.file#)|| '.' || TO_CHAR(s.block#), NULL, NULL
FROM SYS.USER$ u, SYS.TS$ ts, SYS.SEG$ s, SYS.FILE$ f
WHERE s.ts# = ts.ts#
   AND s.user# = u.user#
   AND s.type# NOT IN (1, 5, 6, 8, 10)
   AND s.ts# = f.ts#
   AND s.file# = f.relfile#
/

You can query this view to determine whether a segment is currently compressed, for example:

  • To determine whether a segment is currently compressed, use the following predicate in a query:

    BITAND(spare1, 2048) > 0
    
    

    For example, enter a statement similar to the following:

    SQL> SELECT * FROM ALL_SEGS WHERE BITAND(spare1, 2048) > 0;
    
    
  • To determine whether a segment contains any compressed blocks, use the following predicate in a query:

    BITAND(spare1, 4096) > 0
    
    

    For example, enter a statement similar to the following:

    SQL> SELECT * FROM ALL_SEGS WHERE BITAND(spare1, 4096) > 0;
    

8.2.2 Tablespaces and Compression Settings

To determine the compression settings on a tablespace, log in as the SYS user and enter the following command to create the COMPRESSION_TS view:

SQL> CREATE OR REPLACE VIEW COMPRESSION_TS (tablespace_name, flags) AS SELECT ts.name, ts.flags FROM
SYS.TS$ ts WHERE ts.online$ !=3;

You can query this view to determine the compression state of tablespaces, for example:

  • To determine whether a tablespace is currently set to DEFAULT COMPRESS, use the following predicate in a query:

    BITAND(flags, 64) > 0
    
    

    For example, enter a statement similar to the following:

    SQL> SELECT * FROM COMPRESSION_TS WHERE BITAND(flags, 64) > 0
    
    
  • To determine whether a tablespace is currently set to DEFAULT NOCOMPRESS, use the following predicate in a query:

    BITAND(flags, 64) == 0
    
    

    For example, enter a statement similar to the following:

    SQL> SELECT * FROM COMPRESSION_TS WHERE BITAND(flags, 64) == 0;
    

9 Product Release Issues

This section contains the following topics:

9.1 Character Sets

The following sections provide information on restrictions and updates to character sets.

9.1.1 Character Set Scanner Utility

The Character Set Scanner (csscan) utility checks all character data in the database and tests for the effects of, and problems with, changing the character set encoding.

You must set the LD_LIBRARY_PATH environment variable to include the $ORACLE_HOME/lib directory before running this utility from the $ORACLE_HOME directory.


See Also:

Oracle9i Database Globalization Support Guide for more information on the Character Set Scanner utility.

9.2 Demonstration Schema

If you select a multibyte character set or UTF as the national character set in Oracle9i release 2 (9.2.0.1.0), then you must recreate the demonstration schema and the database installation.

For more information on creating schemas, schema dependencies, and requirements, refer to the readme.txt file in the $ORACLE_HOME/demo/schema directory.

9.3 Custom Installation and Global Database Name

When performing a custom Oracle Internet Directory server installation, do not change the global database name or the name of the Oracle SID.

9.4 Oracle Real Application Clusters

Review the following sections before you install Oracle Real Application Clusters.

9.4.1 Restrictions for Installing Real Application Clusters

If you are installing Oracle9i release 2 (9.2.0.1.0) Real Applications Clusters on a cluster that already contains an Oracle home for a previous release of Real Application Clusters, then you must run the Oracle Universal Installer from the cluster node that contains the oraInventory installation registry.

Doing this ensures that product installation inventories are synchronized on all nodes with information about existing Oracle home directories.

9.4.2 Oracle Cluster Management Software Installation Issues

You must install Oracle Cluster Management Software (OCMS) before installing Oracle Real Application Clusters. The following section describes how to install OCMS.


See Also:

Oracle9i Administrator’s Reference Release 2 (9.2.0.1.0) for UNIX Systems, Appendix F, for information about the OCMS.

9.4.2.1 Installing OCMS for the First Time

To install OCMS on a system that does not have an OCMS installation:

  1. Determine the values that you want to assign to the following parameters:

    • PrivateNodeNames

    • PublicNodeNames

    • CmDiskFile

    • WatchdogTimerMargin

    See the Oracle9i Administrator's Reference Release 2 (9.2.0.1.0) for UNIX Systems, Appendix F, for information on determining the values for these parameters. When you install OCMS, the Oracle Universal Installer prompts for these values.

  2. Use the Oracle Universal Installer to install OCMS. When prompted, provide values for the parameters listed in step 1.

    The Oracle Universal Installer propagates OCMS, creates oracm configuration files, and copies the oracm and watchdogd executables to all nodes of the cluster.

  3. Exit the Installer.

  4. Start the cluster on all of the nodes as follows:

    $ su
    # /ORACLE_HOME/oracm/bin/ocmstart.sh
    
    
  5. Install Oracle Real Application Clusters.


See Also:

Oracle9i Administrator's Reference Release 2 (9.2.0.1.0) for UNIX Systems for information on the Watchdog Daemon.

9.4.2.2 Watchdog Support

The IBM S/390 based Linux kernel does not support the watchdog device. This means that the Oracle Cluster Manager is always started with /dev/null as the watchdog device for this platform.

9.4.3 Real Application Clusters Custom Installation Requirement

If you want to create an Oracle Enterprise Manager repository in an existing database, and you want to use the DRSYS tablespace for the repository, then ensure that the DRSYS tablespace raw device data file has an additional 50 MB of free space. This is in addition to the 250 MB size required for this raw device.

9.4.4 Real Application Clusters SYSDBA Privileges

After you have created a cluster database using the DBCA, password privileges are revoked for all users except SYSDBA. As SYSDBA, you must grant privileges explicitly to the database user accounts that you plan to use for adding or deleting an instance to or from the cluster database.

For example, to grant SYSDBA privileges to the administrative user SYS, enter the following commands:

$ sqlplus "/ AS SYSDBA"
SQL> GRANT SYSDBA TO SYS;
SQL> EXIT;

9.4.5 z/VM Notes

If the Linux server runs as a VM guest, you must format minidisks in the CMS format with a block size of 4096 KB before you create a filesystem. Shared disks, for example clusters, are defined in the VM directory with a multiple write (MW) access mode.

9.5 Platform-Specific Product Restrictions

The following list describes additional product-specific restrictions not listed in the Oracle9i Installation Guide Release 2 (9.2.0.1.0) for UNIX Systems:

  • The following precompilers are not supported:

    • Pro*COBOL

    • Pro*FORTRAN

    • SQL Module for Ada

  • The following Oracle Advanced Security protocols are not supported:

    • Radius challenge response authentication

    • CyberSafe

    • DCE Integration

    • Entrust

    • nCipher

  • Generic Connectivity is not supported.

  • The INSO_FILTER is not available for Oracle Text.

10 Documentation Accessibility

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, seven days a week. For TTY support, call 800.446.2398.


Oracle 9i Release Notes, Release 2 (9.2.0.1.0) for IBM S/390 Based Linux

A97686-04

Copyright © 1996, 2006, 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 Corporation, 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 Retek 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.