Oracle database 12c client installation guide 4

[1]Oracle® Database
Client Installation Guide
12c Release 1 (12.1) for IBM: Linux on POWER Big Endian Sys-
tems
E64366-02
March 2016

Oracle Database Client Installation Guide, 12c Release 1 (12.1) for IBM: Linux on POWER Big Endian Systems
E64366-02
Copyright © 2016, Oracle and/or its affiliates. All rights reserved.
Primary Author: Nisha Sridhar
Contributing Author: Bharathi Jayathirtha
Contributors: Janelle Simmons, David Austin, Rohitash Panda, Subhranshu Banerjee, Mark Bauer, Robert
Chang, Jonathan Creighton, Sudip Datta, Thirumaleshwara Hasandka, Joel Kallman, George Kotsovolos,
Simon Law, Shekhar Vaggu, Richard Long, Rolly Lv, Padmanabhan Manavazhi, Sreejith Minnanghat,
Krishna Mohan, Rajendra Pingte, Hanlin Qian, Roy Swonger, Namrata Bhakthavatsalam, Ranjith Kundapur,
Aneesh Khandelwal , Barb Lundhild, Barbara Glover, Binoy Sukumaran, Prasad Bagal, Martin Widjaja,
Ajesh Viswambharan, Eric Belden, Sivakumar Yarlagadda, Rudregowda Mallegowda , Matthew McKerley,
Trivikrama Samudrala, Akshay Shah, Sue Lee, Sangeeth Kumar, James Spiller, Saar Maoz, Rich Long, Mark
Fuller, Sunil Ravindrachar, Sergiusz Wolicki, Eugene Karichkin, Joseph Francis, Srinivas Poovala, David
Schreiner, Neha Avasthy, Dipak Saggi, Sudheendra Sampath, Mohammed Shahnawaz Quadri, Shachi
Sanklecha, Zakia Zerhouni, Jai Krishnani, Darcy Christensen, Kevin Flood, Clara Jaeckel, Emily Murphy,
Terri Winters
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it
on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users
are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and
adaptation of the programs, including any operating system, integrated software, any programs installed on
the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to
the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages
caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of
third-party content, products, or services, except as set forth in an applicable agreement between you and
Oracle.

iii
Contents
Preface................................................................................................................................................................. v
Audience....................................................................................................................................................... v
Documentation Accessibility..................................................................................................................... v
Command Syntax........................................................................................................................................ v
Related Documentation.............................................................................................................................. vi
Typographic Conventions.......................................................................................................................... vi
1 Overview of Oracle Database Client Installation
1.1 Planning Your Installation......................................................................................................... 1-1
1.2 Installation Considerations........................................................................................................ 1-1
1.3 Oracle Database Client Installation Types .............................................................................. 1-2
1.4 Oracle Database Client and Oracle Database Interoperability............................................. 1-2
1.5 Simplified Patching of Timestamp with Time Zone Data Type .......................................... 1-3
2 Oracle Database Client Preinstallation Tasks
2.1 Logging In to the System as root .............................................................................................. 2-1
2.2 Checking the Hardware Requirements ................................................................................... 2-2
2.2.1 Memory Requirements ....................................................................................................... 2-2
2.2.2 System Architecture ............................................................................................................ 2-3
2.2.3 Disk Space Requirements ................................................................................................... 2-3
2.2.4 Display Requirements......................................................................................................... 2-4
2.2.5 Recommended Hardware Requirement for SQL Developer ........................................ 2-4
2.3 Checking the Software Requirements...................................................................................... 2-4
2.3.1 Instant Client Light Requirements.................................................................................... 2-9
3 Installing and Removing Oracle Database Client
3.1 Downloading and Installing the Oracle Database Client Software..................................... 3-1
3.2 Removing the Oracle Database Client Software .................................................................... 3-2
4 Oracle Database Client Postinstallation Tasks
4.1 Required Postinstallation Tasks................................................................................................ 4-1
4.1.1 Updating Instant Client ...................................................................................................... 4-1
4.1.2 Connecting with Instant Client.......................................................................................... 4-2
4.2 Recommended Postinstallation Tasks ..................................................................................... 4-2

iv
4.2.1 Connecting Instant Client or Instant Client Light to an Oracle Database................... 4-2
4.2.1.1 Specifying a Connection by Using the Easy Connect Naming Method............... 4-3
4.2.1.2 Specifying a Connection Using an Empty Connect String and TWO_TASK...... 4-3
4.2.2 Setting the NLS_LANG Environment Variable .............................................................. 4-4
4.3 Required Product-Specific Postinstallation Tasks.................................................................. 4-4
4.3.1 Configuring Oracle Precompilers...................................................................................... 4-4
4.3.1.1 Configuring Pro*C/C++.............................................................................................. 4-4
4.3.2 Compiling with GCC/G++ ................................................................................................ 4-4
Index

