Skip Headers

Oracle® Developer Suite Installation Guide 10g (9.0.4) for Windows, Linux, Solaris, and HP-UX Part No. B10579-02 |
| Library | Contents | Index

# 2 Getting Started

This chapter describes the Oracle Developer Suite and Oracle Developer Suite Documentation Library hardware and software requirements. The topics include:

- Hardware Requirements

- Operating Environments Supported

- Operating Environment Software Requirements

- Certified Software

- Online Documentation Requirements

- Coexistence in One Oracle Home

- Directories Used by the Installer

- Preinstallation Tasks

- Preparing to Start the Installer

## 2.1 Hardware Requirements

Table 2-1 contains the basic hardware requirements for Oracle Developer Suite.

Table 2-1 Oracle Developer Suite Hardware Requirements

Hardware Item | Requirements
--- | ---
CPU | One of the following: A Pentium or compatible processor (500 MHz recommended) A SPARC processor (200 MHz recommended) An HP PA-RISC 64-bit processor (300 MHz recommended)
Memory | 128 MB Foot 1
Disk Space Foot 2 | J2EE Development Windows: 508 MB Solaris: 528 MB HP-UX: 1.1 GBFoot 3 Linux: 600 MB Business Intelligence (Windows only) 636 MB Rapid Application Development (Windows only) 943 MB Complete Windows - 943 MB Solaris - 865 MB HP-UX: 1.6 GBFootref 3 Linux: 850 MB
Total Pagefile Size, TMP, or Swap SpaceFoot 4 | Windows: 384 MB Linux, Solaris, HP-UX: 500 MB
Video | The computer must be capable of displaying a minimum of 256 colors.

Footnote 1 Minimum required to install. This is not the minimum for all Oracle Developer Suite components. See Table 2-2 for individual component memory requirements.
Footnote 2 Disk space required for installing English language only. The actual disk space required depends on the languages selected for installation. Additional temporary disk space of 50 MB, typically on the C drive, is also required.
Footnote 3 The disk space requirement for HP-UX is larger than for other operating environments because both 32-bit and 64-bit Oracle client side libraries for HP-UX are installed.
Footnote 4 If you are using Oracle9i JDeveloper in a multiuser Linux, Solaris, or HP-UX environment, you should use 1 GB swap space.

Table 2-2 contains the memory requirements for each Oracle Developer Suite component.

Table 2-2 Memory Requirements for Oracle Developer Suite Components

Component | Memory
--- | ---
Oracle9i JDeveloper (including Oracle Business Intelligence Beans, and UIX and Bali subcomponents) | Minimum: 256 MB Recommended: 512 MB
Oracle Reports Developer | Minimum: 128 MB Recommended: 256 MB
Oracle Discoverer Administrator | Minimum: 128 MB Recommended: 256 MB
Oracle Discoverer Desktop | 128 MB
Oracle Forms Developer | Minimum: 128 MB Recommended: 256 MB
Oracle Software Configuration Manager | 256 MB
Oracle Designer | 256 MB

## 2.2 Operating Environments Supported

Oracle Developer Suite is available for the Microsoft Windows NT/2000/XP Professional, Sun Solaris, HP PA-RISC HP-UX (64-bit), and Linux x86 operating environments. Table 2-3 lists the operating environments and the Oracle Developer Suite components that are installed with each environment.

Note: In this document, the term "Linux" refers to Linux x86 operating environments.

Table 2-3 Operating Environments and Oracle Developer Suite Components

Component | NT/2000/XP Professional | Solaris | Linux | HP-UX
--- | --- | --- | --- | ---
Oracle9i JDeveloper (including Oracle Business Intelligence Beans, and UIX and Bali subcomponents) | YES | YES | YES | YES
Oracle Reports Developer | YES | YES | YES | YES
Oracle Discoverer Administrator (formerly Discoverer Administration Edition) including Oracle Discoverer Desktop | YES | no | no | no
Oracle Forms Developer | YES | YES | YES | YES
Oracle Software Configuration Manager | YES | no | no | no
Oracle Designer | YES | no | no | no

Linux, Solaris, and HP-UX Notes:

- Oracle9i Developer Suite Release 2 (9.0.2) for Linux, Solaris, and HP-UX included the full Windows distribution pack. The Windows distribution pack for Oracle Developer Suite 10g (9.0.4) may not be in the initial Linux, Solaris, and HP-UX release pack. You will receive it when it becomes available; meanwhile, you will be able to download it from Oracle Technology Network (`http://otn.oracle.com`).

- The following Linux, Solaris, and HP-UX desktops have been certified for JDeveloper:

  - Solaris/CDE

  - HP-UX/CDE

  - HP-UX/VUE

  - Linux/GNOME

  - Linux/KDE2

## 2.3 Operating Environment Software Requirements

This section lists the operating environment requirements for Windows, Linux, Solaris, and HP-UX.

### 2.3.1 Windows Operating Environment

Table 2-4 contains the Windows operating environment software requirements for Oracle Developer Suite.

Table 2-4 Oracle Developer Suite Windows Software Requirements

Software Item | Requirement
--- | ---
Windows Operating Environment | Microsoft Windows NT 4.0 with Service Pack 6a Microsoft Windows 2000 Service Pack 3 or greater Microsoft Windows XP Professional Edition Service Pack 1 or greater

