Skip Headers
Oracle® Database Quick Installation Guide
10g Release 2 (10.2) for Solaris Operating System (SPARC 64-Bit)

Part Number B15691-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Feedback

  View PDF

Oracle® Database

Quick Installation Guide

10g Release 2 (10.2) for Solaris Operating System (SPARC 64-Bit)

B15691-02

November 2005


Oracle Database Quick Installation Guide, 10g Release 2 (10.2) for Solaris Operating System (SPARC 64-Bit)

B15691-02

Copyright © 2005, 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.

This guide describes how to quickly install Oracle Database 10g on Solaris SPARC systems. It includes information about the following:

  1. Reviewing Information About This Guide

  2. Logging In to the System as root

  3. Checking the Hardware Requirements

  4. Checking the Software Requirements

  5. Creating Required Operating System Groups and User

  6. Creating Required Directories

  7. Configuring Kernel Parameters

  8. Configuring the oracle User's Environment

  9. Mounting the Product Disc

  10. Installing Oracle Database

  11. Installing Products from the Oracle Database 10g Companion CD

  12. What to Do Next?

  13. Additional Information

  14. Documentation Accessibility

1 Reviewing Information About This Guide

This guide describes how to install Oracle Database by using the default installation options.

Tasks Described in This Guide

The procedures in this guide describe how to:

Results of a Successful Installation

After you successfully install Oracle Database:

Tasks Not Described in This Guide

This guide covers the Basic Installation scenario and does not describe how to complete the following tasks:

Where to Get Additional Installation Information

For more information about installing Oracle Database, including information about the tasks not described in this guide, refer to one of the following guides:

Both these guides are available on the product disc. To access them, use a Web browser to open the welcome.htm file located in the top-level directory of the installation media, and then select the Documentation tab.

2 Logging In to the System as root

Before you install Oracle Database, you must complete several tasks as the root user. To log in as the root user, complete one of the following procedures:


Note:

You must install the software from an X Window System workstation, an X terminal, or a PC or other system with X server software installed.

3 Checking the Hardware Requirements

The system must meet the following minimum hardware requirements:

To ensure that the system meets these requirements, follow these steps:

  1. To determine the physical RAM size, enter the following command:

    # /usr/sbin/prtconf | grep "Memory size"
    
    

    If the size of the physical RAM installed in the system is less than the required size, then you must install more memory before continuing.

  2. To determine the size of the configured swap space, enter the following command:

    # /usr/sbin/swap -s
    
    

    If necessary, refer to your operating system documentation for information about how to configure additional swap space.

  3. To determine the available RAM and swap space, enter the following command:

    # sar -r n i
    
    

    where, n is the number of seconds to delay for the next iterations and i is the number of iterations you want to test.


    Note:

    Oracle recommends that you take multiple values for the available RAM and swap space before freezing on a value. This is because the available RAM and swap space keep changing depending on the user interactions with the computer.

  4. To determine the amount of free disk space available in the /tmp directory, enter the following command:

    # df -k /tmp
    # df -h /tmp (on Solaris 10)
    
    

    If there is less than 400 MB of disk space available in the /tmp directory, then complete one of the following steps:

    • Delete unnecessary files from the /tmp directory.

    • Set the TMP and TMPDIR environment variables when setting the oracle user's environment (described later).

    • Extend the file system that contains the /tmp directory. If required, contact your system administrator for information about extending file systems.

  5. To determine the amount of free disk space available on the system, enter the following command:

    # df -k
    # df -h (on Solaris 10)
    
    

    The following table shows the approximate disk space requirements for software files for each installation type.

    Installation Type Requirement for Software Files (GB)
    Enterprise Edition 2.0
    Standard Edition 1.5
    Custom (maximum) 2.5

  6. To determine whether the system architecture can run the software, enter the following command:

    # /bin/isainfo -kv
    
    

    The following is the expected output of this command:

    64-bit sparcv9 kernel modules
    
    

    If you do not see the expected output, then you cannot install the software on this system.

4 Checking the Software Requirements

The system must meet the following minimum software requirements, depending on the distribution and version of your operating system:


Note:

Oracle Universal Installer performs checks on your system to verify that it meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.