v
Preface
This guide provides instructions about installing and configuring Oracle Database
Client for Linux on POWER Systems. This guide also describes about installing and
configuring database using response files, globalization support, ports, and
troubleshooting.
The preface contains the following topics:
■ Audience
■ Documentation Accessibility
■ Command Syntax
■ Related Documentation
■ Typographic Conventions
Audience
This guide is intended for anyone responsible for installing Oracle Database Client 12c
Release 1 (12.1). Additional platform-specific installation guides for Oracle Database,
Oracle Real Application Clusters, Oracle Clusterware, Oracle Database Examples, and
Oracle Enterprise Manager Grid Control are available at
http://docs.oracle.com/en/database/database.html
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support
through My Oracle Support. For information, visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing
impaired.
Command Syntax
UNIX command syntax appears in monospace font. The dollar character ($), number
sign (#), or percent character (%) are UNIX command prompts. Do not enter them as

vi
part of the command. The following command syntax conventions are used in this
guide:
Convention Description
backslash A backslash is the UNIX command continuation character. It is used in
command examples that are too long to fit on a single line. Enter the
command as displayed (with a backslash) or enter it on a single line
without a backslash:
dd if=/dev/rdsk/c0t1d0s6 of=/dev/rst0 bs=10b
count=10000
braces { } Braces indicate required items:
.DEFINE {macro1}
brackets [ ] Brackets indicate optional items:
cvtcrt termname [outfile]
ellipses ... Ellipses indicate an arbitrary number of similar items:
CHKVAL fieldname value1 value2 ... valueN
italics Italic type indicates a variable. Substitute a value for the variable:
library_name
vertical line | A vertical line indicates a choice within braces or brackets:
FILE filesize [K|M]
Related Documentation
The product-specific and platform-specific documentation for Oracle Database
products are available in both, PDF and HTML formats. You can view and download
the documentation at
http://docs.oracle.com/en/
See Oracle Database Client Release Notes for IBM: Linux on POWER Big Endian Systems for
important information that was not available when this book was released.
Typographic Conventions
The following text conventions are used in this document:
Convention Meaning
boldface Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code
in examples, text that appears on the screen, or text that you enter.

1
Overview of Oracle Database Client Installation 1-1
1Overview of Oracle Database Client Installation
This chapter describes the different installation types of Oracle Database Client and
issues to consider before you install Oracle Database Client:
■ Planning Your Installation
■ Installation Considerations
■ Oracle Database Client Installation Types
■ Oracle Database Client and Oracle Database Interoperability
■ Simplified Patching of Timestamp with Time Zone Data Type
1.1 Planning Your Installation
The Oracle Database Client installation process consists of the following phases:
1. Read the release notes: Read the Oracle Database Client Release Notes for IBM: Linux
on POWER Big Endian Systems before you begin the installation.
2. Review the licensing information: Although the installation media in your media
pack contain many Oracle components, you are permitted to use only those
components for which you have purchased licenses.
Oracle Support Services does not provide support for components for which
licenses have not been purchased.
See Also: Oracle Database Licensing Information
3. Plan the installation: This chapter describes the Oracle products that you can
install and issues that you must consider before starting the installation.
4. Complete preinstallation tasks: Chapter 2 describes preinstallation tasks that you
must complete before installing the product.
5. Install the software: Chapter 3 describes how to install Oracle Database Client.
6. Complete postinstallation tasks: Chapter 4 describes recommended and required
postinstallation tasks.
1.2 Installation Considerations
This section contains hardware and software certification information that you should
consider before deciding to install this product.
The platform-specific hardware and software requirements included in this guide
were current when this guide was published. However, because new platforms and

Oracle Database Client Installation Types
1-2 Oracle Database Client Installation Guide
operating system software versions might 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 My
Oracle Support website is available at
https://support.oracle.com/
You must register online before using My Oracle Support. After logging in, from the
menu options, select the Certifications tab. On the Certifications page, use the
Certification Search options to search by Product, Release, and Platform. You can also
search using the Certification Quick Link options such as Product Delivery and
Lifetime Support.
1.3 Oracle Database Client Installation Types
The Instant Client Enables you to install only the shared libraries required by Oracle
Call Interface (OCI), Oracle C++ Call Interface (OCCI), Pro*C, or Java Database
Connectivity (JDBC) OCI applications. This installation type requires much less disk
space than the other Oracle Database Client installation types.
For more information about Instant Client, see Oracle Call Interface Programmer's Guide
or Oracle Database JDBC Developer's Guide.
Included in the Instant Client installation is Instant Client Light. You may want to use
this version of Instant Client if the applications generate error messages in American
English only. Instant Client Light is beneficial to application that use one of the
supported character sets and can accept error messages in American English. The
following are the supported character sets:
■ US7ASCII
■ WE8DEC
■ WE8MSWIN1252
■ WE8ISO8859P1
■ WE8EBCDIC37C for EBCDIC platforms only
■ WE8EBCDIC1047 for EBCDIC platforms only
■ UTF8
■ AL32UTF8
■ AL16UTF16
The advantage of using Instant Client Light is that it has a smaller footprint than
the regular Instant Client. The shared libraries, which an application must load,
are only 34 MB as opposed to the 110 MB that regular Instant Client uses.
Therefore, the applications use less memory.
1.4 Oracle Database Client and Oracle Database Interoperability
For information about interoperability between Oracle Database Client and Oracle
Database releases, see Note 207303.1 on the My Oracle Support website at
https://support.oracle.com/

Simplified Patching of Timestamp with Time Zone Data Type
Overview of Oracle Database Client Installation 1-3
1.5 Simplified Patching of Timestamp with Time Zone Data Type
Starting with Oracle Database 11g Release 2 (11.2), the patching process of TIMESTAMP
WITH TIMEZONE data type values is simplified.
For information about simplified patching process and how certain clients work with
server with different time zone files "Oracle Database 12c Release 1 (12.1) New
Features in Globalization" and "Clients and Servers Operating with Different Versions
of Time Zone Files" in Oracle Database Globalization Support Guide.

Simplified Patching of Timestamp with Time Zone Data Type

2
Oracle Database Client Preinstallation Tasks 2-1
2Oracle Database Client Preinstallation Tasks
This chapter describes the tasks that you must complete before you install Oracle
Instant Client. It includes the following information:
■ Logging In to the System as root
■ Checking the Hardware Requirements
■ Checking the Software Requirements
2.1 Logging In to the System as root
Before you install the Oracle software, you must complete several tasks as the root
user. To log in as the root user, complete the following procedure:
■ If you are installing the software from an X Window System workstation or X
terminal, then:
1. Start a local terminal session (xterm).
2. 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.acme.com
3. 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
4. If you are not logged in as the root user, then enter the following command to
switch user to root:
$ su - root
password:
#
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.

Checking the Hardware Requirements
■ If you are installing the software from a PC or other system with X server software
installed, then:
1. Start the X server software.
2. Configure the security settings of the X server software to permit remote hosts to
display X applications on the local system.
3. 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).
4. 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:
#
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 need to complete the
tasks in a different order.
2.2 Checking the Hardware Requirements
The system must meet the following minimum hardware requirements for Oracle
Database Client 12c Release 1 (12.1):
■ Memory Requirements
■ System Architecture
■ Disk Space Requirements
■ Display Requirements
■ Recommended Hardware Requirement for SQL Developer
2.2.1 Memory Requirements
The following are the memory requirements for Oracle Database Client 12c Release 1
(12.1):
■ 256 MB of RAM.
To determine the physical RAM size, enter the following command:
# grep MemTotal /proc/meminfo
If the size of the physical RAM is less than the required size, then you must install
more memory before continuing.
■ The following table describes the relationship between installed RAM and the
configured swap space recommendation:
Note: On Linux on POWER Systems, 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.