Note: Newer versions of Windows allow you to use a system drive other than C. This guide refers to the system drive as the "system default drive." You are not limited to using C as the system default drive. Most examples in this guide use C as the system default drive.

### 2.3.2 Solaris Operating Environment for Sun SPARC workstations

For Solaris running on Sun SPARC workstations, Oracle Developer Suite requires either Solaris 8 (2.8) or Solaris 9 (2.9). Table 2-5 contains the Solaris patchset requirements for Oracle Developer Suite. You can download the patches from

`http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/J2SE`.

Note: Oracle9i JDeveloper running on Solaris requires the CDE windows manager.

Table 2-5 Solaris Operating Environment Patchset Requirements

Software Item | Requirement
--- | ---
Solaris 8 (2.8) | 108652-74: X11 6.4.1: Xsun 108921-17: CDE 1.4: dtwm 108940-57: Motif 1.2.7 and 2.1.1: Runtime library patch 112003-03 Unable to load fontset in 64-bit Solaris 8 iso-1 or iso-15 108773-18: IIIM and X input & output method 112138-01: usr/bin/domainname patch 111310-01 /usr/lib/libdhcpagent.so.1 109147-26 linker 111308-04 /usr/lib/libmtmalloc.so.1 112438-02 /kernel/drv/random 108434-13: 32-bit shared library patch for C++ 111111-03 /usr/bin/nawk 112396-02 /usr/bin/fgrep 110386-03 RBAC Feature 111023-02 /kernel/fs/mntfs, /kernel/fs/sparcv9/mntfs 108987-13 Patch for patchadd and patchrm 108528-24: kernel update 108989-02 /usr/kernel/sys/acctctl , /usr/kernel/sys/exacctsys 108993-26 LDAP2 client, libc, libthread and libnsl libraries
Solaris 9 (2.9) | 113096-03: X11 6.6.1: OWconfig 112785-26 X11 6.6.1: Xsun

Table 2-6 contains the Solaris 8 (2.8) and Solaris 9 (2.9) package requirements for Oracle Developer Suite. To verify that an operating system package is installed on your computer, run the `pkginfo` command with the name of the package. Do this for each package listed. The syntax for `pkginfo` is:

`pkginfo` `package_name`

For example:

`prompt>``pkginfo SUNWarc`

If your computer is missing a package, contact your system administrator.

Table 2-6 Solaris Operating Environment Package Requirements

Software Item | Requirement
--- | ---
Solaris 8 (2.8) | SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1of SUNWxwfnt SUNWi1cs SUNWi15cs
Solaris 9 (2.9) | SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1of SUNWxwfnt SUNWi1cs SUNWi15cs

### 2.3.3 HP-UX Operating Environment

For the HP PA-RISC HP-UX (64-bit) operating environment, Oracle Developer Suite requires either version 11.00 or version 11.11. Table 2-7 contains the HP-UX operating environment software requirements for Oracle Developer Suite. You can download the HP-UX operating environment patches from `http://itresourcecenter.hp.com`.

Table 2-7 HP-UX Operating Environment Software Requirements

Software Item | Requirement
--- | ---
HP-UX Operating Environment | HP PA-RISC HP-UX 11.00 (64-bit) HP PA-RISC HP-UX 11.11 (64-bit)
HP-UX 11.00 Patches | Sept 2002 Quality Pack (QPK1100 B.11.00.58.5) PHKL_27813 PHSS_26559 Required HP-UX 11.00 patches for Java 2 SDK 1.4.1.05 for PA-RISC (which can be found at `http://www.hp.com/products1/unix/java/patches/index.html`, or `http://www.hp.com/products1/unix/java/java2/sdkrte14/downloads/index.html`)
HP-UX 11.00 Software and Packages | HP Java 2 SDK 1.4.1 (version 1.4.1.05 or higher) for PA-RISC X11MotifDevKit (B.11.00.01 or higher)
HP-UX 11.11 Patches | Dec 2001 Consolidate Patches (Dec01GQPK11i_Aux_Patch B.03.02.06) PHKL_25212 PHKL_25506 PHKL_27091 PHKL_28267 PHNE_28089 PHSS_24638 PHSS_26263 PHSS_26792 PHSS_26793 Required HP-UX 11.11 patches for Java 2 SDK 1.4.1.05 for PA-RISC (which can be found at `http://www.hp.com/products1/unix/java/patches/index.html`, or `http://www.hp.com/products1/unix/java/java2/sdkrte14/downloads/index.html`)
HP-UX 11.11 Software and Packages | HP Java 2 SDK 1.4.1 (version 1.4.1.05 or higher) for PA-RISC X11MotifDevKit (B.11.11.01 or higher)

### 2.3.4 Linux Operating Environment

Table 2-8 contains the Linux x86 operating environment software requirements for Oracle Developer Suite. For more information on Red Hat Linux patches, see `http://www.redhat.com`. For more information on United Linux patches, see `http://www.unitedlinux.com`.

Table 2-8 Linux x86 Operating Environment Software Requirements