To ensure that the system meets these requirements, follow these steps:

  1. To determine which version of Solaris is installed, enter the following command:

    # uname -r
    
    
    5.9
    
    

    In this example, the version shown is Solaris 9 (5.9). If necessary, refer to your operating system documentation for information about upgrading the operating system.

  2. To determine whether the required packages are installed, enter a command similar to the following:

    # pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibm \ SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1of \
    SUNWi1cs SUNWi15cs SUNWxwfnt
    
    

    If a package is not installed, or if the version is lower than the required version, then install it.

In addition, you need to verify that the following patches are installed on the system. The procedure following the table describes how to check these requirements.


Note:

There may be more recent versions of the patches listed installed on the system. If a listed patch is not installed, determine whether a more recent version is installed before installing the version listed.


Note:

The following patches are not required for silent installations:
  • 108652-66, X11 6.4.1: Xsun patch

  • 108773-18, SunOS 5.8: IIIM and X I/O Method patch

  • 108921-16, CDE 1.4: dtwm patch

  • 108940-53, Motif 1.2.7 and 2.1.1: Runtime lib. patch for Solaris 8


To ensure that the system meets these requirements, follow these steps:

  1. To determine whether an operating system patch is installed, enter a command similar to the following:

    # /usr/sbin/patchadd -p | grep patch_number
    
    

    If an operating system patch is not installed, then download it from the following Web site and install it:

    http://sunsolve.sun.com

  2. If you require a CSD or a SupportPac for WebSphere MQ, refer to the following Web site for download and installation information:

    http://www.ibm.com/software/integration/mqfamily/support/summary/sun.html
    

5 Creating Required Operating System Groups and User

The following local operating system groups and users are required if you are installing Oracle Database:

To determine whether these groups and users already exist, and if necessary, to create them, follow these steps:

  1. To determine whether the oinstall group exists, enter the following command:

    # more /var/opt/oracle/oraInst.loc
    
    

    If the output of this command shows the oinstall group name, then the group already exists.

    If the oraInst.loc file exists, then the output from this command is similar to the following:

    inventory_loc=/u01/app/oracle/oraInventory
    inst_group=oinstall
    
    

    The inst_group parameter shows the name of the Oracle Inventory group, oinstall.

  2. To determine whether the dba group exists, enter the following command:

    # grep dba /etc/group
    
    

    If the output from this commands shows the dba group name, then the group already exists.

  3. If necessary, enter the following commands to create the oinstall and dba groups:

    # /usr/sbin/groupadd oinstall
    # /usr/sbin/groupadd dba
    
    
  4. To determine whether the oracle user exists and belongs to the correct groups, enter the following command:

    # id -a oracle
    
    

    If the oracle user exists, this command displays information about the groups to which the user belongs. The output should be similar to the following, indicating that oinstall is the primary group and dba is a secondary group:

    uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)
    
    
  5. If necessary, complete one of the following actions:

    • If the oracle user exists, but its primary group is not oinstall or it is not a member of the dba group, then enter the following command:

      # /usr/sbin/usermod -g oinstall -G dba oracle
      
      
    • If the oracle user does not exist, enter the following command to create it:

      # /usr/sbin/useradd -g oinstall -G dba oracle
      
      

      This command creates the oracle user and specifies oinstall as the primary group and dba as the secondary group.

  6. Enter the following command to set the password of the oracle user:

    # passwd -r files oracle
    
    
  7. To determine whether the nobody user exists, enter the following command:

    # id nobody
    
    

    If this command displays information about the nobody user, then you do not have to create the user.

    If the nobody user does not exist, then enter the following command to create it:

    # /usr/sbin/useradd nobody
    

6 Configuring Kernel Parameters

On Solaris 8 and Solaris 9, verify that the following kernel parameters are set to values greater than or equal to the recommended value shown:

Parameter Recommended Value
noexec_user_stack 1
semsys:seminfo_semmni 100
semsys:seminfo_semmns 1024
semsys:seminfo_semmsl 256
semsys:seminfo_semvmx 32767
shmsys:shminfo_shmmax 4294967295
shmsys:shminfo_shmmin 1
shmsys:shminfo_shmmni 100
shmsys:shminfo_shmseg 10


Note:

The following parameters are obsolete in Solaris 9:
  • semsys:seminfo_semmni

  • shmsys:shminfo_shmseg


On Solaris 10, verify that the kernel parameters shown in the following table are set to values greater than or equal to the recommended value shown. The table aslo contains the resource controls that replace the /etc/system file for a specific kernel parameter.