Available RAM Swap Space Required
Up to 256 MB 3 times the size of RAM
Between 257 MB and 512 MB 2 times the size of RAM
Between 513 MB and 726 MB 1.5 times the size of RAM
More than 726 MB 0.75 times the size of RAM
Checking the Hardware Requirements
To determine the size of the configured swap space, enter the following command:
# grep SwapTotal /proc/meminfo
If necessary, see the operating system documentation for information about how to
configure additional swap space.
To determine the available RAM and swap space, enter the following command:
# free
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 the operating system vendor for swap space allocation
guidance for your server. The vendor guidelines supersede the
swap space requirements listed in this guide.
2.2.2 System Architecture
To determine whether the system architecture can run the software, enter the
following command:
# uname -m
Note: This command displays the processor type. 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.
2.2.3 Disk Space Requirements
The following are the disk space requirements for Oracle Database Client 12c Release 1
(12.1):
■ The minimum disk space requirement for a client install in the /tmp directory is
120 MB. The minimum disk space requirement in the /tmp directory depends on
the installation type you have selected. The following table lists the minimum disk
space requirements for the /tmp directory in each type of installation.
To determine the amount of disk space available, enter the following command:
# df -k /tmp

Checking the Software Requirements
If there is less than 120 MB of free space available in the /tmp directory, then
complete one of the following steps:
– Delete unnecessary files from the /tmp directory to meet the 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 client install requires 130 MB disk space for software files on Linux on
POWER Systems:
2.2.4 Display Requirements
The minimum display requirement for Oracle Database 12c Release 1 (12.1) is a
resolution of 1024 x 768 or higher.
2.2.5 Recommended Hardware Requirement for SQL Developer
The following are the recommended CPU, Memory and Display requirements for SQL
Developer:
Resource Recommended
Memory 1 GB RAM (recommended), 256 MB RAM (minimum)
Display 65536 colors, set to at least 1024 X 768 resolution
2.3 Checking the Software Requirements
Depending on the products that you intend to install, verify that the following
software is installed on the system:
Item Requirement
Operating system The following (or a later version) of the operating system are
supported:
■ Red Hat Enterprise Linux Server 6.6
■ Red Hat Enterprise Linux Server 7
■ SUSE Linux Enterprise Server 11 SP3
Kernel version The system must be running the following kernel version (or a
later version):
■ Red Hat Enterprise Linux Server 6.6
(2.6.32-431.29.2.el6.ppc64)
■ Red Hat Enterprise Linux Server 7 (3.10.0-123.8.1.el7.ppc64)
■ SUSE Linux Enterprise Server 11 SP3 (3.0.76-0.11-ppc64)