Software Item | Requirement
--- | ---
Linux x86 Operating Environment | Red Hat Enterprise Linux AS 2.1 Red Hat Enterprise Linux ES 2.1 United Linux 1.0
Red Hat Linux Operating System Patches | Kernel Errata 25 (`2.4.9-e.25```)
Red Hat Linux Operating System Software and Packages | gcc-2.96 pdksh-5.2.14 openmotif-2.1.30 XFree86-4.1.0
United Linux Operating System Patches | For the most current information, refer to the Oracle Developer Suite 10g Release Notes Addendum, which is available at Oracle Technology Network (`http://otn.oracle.com`).
United Linux Operating System Software and Packages | gcc_old-2.95 pdksh-5.2.14 openmotif-2.1.30 xf86-4.2.0

## 2.4 Certified Software

You can view a complete list of certified software for Oracle Developer Suite on OracleMetaLink, at

`http://metalink.oracle.com`.

## 2.5 Online Documentation Requirements

The Oracle Developer Suite Documentation Library contains online documentation in HTML and Adobe PDF formats. See Appendix C, "Installing the Documentation Library" for instructions on installing and viewing the contents of the Documentation Library.

Table 2-9 contains the tools and disk space requirements for the Oracle Developer Suite Documentation Library.

Table 2-9 Online Documentation Requirements

Item | Requirements
--- | ---
Online Readers | Requires one of the following: HTML Netscape Navigator 4.7 or higher Microsoft Internet Explorer 5.0 or higher PDF Acrobat Reader 3.0 or higher Acrobat Reader+Search 3.0 or higher Acrobat Exchange 3.0 or higher PDFViewer Web browser plug-in 1.0 or higher
Disk Space | 130 MB

## 2.6 Coexistence in One Oracle Home

This section provides information about the coexistence of Oracle products in one Oracle home, and guidelines for installing multiple Oracle products on one computer.

### 2.6.1 Oracle Home Considerations

Your Oracle home is the top-level directory in which you install Oracle software.

- Oracle Developer Suite 10g (9.0.4) cannot share the same Oracle home with its previous versions (Oracle9iDS Release 2 (9.0.2) or Oracle Internet Developer Suite Release 1.0.2.x).

- Oracle Developer Suite 10g (9.0.4) cannot share the same Oracle home with any Oracle databases, including Oracle9i Database Release 2.

- Oracle Developer Suite 10g (9.0.4) cannot share the same Oracle home with a Oracle Application Server Forms and Reports Services 10g standalone server instance.

- Oracle Developer Suite 10g (9.0.4) can coexist in the same Oracle home with any installation of Oracle Application Server 10g (9.0.4), with the exception of Oracle Application Server Infrastructure.

  Note: This does not apply to any other version of Oracle Application Server.

- For Linux, Solaris, and HP-UX only: If there are existing Oracle homes set on the computer where you are installing Oracle Developer Suite, refer to Section 2.8.5.1.1, "Preventing Conflicts With Other Oracle Homes".

In this guide, directory paths may contain the placeholder text `oracle_home`, which represents the path to your actual Oracle home directory.

Note: If you install Oracle Developer Suite 10g (9.0.4) and Oracle Application Server 10g (9.0.4) to the same Oracle home, do not try to start Oracle Application Server Containers for J2EE (OC4J) on port 8888 from `oracle_home``\j2ee\home`. If you do, the OC4J instance will fail.

### 2.6.2 Performing Multiple Installations of Oracle Developer Suite

The following guidelines apply to installing multiple instances of Oracle Developer Suite 10g (9.0.4) on the same computer. The guidelines also apply to installing Oracle Developer Suite 10g (9.0.4) on a computer that has existing installations of Oracle9iDS or Oracle Internet Developer Suite:

1. Make sure you reboot the computer after you install Oracle Developer Suite the first time.

2. Make sure you have sufficient disk space to handle all of your installations. See Table 2-1 to determine the disk space requirements.

3. Install subsequent instances into a different Oracle home from the previous one.

4. Reboot the computer after the last installation is completed (Windows only).

### 2.6.3 Oracle Developer Suite Installation and Oracle Databases

Note: Oracle Developer Suite can not share an Oracle home with an Oracle database.

When you install Oracle Developer Suite, and you have either already installed an Oracle database on the same computer, or plan to install an Oracle database on the same computer:

- Make sure you have sufficient disk space to handle both installations. See the specific Oracle database installation guide and Table 2-1 in this guide to determine the total disk space requirements.

- Windows only: If you have not installed the Oracle database, install it first, and then reboot the computer after the database installation is completed.

- Install Oracle Developer Suite into a different Oracle home from the Oracle database.

- Windows only: Reboot the computer after you have installed Oracle Developer Suite.

## 2.7 Directories Used by the Installer

The installer writes files to the following directories:

Table 2-10 Directories Used by the Installer