Parameter Resource Control Recommended Value
noexec_user_stack NA 1
semsys:seminfo_semmni project.max-sem-ids 100
semsys:seminfo_semmsl process.max-sem-nsems 256
shmsys:shminfo_shmmax project.max-shm-memory 4294967295
shmsys:shminfo_shmni project.max-shm-ids 100


Note:

On Solaris 10, you are not required to make changes to the /etc/system file to implement the System V TPC. Solaris 10 uses the resource control facility for its implementation.

On Solaris 8 and Solaris 9, to view the current value specified for these kernel parameters, and to change them if necessary, follow these steps:

  1. To view the current values of these parameters, enter the following commands:

    # grep noexec_user_stack /etc/system
    # /usr/sbin/sysdef | grep SEM
    # /usr/sbin/sysdef | grep SHM
    
    
  2. If you must change any of the current values, follow these steps:

    1. Create a backup copy of the /etc/system file, by using a command similar to the following:

      # cp /etc/system /etc/system.orig
      
      
    2. Open the /etc/system file in any text editor, and if required, add lines similar to the following (edit the lines if the file already contains them):

      set noexec_user_stack=1
      set semsys:seminfo_semmni=100
      set semsys:seminfo_semmns=1024
      set semsys:seminfo_semmsl=256
      set semsys:seminfo_semvmx=32767
      set shmsys:shminfo_shmmax=4294967295
      set shmsys:shminfo_shmmin=1
      set shmsys:shminfo_shmmni=100
      set shmsys:shminfo_shmseg=10
      
    3. Enter the following command to restart the system:

      # /usr/sbin/reboot
      
      
    4. When the system restarts, log in and switch user to root.

On Solaris 10, use the following procedure to view the current value specified for resource controls, and to change them if necessary:

  1. To view the current values of the resource control, enter the following commands:

    # id -p // to verify the project id
    uid=0(root) gid=0(root) projid=1 (user.root)
    # prctl -n project.max-shm-memory -i project user.root
    # prctl -n project.max-sem-ids -i project user.root
    
    
  2. If you must change any of the current values, then:

    1. To modify the value of max-shm-memory to 6 GB:

      # prctl -n project.max-shm-memory -v 6gb -r -i project user.root
      
      
    2. To modify the value of max-sem-ids to 256:

      # prctl -n project.max-sem-ids -v 256 -r -i project user.root
      

7 Creating Required Directories

Create directories with names similar to the following, and specify the correct owner, group, and permissions for them:

The Oracle base directory must have 3 GB of free disk space, or 4 GB of free disk space if you choose not to create a separate Oracle data file directory.


Note:

If you do not want to create a separate Oracle data file directory, you can install the data files in a subdirectory of the Oracle base directory. However, this is not recommended for production databases.

To determine where to create these directories:

  1. Enter the following command to display information about all mounted file systems:

    # df -k
    
    

    This command displays information about all the file systems mounted on the system, including:

    • The physical device name

    • The total amount, used amount, and available amount of disk space, in kilobytes

    • The mount point directory for that file system

  2. From the display, identify either one or two file systems that meet the following requirements:

    • A single file system with at least 1.2 GB of free disk space

    • Two or more file systems with at least 1.2 GB of free disk space in total

  3. Note the name of the mount point directory for each file system that you identified.

In the following examples, /u01 is the mount point directory used for the software, and /u02 is the mount point directory used for the Oracle data file directory. You must specify the appropriate mount point directories for the file systems on your system.

To create the required directories and specify the correct owner, group, and permissions for them:


Note:

In the following procedure, replace /u01 and /u02 with the appropriate mount point directories that you identified in Step 3 previously.

  1. Enter the following command to create subdirectories in the mount point directory that you identified for the Oracle base directory:

    # mkdir -p /u01/app/oracle
    
    
  2. If you intend to use a second file system for the Oracle Database files, then create an oradata subdirectory in the mount point directory that you identified for the Oracle data file directory (shown as /u02 in the examples):

    # mkdir /u02/oradata
    
    
  3. Change the owner and group of the directories that you created to the oracle user and the oinstall group:

    # chown -R oracle:oinstall /u01/app/oracle
    # chown -R oracle:oinstall /u02/oradata
    
    
  4. Change the permissions on the directories that you created to 775:

    # chmod -R 775 /u01/app/oracle
    # chmod -R 775 /u02/oradata
    