Red Hat
Enterprise Linux
Server 6.6
Packages
The following packages (or a later version) must be installed:
binutils-2.20.51.0.2-5.42.el6.ppc64
libstdc++-devel-4.4.7-11.el6.ppc64
compat-libstdc++-33-3.2.3-69.el6.ppc64
libstdc++-4.4.7-11.el6.ppc64
libstdc++-4.4.7-11.el6.ppc
libstdc++-devel-4.4.7-11.el6.ppc
libstdc++-docs-4.4.7-11.el6.ppc64
compat-libstdc++-33-3.2.3-69.el6.ppc
compat-libstdc++-296-2.96-144.el6.ppc
gcc-gnat-4.4.7-11.el6.ppc64
gcc-4.4.7-11.el6.ppc64
gcc-gfortran-4.4.7-11.el6.ppc64
compat-gcc-34-3.4.6-19.el6.ppc64
compat-gcc-34-c++-3.4.6-19.el6.ppc64
libgcc-4.4.7-11.el6.ppc
libgcc-4.4.7-11.el6.ppc64
gcc-objc++-4.4.7-11.el6.ppc64
gcc-c++-4.4.7-11.el6.ppc64
compat-gcc-34-g77-3.4.6-19.el6.ppc64
gcc-objc-4.4.7-11.el6.ppc64
gcc-java-4.4.7-11.el6.ppc64
libaio-0.3.107-10.el6.ppc64
libaio-0.3.107-10.el6.ppc
libaio-devel-0.3.107-10.el6.ppc64
libgcc-4.4.7-11.el6.ppc64
libgcc-4.4.7-11.el6.ppc
glibc-devel-2.12-1.149.el6.ppc
glibc-devel-2.12-1.149.el6.ppc64
glibc-2.12-1.149.el6.ppc
glibc-headers-2.12-1.149.el6.ppc64
compat-glibc-2.5-46.2.ppc64
glibc-common-2.12-1.149.el6.ppc64
glibc-2.12-1.149.el6.ppc64
glibc-utils-2.12-1.149.el6.ppc64
compat-glibc-headers-2.5-46.2.ppc64
GNU Make 3.81 - make-3.81-20.el6.ppc64
sysstat-9.0.4-27.el6.ppc64
IBM XL C/C++ for Linux, V12.1
Item Requirement

Red Hat
Enterprise Linux
Server 7 Packages
binutils-2.23.52.0.1-16.el7.ppc64
compat-gcc-44-c++-4.4.7-8.el7.ppc64
compat-libstdc++-33-3.2.3-68.7.ppc
compat-gcc-44-4.4.7-8.el7.ppc64
compat-glibc-headers-2.12-4.el7.ppc64
compat-glibc-2.12-4.el7.ppc64
compat-libstdc++-33-3.2.3-68.7.ppc64
libstdc++-devel-4.8.2-16.2.el7_0.ppc64
libstdc++-devel-4.8.2-16.2.el7_0.ppc
libstdc++-4.8.2-16.2.el7_0.ppc
libstdc++-4.8.2-16.2.el7_0.ppc64
gcc-gnat-4.8.2-16.2.el7_0.ppc64
gcc-4.8.2-16.2.el7_0.ppc64
gcc-c++-4.8.2-16.2.el7_0.ppc64
gcc-objc++-4.8.2-16.2.el7_0.ppc64
gcc-objc-4.8.2-16.2.el7_0.ppc64
gcc-gfortran-4.8.2-16.2.el7_0.ppc64
libgcc-4.8.2-16.2.el7_0.ppc64
libgcc-4.8.2-16.2.el7_0.ppc
libaio-devel-0.3.109-12.el7.ppc64
libaio-0.3.109-12.el7.ppc64
libaio-0.3.109-12.el7.ppc
glibc-2.17-55.el7_0.1.ppc64
glibc-2.17-55.el7_0.1.ppc
glibc-devel-2.17-55.el7_0.1.ppc
glibc-headers-2.17-55.el7_0.1.ppc64
glibc-utils-2.17-55.el7_0.1.ppc64
glibc-common-2.17-55.el7_0.1.ppc64
GNU Make 3.82
sysstat-10.1.5-4.el7.ppc64
java-1.7.0-openjdk-1.7.0.71-2.5.3.1.el7_0.ppc64
Item Requirement