Directory | Description
--- | ---
Oracle home directory | This directory contains Oracle Developer Suite files. You specify this directory when you install Oracle Developer Suite. For more information, see Section 2.6.1, "Oracle Home Considerations".
Inventory directory | The installer uses this directory to keep track of Oracle products that are installed on the computer. In subsequent installations, the installer uses the same inventory directory. For more information, see Section 2.9.3, "The Installer Inventory Directory".
Linux, Solaris, and HP-UX only: `/var/opt/oracle` or `/etc` directories. | This directory contains information about locations of Oracle homes on your Linux, Solaris, or HP-UX computer. For more information, see Section 2.9.3, "The Installer Inventory Directory". Note: On a Windows computer, this information is stored in the Windows Registry.
Linux, Solaris, and HP-UX only: `/tmp` directory | The installer writes files needed only during installation to a temporary directory. By default, the temporary directory is `/tmp`. To specify a different directory, set the `TMP` environment variable.
Windows only: temp directory | The installer writes files needed only during installation to a temporary directory. The installer uses the directory specified in the `%TEMP%` system environment variable.

## 2.8 Preinstallation Tasks

Before installing Oracle Developer Suite, review the Oracle Developer Suite release notes. The release notes are available in the Oracle Developer Suite Documentation Library. To view the release notes, see Section C.3.1, "Viewing the Release Notes from Disk". The latest release notes and release notes addendum are also available on Oracle Technology Network at

`http://otn.oracle.com`

The preinstallation tasks for Oracle Developer Suite are divided into the following parts:

- General Checklist

- Setting the Locale

- Using Assistive Technologies (Windows only)

- Installing Java Access Bridge (Windows only)

- Setting Environment Variables (Linux, Solaris, and HP-UX only)

- Creating Linux, Solaris, and HP-UX Accounts and Groups

- Completing Component-specific Preinstallation Tasks

- Information Needed During Installation

- Migration or Upgrading

### 2.8.1 General Checklist

1. HP-UX only:

   1. Download the HP Java 2 SDK 1.4.1 (version 1.4.1.05 or higher) for PA-RISC (for HP-UX 11.00 or HP-UX 11.11, depending on your operating system version) from `http://www.hp.com/products1/unix/java/java2/sdkrte14/index.html`.

   2. Install the SDK.

2. - If you have Windows NT, 2000, or XP Professional, ensure that you are logged on to your computer as a member of the Administrators group.

   - On Linux, Solaris, or HP-UX, ensure that you are not logged in as the `root` user; otherwise, you will not be able to run the installer. See Section 2.8.6, "Creating Linux, Solaris, and HP-UX Accounts and Groups" for more information.

   - Ensure that your `PATH,CLASSPATH,LD_LIBRARY_PATH`(Linux, Solaris, and HP-UX only), and`SHLIB_PATH` (HP-UX only) environment variable values do not exceed 1,024 characters. Variable values greater than 1,204 characters will generate errors such as "Word too long" during installation.

   - Stop all Oracle services or Oracle processes, and close all other open applications.

### 2.8.2 Setting the Locale

The installer user interface language is based on settings in the Java Virtual Machine (JVM) locale, which is based on the operating environment locale. To run the installer with a particular locale, set your operating environment's locale before you start the installer.

The installer supports the locale languages listed in Table 2-11:

Table 2-11 Languages Displayable by the Installer

Language | ISO-639 Language Code
--- | ---
English | en
French | fr
German | de
Italian | it
Japanese | ja
Korean | ko
Brazilian Portuguese | pt_BR
Simplified Chinese | zh_CN
Traditional Chinese | zh_TW

If your locale is not listed in this table, the installer appears in English.

### 2.8.3 Using Assistive Technologies (Windows only)

If you use assistive technologies such as screen readers to work with Java-based applications and applets, run `access_setup.bat` before starting your screen reader.

The file `access_setup.bat` is located on your CD-ROM Disk 1, or on your DVD:

Media | Location of File
--- | ---
CD-ROM | `\install\win32`
DVD | `\developer_suite\install\win32`

### 2.8.4 Installing Java Access Bridge (Windows only)

If you use assistive technologies such as screen readers to work with Java-based applications and applets, the Windows-based computer where you are installing Oracle Developer Suite must have Sun's Java Access Bridge installed in all the Java virtual machine locations on the computer.

The installer installs files for JDK/JRE 1.4.1 and JDK/JRE 1.1.8 on your computer, but it will install Java Access Bridge 1.0.3 files in the JDK/JRE 1.4.1 location only.

If you use assistive technologies, you should perform one of the following steps:

- If you don't have JDK/JRE 1.1.8 installed on your computer:

  Proceed with your installation. After you have finished installing Oracle Developer Suite, ensure that you have Java Access Bridge 1.0.3 installed in all your JDK/JRE locations. This will ensure that all your applications that require assistive technologies work correctly.

- If you do have JDK/JRE 1.1.8 on your computer:

  You must install the production version of Java Access Bridge 1.0.2 in the JDK/JRE 1.1.8 location on your computer before you install Oracle Developer Suite.

  To download and install Java Access Bridge 1.0.2:

  1. Download the zip file for Java Access Bridge 1.0.2 from

     `http://java.sun.com/products/accessbridge/`.

     Refer to the Java Access Bridge documentation available from the web site for installation instructions and other information.

  2. After downloading the file, extract the contents to a folder; for example, `accessbridge_home`.

  3. Install Java Access Bridge by running `install.exe` from the `accessbridge_home``\installer` folder, where

     `accessbridge_home` is the folder you created in the previous step.

  4. Confirm that you want to install the Java Access Bridge into each of the Java virtual machines displayed in the dialog.

     Note: Do not install Java Access Bridge 1.0.2 into a Java virtual machine with a version higher than 1.1.18.

  5. Click OK when you see the Installation Completed message.