8 Configuring the oracle User's Environment

You run Oracle Universal Installer from the oracle account. However, before you start Oracle Universal Installer, you must configure the environment of the oracle user. To configure the environment, you must:

To set the oracle user's environment:

  1. Start a new terminal session.

  2. Enter the following command to ensure that X Window applications can display on this system:

    $ xhost fully_qualified_remote_host_name
    
    
  3. Complete one of the following steps:

    • If the terminal session is not connected to the system where you want to install the software, then log in to that system as the oracle user.

    • If the terminal session is connected to the system where you want to install the software, then switch user to oracle:

      $ su - oracle
      
      
  4. To determine the default shell for the oracle user, enter the following command:

    $ echo $SHELL
    
    
  5. Open the oracle user's shell startup file in any text editor:

    • C shell (csh or tcsh):

      % vi .login
      
      
  6. Enter or edit the following line in the shell startup file, specifying a value of 022 for the default file mode creation mask:

    umask 022
    
    
  7. If the ORACLE_SID, ORACLE_HOME, or ORACLE_BASE environment variable is set in the file, then remove the appropriate lines from the file.

  8. Save the file, and exit from the editor.

  9. To run the shell startup script, enter the following command:

    • Bourne shell, Bash shell on SUSE, or Korn shell:

      $ . ./.profile
      
      
    • C shell:

      % source ./.login
      
      
  10. If you are not installing the software on the local system, then enter a command similar to the following to direct X applications to display on the local system:

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY
      
      
    • C shell:

      % setenv DISPLAY local_host:0.0
      
      

    In this example, local_host is the host name or IP address of the system that you want to use to display Oracle Universal Installer (your workstation or PC).

  11. If you determined that the /tmp directory had insufficient free disk space when checking the hardware requirements, then enter the following commands to set the TMP and TMPDIR environment variables. Specify a directory on a file system with sufficient free disk space.

    • Bourne, Bash, or Korn shell:

      $ TMP=/directory
      $ TMPDIR=/directory
      $ export TMP TMPDIR
      
      
    • C shell:

      % setenv TEMP /directory
      % setenv TMPDIR /directory
      
      
  12. Enter commands similar to the following to set the ORACLE_BASE and ORACLE_SID environment variables:

    • Bourne, Bash, or Korn shell:

      $ ORACLE_BASE=/u01/app/oracle
      $ ORACLE_SID=sales
      $ export ORACLE_BASE ORACLE_SID
      
      
    • C shell:

      % setenv ORACLE_BASE /u01/app/oracle
      % setenv ORACLE_SID sales
      
      

    In these examples, /u01/app/oracle is the Oracle base directory that you created earlier, and sales is the name that you want to call the database (typically no more than five characters).

  13. Enter the following commands to ensure that the ORACLE_HOME and TNS_ADMIN environment variables are not set:

    • Bourne, Bash, or Korn shell:

      $ unset ORACLE_HOME
      $ unset TNS_ADMIN
      
      
    • C shell:

      % unsetenv ORACLE_HOME
      % unsetenv TNS_ADMIN
      
      
  14. To verify that the environment has been set correctly, enter the following commands:

    $ umask
    $ env | more
    
    

    Verify that the umask command displays a value of 22, 022, or 0022 and the environment variables that you set in this section have the correct values.

9 Mounting the Product Disc

On most Solaris systems, the product disc mounts automatically when you insert it into the drive. If the disc does not mount automatically, then follow these steps to mount it:

  1. Switch user to root:

    $ su - root
    
    
  2. If necessary, enter a command similar to the following to eject the currently mounted disc, then remove it from the drive:

    # eject
    
    
  3. Insert the disc into the disc drive.

  4. To verify that the disc mounted automatically, enter a command similar to the following:

    # ls /dvd/dvd0
    
    
  5. If this command fails to display the contents of the disc, then enter a command similar to the following:

    # /usr/sbin/mount -r -F hsfs /dev/dsk/cxtydzs2 /dvd
    
    

    In this example, /dvd is the disc mount point directory and /dev/dsk/cxtydzs2 is the device name for the disc device, for example /dev/dsk/c0t2d0s2.

  6. If Oracle Universal Installer displays the Disk Location dialog box, then enter the disc mount point directory path. For example:

    • Disc mounted automatically:

      /dvd/dvd0
      
      
    • Disc mounted manually:

      /dvd
      

10 Installing Oracle Database