SUSE Linux
Enterprise Server
11 SP3 Packages
binutils-2.23.1-0.17.18
libstdc++33-3.3.3-11.9
libstdc++46-4.6.9-0.11.38
libstdc++6-32bit-4.7.2_20130108-0.15.45
libstdc++43-4.6.9-0.11.38
libstdc++43-32bit-4.6.9-0.11.38
libstdc++46-32bit-4.6.9-0.11.38
libstdc++43-devel-4.3.4_20091019-0.37.30
libstdc++43-devel-32bit-4.3.4_20091019-0.37.30
libstdc++6-4.7.2_20130108-0.15.45
libstdc++-devel-4.3-62.198
gcc43-c++-4.3.4_20091019-0.37.30
gcc-c++-4.3-62.198
gcc-info-4.3-62.198
gcc43-locale-4.3.4_20091019-0.37.30
gcc-locale-4.3-62.198
libgcc43-32bit-4.6.9-0.11.38
libgcc_s1-4.7.2_20130108-0.15.45
libgcc_s1-32bit-4.7.2_20130108-0.15.45
gcc-4.3-62.198
gcc43-info-4.3.4_20091019-0.37.30
libgcc46-4.6.9-0.11.38
libgcc46-32bit-4.6.9-0.11.38
gcc43-32bit-4.3.4_20091019-0.37.30
gcc-32bit-4.3-62.198
libgcc43-4.6.9-0.11.38
gcc43-4.3.4_20091019-0.37.30
libaio-devel-0.3.109-0.1.46
libaio-devel-32bit-0.3.109-0.1.46
libaio-0.3.109-0.1.46
libaio-32bit-0.3.109-0.1.46
libgcc43-32bit-4.6.9-0.11.38
libgcc_s1-4.7.2_20130108-0.15.45
libgcc_s1-32bit-4.7.2_20130108-0.15.45
libgcc46-4.6.9-0.11.38
libgcc46-32bit-4.6.9-0.11.38
libgcc43-4.6.9-0.11.38
glibc-profile-32bit-2.11.3-17.54.1
glibc-info-2.11.3-17.54.1
glibc-devel-2.11.3-17.54.1
glibc-2.11.3-17.54.1
glibc-profile-2.11.3-17.54.1
Item Requirement

The following procedure describes how to verify and ensure that the system meets
these requirements:
1. To determine which distribution and version of Linux is installed, enter the
following command:
# cat /etc/issue
SUSE Linux
Enterprise Server
11 SP3 Packages
glibc-32bit-2.11.3-17.54.1
glibc-locale-2.11.3-17.54.1
glibc-html-2.11.3-17.54.1
glibc-devel-32bit-2.11.3-17.54.1
glibc-i18ndata-2.11.3-17.54.1
glibc-locale-32bit-2.11.3-17.54.1
sysstat-8.1.5-7.45.24
C/C++ Runtime
Environment
Download the IBM XL C/C++ for Linux, V12.1 Runtime
Environment at
http://www-01.ibm.com/support/docview.wss?uid=swg24032628
You must also download and install the XL Optimization
Libraries component from this link.
Compilers The version of GNU C and C++ compilers listed under Packages
are supported.
Pro*FORTRAN IBM XL Fortran Advanced Edition V10.1 for Linux.
Oracle JDBC- OCI
Drivers
You can use the following JDBC - OCI drivers; however, these are
not required for the installation:
■ JDBC-OCI 1.6.0 or later versions on RHEL 6.6
■ JDBC-OCI 1.7.0_71 or later on RHEL 7
■ JDBC-OCI 1.7.0 or later versions on SUSE 11
Oracle ODBC
Driver
To use ODBC, you must also install the following additional
ODBC RPMs, depending on your operating system.
Red Hat Enterprise Linux Server 6.6
unixODBC.ppc - 2.2.14-14.el6
unixODBC.ppc64 - 2.2.14-14.el6
unixODBC-devel.ppc - 2.2.14-14.el6
unixODBC-devel.ppc64 - 2.2.14-14.el6
Red Hat Enterprise Linux Server 7
unixODBC.ppc64 - 2.3.1-10.el7
unixODBC-devel.ppc64 - 2.3.1-10.el7
unixODBC.ppc - 2.3.1-10.el7
unixODBC-devel.ppc - 2.3.1-10.el7
SUSE Linux Enterprise Server 11 SP3:
unixODBC-devel-32bit-2.2.12-198.17
unixODBC-32bit-2.2.12-198.17
unixODBC-2.2.12-198.17
unixODBC-devel-2.2.12-198.17
Item Requirement

