This guide contains information required to install Oracle Database Client 11g Release 2 (11.2). Ensure that you review information related to the platform on which you intend to install Oracle Database Client.
This chapter describes the tasks that you must complete before you start Oracle Universal Installer. It includes information about the following tasks:
Before you install the Oracle software, you must complete several tasks as the root user. To log in as the root user, complete one of the following procedures:
Note:
Unless you intend to complete a silent-mode installation, you must install the software from an X Window System workstation, an X terminal, or a PC or other system with X server software installed.For more information about silent-mode installations, refer to Appendix A.
If you are installing the software from an X Window System workstation or X terminal, then:
Start a local terminal session, for example, an X terminal (xterm).
If you are not installing the software on the local system, then enter the following command to enable the remote host to display X applications on the local X server:
$ xhost fully_qualified_remote_host_name
For example:
$ xhost somehost.example.com
If you are not installing the software on the local system, then use the ssh, rlogin, or telnet command to connect to the system where you want to install the software:
$ telnet fully_qualified_remote_host_name
If you are not logged in as the root user, then enter the following command to switch user to root:
$ su - root password: #
If you are installing the software from a PC or other system with X server software installed, then:
Note:
If necessary, refer to the X server documentation, or contact your X server vendor or system administrator for more information about completing this procedure. Depending on the X server software that you are using, you may have to complete the tasks in a different order.Start the X server software.
Configure the security settings of the X server software to permit remote hosts to display X applications on the local system.
Connect to the remote system where you want to install the software and start a terminal session on that system, for example, an X terminal (xterm).
If you are not logged in as the root user on the remote system, then enter the following command to switch user to root:
$ su - root password: #
The system must meet the following minimum hardware requirements for Oracle Database Client 11g Release 2:
The following are the memory requirements for Oracle Database Client 11g Release 2 (11.2):
At least 256 MB of RAM.
To determine the RAM size, enter the following command:
# /usr/sbin/lsattr -E -l sys0 -a realmem
If the size of the RAM is less than the required size, then you must install more memory before you continue with the installation.
The following table describes the relationship between installed RAM and the configured swap space recommendation:
| RAM | Swap Space |
|---|---|
| 256 MB | 3 times the size of RAM |
| Between 256 MB and 512 MB | 2 times the size of RAM |
| Between 512 MB and 2 GB | 1.5 times the size of RAM |
| Between 2 GB and 16 GB | Equal to the size of RAM |
| More than 16 GB | 16 GB |
To determine the size of the configured swap space, enter the following command:
# /usr/sbin/lsps -a
If necessary, refer to the operating system documentation for information about how to configure additional swap space.
IMPORTANT:
Oracle recommends that you take multiple values for the available RAM and swap space before finalizing on a value. This is because the available RAM and swap space keep changing depending on the user interactions with the computer.
Contact your operating system vendor for swap space allocation guidance for your server. The vendor guidelines supersede the swap space requirements listed in this guide.
To determine whether the system architecture can run the software, enter the following command:
# /usr/bin/getconf HARDWARE_BITMODE
The expected output of this command is 64. If you do not see the expected output, then you cannot install the software on this system.
To determine if the system is started in 64-bit mode, enter the following command:
# bootinfo -K
The result of this command must be 64, indicating that the 64-bit kernel is enabled.
Note:
For AIX Based Systems, Oracle Database 11g supports 64-bit kernel and does not provide support for 32-bit kernel applications.Note:
Verify that the processor architecture matches the Oracle software release to install. If you do not see the expected output, then you cannot install the software on this system.The following are the disk space requirements for Oracle Database Client 11g Release 2 (11.2):
The minimum disk space requirement for a client install in the /tmp directory is 130 MB
To determine the amount of disk space available in the /tmp directory, enter the following command:
# df -k /tmp
If free disk space available in the /tmp directory is less than what is required, then complete one of the following steps:
Delete unnecessary files from the /tmp directory to meet the disk space requirement.
Set the TMP and TMPDIR environment variables when setting the oracle user's environment.
Extend the file system that contains the /tmp directory. If necessary, contact the system administrator for information about extending file systems.
To determine the amount of free disk space on the system, enter the following command:
# df -k
The following table describes the disk space requirements for software files for each installation type on AIX Based Systems
The minimum display requirement for Oracle Database 11g Release 2 (11.2) is a resolution of 1024 x 768 or higher.
Depending on the products that you intend to install, verify that the following softwares are installed on the system.
Note:
The platform-specific hardware and software requirements included in this guide were current when this guide was published. However, because new platforms and operating system software versions may be certified after this guide is published, review the certification matrix on the My Oracle Support website for the most up-to-date list of certified hardware platforms and operating system versions:The following or later versions of the operating system are required for Oracle Database Client 11g Release 2 (11.2):
Note:
Oracle Universal Installer performs checks to verify that the system meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.AIX 5L V5.3 TL 09 SP1 ("5300-09-01"), 64 bit kernel
AIX 6.1 TL 02 SP1 ("6100-02-01), 64-bit kernel
AIX 7.1 TL 0 SP1 ("7100-00-01"), 64-bit kernel
AIX 7.2 TL 0 SP1 ("7200-00-01"), 64-bit kernel
The following operating system filesets are required for AIX 5L:
bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.libperfstat 5.3.9.0 or later
bos.perf.perfstat
bos.perf.proctools
xlC.aix50.rte.10.1.0.0 or later
xlC.rte.10.1.0.0 or later
gpfs.base 3.2.1.8 or later
The following operating system filesets are required for AIX 6.1:
bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.libperfstat 6.1.2.1 or later
bos.perf.perfstat
bos.perf.proctools
xlC.aix61.rte.10.1.0.0 or later
xlC.rte.10.1.0.0 or later
gpfs.base 3.2.1.8 or later
The following operating system filesets are required for AIX 7.1:
bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.libperfstat
bos.perf.perfstat
bos.perf.proctools
xlC.rte.11.1.0.2 or later
gpfs.base 3.3.0.11 or later
The following operating system filesets are required for AIX 7.2:
bos.adt.base
bos.adt.lib
bos.adt.libm
bos.perf.libperfstat
bos.perf.perfstat
bos.perf.proctools
xlC.aix61.rte.13.1.2.0 or later
xlc.rte.13.1.2.0 or later
Note:
On AIX 5L operating system, if you set the value of LOCK_SGA parameter to true, then you must ensure that the CAP_BYPASS_RAC_VMM and CAP_PROPAGATE privileges are enabled for the operating system account that is used to start the respective database instances. Otherwise, setting the value of LOCK_SGA parameter to TRUE alone does not ensure startup of the database instance.
The GPFS fileset is required only if you want to use the IBM GPFS cluster file system as the shared storage for Oracle clusterware or database files.
To determine the distribution and version of AIX installed, enter the following command:
# oslevel -s
For AIX 5L: If the operating system version is lower than AIX 5.3 TL 9 SP 1, then upgrade your operating system to this, or a later, level.
For AIX 6.1: If the operating system version is lower than AIX 6.1 TL 2 SP 1, then upgrade your operating system to this, or a later, level.
For AIX 7.1: If the operating system version is lower than AIX 7.1 TL 0 SP 1, then upgrade your operating system to this, or a later, level.
For AIX 7.2: If the operating system version is lower than AIX 7.2 TL 0 SP 1, then upgrade your operating system to this, or a later, level.
AIX maintenance packages are available at:
To determine whether the required filesets are installed and committed, enter a command similar to the following:
# lslpp -l bos.adt.base bos.adt.lib bos.adt.libm bos.perf.perfstat \ bos.perf.libperfstat bos.perf.proctools
To determine the supported kernel mode, enter a command similar to the following:
# getconf KERNEL_BITMODE
Note:
The expected output of this command is 64. If you do not see the expected output, then you cannot install the software on this system.
Oracle Database 11g supports 64-bit kernel and does not provide support for 32-bit kernel applications.
The following is the minimum compiler requirement for Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, and Oracle XML Developer's Kit (XDK) with Oracle Database 11g Release 2:
IBM XL C/C++ Enterprise Edition for AIX, V9.0 April 2008 PTF:
You can download this software from the following link:
http://www-01.ibm.com/support/docview.wss?uid=swg24019055
Even if you do not install the IBM XL C/C++ compiler, you require the compiler for AIX Runtime Environment Component. The runtime environment file sets can be downloaded with no license requirements. The minimum recommended runtime environment for AIX 5.3 and AIX 6.1 is available at the following URL:
For AIX 5.3 and AIX 6.1:
IBM XL C/C++ for AIX, V10.1 Runtime Environment
http://www-01.ibm.com/support/docview.wss?rs=2239&uid=swg24019829
For AIX 7.1:
September 2010 Runtime for XL C/C++ for AIX, V11.1
http://www-01.ibm.com/support/docview.wss?uid=swg24028034
For AIX 7.2:
November 2015 Runtime for XL C/C++ for AIX, V13.1
http://www-01.ibm.com/support/docview.wss?uid=swg24041340
Depending on the components you want to use, you must ensure that the following software are installed:
Use JDK 6 (Java 6 64-bit 6.0.0.50 IZ30726 (SR2)) or JDK 5 (Java 5 64-bit 5.0.0.250 IZ55274 (SR10)) with the JNDI extension with the Oracle Java Database Connectivity and Oracle Call Interface drivers. However, these are not mandatory for the database installation. Note that JDK 1.5 is installed with this release
Oracle ODBC driver on AIX is certified with ODBC Driver Manager 2.2.12. You can download and install the Driver Manager from the following link:
ODBC Driver Manager is not required to install Oracle Database.
To use ODBC, install gcc 3.4.5.
Starting with Oracle Database 11g Release 2 (11.2), the 64-bit client software does not contain any 32-bit client binaries. If you require 32-bit client binaries on 64-bit platforms, then install the 32-bit binaries from the respective 32-bit client software into a separate Oracle home.
See Also:
My Oracle Support note 883702.1 for more information:https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=883702.1
You do not require a web browser to install Oracle Database. However, browsers are required to access documentation, and if you intend to use Oracle Enterprise Manager Database Control and Oracle Application Express. Web browsers must support JavaScript, and the HTML 4.0 and CSS 1.0 standards.
Oracle Enterprise Manager Database Control supports the following browsers:
Microsoft Internet Explorer 10.0 (supports Oracle Enterprise Manager Database Control 11.2.0.3 and higher)
Microsoft Internet Explorer 9.0
Microsoft Internet Explorer 8.0
Microsoft Internet Explorer 7.0 SP1
Microsoft Internet Explorer 6.0 SP2
Firefox 21.0 (supports Oracle Enterprise Manager Database Control 11.2.0.4)
Firefox 17.0.6 ESR (supports Oracle Enterprise Manager Database Control 11.2.0.4)
Firefox 3.6
Firefox 3.5
Firefox 3.0.7
Firefox 2.0
Safari 4.0.x
Safari 3.2
Safari 3.1
Google Chrome 27.0 (supports Oracle Enterprise Manager Database Control 11.2.0.4)
Google Chrome 4.0
Google Chrome 3.0
Netscape Navigator 9.0
Netscape Navigator 8.1
The following products are certified for use with:
Pro* COBOL
IBM COBOL for AIX Version 4.1 (September 2010 PTF)
IBM COBOL for AIX Version 3.1
Micro Focus Server Express 5.1
Pro* FORTRAN
IBM XL Fortran Enterprise Edition for AIX, V11.1 April 2008 PTF
Ada
OC Systems PowerAda 5.5
For more information about OC Systems and PowerAda, refer to the following URL:
The following, or later, patches are required for Oracle Database 11g Release 2 (11.2) for AIX Based Systems:
Note:
AIX APAR numbers are tied to AIX versions and technology levels (TL). Download and install the APAR that matches your AIX versions and TL from the IBM fix central website at the following URL:
If you are using a later TL level than the minimum level listed for this release, then check with IBM to determine if the required APARs listed here are included in the TL level that you have on your system. If they are included, then you do not need to install them. If they are not included, then you must install the equivalent APAR for the appropriate TL level.
| Installation Type or Product | Requirement |
|---|---|
| All installations | Authorized Problem Analysis Reports (APARs) for AIX 5L:
If you are using the minimum operating system TL level for AIX 5L listed above, then install the following Authorized Problem Analysis Reports (APARs) for AIX 5L V5.3 TL 09 SP1:
These 5.3 fixes are present in the following TL levels:
|
| All installations | Authorized Problem Analysis Reports (APARs) for AIX 6.1:
If you are using the minimum operating system TL level for AIX 6.1 listed above, then install the following Authorized Problem Analysis Reports (APARs) for AIX 6.1 TL 02 SP1:
These 6.1 fixes are present in the following TL levels:
If you are using a later TL level than the minimum level listed for this release, apply the following additional operating system patch for defect: BIND64 CORES WITH -BLAZY OPTION Download the appropriate patch for your operating system TL level using the following APAR numbers:
|
| All installations | Authorized Problem Analysis Reports (APARs) for AIX 7.1:
If you are using the minimum operating system TL level for AIX 7.1 listed above, then install the following Authorized Problem Analysis Reports (APARs) for AIX 7.1 TL 0 SP1:
|
| All installations | Authorized Problem Analysis Reports (APARs) for AIX 7.2:
If you are using the minimum operating system TL level for AIX 7.2 listed above, then install the following Authorized Problem Analysis Reports (APARs) for AIX 7.2 TL 0 SP1:
Note: Install IV80412m1a as it includes the required fix for IV79441. |
The following procedure describes how to check these requirements:
To determine whether an APAR is installed, enter a command similar to the following:
# /usr/sbin/instfix -i -k "IZ42940 IZ49516 IZ52331 IZ41855 IZ52319"
If an APAR is not installed, then download it from the following website and install it:
If you require a CSD for WebSphere MQ, then refer to the following website for download and installation information:
In addition to the requirements described in the preceding section, if you plan to use Instant Client Light, then the applications must use the following languages and character sets:
Language: Any language that is supported by Oracle
Territory: Any territory that is supported by Oracle
Character sets:
Single byte
US7ASCII
WE8DEC
WE8MSWIN1252
WE8ISO8859P1
Unicode
UTF8
AL16UTF16
AL32UTF8
Instant Client Light can connect to databases having one of the following database character sets:
US7ASCII
WE8DEC
WE8MSWIN1252
WE8ISO8859P1
WE8EBCDIC37C
WE8EBCDIC1047
UTF8
AL32UTF8
The language, territory, and character sets are determined by the NLS_LANG environment variable.
Depending on whether this is the first time Oracle software is being installed on this system and on the products that you are installing, you may have to create the following operating system group and user:
The Oracle Inventory group (typically, oinstall)
You must have a group whose members are given access to write to the Oracle Central Inventory (oraInventory).
Installation logs and trace files from installations of Oracle software. These files are also copied to the respective Oracle homes for future reference.
Other metadata inventory information regarding Oracle installations are stored in the individual Oracle home inventory directories, and are separate from the Central Inventory.
For new installations, Oracle recommends that you allow Oracle Universal Installer to create the Central Inventory directory. By default, if you create an Oracle path in compliance with OFA structure, such as /u01/app, then the Central Inventory is created in the path u01/app/oraInventory, using correct permissions to allow all Oracle installation owners to write to this directory.
The Oracle software owner user (typically, oracle)
You must create this user the first time you install Oracle software on the system. This user owns all of the software installed during the installation. This user must have the Oracle Inventory group as its primary group. It must also have the OSDBA and OSOPER groups as secondary groups.
Note:
In Oracle documentation, the user created to own the Oracle Database installations is referred to as the oracle user.
An Oracle Database installation must be owned by the Oracle software owner user (oracle)and the primary group of the Oracle software owner user must be the Oracle Inventory group (oinstall).
A single Oracle Inventory group is required for all installations of Oracle software on the system. After the first installation of Oracle software, you must use the same Oracle Inventory group for all subsequent Oracle software installations on that system. However, you can choose to create different Oracle software owner users for separate installations.
Note:
The following sections describe how to create local users and groups. As an alternative to creating local users and groups, you could create the appropriate users and groups in a directory service, for example, Network Information Services (NIS). For information about using directory services, contact the system administrator or refer to the operating system documentation.The following sections describe how to create the required operating system users and groups:
You must create the Oracle Inventory group if it does not exist. The following sections describe how to determine the Oracle Inventory group name, if it exists, and how to create it if necessary:
Determining Whether the Oracle Inventory Group Exists
When you install Oracle software on the system for the first time, Oracle Universal Installer creates the oraInst.loc file. This file identifies the name of the Oracle Inventory group (typically, oinstall), and the path of the Oracle Inventory directory.
An oraInst.loc file has content similar to the following:
inventory_loc=central_inventory_location inst_group=group
In the preceding example, central_inventory_location is the location of the Oracle Central Inventory, and group is the name of the group that has permissions to write to the central inventory.
If you have an existing Oracle Inventory, then ensure that you use the same Oracle Inventory for all Oracle software installations, and ensure that all Oracle software users you intend to use for installation have permissions to write to this directory.
To determine whether the Oracle Inventory group exists, enter the following command:
# more /etc/oraInst.loc
If the oraInst.loc file exists, then the output from this command is similar to the following:
inventory_loc=/u01/app/oraInventory inst_group=oinstall
In the previous output example:
The inventory_loc parameter shows the location of the Oracle Inventory
The inst_group parameter shows the name of the Oracle Inventory group (in this example, oinstall).
Creating the Oracle Inventory Group
If the oraInst.loc file does not exist, then create the Oracle Inventory group as follows:
You must create an Oracle software owner user in the following circumstances:
If an Oracle software owner user does not exist; for example, if this is the first installation of Oracle software on the system
If an Oracle software owner user exists, but you want to use a different operating system user
To determine if an Oracle software owner user (oracle) exists, enter the following command:
# id oracle
If the oracle user exists, then the output from this command is similar to the following:
uid=54321(oracle) gid=54321(oinstall) groups=54322(dba),54323(oper)
If the user exists, then determine whether you want to use the existing user or create another oracle user. If you want to use the existing user, then ensure that the user's primary group is the Oracle Inventory group. Refer to one of the following sections for more information:
Note:
If necessary, contact the system administrator before using or modifying an existing user.If you want to use the existing Oracle software owner user, and the user's primary group is the Oracle Inventory group, then refer to the "Identifying Required Software Directories" section.
To modify an existing user, refer to the "Modifying an Oracle Software Owner User" section.
To create a user, refer to the following section.
If the Oracle software owner user does not exist or if you require a new Oracle software owner user, then create it as follows. In the following procedure, use the user name oracle unless a user with that name exists.
# smit security
Choose the appropriate menu items to create the oracle user, specifying the following information:
In the Primary GROUP field, specify the Oracle Inventory group, for example oinstall.
In the Group SET field, specify the OSDBA group and if required, the OSOPER group. For example dba, asmdba, or oper.
Press F10 to exit.
Set the password of the oracle user:
# passwd oracle
Refer to the "Identifying Required Software Directories" section to continue.
If the oracle user exists, but its primary group is not oinstall, then enter a command similar to the following to modify it:
Enter the following command:
# smit security
Choose the appropriate menu items to modify the oracle user.
In the Primary GROUP field, specify the Oracle Inventory group, for example oinstall.
In the Group SET field, specify the required secondary groups, for example dba.
Press F10 to exit.
You must identify or create the following directories for the Oracle software:
Note:
Ensure that the paths you select for Oracle software, such as the Oracle home path and the Oracle base path, use only ASCII characters. Because installation owner names are used by default for some paths, this ASCII character restriction applies to user names, file names, and directory names.The Oracle base directory is a top-level directory for Oracle software installations. On UNIX systems, the Optimal Flexible Architecture (OFA) guidelines recommend that you use a path similar to the following for the Oracle base directory:
/mount_point/app/software_owner
In this example:
mount_point is the mount point directory for the file system that contains the Oracle software.
The examples in this guide use /u01 for the mount point directory.
software_owner is the operating system user name of the software owner installing the Oracle software, for example oracle.
You must specify the ORACLE_BASE folder that contains all Oracle products.
Note:
If you have an existing Oracle base, then you can select it from the Use existing drop down box. By default, the drop down box contains the existing value for Oracle base selected. Refer to "Installing the Oracle Database Client Software" for information.If you do not have an Oracle base, then you can create a new one by editing the text in the list box.
You can use the same Oracle base directory for multiple installations or you can create separate Oracle base directories for different installations. If different operating system users install Oracle software on the same system, then each user must create a separate Oracle base directory. The following example Oracle base directories could all exist on the same system:
/u01/app/oracle /u01/app/orauser
The following sections describe how to identify existing Oracle base directories that may be suitable for the installation and how to create an Oracle base directory if necessary.
Regardless of whether you create an Oracle base directory or decide to use an existing one, you must set the ORACLE_BASE environment variable to specify the full path to this directory.
The Oracle Inventory directory (oraInventory) stores an inventory of all software installed on the system. It is required, and shared by all Oracle software installations on a single system. If you have an existing Oracle Inventory path, then Oracle Universal Installer continues to use that Oracle Inventory.
The first time you install Oracle software on a system, Oracle Universal Installer provides an OFA-compliant path in the format /u[01-09]/app, such as /u01/app. The user running the installation has permissions to write to that path. If this is true, then Oracle Universal Installer creates the Oracle Inventory directory in the path /u[01-09]/app/oraInventory. For example:
/u01/app/oraInventory
If you have set ORACLE_BASE for the oracle user during installation, then Oracle Universal Installer creates the Oracle Inventory directory in the path ORACLE_BASE/../oraInventory. For example, if ORACLE_BASE is set to /u01/app/oracle/, then the Oracle Inventory directory is created in the path /u01/app/oraInventory.
If you have created neither an OFA-compliant path nor set ORACLE_BASE, then the Oracle Inventory directory is placed in the home directory of the user that is performing the installation. For example:
/home/oracle/oraInventory
Oracle Universal Installer creates the directory that you specify and sets the correct owner, group, and permissions for it. You do not have to create it.
Note:
All Oracle software installations rely on this directory. Ensure that you back it up regularly.
Do not delete this directory unless you have completely removed all Oracle software from the system.
By default, the Oracle Inventory directory is not installed under the Oracle Base directory. This is because all Oracle software installations share a common Oracle Inventory, so there is only one Oracle Inventory for all users. Whereas, there is a separate Oracle Base for each user.
The Oracle home directory is the directory where you choose to install the software for a particular Oracle product. You must install different Oracle products, or different releases of the same Oracle product, in separate Oracle home directories. When you run Oracle Universal Installer, it prompts you to specify the path to this directory, and a name that identifies it. In accordance with the OFA guidelines, Oracle strongly recommends that the Oracle home directory you specify is a subdirectory of the Oracle base directory for the user account performing the installation. Oracle recommends that you specify a path similar to the following for the Oracle home directory:
$ORACLE_BASE/product/11.2.0/client_1
Oracle Universal Installer creates the directory path that you specify under the Oracle base directory. It also sets the correct owner, group, and permissions on it. You do not have to create this directory.
Caution:
During installation, you must not specify an existing directory that has predefined permissions applied to it as the Oracle home directory. If you do, then you may experience installation failure due to file and group ownership permission errors.Before starting the installation, you must either identify an existing Oracle base directory or if required, create one. This section contains information about the following:
Note:
You can choose to create an Oracle base directory, even if other Oracle base directories exist on the system.Existing Oracle base directories may not have paths that follow OFA guidelines. However, if you identify an existing Oracle Inventory directory or existing Oracle home directories, then you can usually identify the Oracle base directories, as follows:
Identifying an existing Oracle Inventory directory
Enter the following command to view the contents of the oraInst.loc file:
# more /etc/oraInst.loc
If the oraInst.loc file exists, then the output from this command is similar to the following:
inventory_loc=/u01/app/oraInventory inst_group=oinstall
The inventory_loc parameter identifies the Oracle Inventory directory (oraInventory). The parent directory of the oraInventory directory is typically an Oracle base directory. In the previous example, /u01/app/oracle is an Oracle base directory.
Identifying existing Oracle home directories
Enter the following command to view the contents of the oratab file:
# more /etc/oratab
If the oratab file exists, then it contains lines similar to the following:
*:/u03/app/oracle/product/11.2.0/dbhome_1:N *:/opt/orauser/infra_904:N *:/oracle/9.2.0:N
The directory paths specified on each line identify Oracle home directories. Directory paths that end with the user name of the Oracle software owner to use are valid choices for an Oracle base directory. If you intend to use the oracle user to install the software, then you could choose one of the following directories from the previous example:
/u03/app/oracle /oracle
Note:
If possible, choose a directory path similar to the first (/u03/app/oracle). This path complies with the OFA guidelines.Identifying existing Oracle base directories
After you have located the Oracle home directory, run a similar command to confirm the location of Oracle base:
cat /u01/app/oraInventory/ContentsXML/inventory.xml
To continue:
If an Oracle base directory exists and you want to use it, then refer to the "Configuring Oracle Software Owner Environment" section.
When you configure the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify the directory you chose.
If an Oracle base directory does not exist on the system or to create an Oracle base directory, refer to the following section.
Before you create an Oracle base directory, you must identify an appropriate file system with disk space.
To identify an appropriate file system:
To determine the free disk space on each mounted file system use the following command:
# df -k
From the display, identify a file system that has appropriate free space.
Note the name of the mount point directory for the file system that you identified.
To create the Oracle base directory and specify the correct owner, group, and permissions for it:
Enter commands similar to the following to create the recommended subdirectories in the mount point directory that you identified and set the appropriate owner, group, and permissions on them:
# mkdir -p /mount_point/app # chown -R oracle:oinstall /mount_point/app # chmod -R 775 /mount_point/app/
For example:
# mkdir -p /u01/app # chown -R oracle:oinstall /u01/app # chmod -R 775 /u01/app/
When you configure the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify the Oracle base directory that you have created.
You run Oracle Universal Installer from the oracle account. However, before you start Oracle Universal Installer you must configure the environment of the oracle user. To configure the environment, you must:
Set the default file mode creation mask (umask) to 022 in the shell startup file.
Set the DISPLAY environment variable.
Note:
Ensure that thePATH variable contains $ORACLE_HOME/bin before /usr/X11R6/bin.Caution:
Use shell programs supported by your operating system vendor. If you use a shell program that is not supported by your operating system, then you can encounter errors during installation.To set the oracle user's environment:
Start a new X terminal session (xterm).
Enter the following command to ensure that X Window applications can display on this system:
$ xhost fully_qualified_remote_host_name
For example:
$ xhost somehost.example.com
If you are not logged in to the system where you want to install the software, then log in to that system as the oracle user.
If you are not logged in as the oracle user, then switch user to oracle:
$ su - oracle
To determine the default shell for the oracle user, enter the following command:
$ echo $SHELL
To run the shell startup script, enter one of the following commands:
Bash shell:
$ . ./.bash_profile
Bourne or Korn shell:
$ . ./.profile
C shell:
% source ./.login
If you are not installing the software on the local system, then enter a command similar to the following to direct X applications to display on the local system:
Bourne, Bash, or Korn shell:
$ DISPLAY=local_host:0.0
C shell:
% setenv DISPLAY local_host:0.0
In this example, local_host is the host name or IP address of the system to use to display Oracle Universal Installer (your workstation or PC).
If you determined that the /tmp directory has less than 400 MB of free disk space, then identify a file system with at least 400 MB of free space and set the TMP and TMPDIR environment variables to specify a temporary directory on this file system:
To determine the free disk space on each mounted file system, use the following command:
# df -k
If necessary, enter commands similar to the following to create a temporary directory on the file system that you identified, and set the appropriate permissions on the directory:
su - root $ mkdir /mount_point/tmp $ chmod a+wr /mount_point/tmp #exit
Enter commands similar to the following to set the TMP and TMPDIR environment variables:
Bourne, Bash, or Korn shell:
$ TMP=/mount_point/tmp $ TMPDIR=/mount_point/tmp $ export TMP TMPDIR
C shell:
% setenv TMP /mount_point/tmp % setenv TMPDIR /mount_point/tmp
Enter the following commands to ensure that the ORACLE_HOME and TNS_ADMIN environment variables are not set:
Bourne, Bash, or Korn shell:
$ unset ORACLE_HOME $ unset TNS_ADMIN
C shell:
% unsetenv ORACLE_HOME % unsetenv TNS_ADMIN
Also, ensure that the $ORACLE_HOME/bin path is removed from your PATH environment variable.
Note:
If theORACLE_HOME environment variable is set, then Oracle Universal Installer uses the value that it specifies as the default path for the Oracle home directory. However, if you set the ORACLE_BASE environment variable, then Oracle recommends that you unset the ORACLE_HOME environment variable and choose the default path suggested by Oracle Universal Installer.To verify that the environment has been set correctly, enter the following commands:
$ umask $ env | more
Verify that the umask command displays a value of 22, 022, or 0022 and the environment variables that you set in this section have the correct values.