### 2.8.5 Setting Environment Variables (Linux, Solaris, and HP-UX only)

The tasks in this section are required on Linux, Solaris, and HP-UX platforms only.

#### 2.8.5.1 ORACLE_HOME

##### 2.8.5.1.1 Preventing Conflicts With Other Oracle Homes

To prevent a conflict between the software in an existing Oracle home and the Oracle Developer Suite installation, you must remove all references to the existing Oracle home in your environment. Follow these steps to remove these references.

1. Unset your existing Oracle home variable by using the following command.

   C shell | Bourne/Korn shell
   --- | ---
   `prompt>` `unsetenv ORACLE_HOME` | `prompt>` `ORACLE_HOME=; export ORACLE_HOME`

2. In your `PATH`, `CLASSPATH,LD_LIBRARY_PATH`, and `SHLIB_PATH` (HP-UX only) environment variables, remove any references to the environment variable `ORACLE_HOME`.

#### 2.8.5.2 DISPLAY

Setting the `DISPLAY` environment variable allows you to run the installer remotely and view the installer UI from your local computer.

On the remote computer, set `DISPLAY` to the system name or IP address of your local computer.

Note: A PC X emulator can be used to run the install if it supports a PseudoColor color model or PseudoColor visual. Set the PC X emulator to use a PseudoColor visual, and then start the installer. Refer to the X emulator documentation for instructions on how to change the color model or visual settings.

If you get an Xlib error similar to "Failed to connect to server", "Connection refused by server", or "Can't open display" when starting the installer, then run the following commands on your local computer:

Shell Types | On the remote computer | On your local computer
--- | --- | ---
C shell | `prompt>` `setenv DISPLAY` `hostname``:0.0` | `prompt>` `xhost +` `server_name`
Bourne or Korn shell | `prompt>` `DISPLAY=``hostname``:0.0`; `export DISPLAY` | `prompt>` `xhost + server_name`

#### 2.8.5.3 TMP

During installation, the installer uses a temporary directory for swap space. You must ensure that this directory meets the hardware requirements listed in Table 2-1 before you start your installation. The installation may fail if you do not have sufficient space. The installer checks for the `TMP` environment variable to locate the temporary directory. If this environment variable does not exist, then the installer uses the `/tmp` directory.

The following are instructions for setting the `TMP` environment variable.

C shell | Bourne/Korn shell
--- | ---
`prompt>` `setenv TMP` `full_path` | `prompt>` `TMP=``full_path``; export TMP`

#### 2.8.5.4 TNS_ADMIN

`TNS_ADMIN` points to the directory where network configuration files are stored.

If `TNS_ADMIN` is set to an existing directory on your computer, you will have conflicts between that directory and the directory where the Oracle Developer Suite network configuration files are created. You will also have conflicts if the configuration files are in a common directory outside of the Oracle home for your other Oracle products. For example, your computer may use `/var/opt/oracle/tnsnames.ora` for database aliases.

To prevent conflicts between the network configuration files for different Oracle products, copy the existing configuration files from either the existing `TNS_ADMIN` directory or the common directory to the other product's `oracle_home``/network/admin` and unset `TNS_ADMIN` using the following command:

C shell | Bourne/Korn shell
--- | ---
`prompt>` `unsetenv TNS_ADMIN` | `prompt>` `TNS_ADMIN=;export TNS_ADMIN`

### 2.8.6 Creating Linux, Solaris, and HP-UX Accounts and Groups

The tasks in this section are required on Linux, Solaris, and HP-UX platforms only.

#### 2.8.6.1 Group Name for the Installer Inventory

Create a group that has read and write access to the `oraInventory` directory. The installer uses the `oraInventory` directory to keep track of the Oracle products installed on a computer. You can allow a user to install Oracle products to the computer by giving it write access to `oraInventory`. To do this, make all the users members of the same group. This guide refers to the group as the `devsuitegrp` group.

Use a an operating environment utility to create the group. For example:

- On Solaris, use the `admintool` or `groupadd` utility.

- On HP-UX, use the `SAM` utility.

- On Linux x86, use `/usr/sbin/groupadd` and`/usr/sbin/useradd`.

These utilities are described in your operating environment documentation.

The `devsuitegrp` group will own the installer's `oraInventory` directory. Any user account that runs an Oracle installation must be a member of the `devsuitegrp` group.

#### 2.8.6.2 User for Oracle Software

If this is the first time you are installing Oracle software on this computer, Oracle recommends that you start by creating a new user. Use this user specifically for installing and administering Oracle software.

Create the user with the properties listed in Table 2-12.

Table 2-12 Oracle Account Properties

Variable | Property
--- | ---
name | Choose any name This guide uses the name `oracle`.
Group Identifier | The `devsuitegrp` group.
Home directory | Choose a home directory consistent with other user home directories. The home directory of the `oracle` account does not have to be the same as the Oracle home directory.
Login Shell | The default shell can be either the C, Bourne, or Korn shell.

Note: Use this user only for installing and maintaining Oracle software. Never use it for purposes unrelated to the installer. Do not use `root` for the Oracle user.