Note: Only the distributions and versions listed in the previous
table are supported. Do not install the software on other versions of
Linux on POWER Systems.
2. To determine whether the required kernel is installed, enter the following
command:
# uname -r
The following is sample output displayed by running this command on a Red Hat
Enterprise Linux 4.0 system:
2.6.9-11.EL
In this example, the output shows the kernel version (2.6.9) and errata level (11.EL)
on the system.
If the kernel version does not meet the requirement specified earlier in this section,
then contact your operating system vendor for information about obtaining and
installing kernel updates.
3. To determine whether the required packages are installed, enter commands similar
to the following:
# rpm -q package_name
If a package is not installed, then install it from your Linux distribution media or
download the required package version from your Linux vendor's website.
2.3.1 Instant Client Light Requirements
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
* WE8EBCDIC37C for EBCDIC platforms only
* WE8EBCDIC1047 for EBCDIC platforms only
– Unicode
* UTF8
* AL32UTF8
* AL16UTF16

The advantage of using Instant Client Light is that it has a smaller foot-
print than the regular Instant Client. The shared libraries, which an appli-
cation must load, are only 34 MB as opposed to the 110 MB that regular
Instant Client uses. Therefore, the applications use less memory.
The language, territory, and character sets are determined by the NLS_LANG
environment variable.
Note: Ensure that you set the NLS_LANG environment variable to the
required character set before you run Oracle Database Instant Client.

3
Installing and Removing Oracle Database Client 3-1
3Installing and Removing Oracle Database
Client
The Oracle Database Client software is available on Oracle Technology Network
website. This chapter describes the following sections:
■ Downloading and Installing the Oracle Database Client Software
■ Removing the Oracle Database Client Software
3.1 Downloading and Installing the Oracle Database Client Software
The following steps describe how to install the Oracle software:
1. Download the Instant Client for Linux on POWER Systems (32-bit and 64-bit)
package from the Instant Client Downloads page on Oracle Technology Network
at
http://www.oracle.com/technetwork/index.html
2. Create a directory on your computer, for example, instantclient. Choose a
directory to install the Oracle Instant Client and unzip the downloaded zip file in
that directory. The unzipped file creates the instantclient_12_1 directory.
3. Set the LD_LIBRARY_PATH and the NLS_LANG environment variables to the full path
of the instantclient_12_1 directory. For example, if you unzipped the Instant
Client zip file in the /bin/oracle directory, then set the LD_LIBRARY_PATH
environment variable to /bin/oracle/instantclient_12_1.
See the "Instant Client Light Requirements" section for information about setting
the NLS_LANG environment variable to the required character set.
This completes the installation of Oracle Database Client. To connect to the Oracle
Database server, run the client from the Oracle Database Instant Client
environment.
4. The Object Type Translator Utility (OTT) utility may have to be modified to reflect
the correct environment variable LD_LIBRARY_PATH as ORACLE_HOME may not be
available.

Note: If you want to use VAC compiler, then you need to set the
following values in the environment:
■ COMPILER=VAC
■ VAC_VERSION=12.1 (if it is 12.1 or any other VAC version that is
in use)
In addition to the preceding task:
■ Ensure that xlC is in the PATH of your environment.
■ Also, set COMPILER_MODE = 32/64 depending on whether you
want to build 32/64-bit demo executable or otherwise,
respectively.
Removing the Oracle Database Client Software
3.2 Removing the Oracle Database Client Software
To remove the Oracle Database Client software, delete the instantclient_12_1
directory.

