| Oracle® Developer Suite Installation Guide 10g Release 2 (10.1.2) for Solaris, Windows and Linux x86 B16012-04 |
|
 Previous |
 Next |
| Oracle® Developer Suite Installation Guide 10g Release 2 (10.1.2) for Solaris, Windows and Linux x86 B16012-04 |
|
Previous |
Next |
This chapter describes the Oracle Developer Suite and Oracle Developer Suite Documentation Library hardware and software requirements. The topics include:
You can obtain Oracle products from Oracle E-Delivery at http://edelivery.oracle.com/. Oracle products are distributed as "E-Packs". An E-Pack is an electronic version of the software that is also available to Oracle Customers on CD ROM or DVD ROM.
Refer to the CD/Media Pack description or the list of products that you purchased on your Oracle Ordering Document. Then, view the License List to help you decide which Product Pack you need to select in order to search for the appropriate E-Pack(s) to download. Prior to downloading, verify that the product you are looking for is in the License and Options section of the E-Pack Read Me. Oracle recommends that you print the Read Me to reference.
Refer to the Read Me link that is on each E-Pack Download page. In addition to listing the licensable products and options contained in the pack, the Read Me lists downloadable files that are required to run each product and which downloadable files are optional. Oracle recommends that you print the Read Me to reference.
In addition to having the required disk space necessary to install and run your Oracle software, you'll need to have sufficient disk space to download all the required software files and have enough disk space to extract them.
After extracting the software from the Zip files, you can burn them onto CD-ROM and install from them, or install from your computer's hard drive.
All Oracle E-Delivery files have been archived using Info-ZIP's highly portable Zip utility. After downloading one or more of the archives, you will need the UnZip utility (for UNIX or Windows platforms) or the WinZip utility (for Windows platforms) to extract the files.You must unzip the archive on the platform for which it was intended. For example, if you download the file for the Solaris Operating System (SPARC) version of Oracle Developer Suite, you must unzip the file on a Solaris Operating System (SPARC) computer. If you unzip the file on a Windows computer, and then move the stage area to a Solaris Operating System (SPARC) machine, the stage area files will be corrupted because Windows will not preserve the case sensitivity or the permission bits of UNIX file names.
Verify that the file size of your downloaded file matches the file size displayed on E- Delivery. Unzip each Zip file to its own temporary directory, and create a separate CD from the contents of each. Do not burn a CD containing the Zip file itself; you need the unzipped contents of the Zip files to do the installation. For example, create a directory structure called oraDS10g on your hard drive:
c:\oraDS10g
Then create a new directory for each Zip file you downloaded, regardless whether you are going to burn it to CD-ROM or install it from your computer's hard drive:
c:\oraDS10g\Disc1
c:\oraDS10g\Disc2
etc.
When you burn the files to CD-ROM, the contents of each disc must be at the root of the CD image.
To install from CD-ROM or from your hard drive, see Section 2.11.4, "Starting the Installer".
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:
|
|
Memory |
128 MB Foot 1 |
|
Disk Space Foot 2 |
J2EE Development
Business Intelligence (Windows only)
Rapid Application Development (Windows only)
Complete
|
|
Total Pagefile Size, TMP, or Swap SpaceFoot 3 |
|
|
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 If you are using Oracle JDeveloper 10g in a multiuser Linux or Solaris 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 |
|---|---|
|
Oracle10g JDeveloper (including Oracle Business Intelligence Beans, and UIX and Bali subcomponents) |
|
|
Oracle Reports Developer |
|
|
Oracle Business Intelligence Discoverer Administrator |
|
|
Oracle Business Intelligence Discoverer Desktop |
128 MB |
|
Oracle Forms Developer |
|
|
Oracle Designer |
256 MB |
Oracle Developer Suite is available for the Microsoft Windows 2000/XP Professional, Sun Solaris, 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
Linux and Solaris Notes:
The following Linux and Solaris desktops have been certified for JDeveloper:
Solaris/CDE
Linux/GNOME
Linux/KDE2
This section lists the operating environment requirements for Windows, Linux and Solaris.
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 |
|
|
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. |
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: Oracle10g JDeveloper running on Solaris requires the CDE windows manager. |
Table 2-5 Solaris Operating Environment Patchset Requirements
| Software Item | Requirement |
|---|---|
|
Solaris 8 (2.8) |
|
|
Solaris 9 (2.9) |
|
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) |
|
|
Solaris 9 (2.9) |
|
Depending on your distribution of Linux, see one of the following sections for information on checking the software requirements:
Section 2.4.3.1, "Software Requirements for Red Hat Enterprise Linux AS/ES 2.1 Systems"
Section 2.4.3.2, "Software Requirements for Red Hat Enterprise Linux AS/ES 3.0 Systems"
Section 2.4.3.3, "Software Requirements for Red Hat Enterprise Linux AS/ES 4.0 Systems"
Section 2.4.3.4, "Software Requirements for SUSE Linux Enterprise Server 8 Systems"
Section 2.4.3.5, "Software Requirements for SUSE Linux Enterprise Server 9 Systems"
Oracle does not support customized kernels or modules not supported by the Linux vendor.
You can install Oracle Developer Suite 10g (10.1.2.0.2) on a Linux system that is not on a network.
Table 2-7 lists the software requirements for Red Hat Enterprise Linux AS/ES 2.1 systems and the procedure that follows the table describes how to ensure your system meets these requirements and any additional requirements for installing Oracle Developer Suite.
|
Note: Oracle Developer Suite 10g (10.1.2.0.2) is certified with the following operating system specific software. For the most current list of supported operating system specific software, for example JDK version, operating system version, check OracleMetaLink (http://metalink.oracle.com). |
Table 2-7 Software Requirements for Red Hat Enterprise Linux AS/ES 2.1 Systems
| Item | Requirements |
|---|---|
|
Operating System |
Red Hat Enterprise Linux AS/ES 2.1 For more information on Red Hat, see: http://www.redhat.com |
|
Red Hat Update |
Update 5 |
|
Red Hat Patches |
Errata 49 kernel or a higher errata patch approved by Red Hat For example, one of the following, depending on the type of Red Hat installation:
|
|
Software packages (check that these versions or higher versions are installed) |
glibc-2.2.4-32.17 glibc-common-2.2.4-32.17 gcc-2.96-128.7.2 gcc-c++-2.96-128.7.2 pdksh-5.2.14-22 openmotif-2.1.30-12 sysstat-4.0.1-15.2.1as compat-glibc-6.2-2.1.3.2 compat-libstdc++-6.2-2.9.0.16 libstdc++-2.96-128.7.2 gnome-libs-1.2.13-16 binutils-2.11.90.0.8-12.4 make-3.79.1-8 db1-1.85-7 db3-3.3.11-5 |
To ensure that the system meets all the requirements, follow these steps:
Log in as the root user.
To determine which distribution and version of Linux is installed, enter the following command:
# cat /etc/issue
Red Hat Linux Advanced Server release 2.1AS/\m (Pensacola)
|
Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0, 4.0, and SUSE Linux Enterprise Server 8 and 9 are certified and supported. For the most current list of supported Linux Operating Systems, check OracleMetaLink (http://metalink.oracle.com). |
To check that Update 5 is installed:
# cat /etc/redhat-release
Red Hat Linux Advanced Server release 2.1AS/\m (Pensacola Update 5)
If Update 5 is installed, errata 49 is installed and all the required software packages are installed.
To determine which version of the Linux kernel is installed, enter the following command
# uname -r
kernel-smp-2.4.9-e.49
In this example, the version shown is 2.4.9 with errata 49. If necessary, see your operating system documentation for information on upgrading the kernel.
For more information on Red Hat patches, see:
http://www.redhat.com
To determine whether any other package is installed, enter a command similar to the following:
# rpm -q package_name
If a package is missing, download it and install it using the following command:
# rpm -i package_name
When installing a package, make sure you are using the correct architecture and optimization rpm file. To check the architecture of an rpm file, run the following command:
# rpm -q package_name --queryformat "%{arch}\n"
In the following example, the glibc rpm file is suitable for an Intel architecture
# rpm -q glibc --queryformat "%{arch}\n"
i686
Table 2-8 lists the software requirements for Red Hat Enterprise Linux AS/ES 3.0 systems and the procedure that follows the table describes how to ensure your system meets these requirements and any additional requirements for installing Oracle Developer Suite.
|
Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0, 4.0, and SUSE Linux Enterprise Server 8 and 9 are certified and supported. For the most current list of supported Linux operating systems, check OracleMetaLink (http://metalink.oracle.com). |
Table 2-8 Software Requirements for Red Hat Enterprise Linux AS/ES 3.0 Systems
| Item | Requirements |
|---|---|
|
Operating System |
Red Hat Enterprise Linux AS/ES 3.0 For more information on Red Hat, see: http://www.redhat.com The minimum supported kernel versions are:
|
|
Red Hat Update |
Update 3 |
|
Software packages (check that these versions or higher versions are installed) |
glibc-2.3.2-95.27 glibc-common-2.3.2-95.27 binutils-2.14.90.0.4-35 compat-glibc-7.x-2.2.4.32.6 compat-libstdc++-7.3-2.96.128 compat-libstdc++-devel-7.3-2.96.128 gcc-3.2.3-42 gcc-c++-3.2.3-42 libstdc++-3.2.3-42 libstdc++-devel-3.2.3-42 openmotif21-2.1.30-8 pdksh-5.2.14-21 setarch-1.3-1 make-3.79.1-17 gnome-libs-1.4.1.2.90-34.1 sysstat-4.0.7-4.EL3.3 compat-db-4.0.14-5 Note: For Red Hat Enterprise Linux AS/ES 3.0, the equivalent version of openmotif 2.1.30-8 is openmotif21-2.1.30-8. The openmotif21-2.1.30-8 package can be installed from disk number 3 of the Red Hat Enterprise Linux AS/ES 3.0 distribution by entering: $ rpm -ivh openmotif21-2.1.30-8 |
To ensure that the system meets all the requirements, follow these steps:
Log in as the root user.
To determine which distribution and version of Linux is installed, enter the following command:
# cat /etc/issue
Red Hat Enterprise Linux AS release 3 (Taroon)
|
Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0 and SUSE Linux Enterprise Server 8 and 9 are certified and supported. For the most current list of supported Linux operating systems, check OracleMetaLink (http://metalink.oracle.com/). |
To check that Update 3 is installed:
# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 3 (Taroon Update 3)
To determine whether any other package is installed, enter a command similar to the following:
# rpm -q package_name
If a package is missing, download it and install it using the following command:
# rpm -i package_name
When installing a package, make sure you are using the correct architecture and optimization rpm file. To check the architecture of an rpm file, run the following command:
# rpm -q package_name --queryformat "%{arch}\n"
In the following example, the glibc rpm file is suitable for an Intel architecture
# rpm -q glibc --queryformat "%{arch}\n"
i686
If the hugemem kernel is used, set the architecture using following command:
prompt> setarch i386
lists the software requirements for Red Hat Enterprise Linux AS/ES 4.0. The procedure that follows the table describes how to ensure that your system meets these requirements and any additional requirements for installing Oracle Application Server.
|
Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0, 4.0 and SUSE Linux Enterprise Server 8 and 9 are certified and supported. For the most current list of supported Linux Operating Systems, check OracleMetaLink (http://metalink.oracle.com/). |
Table 2-9 Software Requirements for Red Hat Enterprise Linux AS/ES 4.0 Systems
| Item | Requirements |
|---|---|
|
Operating System |
Red Hat Enterprise Linux AS/ES 4.0 For more information on Red Hat, see The minimum supported kernel versions are:
|
|
Red Hat Update |
Update 1 |
|
Software packages (check that these versions or higher versions are installed) |
glibc-2.3.4-2.9 glibc-common-2.3.4-2.9 binutils-2.15.92.0.2-13 compat-libstdc++-296-2.96-132.7.2 gcc-3.4.3-22.1 gcc-c++-3.4.3-22.1 libstdc++-3.4.3-22.1 libstdc++-devel-3.4.3-22.1 openmotif21-2.1.30-11.RHEL4.4 pdksh-5.2.14-30 setarch-1.6-1 make-3.80-5 gnome-libs-1.4.1.2.90-44.1 sysstat-5.0.5-1 compat-db-4.1.25-9 control-center-2.8.0-12 xscreensaver-4.18-5.rhel4.2 |
|
64-bit Certification |
For latest status on Red Hat Enterprise Linux AS/ES 4.0 (64-bit) certification on AMD64 and Intel EM64T, check the Certification status on OracleMetaLink ( |
To ensure that the system meets all the requirements, follow these steps:
Log in as the root user.
To determine which distribution and version of Linux is installed, enter the following command:
# cat /etc/issue Red Hat Enterprise Linux AS release 4 (Nahant Update 1)
To check that Update 1 is installed:
# cat /etc/redhat-release Red Hat Enterprise Linux AS release 4 (Nahant Update 1)
To determine whether any other package is installed, enter a command similar to the following:
# rpm -q package_name
If a package is missing, download it and install it using the following command:
# rpm -i package_name
When installing a package, make sure you are using the correct architecture and optimization rpm file. To check the architecture of an rpm file, run the following command:
# rpm -q package_name --queryformat "%{arch}\n"
In the following example, the glibc rpm file is suitable for an Intel architecture
# rpm -q glibc --queryformat "%{arch}\n"
i686
If the hugemem kernel is used, set the architecture using following command:
prompt> setarch i386
Table 2-10 lists the software requirements for SUSE Linux Enterprise Server 8 systems and the procedure that follows the table describes how to ensure your system meets these requirements and any additional requirements for installing Oracle Application Server.
|
Note: Oracle Developer Suite 10g (10.1.2.0.2) is certified with the following operating system specific software. For the most current list of supported operating system specific software, for example JDK version, operating system version, check OracleMetaLink (http://metalink.oracle.com/). |
Table 2-10 Software Requirements for SUSE Linux Enterprise Server 8 Systems
| Item | Requirements |
|---|---|
|
Operating System |
SUSE Linux Enterprise Server 8 For more information on SUSE Linux Enterprise Server, see:
SP3 is certified for Oracle Developer Suite 10g (10.1.2.0.2). For SUSE Linux Enterprise Server 8 SP3, the minimum supported kernel versions are:
|
|
Software packages (check that these versions or higher versions are installed) |
glibc-2.2.2-124 gcc-3.2.2-38 gcc-c++-3.2.2-38 pdksh-5.2.14 openmotif-2.1.30MLI4 sysstat-4.0.3 libstdc++-3.2.2 make-3.79.1-407 binutils-2.12.90.0.15-50 compat-2003.1.10-0 |
To ensure that the system meets all the requirements, follow these steps:
Log in as the root user.
To determine which distribution and version of Linux is installed, enter the following command:
# cat /etc/issue
Welcome to SUSE Linux Enterprise Server 8 (i586) - Kernel \r (\l)
|
Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0 and SUSE Linux Enterprise Server 8 and 9 are certified and supported. For the most current list of supported Linux operating systems, check OracleMetaLink (http://metalink.oracle.com/). |
To determine the service pack version, enter the following command:
# uname -r
k_smp-2.4.21-138
If the kernel version contains the string 2.4.21, SP3 is installed. SP3 is certified for Oracle Developer Suite 10g (10.1.2.0.2).
To determine whether any other package is installed, enter a command similar to the following:
# rpm -q package_name
If a package is missing, download it and install it using the following command:
# rpm -i package_name
When installing a package, make sure you are using the correct architecture and optimization rpm file. To check the architecture of an rpm file, run the following command:
# rpm -q package_name --queryformat "%{arch}\n"
In the following example, the glibc rpm file is suitable for an Intel architecture
# rpm -q glibc --queryformat "%{arch}\n"
i686
Create the following symbolic link for the Perl executable if it does not already exist:
# ln -sf /usr/bin/perl /usr/local/bin/perl
Create the following symbolic link for the fuser executable if it does not already exist:
# ln -sf /bin/fuser /sbin/fuser
If the orarun package was installed on a SUSE Linux Enterprise Server system, complete the following steps as the oracle user to reset the environment:
Enter the following commands:
prompt> cd /etc/profile.d prompt> mv oracle.csh oracle.csh.bak prompt> mv oracle.sh oracle.sh.bak prompt> mv alljava.sh alljava.sh.bak prompt> mv alljava.csh alljava.csh.bak
Use any text editor to comment out the following line from the $HOME/.profile file:
. ./.oracle
Log out of the oracle user account.
Log into the oracle user account for the changes to take effect.
If any Java packages are installed on the system, unset the Java environment variables, for example JAVA_HOME.
|
Note: Oracle recommends that you do not install any of the Java packages supplied with the SUSE Linux Enterprise Server distribution. |
Table 2-11 lists the software requirements for SUSE Linux Enterprise Server 9 systems and the procedure that follows the table describes how to ensure your system meets these requirements and any additional requirements for installing Oracle Developer Suite.
|
Note: Oracle Developer Suite 10g (10.1.2.0.2) is certified with the following operating system specific software. For the most current list of supported operating system specific software, for example JDK version, operating system version, check OracleMetaLink (http://metalink.oracle.com/). |
Table 2-11 Software Requirements for SUSE Linux Enterprise Server 9 Systems
| Item | Requirements |
|---|---|
|
Operating System |
SUSE Linux Enterprise Server 9 For more information on SUSE Linux Enterprise Server, see: http://www.suse.com/ For SUSE Linux Enterprise Server 9, the minimum supported kernel versions are:
|
|
Software packages (check that these versions or higher versions are installed) |
glibc-2.3.3-98.28 gcc-3.3.3-43.24 gcc-c++-3.3.3-43.24 libstdc++-3.3.3-43.24 libstdc++-devel-3.3.3-43.24 openmotif21-libs-2.1.30MLI4-119.1 pdksh-5.2.14-780.1 make-3.80-184.1 gnome-libs-1.4.1.7-671.1 gnome-libs-devel-1.4.1.7-671.1 sysstat-5.0.1-35.1 binutils-2.15.90.0.1.1-32.5 db1-1.85-85.1 compat-2004.7.1-1.2 |
To ensure that the system meets all the requirements, follow these steps:
Log in as the root user.
To determine which distribution and version of Linux is installed, enter the following command:
# cat /etc/issue
Welcome to SuSE Linux 9.0 (i686) - Kernel \r (\l).
|
Note: Red Hat Enterprise Linux AS/ES 2.1, 3.0 and SUSE Linux Enterprise Server 8 and 9 are certified and supported. For the most current list of supported Linux operating systems, check OracleMetaLink (http://metalink.oracle.com/). |
To determine the kernel version, enter the following command:
# uname -r
kernel-bigsmp-2.6.5-7.97
To determine whether any other package is installed, enter a command similar to the following:
# rpm -q package_name
If a package is missing, download it and install it using the following command:
# rpm -i package_name
When installing a package, make sure you are using the correct architecture and optimization rpm file. To check the architecture of an rpm file, run the following command:
# rpm -q package_name --queryformat "%{arch}\n"
In the following example, the glibc rpm file is suitable for an Intel architecture
# rpm -q glibc --queryformat "%{arch}\n"
i686
Create the following symbolic link for the Perl executable if it does not already exist:
# ln -sf /usr/bin/perl /usr/local/bin/perl
Create the following symbolic link for the fuser executable if it does not already exist:
# ln -sf /bin/fuser /sbin/fuser
If the orarun package was installed on a SUSE Linux Enterprise Server system, complete the following steps as the oracle user to reset the environment:
Enter the following commands:
prompt> cd /etc/profile.d prompt> mv oracle.csh oracle.csh.bak prompt> mv oracle.sh oracle.sh.bak prompt> mv alljava.sh alljava.sh.bak prompt> mv alljava.csh alljava.csh.bak
Use any text editor to comment out the following line from the $HOME/.profile file:
. ./.oracle
Log out of the oracle user account.
Log into the oracle user account for the changes to take effect.
If any Java packages are installed on the system, unset the Java environment variables, for example JAVA_HOME.
|
Note: Oracle recommends that you do not install any of the Java packages supplied with the SUSE Linux Enterprise Server distribution. |
You can view a complete list of certified software for Oracle Developer Suite on OracleMetaLink, at:
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-12 contains the tools and disk space requirements for the Oracle Developer Suite Documentation Library.
Table 2-12 Online Documentation Requirements
| Item | Requirements |
|---|---|
|
Requires one of the following: HTML
|
|
|
Disk Space |
130 MB |
This section provides information about the coexistence of Oracle products in one Oracle home, and guidelines for installing multiple Oracle products on one computer.
Your Oracle home is the top-level directory in which you install Oracle software.
Oracle Developer Suite cannot share the same Oracle home with its previous versions (Oracle Developer Suite 10g (9.0.4), Oracle9iDS Release 2 (9.0.2) or Oracle Internet Developer Suite Release 1.0.2.x).
Oracle Developer Suite cannot share the same Oracle home with any Oracle databases, including Oracle Database 10g.
Oracle Developer Suite cannot share the same Oracle home with a Oracle Application Server Forms and Reports Services 10g standalone server instance.
Oracle Developer Suite can coexist in the same Oracle home with any installation of Oracle Application Server 10g (10.1.2), with the exception of Oracle Application Server Infrastructure.
|
Note: This does not apply to any other version of Oracle Application Server. |
For Linux and Solaris only: If there are existing Oracle homes set on the computer where you are installing Oracle Developer Suite, refer to Section 2.9.5.1.1, "Preventing Conflicts With Other Oracle Homes".
In this guide, directory paths may contain the placeholder text DevSuiteHome, which represents the path to your actual Developer Suite directory.
|
Note: If you install Oracle Developer Suite 10g (10.1.2.0.2) and Oracle Application Server 10g (10.1.2.0.2) to the same Oracle home, do not try to start Oracle Application Server Containers for J2EE (OC4J) on port 8888 fromORACLE_HOME\j2ee\home. If you do, the OC4J instance will fail. |
The following guidelines apply to installing multiple instances of Oracle Developer Suite on the same computer. The guidelines also apply to installing Oracle Developer Suite on a computer that has existing installations of Oracle9iDS or Oracle Internet Developer Suite:
Make sure you reboot the computer after you install Oracle Developer Suite the first time.
Make sure you have sufficient disk space to handle all of your installations. See Table 2-1 to determine the disk space requirements.
Install subsequent instances into a different Oracle home from the previous one.
Reboot the computer after the last installation is completed (Windows only).
|
Note: Oracle Developer Suite cannot 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, 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.
The installer writes files to the following directories:
Table 2-13 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.7.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.11.3, "The Installer Inventory Directory". |
|
Linux and Solaris only:
|
This directory contains information about locations of Oracle homes on your Linux or Solaris computer. For more information, see Section 2.11.3, "The Installer Inventory Directory". Note: On a Windows computer, this information is stored in the Windows Registry. |
|
Linux and Solaris only:
|
The installer writes files needed only during installation to a temporary directory. By default, the temporary directory is |
|
Windows only: temp directory |
The installer writes files needed only during installation to a temporary directory. The installer uses the directory specified in the |
Before installing Oracle Developer Suite, review the Oracle Developer Suite Release Notes, which are available in the Oracle Developer Suite Documentation Library. To view them, 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://www.oracle.com/technology/products/ids/.
The preinstallation tasks for Oracle Developer Suite are divided into the following parts:
General tasks:
If you have Windows 2000 or XP Professional, ensure that you are logged on to your computer as a member of the Administrators group.
On Linux or Solaris, ensure that you are not logged in as the root user; otherwise, you will not be able to run the installer. See Section 2.9.6, "Creating Linux and Solaris Accounts and Groups" for more information.
Ensure that your PATH,CLASSPATH,LD_LIBRARY_PATH 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 and Oracle processes, and close all other open applications.
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 the locale for your operating environment before you start the Oracle Universal Installer.
The installer supports the locale languages listed in Table 2-14:
Table 2-14 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.
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 |
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.
If you use assistive technologies, you should perform one of the following steps:
If you don't have JDK/JRE 1.4.2 installed on your computer:
Proceed with your installation. After you have finished installing Oracle Developer Suite, ensure that you have Java Access Bridge 1.2 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.4.2 on your computer:
You must install the production version of Java Access Bridge 1.2 in the JDK/JRE 1.4.2 location on your computer before you install Oracle Developer Suite.
To download and install Java Access Bridge 1.2:
Download the Zip file for Java Access Bridge 1.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.
After downloading the file, extract the contents to a folder; for example, accessbridge_home.
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.
Confirm that you want to install the Java Access Bridge into each of the Java virtual machines displayed in the dialog.
Click OK when you see the Installation Completed message.
The tasks in this section are required on Linux and Solaris platforms only.
DevSuiteHome is an environment variable (UNIX) or registry key (Windows) that indicates the directory where Developer Suite is installed. It is similar to ORACLE_HOME.
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.
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 |
In your PATH, CLASSPATH, and LD_LIBRARY_PATH environment variables, remove any references to the environment variable ORACLE_HOME.
Setting the DISPLAY environment variable allows you to run the installer remotely and view the installer user interface 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 |
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 |
TNS_ADMIN points to the directory where network configuration files are stored.
If TNS_ADMIN is set to an existing directory on your computer, there will be conflicts between that directory and the directory where the Oracle Developer Suite network configuration files are created. There will also be 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 |
The tasks in this section are required on Linux and Solaris platforms only.
Create a group that has read and write privileges in 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 granting 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 operating system environment utilities to create the group. For example:
On Solaris, use the admintool or groupadd 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.
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-15.
Table 2-15 Oracle Account Properties
| Variable | Property |
|---|---|
|
name |
Specifies the Oracle user name. This guide uses the name |
|
Group Identifier |
Specifies the |
|
Home directory |
Specifies a home directory consistent with other user home directories. The home directory of the |
|
Login Shell |
Specifies the default shell: 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 useroot for the Oracle user. |
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-16.
Table 2-16 Information Needed During Installation
| Item | Installation Type | Example |
|---|---|---|
|
Oracle home name and path for Oracle Developer Suite 10g (10.1.2.0.2) Foot 1 |
All (for Solaris, Windows and Linux x86) |
Name: Path: or
|
|
Linux and Solaris group name |
All (Linux and Solaris only) |
|
|
Outgoing mail server name |
Business Intelligence, Rapid Application Development, Complete (all platforms). Used only by Oracle Application Server Reports Services. |
|
Footnote 1 See Section 2.7.1, "Oracle Home Considerations" for more details.
Review Appendix A, "Upgrade Notes" if you are migrating or upgrading from:
Oracle Developer Suite 10g (9.0.4)
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)
The following section contains information about pre-installation tasks:
OracleBI Beans supports data stored in the Oracle Database. However, only particular releases and patchsets are supported. You can install the database and required patchsets as either a pre-installation task or a post-installation task. The instructions are discussed with post-installation tasks, in Section 3.2.3.1, "Database Considerations".
This section introduces Oracle Universal Installer and provides information that you should know before you start the installation.
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
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-17 lists the automatic prerequisite checks for Windows:
Table 2-17 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-18 lists the automatic prerequisite checks for Solaris on Sun SPARC computers:
Table 2-18 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-19 lists the automatic prerequisite checks for Linux x86:
Table 2-19 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 |
|
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.
Review the following information about the inventory directory:
For Windows Users:
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 system_default_drive is normally "C:", and is set in the Windows Registry.
For Linux and Solaris Users:
For Linux and Solaris, the default directory location is listed in the file /var/opt/oracle/oraInst.loc on Solaris, and /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 or Solaris 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 and Solaris). The log file name has the form
installActionsyear-date_time.log.
Follow these instructions to start the installer:
Stop all Oracle services such as an Oracle database.
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.
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.
If you are using the autorun feature, the installer will start automatically. Click Install Oracle Developer Suite to start your installation.
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:
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.
To browse the CD-ROM or DVD contents, use Windows Explorer.
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.
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:
Click Exit to quit the installer.
Change to the root directory on the CD-ROM, or to the directory \developer_suite under the root directory of the DVD.
Run wsf.exe.
The Windows System Files installer attempts to find an existing Oracle home. If the installer does not find one, it displays a File Locations dialog. Select 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.
After Windows restarts, or when the Windows System Files installation finishes, restart the Oracle Developer Suite installation.
|
Note: You need access to theroot 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:
Stop all Oracle processes such as the Oracle database.
Read the section for your operating environment to get detailed mounting instructions:
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:
Insert the Oracle Developer Suite Disk 1 CD-ROM or the Oracle Developer Suite and Documentation DVD into the drive.
Log in as the root user.
Ensure that you have a mount point directory for the CD-ROM or DVD. For example, you can create the directory /cdrom:
# mkdir /cdrom
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
Log out as the root user.
Proceed to Section 2.11.4.2.3, "Running the Installer".
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:
Insert the Oracle Developer Suite Disk 1 CD-ROM or the Oracle Developer Suite and Documentation DVD into your drive.
Log in as the root user.
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
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. |
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.
Log out as the root user.
Proceed to Section 2.11.4.2.3, "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 theroot user when you start the installer. If you are, you will receive an error message and the installer will stop. |
Log in with the user that you created for installing Oracle products (see Section 2.9.6.2, "User for Oracle Software").
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.
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.