After configuring the oracle user's environment, start Oracle Universal Installer and install Oracle Database, as follows:

  1. To start Oracle Universal Installer, enter the following commands:

    • If the installation files are on disc, enter commands similar to the following, where directory_path is the path of the db directory on the DVD:

      $ cd /tmp
      $ /directory_path/runInstaller
      
      
    • If the installation files are on the hard disk, change directory to the db directory and enter the following command:

      $ ./runInstaller
      
      

    If Oracle Universal Installer does not start, then refer to Oracle Database Installation Guide for Solaris Operating System (SPARC 64-Bit) for information about how to troubleshoot X Window display problems.

  2. The following table describes the recommended action for each Oracle Universal Installer screen. Use the following guidelines to complete the installation:

    • If you need more assistance, or if you want to choose an option that is not a default, then click Help for additional information.

    • If you encounter errors while installing or linking the software, then refer to Oracle Database Installation Guide for Solaris Operating System (SPARC 64-Bit) for information about troubleshooting.


    Note:

    If you have completed the tasks listed previously, then you can complete the installation by choosing the default values on most screens.

    Screen Recommended Action
    Select Installation Method The Basic Installation option is selected by default.

    Specify the directory path of the Oracle home. Ensure that the UNIX DBA group oinstall is selected. If you want to create a starter database, then specify a name and password for it. Then, click Next.

    Specify Inventory Directory and Credentials This screen is displayed only during the first installation of Oracle products on a system.

    Specify the full path of the Oracle Inventory directory. Ensure that the operating system group selected is oinstall. Then, click Next.

    Product-Specific Prerequisite Checks Verify that all of the prerequisite checks succeed, then click Next.

    Oracle Universal Installer checks the system to verify that it is configured correctly to run Oracle software. If you have completed all of the preinstallation steps in this guide, all of the checks should pass.

    If a check fails, then review the cause of the failure listed for that check on the screen. If possible, rectify the problem and rerun the check. Alternatively, if you are satisfied that your system meets the requirements, then you can select the check box for the failed check to manually verify the requirement.

    Summary Review the information displayed on this screen, and then click Install.
    Install This screen displays status information while the product is being installed.
    Configuration Assistants This screen displays status information for the configuration assistants that configure the software and create a database. When the message is displayed at the end of this process, click OK to continue.
    Execute Configuration Scripts When prompted, read the instructions and then run the scripts mentioned on this screen. Click OK to continue.
    End of Installation The configuration assistants configure several Web-based applications, including Oracle Enterprise Manager Database Control. This screen displays the URLs configured for these applications. Make a note of the URLs used. The port numbers used in these URLs are also recorded in the following file:
    oracle_home/install/portlist.ini
    
    

    To exit from Oracle Universal Installer, click Exit and then click Yes.


11 Installing Products from the Oracle Database 10g Companion CD

The Oracle Database 10g Companion CD contains additional products that you can install. Whether you need to install these products depends on which Oracle Database products or features you plan to use. If you plan to use the following products or features, then you must complete the Oracle Database 10g Products installation from the Companion CD:

For more information about installing software from the Companion CD, refer to Oracle Database Companion CD Quick Installation Guide for Solaris Operating System (SPARC 64-Bit).

12 What to Do Next?

To become familiar with this release of Oracle Database, it is recommended that you complete the following tasks:

13 Additional Information

This section contains information about the following:

Product Licenses

You are welcome to install and evaluate the products included in this media pack for 30 days under the terms of the Trial License Agreement. However, you must purchase a program license if you want to continue using any product after the 30 day evaluation period. See the following section for information about purchasing program licenses.

Purchasing Licenses, Version Updates, and Documentation

You can purchase program licenses, updated versions of Oracle products, and printed versions of Oracle documentation from the Oracle Store Web site:

http://oraclestore.oracle.com

Contacting Oracle Support Services

If you have purchased Oracle Product Support, you can call Oracle Support Services for assistance 24 hours a day, seven days a week. For information about purchasing Oracle Product Support or contacting Oracle Support Services, go to the Oracle Support Services Web site:

http://www.oracle.com/support

Locating Product Documentation

Documentation for Oracle products is available in both HTML and Adobe portable document format (PDF) formats from several locations:

To view PDF documents, download the free Adobe Acrobat Reader from the Adobe Web site, if necessary:

http://www.adobe.com

14 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.