4
Oracle Database Client Postinstallation Tasks 4-1
4Oracle Database Client Postinstallation Tasks
This chapter describes how to complete postinstallation tasks after you have installed
the Oracle Database Client software. It includes information about the following
topics:
■ Required Postinstallation Tasks
■ Recommended Postinstallation Tasks
■ Required Product-Specific Postinstallation Tasks
You must perform the tasks listed in "Required Postinstallation Tasks" on page 4-1.
Oracle recommends that you perform the tasks listed in "Recommended
Postinstallation Tasks" on page 4-2 after all installations.
If you install and intend to use any of the products listed in "Required Product-Specific
Postinstallation Tasks" on page 4-4, then you must perform the tasks listed in the
product-specific subsections.
4.1 Required Postinstallation Tasks
You must perform the tasks described in the following sections after completing an
installation:
■ Updating Instant Client
■ Connecting with Instant Client
4.1.1 Updating Instant Client
To update Instant Client:
1. Download Instant Client from Oracle Technology Network at
http://www.oracle.com/technetwork/database/features/instant-client/inde
x-097480.html
2. If you want to place the files in the existing directory, then ensure that the
directory is empty.
If you want to place the files into a different directory (and remove the previous
files), ensure that you update the PATH environment variable setting to reflect the
new location.
Note: The Instant Client and Instant Client Light installations do not
create an inventory. Therefore, you cannot perform patch upgrades for
these installations using the opatch utility.

Recommended Postinstallation Tasks
4.1.2 Connecting with Instant Client
If you installed the Instant Client installation type, you can configure users’
environments to enable dynamically linked client applications to connect to a database
as follows:
1. Set the appropriate shared library path environment variable for your platform to
specify the directory that contains the Instant Client libraries. For the Instant Client
installation type, this directory is the Oracle home directory that you specified
during the installation, for example:
Your_current_dir/instantclient_12_1
2. Use one of the following methods to specify database connection information for
the client application:
■ Specify a SQL connect URL string using the following format:
//host:port/service_name
For example:
//shobeen:1521/sales_us
■ Set the TNS_ADMIN environment variable to specify the location of the
tnsnames.ora file and specify a service name from that file.
■ Set the TNS_ADMIN and the TWO_TASK environment variables to specify a service
name from the tnsnames.ora file.
Note: It is not required that you specify the ORACLE_HOME
environment variable.
4.2 Recommended Postinstallation Tasks
Oracle recommends that you perform the tasks described in the following sections
after completing an installation:
■ Connecting Instant Client or Instant Client Light to an Oracle Database
■ Setting the NLS_LANG Environment Variable
4.2.1 Connecting Instant Client or Instant Client Light to an Oracle Database
Before you can connect Instant Client (including Instant Client Light) to an Oracle
database, ensure that the LD_LIBRARY_PATH environment variable specifies the
directory that contains the Instant Client libraries. This directory is the ORACLE_
HOME directory that you specified during installation.
For example, the shared libraries for Instant Client or Instant Client Light (if you have
configured Instant Client Light), are in:
Your_current_dir/instantclient_12_1
After checking the LD_LIBRARY_PATH environment variable, you can use any of the
following methods to specify Oracle Database connection information for client
applications:
■ Specifying a Connection by Using the Easy Connect Naming Method
■ Specifying a Connection Using an Empty Connect String and TWO_TASK

Recommended Postinstallation Tasks
4.2.1.1 Specifying a Connection by Using the Easy Connect Naming Method
You can specify a connection address to an Oracle Database directly from a client
application, without having to configure a tnsnames setting for the Instant Client. This
method is convenient as you do not have to create and manage a tnsnames.ora file.
However, the application users must specify the host name and port number when
they want to log in to the application.
For example, if you run SQL*Plus on the client computer and want to connect to the
sales_us database, which is located on a server whose host name is shobeen and port
number is 1521, then you can log in as follows:
Enter user-name: system@admin@//shobeen:1521/sales_us
Similarly, in the application code, you can use Oracle Call Interface net naming
methods to create the Instant Client-to-Oracle Database connection. For example, the
following formats in the OCIServerAttach() call specify the connection information:
■ Specify a SQL connect URL string using the following format:
//host[:port][/service_name]
For example:
//shobeen:1521/sales_us
■ Alternatively, you can specify the SQL connect information as an Oracle Net
keyword-value pair. For example:
"(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (HOST=shobeen) (PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=sales_us)))"
See Also: Oracle Call Interface Programmer's Guide for more
information on using Oracle Call Interface Instant Client
4.2.1.2 Specifying a Connection Using an Empty Connect String and TWO_TASK
You can set the connect string to an empty connect string (""), and then set the TWO_
TASK environment variable to one of the following values:
■ A direct address, as described under "Specifying a Connection by Using the Easy
Connect Naming Method" on page 4-3.
■ Oracle Net keyword-value pair.
■ A tnsnames.ora entry and TNS_ADMIN is set to the location of tnsnames.ora.
■ A tnsnames.ora entry and the following:
– tnsnames.ora file located in $ORACLE_HOME/network/admin.
– The ORACLE_HOME environment variable set to this Oracle home.
This method allows the applications to specify internally a connection string if the
application code itself uses an empty connection string. The benefit of an empty
connect string is that the application itself does not have to specify the tnsnames.ora
entry. Instead, when a user starts the application, the location of the database is
determined by a script or the environment, depending on where you have set the TWO_
TASK environment variable. The disadvantage of using empty strings is that you must
configure this additional information in order for the application to connect to the
database.

