This guide contains information required to install Oracle Database Client 12c. 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.Following are the steps for installing the software from an X Window System workstation or X terminal:
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.us.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:
$ sudo sh password: #
Following are the steps for installing the software from a PC or other system with X server software:
Note:
If necessary, refer to your X server documentation 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:
$ sudo sh password: #
This section describes the following operating system tasks you must complete before you install Oracle Database:
Run the following commands to check your current system information:
To determine the physical RAM size, enter the following command:
# grep MemTotal /proc/meminfo
If the size of the physical RAM installed in the system is less than the required size, then you must install more memory before continuing.
To determine the size of the configured swap space, enter the following command:
# grep SwapTotal /proc/meminfo
If necessary, see your operating system documentation for information about how to configure additional swap space.
To determine the amount of space available in the /tmp directory, enter the following command:
# df -h /tmp
To determine the amount of free disk space on the system, enter the following command:
# df -h
To determine the amount of free RAM and disk swap space on the system, enter the following command:
# free
To determine if the system architecture can run the software, enter the following command:
# uname -m
Verify that the processor architecture matches the Oracle software release to install. For example, you should see the following for a x86-64 bit system:
x86_64
If you do not see the expected output, then you cannot install the software on this system.
Ensure the following general minimum requirements on your system:
Ensure that the system is started with runlevel 3 or runlevel 5.
Ensure display cards provide at least 1024 x 768 display resolution, so that Oracle Universal Installer displays correctly while performing a system console-based installation
Ensure that your system meets the following minimum storage requirements, depending on your system architecture:
Ensure that your Linux x86-64 system meets the disk space requirements for software files as described in Table 2-1
Table 2-1 Disk Space Requirements for Software Files on Linux x86-64
| Installation Type | Disk Space |
|---|---|
|
Instant Client |
260 MB |
|
Administrator |
1.8 GB |
|
Runtime |
1.4 GB |
|
Custom (maximum) |
1.8 GB |
Additional disk space, either on a file system or on an Oracle ASM disk group is required for the fast recovery area if you configure automated backups.
Table 2-2 describes the minimum disk space requirements for software files for each installation type on IBM: Linux on System z:
400 MB of space in the /tmp directory on your Linux system.
If the free 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.
See Also:
"Configuring Oracle Software Owner Environment" for more information about settingTMP and TMPDIRExtend the file system that contains the /tmp directory.
Ensure that your system meets the following memory requirements:
At least 256 MB of RAM
Table 2-3 describes the relationship between the installed RAM and the configured swap space recommendation:
Table 2-3 Swap Space Requirement for Linux
| 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 |
Note:
The HugePages feature allocates non-swappable memory for large page tables using memory-mapped files. If you enable HugePages, then you should deduct the memory allocated to HugePages from the available RAM before calculating swap space.Table 2-4 lists the recommended hardware requirements for SQL Developer.
Secure operating systems are an important basis for general system security. Ensure that your operating system deployment is in compliance with common security practices as described in your operating system vendor security guide.
Depending on the products that you intend to install, verify that you have the required operating system kernel and packages installed.
Requirements listed in this document are current as of the date listed on the title page. To obtain the most current information about kernel requirements, see the online version on the Oracle Technology Network at the following URL:
http://www.oracle.com/technetwork/indexes/documentation/index.html
Oracle Universal Installer performs checks your system to verify that it meets the listed operating system package requirements. To ensure that these checks complete successfully, verify the requirements before you start Oracle Universal Installer.
The Linux distributions and packages listed in this section are supported for this release on x86-64. No other Linux distributions are supported.
Identify operating system requirements for Oracle Grid Infrastructure, and identify additional operating sytem requirements for Oracle Database and Oracle RAC installations.
Supported Oracle Linux 7 and Red Hat Enterprise Linux 7 Distributions for x86-64
Supported Oracle Linux 6 and Red Hat Enterprise Linux 6 Distributions for x86-64
Supported Oracle Linux 5 and Red Hat Enterprise Linux 5 Distributions for x86-64
Note:
The Oracle Unbreakable Enterprise Kernel can be installed on x86-64 servers running either Oracle Linux 5 Update 5, or Red Hat Enterprise Linux 5 Update 5. As of Oracle Linux 5 Update 6, the Oracle Unbreakable Enterprise Kernel is the default system kernel. An x86 (32-bit) release of Oracle Linux including the Oracle Unbreakable Enterprise Kernel is available with Oracle Linux 5 update 7 and later.
The 32-bit packages listed in the following sections are required only for 32-bit client installs.
Oracle Universal Installer requires an X Window System (for example, libx). The libx packages are part of a default Linux installation. If you install Linux using an Oracle RDBMS Server 12cR1 Pre-Install RPM, then the libx packages are installed as part of that RPM. If you perform an install on a system with a reduced set of packages, then you must ensure that libx is installed.
Use the following information to check supported Oracle Linux 7 and Red Hat Linux 7 distributions:
Note:
Starting with Oracle Database 12c Release 1 (12.1.0.2), Oracle Linux 7 and Red Hat Enterprise Linux 7 are supported on Linux x86-64 systems.Table 2-5 x86-64 Supported Linux 7 Minimum Operating System Requirements
| Item | Requirements |
|---|---|
|
Oracle Linux 7 |
Subscribe to the Oracle Linux 7 channel on the Unbreakable Linux Network, or configure a yum repository from the Oracle public yum site, and then install the Oracle Preinstallation RPM. This RPM installs all required kernel packages for Oracle Grid Infrastructure and Oracle Database installations, and performs other system configuration. Supported distributions:
|
|
Red Hat Enterprise Linux 7 |
Supported distributions:
|
|
Packages for Oracle Linux 7 and Red Hat Enterprise Linux 7 |
The following packages (or later versions) must be installed: binutils-2.23.52.0.1-12.el7.x86_64 compat-libcap1-1.10-3.el7.x86_64 gcc-4.8.2-3.el7.x86_64 gcc-c++-4.8.2-3.el7.x86_64 glibc-2.17-36.el7.i686 glibc-2.17-36.el7.x86_64 glibc-devel-2.17-36.el7.i686 glibc-devel-2.17-36.el7.x86_64 ksh libaio-0.3.109-9.el7.i686 libaio-0.3.109-9.el7.x86_64 libaio-devel-0.3.109-9.el7.i686 libaio-devel-0.3.109-9.el7.x86_64 libgcc-4.8.2-3.el7.i686 libgcc-4.8.2-3.el7.x86_64 libstdc++-4.8.2-3.el7.i686 libstdc++-4.8.2-3.el7.x86_64 libstdc++-devel-4.8.2-3.el7.i686 libstdc++-devel-4.8.2-3.el7.x86_64 libXi-1.7.2-1.el7.i686 libXi-1.7.2-1.el7.x86_64 libXtst-1.2.2-1.el7.i686 libXtst-1.2.2-1.el7.x86_64 make-3.82-19.el7.x86_64 sysstat-10.1.5-1.el7.x86_64 |
Use the following information to check supported Oracle Linux 6 and Red Hat Linux 6 distributions:
Table 2-6 x86-64 Supported Linux 6 Operating System Requirements
| Item | Requirements |
|---|---|
|
Oracle Linux 6 |
Subscribe to the Oracle Linux 6 channel on the Unbreakable Linux Network, or configure a yum repository from the Oracle public yum site, and then install the Oracle RDBMS Pre-Install RPM. This RPM installs all required kernel packages for Oracle Grid Infrastructure and Oracle Database installations, and performs other system configuration. Supported distributions:
|
|
Red Hat Enterprise Linux 6 |
Supported distributions:
|
|
Packages for Oracle Linux 6 and Red Hat Enterprise Linux 6 |
The following packages (or later versions) must be installed: binutils-2.20.51.0.2-5.11.el6 (x86_64) compat-libcap1-1.10-1 (x86_64) compat-libstdc++-33-3.2.3-69.el6 (x86_64) compat-libstdc++-33-3.2.3-69.el6 (i686) gcc-4.4.4-13.el6 (x86_64) gcc-c++-4.4.4-13.el6 (x86_64) glibc-2.12-1.7.el6 (i686) glibc-2.12-1.7.el6 (x86_64) glibc-devel-2.12-1.7.el6 (x86_64) glibc-devel-2.12-1.7.el6 (i686) ksh libgcc-4.4.4-13.el6 (i686) libgcc-4.4.4-13.el6 (x86_64) libstdc++-4.4.4-13.el6 (x86_64) libstdc++-4.4.4-13.el6 (i686) libstdc++-devel-4.4.4-13.el6 (x86_64) libstdc++-devel-4.4.4-13.el6 (i686) libaio-0.3.107-10.el6 (x86_64) libaio-0.3.107-10.el6 (i686) libaio-devel-0.3.107-10.el6 (x86_64) libaio-devel-0.3.107-10.el6 (i686) libXext-1.1 (x86_64) libXext-1.1 (i686) libXtst-1.0.99.2 (x86_64) libXtst-1.0.99.2 (i686) libX11-1.3 (x86_64) libX11-1.3 (i686) libXau-1.0.5 (x86_64) libXau-1.0.5 (i686) libxcb-1.5 (x86_64) libxcb-1.5 (i686) libXi-1.3 (x86_64) libXi-1.3 (i686) make-3.81-19.el6 sysstat-9.0.4-11.el6 (x86_64) |
Use the following information to check supported Oracle Linux 5 and Red Hat Linux 5 distributions:
Table 2-7 x86-64 Supported Linux 5 Operating System Requirements
| Item | Requirements |
|---|---|
|
Oracle Linux 5 |
Subscribe to the Oracle Linux 5 channel on the Unbreakable Linux Network, and then install the Oracle Validated RPM. This RPM installs all required kernel packages for Oracle Grid Infrastructure and Oracle Database installations, and performs other system configuration. Supported distributions:
|
|
Red Hat Enterprise Linux 5 |
Supported distributions:
|
|
Package requirements for Oracle Linux 5 and Red Hat Enterprise Linux 5 |
The following packages (or later versions) must be installed: binutils-2.17.50.0.6 compat-libstdc++-33-3.2.3 compat-libstdc++-33-3.2.3 (32 bit) gcc-4.1.2 gcc-c++-4.1.2 glibc-2.5-58 glibc-2.5-58 (32 bit) glibc-devel-2.5-58 glibc-devel-2.5-58 (32 bit) ksh libaio-0.3.106 libaio-0.3.106 (32 bit) libaio-devel-0.3.106 libaio-devel-0.3.106 (32 bit) libgcc-4.1.2 libgcc-4.1.2 (32 bit) libstdc++-4.1.2 libstdc++-4.1.2 (32 bit) libstdc++-devel 4.1.2 libXext-1.0.1 libXext-1.0.1 (32 bit) libXtst-1.0.1 libXtst-1.0.1 (32 bit) libX11-1.0.3 libX11-1.0.3 (32 bit) libXau-1.0.1 libXau-1.0.1 (32 bit) libXi-1.0.1 libXi-1.0.1 (32 bit) make-3.81 sysstat-7.0.2 |
Use the following information to check supported SUSE distributions:
Table 2-8 x86-64 Supported SUSE Operating System Requirements
| Item | Requirements |
|---|---|
|
SUSE Linux Enterprise Server |
Supported distributions:
|
|
SUSE 11 |
The following packages (or later versions) must be installed: binutils-2.21.1-0.7.25 gcc-4.3-62.198 gcc-c++-4.3-62.198 glibc-2.11.3-17.31.1 glibc-devel-2.11.3-17.31.1 ksh-93u-0.6.1 libaio-0.3.109-0.1.46 libaio-devel-0.3.109-0.1.46 libcap1-1.10-6.10 libstdc++33-3.3.3-11.9 libstdc++33-32bit-3.3.3-11.9 libstdc++43-devel-4.3.4_20091019-0.22.17 libstdc++46-4.6.1_20110701-0.13.9 libgcc46-4.6.1_20110701-0.13.9 make-3.81 sysstat-8.1.5-7.32.1 xorg-x11-libs-32bit-7.4 xorg-x11-libs-7.4 xorg-x11-libX11-32bit-7.4 xorg-x11-libX11-7.4 xorg-x11-libXau-32bit-7.4 xorg-x11-libXau-7.4 xorg-x11-libxcb-32bit-7.4 xorg-x11-libxcb-7.4 xorg-x11-libXext-32bit-7.4 xorg-x11-libXext-7.4 |
The distributions and packages listed in this section are supported for this release on IBM: Linux on System z. No other IBM: Linux on System z distributions are supported.
Identify operating system requirements for Oracle Grid Infrastructure, and identify additional operating sytem requirements for Oracle Database and Oracle RAC installations.
Supported Red Hat Enterprise Linux 6 Distributions for IBM: Linux on System z
Supported Red Hat Enterprise Linux 5 Distributions for IBM: Linux on System z
Note:
The 32-bit packages listed in the following sections are required only for 32-bit client installs.
Oracle Universal Installer requires an X Window System (for example, libX). The libx packages are part of a default Linux installation. If you perform an install on a system with a reduced set of packages, then you must ensure that libX is installed.
Use the following information to check the supported Red Hat Linux 6 distributions:
Table 2-9 Linux 6 Minimum Operating System Requirements
| Item | Requirements |
|---|---|
|
SSH Requirement |
Ensure that OpenSSH is installed on your servers. OpenSSH is the required SSH software. |
|
Red Hat Enterprise Linux 6 |
Red Hat Enterprise Linux 6.3 (2.6.32-279.el6.s390x or later) Note: You can install on Red Hat Enterprise Linux 6 Update 3, but Oracle recommends that you install on Red Hat Enterprise Linux 6 Update 4 as RHEL 6.4 includes significant I/O performance gains on Open Storage. See My Oracle Support Note 1574412.1 for more information: https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1574412.1 |
|
Packages for Red Hat Enterprise Linux 6 |
The following packages (or later versions) must be installed: binutils-2.20.51.0.2-5.34.el6 (s390x) compat-libstdc++-33-3.2.3-69.el6 (s390) compat-libstdc++-33-3.2.3-69.el6 (s390x) compat-libcap1-1.10-1 (s390x) gcc-4.4.6-4.el6 (s390x) gcc-c++-4.4.6-4.el6 (s390x) glibc-2.12-1.80.el6 (s390) glibc-2.12-1.80.el6 (s390x) glibc-devel-2.12-1.80.el6 (s390) glibc-devel-2.12-1.80.el6 (s390x) ksh-20100621-16.el6 (s390x) libaio-0.3.107-10.el6 (s390) libaio-0.3.107-10.el6 (s390x) libaio-devel-0.3.107-10.el6 (s390x) libgcc-4.4.6-4.el6 (s390) libgcc-4.4.6-4.el6 (s390x) libstdc++-4.4.6-4.el6 (s390x) libstdc++-devel-4.4.6-4.el6 (s390x) libXtst-1.0.99.2-3.el6 (s390) libXtst-1.0.99.2-3.el6 (s390x) libXi-1.3-3.el6 (s390) libXi-1.3-3.el6 (s390x) libXmu-1.0.5-1.el6 (s390) libXaw-1.0.6-4.1.el6 (s390) libXft-2.1.13-4.1.el6 (s390) libXp-1.0.0-15.1.el6 (s390) make-3.81-20.el6 (s390x) sysstat-9.0.4-20.el6 (s390x) |
Use the following information to check supported Red Hat Linux 5 distributions:
Table 2-10 Linux 5 Minimum Operating System Requirements
| Item | Requirements |
|---|---|
|
SSH Requirement |
Ensure that OpenSSH is installed on your servers. OpenSSH is the required SSH software. |
|
Red Hat Enterprise Linux 5 |
Red Hat Enterprise Linux 5.8 (2.6.18-308.el5 s390x or later) |
|
Package requirements for Red Hat Enterprise Linux 5 |
The following packages (or later versions) must be installed: binutils-2.17.50.0.6-20.el5 (s390x) compat-libstdc++-33-3.2.3-61 (s390) compat-libstdc++-33-3.2.3-61 (s390x) gcc-c++-4.1.2-52.el5 (s390x) glibc-2.5-81 (s390) glibc-2.5-81 (s390x) glibc-devel-2.5-81 (s390) glibc-devel-2.5-81 (s390x) ksh-20100621-5.el5 (s390x) libaio-0.3.106-5 (s390) libaio-0.3.106-5 (s390x) libaio-devel-0.3.106-5 (s390) libaio-devel-0.3.106-5 (s390x) libgcc-4.1.2-52.el5 (s390) libgcc-4.1.2-52.el5 (s390x) libstdc++-4.1.2-52.el5 (s390) libstdc++-4.1.2-52.el5 (s390x) libstdc++-devel-4.1.2-52.el5 (s390x) libstdc++44-devel-4.4.6-3.el5.1 (s390) libstdc++44-devel-4.4.6-3.el5.1 (s390x) libXtst-1.0.1-3.1 (s390) libXtst-1.0.1-3.1 (s390x) libXi-1.0.1-4.el5_4 (s390) libXi-1.0.1-4.el5_4 (s390x) make-3.81-3.el5 (s390x) sysstat-7.0.2-11.el5 (s390x) |
Use the following information to check supported SUSE distributions:
Table 2-11 SUSE 11 Minimum Operating System Requirements
| Item | Requirements |
|---|---|
|
SSH Requirement |
Ensure that OpenSSH is installed on your servers. OpenSSH is the required SSH software. |
|
SUSE Linux Enterprise Server |
SUSE Linux Enterprise Server 11 SP2 (3.0.13-0.27-default s390x or later). |
|
SUSE 11 |
The following packages (or later versions) must be installed: binutils-2.21.1-0.7.25 (s390x) gcc-4.3-62.198 (s390x) gcc-c++-4.3-62.198 (s390x) glibc-2.11.3-17.31.1 (s390x) glibc-32bit-2.11.3-17.31.1 (s390x) glibc-devel-2.11.3-17.31.1 (s390x) glibc-devel-32bit-2.11.3-17.31.1 (s390x) ksh-93u-0.6.1 (s390x) make-3.81-128.20 (s390x) libaio-0.3.109-0.1.46 (s390x) libaio-32bit-0.3.109-0.1.46 (s390x) libaio-devel-0.3.109-0.1.46 (s390x) libaio-devel-32bit-0.3.109-0.1.46 (s390x) libcap1-1.10-6.10 (s390x) libgcc46-4.6.1_20110701-0.13.9 (s390x) libstdc++33-3.3.3-11.9 (s390x) libstdc++33-32bit-3.3.3-11.9 (s390x) libstdc++43-devel-32bit-4.3.4_20091019-0.22.17 (s390x) libstdc++43-devel-4.3.4_20091019-0.22.17 (s390x) libstdc++46-32bit-4.6.1_20110701-0.13.9 (s390x) libstdc++46-4.6.1_20110701-0.13.9 (s390x) sysstat-8.1.5-7.32.1 (s390x) xorg-x11-libs-32bit-7.4-8.26.32.1 (s390x) xorg-x11-libs-7.4-8.26.32.1 (s390x) xorg-x11-libX11-32bit-7.4-5.9.1 (s390x) xorg-x11-libX11-7.4-5.9.1 (s390x) xorg-x11-libXau-32bit-7.4-1.15 (s390x) xorg-x11-libXau-7.4-1.15 (s390x) xorg-x11-libxcb-7.4-1.20.34 (s390x) xorg-x11-libxcb-32bit-7.4-1.20.34 (s390x) xorg-x11-libXext-32bit-7.4-1.16.21 (s390x) xorg-x11-libXext-7.4-1.16.21 (s390x) |
You are not required to install additional drivers and packages, but you may choose to install or configure drivers and packages in the following list:
Installation Requirements for Lightweight Directory Access Protocol
Installation Requirements for Programming Environments for Linux
Note:
Oracle Database Smart Flash Cache is an Enterprise Edition only feature.Review the following sections if you plan to install Open Database Connectivity (ODBC):
Open Database Connectivity (ODBC) is a set of database access APIs that connect to the database, prepare, and then run SQL statements on the database. An application that uses an ODBC driver can access non-uniform data sources, such as spreadsheets and comma-delimited files.
Review the minimum supported ODBC driver, and install the following ODBC driver, or later releases, for all distributions of Linux:
unixODBC-2.3.1 or later
Review the following sections to install PAM:
Pluggable Authentication Modules (PAM) is a system of libraries that handle user authentication tasks for applications. On Linux, external scheduler jobs require PAM. Oracle strongly recommends that you install the latest Linux-PAM library for your Linux distribution.
Use a package management system (yum, up2date, YaST) for your distribution to install the latest pam library.
Review the following sections to install Oracle Messaging Gateway:
Oracle Messaging Gateway is a feature of the Oracle database. It enables communication between applications based on non-Oracle messaging systems and Oracle Streams Advanced Queuing.
Oracle Messaging Gateway supports the integration of Oracle Streams Advanced Queuing (AQ) with applications based on WebSphere and TIBCO Rendezvous. For information on supported versions see Oracle Database Advanced Queuing User's Guide.
Note:
Oracle Messaging Gateway does not support the integration of Advanced Queuing with TIBCO Rendezvous on IBM: Linux on System z.Oracle Messaging Gateway is installed with Oracle Database.
If you require a CSD or Fix Pack for IBM WebSphere MQ, then see the following website for more information:
Review the following sections to install Lightweight Directory Access Protocol:
Lightweight Directory Access Protocol (LDAP) is an application protocol for accessing and maintaining distributed directory information services over IP networks. You require the LDAP package if you want to use features requiring LDAP, including the Oracle Database scripts odisrvreg and oidca for Oracle Internet Directory, or schemasync for third-party LDAP directories.
LDAP is included in a default Linux operating system installation.
If you did not perform a default Linux installation, and you intend to use Oracle scripts requiring LDAP, then use a package management system (up2date, YaST) for your distribution to install a supported LDAP package for your distribution, and install any other required packages for that LDAP package.
Review the following sections to install programming environments:
Oracle Database supports multiple programming languages for application development in different environments. Some languages require that you install additional compiler packages for the operating system.
Programming environments are options. They are not required for Oracle Database.
See Also :
Oracle Database Development Guide for an overview of programming environmentsEnsure that your system meets the requirements for the programming environment you want to configure:
Table 2-12 Requirements for Programming Environments for Linux x86-64
| Programming Environments | Support Requirements |
|---|---|
|
Java Database Connectivity (JDBC) / Oracle Call Interface (OCI) |
JDK 6 (Java SE Development Kit release 1.6.0_37 or later updates to 1.6) with the JNDI extension with Oracle Java Database Connectivity. JDK 1.6 is installed with this release. |
Oracle C++ Oracle C++ Call Interface Pro*C/C++ Oracle XML Developer's Kit (XDK) |
Intel C/C++ Compiler 12.0.5 or later, and the version of GNU C and C++ compilers listed in the software requirements section in this document for your platform. Oracle C++ Call Interface (OCCI) applications can be built only with Intel C++ Compiler 12.0.5 used with the standard template libraries of the gcc versions listed in the software requirements section in this document for your platform. Oracle XML Developer's Kit is supported with the same compilers as OCCI. |
|
Pro*COBOL |
Micro Focus Server Express 5.1 |
Table 2-13 Requirements for Programming Environments for IBM: Linux on System z
| Programming Environments | Support Requirements |
|---|---|
|
Java Database Connectivity (JDBC) / Oracle Call Interface (OCI) |
JDK 1.6 is installed with this release. |
|
Pro*COBOL |
Micro Focus Server Express 5.1 |
Web browsers are required only if you intend to use Oracle Enterprise Manager Database Express and Oracle Enterprise Manager Cloud Control. Web browsers must support Java Script, and the HTML 4.0 and CSS 1.0 standards. For a list of browsers that meet these requirements see the Enterprise Manager certification matrix on My Oracle Support:
https://support.oracle.com
See Also:
Oracle Enterprise Manager Cloud Control Basic Installation Guide for steps on how to access the Enterprise Manager certification matrixTo ensure that the system meets these requirements, follow these steps:
To determine the distribution and version of Linux installed, enter one of the following commands:
# cat /etc/oracle-release # cat /etc/redhat-release # lsb_release -id
To determine whether the required kernel errata is installed, enter the following command:
# uname -r
The following is sample output displayed by running this command on an Oracle Linux 6 system:
2.6.39-100.7.1.el6uek.x86_64
Review the required errata level for your distribution. If the errata level is previous to the required minimum errata update, then obtain and install the latest kernel update from your Linux distributor.
To determine whether the required packages are installed, enter commands similar to the following:
# rpm -q package_name
Alternatively, if you require specific system architecture information, then enter the following command:
# rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" | grep package_name
You can also combine a query for multiple packages, and review the output for the correct versions. For example:
# rpm -q binutils compat-libstdc++ gcc glibc libaio libgcc libstdc++ \ make sysstat unixodbc
If a package is not installed, then install it from your Linux distribution media or download the required package version from your Linux distributor's website.
In addition to the requirements described in the preceding sections, 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.
The 64-bit Oracle Database 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.
The 64-bit Oracle Database Client preinstallation requirements apply to 32-bit Oracle Database Client also.
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
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
Creating the Oracle Inventory Group
If the oraInst.loc file does not exist, then create the Oracle Inventory group as follows:
# /usr/sbin/groupadd oinstall
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 Database Client 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.
To create the oracle user, enter a command similar to the following:
# /usr/sbin/useradd -g oinstall[ -G dba]oracle
In this command:
The -g option specifies the primary group, which must be the Oracle Inventory group, for example, oinstall
The -G option specifies optional secondary groups. It must include the OSDBA group, and if required the OSOPER group. For example, dba, osoper.
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:
# /usr/sbin/usermod -g oinstall -G dba oracle
Specify the primary group using the -g option and any required secondary group using the -G option.
Note:
Oracle does not support modifying existing Oracle Database server or other Oracle software installation owners. Oracle only supports modifying an Oracle Database Client software owner.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/12.1.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/12.1.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 -h
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.
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 + RemoteHost
where RemoteHost is the 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:
$ sudo mkdir /mount_point/tmp $ sudo 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
If you have had an existing installation on your system, and you are using the same user account to install this installation, then unset the ORACLE_HOME, ORACLE_BASE, ORACLE_SID, TNS_ADMIN environment variables and any other environment variable set for the Oracle installation user that is connected with Oracle software homes.
Enter the following commands to ensure that the ORACLE_HOME, ORACLE_BASE, ORACLE_SID and TNS_ADMIN environment variables are not set:
Bourne, Bash, or Korn shell:
$ unset ORACLE_HOME $ unset ORACLE_BASE $ unset ORACLE_SID $ unset TNS_ADMIN
C shell:
% unsetenv ORACLE_HOME % unsetenv ORACLE_BASE % unsetenv ORACLE_SID % unsetenv TNS_ADMIN
Use the following command to check the PATH environment variable:
$ echo $PATH
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. 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.