### 2.8.7 Completing Component-specific Preinstallation Tasks

Components that are not listed here have no component-specific preinstallation tasks.

#### 2.8.7.1 Oracle Software Configuration Manager

There are no specific preinstallation requirements. However, to effectively use Software Configuration Manager, Oracle recommends that you review the Oracle SCM Repository Installation Guide, which is available from the Start menu of the Oracle SCM client.

### 2.8.8 Information Needed During Installation

The installer guides you through the installation screens. Depending on your operating environment and the installation options you select, you will need the information listed in Table 2-13.

Table 2-13 Information Needed During Installation

Item | Installation Type | Example
--- | --- | ---
Oracle home name and path for Oracle Developer Suite Foot 1 | All (Windows, Linux, Solaris, and HP-UX) | Name: `DevSuiteHome` Path: `C:\DevSuiteHome` or `/private/DevSuiteHome`
Linux, Solaris, and HP-UX group name | All (Linux, Solaris, and HP-UX only) | `devsuitegrp`
Outgoing mail server name | Business Intelligence, Rapid Application Development, Complete (all platforms). Used only by Oracle Application Server Reports Services. | `mysmtp01.mycorp.com`
Java SDK directory | All (HP-UX only) | `/opt/java/java.1.4.1`

Footnote 1 See Section 2.6.1, "Oracle Home Considerations" for more details.

### 2.8.9 Migration or Upgrading

Review Appendix A, "Upgrade Notes" if you are migrating or upgrading from:

- Oracle9iDS Release 2 (9.0.2)

- Oracle Internet Developer Suite release 1, version 1.0.2.x (the former version of Oracle9i Developer Suite)

- A 9.0.3 or earlier version of any Oracle Developer Suite component (for instance, Oracle JDeveloper, Oracle Repository, and so forth)

## 2.9 Preparing to Start the Installer

This section introduces Oracle Universal Installer and provides you information that you should know before you start the installation.

### 2.9.1 About Oracle Universal Installer

Oracle Developer Suite uses Oracle Universal Installer to install components and to configure environment variables. The installer guides you through each step of the installation process.

Oracle Universal Installer automates the tasks of:

- Providing installation options for products, based on the target computer's operating environment

- Detecting pre-set environment variables and configuration settings

- Setting environment variables and configuration during installation

- Deinstalling products

### 2.9.2 Installer Prerequisite Checks

The installer does an automatic prerequisite check on your computer before starting the installation. The following tables list the prerequisite checks that the installer performs.

Table 2-14 lists the automatic prerequisite checks for Windows:

Table 2-14 Installer Prerequisite Checks for Windows

Prerequisite Checks | See Also
--- | ---
Verify the computer can display a minimum of 256 colors | Table 2-1, "Oracle Developer Suite Hardware Requirements"
Verify the minimum CPU speed | Table 2-1, "Oracle Developer Suite Hardware Requirements"
Verify the operating system requirements | Table 2-3, "Operating Environments and Oracle Developer Suite Components" Table 2-4, "Oracle Developer Suite Windows Software Requirements"

Table 2-15 lists the automatic prerequisite checks for Solaris on Sun SPARC computers:

Table 2-15 Installer Prerequisite Checks for Solaris

Prerequisite Checks | See Also
--- | ---
Verify the computer can display a minimum of 256 colors | Table 2-1, "Oracle Developer Suite Hardware Requirements"
Verify that the minimum swap space is available | Table 2-1, "Oracle Developer Suite Hardware Requirements"
Verify the minimum CPU speed | Table 2-1, "Oracle Developer Suite Hardware Requirements"
Verify Operating System requirements | Table 2-3, "Operating Environments and Oracle Developer Suite Components" Table 2-5, "Solaris Operating Environment Patchset Requirements" Table 2-6, "Solaris Operating Environment Package Requirements"

Table 2-16 lists the automatic prerequisite checks for Linux x86:

Table 2-16 Installer Prerequisite Checks for Linux

Prerequisite Checks | See Also
--- | ---
Verify that the minimum swap space is available | Table 2-1, "Oracle Developer Suite Hardware Requirements"
Verify the minimum CPU speed | Table 2-1, "Oracle Developer Suite Hardware Requirements"
Verify Operating System requirements | Table 2-3, "Operating Environments and Oracle Developer Suite Components" Table 2-8, "Linux x86 Operating Environment Software Requirements"

Table 2-17 lists the automatic prerequisite checks for HP-UX:

Table 2-17 Installer Prerequisite Checks for HP-UX

Prerequisite Checks | See Also
--- | ---
Verify that the minimum swap space is available | Table 2-1, "Oracle Developer Suite Hardware Requirements"
Verify the minimum CPU speed | Table 2-1, "Oracle Developer Suite Hardware Requirements"
Verify Operating System requirements | Table 2-3, "Operating Environments and Oracle Developer Suite Components" Table 2-7, "HP-UX Operating Environment Software Requirements"

### 2.9.3 The Installer Inventory Directory

The installer creates the inventory directory the first time it runs on your computer. The inventory directory keeps a record of the products that the installer has installed, as well as other installation information. If you have previously installed Oracle products on your computer, then you may already have an inventory directory.

Please review the following information about the inventory directory:

- Do not delete or alter the inventory directory or its contents. Doing so can prevent the installer from locating products that you have installed on your computer.

- For Windows, the installer automatically creates the inventory directory as `system_default_drive``:\Program Files\Oracle\Inventory` when you install the first Oracle product on your computer. The value of s`ystem_default_drive` is normally "C:", and is set in the Windows Registry.

- For Linux, Solaris, and HP-UX, the default directory location is listed in the file `/var/opt/oracle/oraInst.loc` (`/etc/oraInst.loc` on Linux). The first time you install an Oracle product on your computer, the installer prompts you for an existing directory to use as the inventory directory. The installer then creates `oraInst.loc` and lists your inventory directory in it.

- If you specify a Linux, Solaris, or HP-UX group name during installation, you are granting any user that belongs to that group the permission to write to the `oraInventory` directory. Later on, if another user attempts to run the installer, then they must have user-level permission to write to the `oraInventory` directory, or they must belong to the group you specified. If they do not have permission, then the installation fails.

The installer writes a log of its actions to a file in the directory `system_default_drive``:\Program Files\Oracle\Inventory\logs` (Windows) or `inventory_location``/logs` (Linux, Solaris, and HP-UX). The log file name has the form

`installActions` `year``-``date``_``time``.log`.

### 2.9.4 Starting the Installer

Follow these instructions to start the installer:

#### 2.9.4.1 For Windows users

Note: If you encounter a Windows System Files error during installation, click OK to close the error dialog. Then follow the instructions for running the Windows System Files installation later in this section.

1. Stop all Oracle services such as an Oracle database.

2. CD-ROM:Insert the Oracle Developer Suite CD-ROM labeled "Disk 1" into your computer's CD-ROM drive.

   DVD: Insert the Oracle Developer Suite DVD labeled "Oracle Developer Suite and Documentation" into your computer's DVD drive.

3. CD-ROM: If you are not using the autorun feature, locate the program `setup.exe` in the root directory of the CD-ROM. Start the installer by running this program.

   DVD: If your are not using the autorun feature, locate the program `setup.exe` in the directory `\developer_suite` under the root directory of the DVD. Start the installer by running this program.

4. If you are using the autorun feature, the installer will start automatically. Click Install Oracle Developer Suite to start your installation.

5. For users of Windows assistive technologies: To disable the autorun feature, hold down the Shift key after inserting the CD-ROM or DVD. Alternatively, if the autorun window appears, press ALT-F4 to close the window. Then do one of the following:

   1. CD-ROM: To install Oracle Developer Suite, locate the program `setup.exe` in the root directory of the CD-ROM. Start the installer by running this program.

      DVD: To install Oracle Developer Suite, locate the program `setup.exe` in the directory `\developer_suite` under the root directory of the DVD. Start the installer by running this program.

   2. To browse the CD-ROM or DVD contents, use Windows Explorer.

   3. To learn about Oracle Developer Suite, point your browser to the file `\doc\welcome\index.htm` on the CD-ROM, or `\developer_suite\doc\welcome\index.htm` on the DVD.

Proceed to Section 3.1, "Installing Oracle Developer Suite" to continue.

##### 2.9.4.1.1 Windows System Files Installation

Oracle Developer Suite requires several files to be present in your Windows system directory. During the Oracle Developer Suite installation, files already present on your computer are examined to ensure that they meet the requirements for Oracle Developer Suite. If a file is not present or is present but outdated, the installer installs the required file.

If an outdated file is in use by another process at the time of installation, then the installer will stop and display an error dialog. This is because Windows needs to restart for the updated file to take effect. The installer cannot automatically shut down and then start up again after a system restart.

Oracle Developer Suite includes a supplementary installation for the required Windows system files. This installation will automatically reboot the computer if necessary when it is finished.

If you encounter the Windows System Files error during the Oracle Developer Suite installation, click OK to close the error dialog, then use the following instructions to start the Windows System Files installation. You cannot proceed with the Oracle Developer Suite installation if you do not run the Windows System Files installation.

To start the Windows System Files installation:

1. Click Exit to quit the installer.

2. Change to the root directory on the CD-ROM, or to the directory `\developer_suite` under the root directory of the DVD.

3. Run `wsf.exe`.

   The Windows System Files installer is controlled by script that attempts to find an existing Oracle home. If the installer does not find one, it displays a File Locations dialog. Choose your Oracle home from the dialog.

   Windows restarts automatically, if it is required; otherwise, the Windows System Files installation ends without displaying the Installation Finished dialog.

4. After Windows restarts, or when the Windows System Files installation finishes, restart the Oracle Developer Suite installation.

#### 2.9.4.2 For Linux, Solaris, and HP-UX users

Note: You need access to the `root` account.

For operating environments that do not support automatic mounting, you must manually mount the installation CD-ROM or DVD. You must have `root` privileges to mount or unmount a CD-ROM or DVD. Be sure to unmount a CD-ROM or DVD before removing it from the drive.

Note: The Oracle Developer Suite installation CD-ROM is in RockRidge format. The Oracle Developer Suite and Documentation DVD is in DVD-ROM format.

To mount the installation CD-ROM or DVD:

1. Stop all Oracle processes such as the Oracle database.