Required Product-Specific Postinstallation Tasks
4.2.2 Setting the NLS_LANG Environment Variable
NLS_LANG is an environment variable that specifies the locale behavior for Oracle
software. This variable sets the language and territory used by the client application
and the database user session. It also declares the character set of the client, which is
the character set of data entered or displayed by an Oracle client program, such as
SQL*Plus.
Note: The character set of the data displayed is determined by the
environment of the operating system, such as keyboard driver and
fonts in use. The NLS_LANG character set should match the operating
system.
See the "Setting Up a Globalization Support Environment" section in Oracle Database
Globalization Support Guide for information about Globalization Support.
4.3 Required Product-Specific Postinstallation Tasks
The following sections describe postinstallation tasks that you must perform if you
install and intend to use Oracle Precompliers:
Note: You must perform postinstallation tasks only for products
that you intend to use.
4.3.1 Configuring Oracle Precompilers
This section describes postinstallation tasks for Pro*C/C++.
Note: All precompiler configuration files are located in the $ORACLE_
HOME/precomp/admin directory.
4.3.1.1 Configuring Pro*C/C++
Verify that the PATH environment variable setting includes the directory that contains
the C compiler executable. The default directory for the gcc compiler executable is
/usr/bin.
For more information about setting environment variables, see Pro*C/C++
Programmer's Guide.
4.3.2 Compiling with GCC/G++
You can configure GNU Compiler Collection (GCC) as the primary compiler if the
primary supported compiler is not available. Remember that you must use one
compiler to compile all your Oracle modules. You cannot compile some modules with
the primary compiler and others with a different compiler.
If both, the primary supported compiler for the operating system and GCC are
available, then use the primary supported compiler. However, if the primary
supported compiler is not available, then use GCC.
The Instant Client is built using the xlc and c++ libraries. To link with a gcc based
application, the xlc 12.1 RTE is required and can be found at
http://www-01.ibm.com/support/docview.wss?uid=swg24040214#DNLD

For example, the demo program Your_current_dir/instantclient_12_
1/sdk/demo/occidml.cpp can be compiled and linked with the g++ compiler as
follows:
g++ -m64 -c -I../include -D__LP64__ -I../include -DLINUX -DLINUX_PPC64 -D_
GNU_SOURCE -D_REENTRANT -g occidml.cpp
g++ -m64 -o occidml -g occidml.o -L/rdbms/lib/ -L/lib/ -L../../ -locci
-lclntsh -lxl -Wl,-rpath /usr/local/remote/packages/vac/vac/12.1/lib/
-L/usr/local/packages/vac/vac/12.1/lib -libmc++ -lpthread

Index-1
Index
C
character sets, 2-9
checking system requirements, 2-8
checking the gcc version, 2-9
checking the gcc version, 2-9
D
disk space requirements, 2-3
display requirements, 2-4
E
environment variables
LD_LIBRARY_PATH, 3-1
NLS_LANG, 2-10, 3-1, 4-4
H
hardware requirement, 2-2
display requirements, 2-4
hardware requirement for SQL developer, 2-4
memory requirements, 2-2
system architecture, 2-3
hardware requirement for SQL developer, 2-4
hardware requirements
disk space requirements, 2-3
I
installation
available products, 1-2
installation considerations, 1-1
Instant Client Light requirements, 2-9
character sets, 2-9
M
memory requirements, 2-2
O
operating system, 2-4
Oracle Database Instant Client
connecting to an Oracle Database, 4-2
Oracle Database Instant Client Light
connecting to an Oracle Database, 4-2
Oracle JDBC/OCI drivers, 2-8
Oracle precompilers, 4-4
Pro C/C++, 4-4
P
postinstallation tasks, 4-1
connecting with Instant Client, 4-2
NLS_LANG, 4-4
Oracle precompilers, 4-4
updating Instant Client, 4-1
preinstallation requirements
hardware requirement, 2-2
logging in to the system as root, 2-1
preinstallation tasks, 2-1
software requirements, 2-4
preinstallation tasks
preinstallation requirements, 2-1
S
software requirements, 2-4
checking system requirements, 2-8
Instant Client Light requirements, 2-9
operating system, 2-4
Oracle JDBC/OCI drivers, 2-8
tools requirement, 2-4
system architecture, 2-3
T
TIMESTAMP WITH TIMEZONE patching, 1-3
tools requirement, 2-4

Oracle database 12c client installation guide 4

More Related Content

What's hot (20)

Viewers also liked (19)

Similar to Oracle database 12c client installation guide 4 (16)

More from bupbechanhgmail (20)

Recently uploaded (20)

Oracle database 12c client installation guide 4