2. Read the section for your operating environment to get detailed mounting instructions:

   - Mounting CD-ROMs and DVDs to Solaris

   - Mounting CD-ROMs and DVDs to HP-UX

   - Mounting CD-ROMs and DVDs to Linux

##### 2.9.4.2.1 Mounting CD-ROMs and DVDs to Solaris

If your computer is set up for auto mounting, then the CD-ROM or DVD is mounted automatically to the directory specified in your auto mount configuration when you insert the disk into the drive.

If your computer is not set up for auto mounting, then you must mount the CD-ROM or DVD manually.

Follow these steps to mount the CD-ROM or DVD manually:

1. Insert the Oracle Developer Suite Disk 1 CD-ROM or the Oracle Developer Suite and Documentation DVD into the drive.

2. Log in as the `root` user.

3. Ensure that you have a mount point directory for the CD-ROM or DVD. For example, you can create the directory `/cdrom`:

   `#` `mkdir` `/cdrom`

4. Mount the CD-ROM or DVD drive to the mount point directory. For example, if your mount point directory is `/cdrom`, enter the following command:

   `#` `mount` `-r -F hsfs` `device_name` `/cdrom`

5. Log out as the `root` user.

6. Proceed to Section 2.9.4.2.4, "Running the Installer".

##### 2.9.4.2.2 Mounting CD-ROMs and DVDs to HP-UX

If your computer is set up for auto mounting, then the CD-ROM or DVD is mounted automatically to the directory specified in your auto mount configuration when you insert the disk into the drive.

If your computer is not set up for auto mounting, then you must mount the CD-ROM or DVD manually.

Note: Before executing any of the following steps, consult the man pages for `pfs_fstab`, `pfs_mount`, `pfs_mountd`, and `pfsd`.

Follow these steps to mount the CD-ROM or DVD manually:

1. Log in as the `root` user.

2. Use the following command to determine the CD-ROM or DVD device_file:

   `#` `ioscan -fun -C disk`

3. If there is not already an entry in the `/etc/pfs_fstab` file for your CD-ROM or DVD `device_file`, you must add one. As the root user, use a text editor to add a line to the `/etc/pfs_fstab` file following this format:

       device_file mount_point filesystem_type options frequency pass

   Example:

       /dev/dsk/c5t2d0 /SD_CDROM pfs-rrip ro 0 0

   Note: This example assumes the existence of an empty `/mnt/cdrom` directory. If one does not exist, create it.

4. Enter the following commands:

   `#` `nohup /usr/sbin/pfs_mountd &`

   `#` `nohup /usr/sbin/pfsd &`

5. Insert the Oracle Developer Suite Disk 1 CD-ROM or Oracle Developer Suite and Documentation DVD into your drive and mount the CD-ROM by entering the following command:

   `#` `/usr/sbin/pfs_mount /SD_CDROM`

6. Log out as the `root` user.

7. Proceed to Section 2.9.4.2.4, "Running the Installer".

##### 2.9.4.2.3 Mounting CD-ROMs and DVDs to Linux

If your computer is set up for CD-ROM or DVD auto mounting, then the CD-ROM or DVD is mounted automatically to the directory specified in your auto mount configuration when you insert the disk into the drive.

If your computer is not set up for auto mounting, then you must mount the CD-ROM or DVD manually.

Follow these steps to mount the CD-ROM or DVD manually:

1. Insert the Oracle Developer Suite Disk 1 CD-ROM or the Oracle Developer Suite and Documentation DVD into your drive.

2. Log in as the `root` user.

3. Ensure that you have a mount point directory for the CD-ROM or DVD. For example, you can create the directory `/mnt/cdrom`:

   `#` `mkdir /mnt/cdrom`

4. Ensure that the following line for `/dev/cdrom` is in `/etc/fstab`:

   `/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0`

   Note: The file /etc/fstab must contain this line exactly as it appears in the text. Replace any other form of the line with the line in the text.

5. Mount the CD-ROM or DVD drive to the mount point directory by entering the following command:

   `#` `/bin/mount /mnt/cdrom`

   This command mounts the CD-ROM or DVD to the mount point directory `/mnt/cdrom`.

6. Log out as the `root` user.

7. Proceed to Section 2.9.4.2.4, "Running the Installer".

##### 2.9.4.2.4 Running the Installer

After you mount the installation CD-ROM or DVD, you can start the installer.

To start the installer from the CD-ROM or DVD:

Note: Be sure you are not logged in as the `root` user when you start the installer. If you are, you will receive an error message and the installer will stop.

1. Log in with the user that you created for installing Oracle products (see Section 2.8.6.2, "User for Oracle Software").

2. Change to a directory other than the mount point directory or its subdirectories. For example, if your mount point directory is `/mnt/cdrom`, change to a directory other than `/mnt/cdrom` or its subdirectories.

3. CD-ROM: Start the installer by entering:

   `prompt>` `mount_point_directory``/runInstaller`

   DVD: Start the installer by entering:

   `prompt>` `mount_point_directory``/developer_suite/runInstaller`

This starts the installer. Proceed to Section 3.1, "Installing Oracle Developer Suite" for further instructions.

#### 2.9.4.3 Running the Installer in Silent or Non-Interactive Mode

See Appendix D, "Silent and Non-Interactive Install"