# Client Installation Guide

This file contains the text from each Client Installation Guide article landing page, release 19c.

# Oracle Database Client Installation Checklist

## Server Hardware Checklist for Oracle Database Client Installation

Oracle Database Client installation requires runlevel 3 or 5, a display resolution of at least 1024 × 768 for Oracle Universal Installer, network connectivity, and at least 256 MB of RAM. On Linux for Arm (aarch64), use a CPU capable of Neoverse N1; Oracle recommends at least an Ampere Altra or Ampere Altra Max processor.

Read More: [Server Hardware Checklist for Oracle Database Client Installation](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/oracle-database-client-installation-checklist/server-hardware-checklist-for-oracle-database-client-installation.html)

## Operating System Checklist for Oracle Database Client on Linux

Linux installations require OpenSSH and a supported kernel and release, with platform-specific requirements for Linux x86-64, IBM Linux on System z, and Linux for Arm (aarch64). Supported distributions include Oracle Linux, Red Hat Enterprise Linux, and SUSE Linux Enterprise Server across listed kernel versions; Linux for Arm support begins with Oracle Database 19c Release Update 19.19, while additional Arm versions support Instant Client only. Review package prerequisites, use the Oracle preinstallation RPM on Oracle Linux, and use the Oracle RPM Checker on IBM Linux on System z to validate required packages.

Read More: [Operating System Checklist for Oracle Database Client on Linux](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/oracle-database-client-installation-checklist/operating-system-checklist-for-oracle-database-client-on-linux.html)

## Server Configuration Checklist for Oracle Database Client

Configure at least 400 MB in /tmp and allocate swap according to available RAM, accounting for HugePages when enabled. Establish the oraInventory and OINSTALL group correctly, create required users and groups with ASCII-only names, follow Optimal Flexible Architecture for mount points, and ensure Oracle home paths and parent directories are not symbolic links and contain only ASCII characters. Plan root privilege delegation, locale settings, and installation-owner permissions before installation.

Read More: [Server Configuration Checklist for Oracle Database Client](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/oracle-database-client-installation-checklist/server-configuration-checklist-for-oracle-database-client.html)

## Oracle User Environment Configuration Checklist for Oracle Database Installation

Plan the oraInventory directory and OINSTALL primary group for all Oracle software installation owners, using existing inventory settings where applicable and following Optimal Flexible Architecture. Create required operating-system users and groups according to security needs, with ASCII-only names and appropriate resource limits. Before reuse, unset Oracle-related environment variables such as ORACLE\_HOME, ORACLE\_BASE, ORACLE\_SID, and TNS\_ADMIN, then configure the Oracle or Grid user environment with umask 022 and a valid DISPLAY setting.

Read More: [Oracle User Environment Configuration Checklist for Oracle Database Installation](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/oracle-database-client-installation-checklist/oracle-user-environment-configuration-checklist-for-oracle-database-installation.html)

## Storage Checklist for Oracle Database Client

Minimum local storage depends on platform and installation type. On Linux x86-64 and Linux for Arm, provide 350 MB for Instant Client, 2.4 GB for Administrator, 2.0 GB for Runtime, and 2.4 GB for Custom or image-based installations. On IBM Linux on System z, provide 274 MB for Instant Client, 1.9 GB for Administrator or Custom, and 1.5 GB for Runtime installations.

Read More: [Storage Checklist for Oracle Database Client](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/oracle-database-client-installation-checklist/storage-checklist-for-oracle-database-client.html)

## Installer Planning Checklist for Oracle Database Client

Before running Oracle Universal Installer, review platform release notes, licensing terms, and the current support certification matrix. Use OUI and CVU to perform prerequisite checks and generate fixup scripts, prevent cleanup cron jobs from running during installation, and select the appropriate Instant Client, Administrator, Runtime, or Custom installation type. Prepare My Oracle Support credentials for updates and security configuration, determine whether separate 32-bit software is required, and verify client-to-database release interoperability.
Read More: [Installer Planning Checklist for Oracle Database Client](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/oracle-database-client-installation-checklist/installer-planning-checklist-for-oracle-database-client.html)


# Checking and Configuring Server Hardware for Oracle Database Client

Verify that servers where you install Oracle Database Client meet the minimum requirements for installation.

This section provides minimum server requirements to complete installation of Oracle Database Client. It does not provide system resource guidelines, or other tuning guidelines for particular workloads.

## Logging In to a Remote System Using X Window System

This procedure explains how to run Oracle Universal Installer on a remote server when GUI applications cannot run locally. Start an X Window System session, configure the local X server to accept remote displays with `xhost`, connect to the target server using `ssh -Y`, and switch to the root user when required; repeat the process for each relevant installation user, such as `oracle` or `grid`.

Read More: [Logging In to a Remote System Using X Window System](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/checking-and-configuring-server-hardware-for-oracle-database-client/logging-in-to-a-remote-system-using-x-window-system.html)

## Setting Remote Display and X11 Forwarding Configuration

Configure the `DISPLAY` environment variable to point to the local X display, using shell-specific syntax such as `export DISPLAY=hostname:0` or `setenv DISPLAY hostname:0`. To prevent installation failures caused by X11 forwarding, create or edit each Oracle installation owner’s `~/.ssh/config`, set `ForwardX11 no`, and ensure that the `.ssh` directory and its files have appropriately restricted ownership and permissions.

Read More: [Setting Remote Display and X11 Forwarding Configuration](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/checking-and-configuring-server-hardware-for-oracle-database-client/setting-remote-display-and-x11-forwarding-configuration.html)

## Checking Server Hardware and Memory Configuration

Verify the server’s readiness for Oracle software by checking physical memory, swap space, `/tmp` capacity, available memory and swap, processor architecture, and shared-memory configuration with `/proc/meminfo`, `df`, `free`, and `uname`. Install additional memory or swap, free or redirect temporary storage when necessary, preserve Oracle temporary directories, confirm the architecture matches the software release, and ensure `/dev/shm` is properly mounted with sufficient capacity.
Read More: [Checking Server Hardware and Memory Configuration](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/checking-and-configuring-server-hardware-for-oracle-database-client/checking-server-hardware-and-memory-configuration.html)


# Configuring Operating Systems for Oracle Database Client on Linux

## Guidelines for Linux Operating System Installation

Before installing Oracle software on Linux, complete the operating system configuration, minimum hardware, and platform-specific prerequisite checks. Ensure the deployment follows security practices recommended in the Linux distribution vendor’s security documentation.

Read More: [Guidelines for Linux Operating System Installation](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/configuring-operating-systems-for-oracle-database-client-on-linux/guidelines-for-linux-operating-system-installation.html)

## About Oracle Linux with the Unbreakable Enterprise Kernel

Oracle Linux includes the Unbreakable Enterprise Kernel by default, providing a stable, optimized kernel with enhancements for Oracle workloads and hardware. Oracle recommends it for enterprise applications, although a RHEL-compatible kernel is available when strict compatibility is required. The Unbreakable Enterprise Kernel is the standard kernel used for Oracle product development, testing, Exadata, Exalogic, benchmarks, and the Oracle Database Preinstallation RPM; Oracle Linux also provides Ksplice for applying kernel updates without rebooting or interrupting services.

Read More: [About Oracle Linux with the Unbreakable Enterprise Kernel](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/configuring-operating-systems-for-oracle-database-client-on-linux/about-oracle-linux-with-the-unbreakable-enterprise-kernel.html)

## Additional Drivers and Software Packages for Linux

Optional Linux components may be required for specific Oracle features: install the latest Linux-PAM library for external scheduler authentication, compatible OCFS2 kernel and tools modules for Oracle Grid Infrastructure shared storage, and any required IBM WebSphere MQ fixes for Messaging Gateway. Oracle ODBC installations require unixODBC 2.3.4 or later, while LDAP packages are needed for LDAP-dependent scripts when not included in the default installation. Programming environments require supported JDK, compiler, Python, COBOL, and architecture-specific packages, with 32-bit libraries added for 32-bit clients; browser support is needed only for Enterprise Manager interfaces and must include JavaScript, HTML 4.0, and CSS 1.0 support. OCFS2, Messaging Gateway, and some features have platform restrictions, including no support on Linux for Arm where specified.

Read More: [Additional Drivers and Software Packages for Linux](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/configuring-operating-systems-for-oracle-database-client-on-linux/additional-drivers-and-software-packages-for-linux.html)

## Checking Kernel and Package Requirements for Linux

Verify the installed Linux distribution with release-identification commands, check the running kernel using `uname -r`, and compare its errata level with the minimum required version for the distribution. Query prerequisite RPMs with `rpm -q` or architecture-aware RPM queries, including packages such as binutils, compilers, glibc, libaio, libraries, make, sysstat, and unixODBC. Install any missing or outdated packages and kernel updates from the Linux distribution media or vendor repositories.
Read More: [Checking Kernel and Package Requirements for Linux](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/configuring-operating-systems-for-oracle-database-client-on-linux/checking-kernel-and-package-requirements-for-linux.html)


# Operating System Requirements for x86-64 Linux Platforms

## About Operating System Requirements for x86-64 Linux Platforms

Before installing Oracle Database or Oracle Grid Infrastructure on x86-64 Linux, verify the supported distribution, kernel, packages, and software requirements for the intended products. Oracle Universal Installer checks required packages, but prerequisites should be validated beforehand using current certification information. All cluster members must run the same operating system version unless undergoing an upgrade.

Read More: [About Operating System Requirements for x86-64 Linux Platforms](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/about-operating-system-requirements-for-x86-64-linux-platforms.html)

## General Guidelines for Operating System Packages

Oracle recommends Oracle Linux with the Oracle Database Preinstallation RPM, which configures the system and installs required dependencies. Reduced installations must include X Window System packages such as libX, while 32-bit packages are needed only for 32-bit client applications accessing 64-bit servers. Oracle Database 12c Release 2 and later do not require gcc or gcc-c++, and these requirements do not apply to Oracle Engineered Systems, which provide their own integrated software environment.

Read More: [General Guidelines for Operating System Packages](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/general-guidelines-for-operating-system-packages.html)

## Supported Oracle Linux 10 Distributions for x86-64

Oracle Linux 10 requires OpenSSH and is supported with UEK 8 kernel 6.12.0-104.43.4.2.el10uek or later, or the Red Hat Compatible Kernel 6.12.0-55.40.1.0.1.el10\_0 or later, beginning with the specified Oracle Database 19c releases. Install the latest required packages, preferably through the oracle-database-preinstall-19c RPM, with optional packages available for IPMI, RAC, Clusterware, ACFS, and Database Client use. Oracle Database Client is supported on Oracle Linux 10, while Instant Client support begins with Oracle Database 19c 19.33.

Read More: [Supported Oracle Linux 10 Distributions for x86-64](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/supported-oracle-linux-10-distributions-for-x86-64.html)

## Supported Oracle Linux 9 Distributions for x86-64

Oracle Linux 9 requires OpenSSH and is supported with UEK 7 kernel 5.15.0-1.43.4.2.el9uek or later, the Red Hat Compatible Kernel 5.14.0-70.22.1.0.2.el9\_0 or later, and Oracle Linux 9.6 with UEK 8 kernel 6.12.0-1.23.3.2.el9uek or later for the applicable releases. Install the latest required packages, preferably using oracle-database-preinstall-19c; optional packages support development, IPMI, Database Client, RAC, Clusterware, and ACFS. Install corresponding 32-bit packages when required by 32-bit clients and review current release updates and known issues.

Read More: [Supported Oracle Linux 9 Distributions for x86-64](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/supported-oracle-linux-9-distributions-for-x86-64.html)

## Supported Oracle Linux 8 Distributions for x86-64

Oracle Linux 8 requires OpenSSH and supports UEK 6, the Red Hat Compatible Kernel, and specified UEK 7 kernel levels beginning with the applicable Database and Grid Infrastructure releases. Required packages should be installed at their latest versions, preferably through oracle-database-preinstall-19c, with optional packages for IPMI, Database Client, KVM, RAC, Clusterware, and ACFS. Install 32-bit equivalents when needed for 32-bit clients, review current patches and known issues, and note that KVM is certified for supported Oracle Linux 8 distributions.

Read More: [Supported Oracle Linux 8 Distributions for x86-64](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/supported-oracle-linux-8-distributions-for-x86-64.html)

## Supported Oracle Linux 7 Distributions for x86-64

Oracle Linux 7 requires OpenSSH and supports specified minimum UEK 4, UEK 5, UEK 6, and Red Hat Compatible Kernel versions. Oracle recommends upgrading to Oracle Linux 8 or later despite continued Oracle Database 19c support. Install the required packages, preferably with oracle-database-preinstall-19c, adding 32-bit versions for 32-bit clients and optional packages for IPMI, RAC, Clusterware, KVM, ACFS, and ACFS Remote. KVM is certified for supported Oracle Linux 7 distributions.

Read More: [Supported Oracle Linux 7 Distributions for x86-64](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/supported-oracle-linux-7-distributions-for-x86-64.html)

## Supported Red Hat Enterprise Linux 10 Distributions for x86-64

Red Hat Enterprise Linux 10 requires OpenSSH and is supported beginning with Oracle Database 19c 19.32 using kernel 6.12.0-55.40.1.0.1.el10\_0 or later. Install the latest versions of the specified system, X Window, runtime, security, storage, and monitoring packages, with optional packages for IPMI, RAC, Clusterware, and ACFS. Review the applicable installation guidance, known issues, and open bugs before deployment.

Read More: [Supported Red Hat Enterprise Linux 10 Distributions for x86-64](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/supported-red-hat-enterprise-linux-10-distributions-for-x86-64.html)

## Supported Red Hat Enterprise Linux 9 Distributions for x86-64

Red Hat Enterprise Linux 9 requires OpenSSH and is supported beginning with Oracle Database 19c 19.19 using kernel 5.14.0-70.22.1.el9\_0 or later. Install the latest required packages, including compatibility, runtime, RDMA, X Window, security, and monitoring components; install 32-bit versions where required for 32-bit clients. Optional packages support database and RAC operations, development, IPMI, Database Client, Clusterware, and ACFS, and current patches and known issues should be reviewed.

Read More: [Supported Red Hat Enterprise Linux 9 Distributions for x86-64](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/supported-red-hat-enterprise-linux-9-distributions-for-x86-64.html)

## Supported Red Hat Enterprise Linux 8 Distributions for x86-64

Red Hat Enterprise Linux 8 requires OpenSSH and kernel 4.18.0-80.el8.x86\_64 or later. Install the latest listed runtime, development, X Window, RDMA, security, storage, and monitoring packages, including 32-bit equivalents when required by client applications. Optional packages support IPMI, Database Client, RAC, Clusterware, and ACFS, while patch levels, known issues, and open bugs should be checked before installation.

Read More: [Supported Red Hat Enterprise Linux 8 Distributions for x86-64](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/supported-red-hat-enterprise-linux-8-distributions-for-x86-64.html)

## Supported Red Hat Enterprise Linux 7 Distributions for x86-64

Red Hat Enterprise Linux 7 requires OpenSSH and version 7.5 with kernel 3.10.0-862.11.6.el7.x86\_64 or later. Although Oracle Database 19c remains supported, upgrading to version 8 or later is strongly recommended. Install the required compatibility, runtime, development, X Window, and monitoring packages, including 32-bit versions for 32-bit clients, and add optional packages for IPMI, RAC, Clusterware, ACFS, and ACFS Remote.

Read More: [Supported Red Hat Enterprise Linux 7 Distributions for x86-64](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/supported-red-hat-enterprise-linux-7-distributions-for-x86-64.html)

## Supported SUSE Linux Enterprise Server 12 Distributions for x86-64

SUSE Linux Enterprise Server 12 requires OpenSSH and SP3 with kernel 4.4.162-94.72-default or later. Install the latest required development, runtime, X Window, capability, networking, RDMA, storage, compression, and monitoring packages, including 32-bit versions when needed for 32-bit clients. Optional net-tools supports RAC and Clusterware, while nfs-kernel-server supports ACFS.

Read More: [Supported SUSE Linux Enterprise Server 12 Distributions for x86-64](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/supported-suse-linux-enterprise-server-12-distributions-for-x86-64.html)

## Supported SUSE Linux Enterprise Server 15 Distributions for x86-64

SUSE Linux Enterprise Server 15 requires OpenSSH and kernel 4.12.14-23-default or later. Install the latest listed runtime, development, X Window, capability, networking, RDMA, system, compression, storage, and monitoring packages, adding 32-bit versions when required for 32-bit clients. Optional net-tools supports RAC and Clusterware, nfs-kernel-server supports ACFS, and current patches and known issues should be reviewed.

Read More: [Supported SUSE Linux Enterprise Server 15 Distributions for x86-64](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/supported-suse-linux-enterprise-server-15-distributions-for-x86-64.html)

## Installing Operating System Packages

Install the latest operating system packages from the vendor’s enabled repository using the platform’s package manager: YUM on Oracle Linux or Red Hat Enterprise Linux, and YaST on SUSE Linux Enterprise Server. Ensure the appropriate software channel or repository is enabled, then install each required package with the corresponding package-manager command, such as installing bc through YUM or YaST.

Read More: [Installing Operating System Packages](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-x86-64-linux-platforms/installing-operating-system-packages.html)


# Operating System Requirements for Linux for Arm (aarch64)

## About Operating System Requirements for Linux for Arm (aarch64)

This section identifies the supported Linux distributions, kernels, and required packages for Linux for Arm (aarch64). Before installation, verify that the system meets the applicable requirements and consult Oracle’s certification matrix for the latest supported hardware and operating system versions, as certifications may change after publication.

Read More: [About Operating System Requirements for Linux for Arm (aarch64)](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-linux-for-arm-aarch64/about-operating-system-requirements-for-linux-for-arm-aarch64.html)

## Supported Oracle Linux 8 Distributions on Linux for Arm (aarch64)

For Oracle Database 19c Release 19.19 and later, Oracle Linux 8.6 or later is supported on Linux for Arm (aarch64) with Unbreakable Enterprise Kernel 7 version 5.15.0-6.80.3.1.el8uek.aarch64 or later; Oracle recommends using the latest available Oracle Linux 8 release. Install the oracle-database-preinstall-19c RPM from the Unbreakable Linux Network or Oracle Linux yum server to automatically install the required database and Grid Infrastructure packages, dependencies, and system configuration.
Read More: [Supported Oracle Linux 8 Distributions on Linux for Arm (aarch64)](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-linux-for-arm-aarch64/supported-oracle-linux-8-distributions-on-linux-for-arm-aarch64.html)


# Operating System Requirements for IBM: Linux on System z

## About Operating System Requirements for IBM: Linux on System z

Before installing Oracle Database or Grid Infrastructure on IBM Linux on System z, verify that the distribution, kernel, packages, and other software meet the release requirements. Consult the current certification matrix because supported platforms may change, and use Oracle Universal Installer checks to confirm package compliance. Thirty-two-bit packages are required only for 32-bit client applications accessing 64-bit servers, and all cluster members must use the same operating system version unless performing an upgrade.

Read More: [About Operating System Requirements for IBM: Linux on System z](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-ibm-linux-on-system-z/about-operating-system-requirements-for-ibm-linux-on-system-z.html)

## Using Oracle RPM Checker on IBM: Linux on System z

Use the Oracle RPM Checker utility to validate required Red Hat Enterprise Linux or SUSE packages before installation. Download the distribution-specific utility from My Oracle Support, install and run it as root, and use the applicable RPM or yum command for RHEL 7, 8, or 9 and SLES 12 or 15; on RHEL, yum can also install the required RPMs. The utility can be removed with the corresponding rpm -e command.

Read More: [Using Oracle RPM Checker on IBM: Linux on System z](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-ibm-linux-on-system-z/using-oracle-rpm-checker-on-ibm-linux-on-system-z.html)

## Supported Red Hat Enterprise Linux 9 Distributions for IBM: Linux on System z

Red Hat Enterprise Linux 9 requires OpenSSH and, beginning with Oracle Database 19c Release 19.23, RHEL 9.2 with kernel 5.14.0-284.30.1.el9\_2.s390x or later. Install current versions of the required development, compiler, runtime, X11, networking, RDMA, security, monitoring, and system-management packages, including glibc-devel, ksh, libaio, libgcc, libstdc++, make, policycoreutils, smartmontools, and sysstat. Optional packages support RAC and Clusterware, application development, IPMI, and Database Client installations.

Read More: [Supported Red Hat Enterprise Linux 9 Distributions for IBM: Linux on System z](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-ibm-linux-on-system-z/supported-red-hat-enterprise-linux-9-distributions-for-ibm-linux-on-system-z.html)

## Supported Red Hat Enterprise Linux 8 Distributions for IBM: Linux on System z

Red Hat Enterprise Linux 8 requires OpenSSH, RHEL 8.3 with kernel 4.18.0-240.el8.s390x or later, and the specified or newer s390x packages. Required components include compilers, glibc and development libraries, KornShell, asynchronous I/O, X11 libraries, RDMA libraries, C++ runtimes, PAM, make, networking tools, policy utilities, smartmontools, and sysstat.

Read More: [Supported Red Hat Enterprise Linux 8 Distributions for IBM: Linux on System z](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-ibm-linux-on-system-z/supported-red-hat-enterprise-linux-8-distributions-for-ibm-linux-on-system-z.html)

## Supported Red Hat Enterprise Linux 7 Distributions for IBM: Linux on System z

Red Hat Enterprise Linux 7 requires OpenSSH, RHEL 7.4 with kernel 3.10.0-693.el7.s390x or later, and the listed or newer s390 and s390x packages. The package set covers binutils, compatibility capabilities, GCC and C++ development tools, glibc, KornShell, X11 libraries, asynchronous I/O, attribute and compiler libraries, PAM, make, and sysstat.

Read More: [Supported Red Hat Enterprise Linux 7 Distributions for IBM: Linux on System z](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-ibm-linux-on-system-z/supported-red-hat-enterprise-linux-7-distributions-for-ibm-linux-on-system-z.html)

## Supported SUSE Linux Enterprise Server 12 Distributions for IBM: Linux on System z

SUSE Linux Enterprise Server 12 requires OpenSSH and kernel 4.4.73-5-default for s390x or later. Install the specified or newer compiler, glibc, asynchronous I/O, X11, capability, C and C++ runtime, XCB, KornShell, and make packages, including both required architecture variants where listed.

Read More: [Supported SUSE Linux Enterprise Server 12 Distributions for IBM: Linux on System z](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-ibm-linux-on-system-z/supported-suse-linux-enterprise-server-12-distributions-for-ibm-linux-on-system-z.html)

## Supported SUSE Linux Enterprise Server 15 Distributions for IBM: Linux on System z

SUSE Linux Enterprise Server 15 requires OpenSSH and kernel 5.3.18-57-default for s390x or later, together with the specified or newer development, compiler, runtime, X11, capability, networking, RDMA, compression, storage, monitoring, and system utilities. Required packages include GCC, glibc, libaio, C and C++ runtimes, X libraries, libcap, libgcc, libgfortran, libpcap, libpcre, libtiff, make, smartmontools, sysstat, and related dependencies; install the latest available 32-bit versions as well when 32-bit clients will access 64-bit servers.
Read More: [Supported SUSE Linux Enterprise Server 15 Distributions for IBM: Linux on System z](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/operating-system-requirements-for-ibm-linux-on-system-z/supported-suse-linux-enterprise-server-15-distributions-for-ibm-linux-on-system-z.html)


# Configuring Users, Groups and Environments for Oracle Database Client

Before installation, create operating system groups and users, and configure user environments.

## Required Operating System Groups and Users

Oracle installations require an installation owner, a shared Oracle Inventory group, and one or more operating-system groups for database or Grid Infrastructure privileges. Administrators should verify whether an existing central inventory and `oraInst.loc` file are present, reuse the same inventory for all installations, confirm group membership and write access, and avoid placing `oraInventory` beneath the Oracle base directory. If no inventory exists, create the inventory group manually; configure `grid` for Grid Infrastructure and `oracle` for database software as needed, ensuring each owner uses the inventory group as its primary group and required privilege groups as secondary groups. Verify existing accounts with group and identity commands, and ensure the `grid` user belongs to `racdba` for Oracle Restart installations.

Read More: [Required Operating System Groups and Users](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/configuring-users-groups-and-environments-for-oracle-database-client/required-operating-system-groups-and-users.html)

## Creating an Oracle Software Owner User

Before installation, create the required Oracle software owner account and configure its group memberships, preferably using a separate owner for each Oracle software product. For example, create `oracle` with a specified user ID, `oinstall` as the primary group, and `dba` as a secondary group. Record the user ID for preinstallation activities, and ensure that user and group IDs are identical across all candidate nodes for Oracle Grid Infrastructure installations.

Read More: [Creating an Oracle Software Owner User](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/configuring-users-groups-and-environments-for-oracle-database-client/creating-an-oracle-software-owner-user.html)

## Configuring Software Owner User Environments

Before running the installer as `grid` or `oracle`, configure each owner’s shell environment with a `022` umask, appropriate file-descriptor and process limits, and a valid `DISPLAY` setting. Update the correct shell startup file, remove or unset conflicting Oracle variables such as `ORACLE_SID`, `ORACLE_HOME`, `ORACLE_BASE`, `ORA_NLS10`, `TNS_ADMIN`, and especially `ORA_CRS_HOME`, and remove Oracle home paths from `PATH`. Set `TMP` and `TMPDIR` to a local filesystem with at least 1 GB of free space when `/tmp` is insufficient; shared temporary filesystems are unsuitable for Oracle RAC. Reload the startup configuration and verify the umask and environment values before installation.
Read More: [Configuring Software Owner User Environments](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/configuring-users-groups-and-environments-for-oracle-database-client/configuring-software-owner-user-environments.html)


# Installing Oracle Database Client

## About Image-Based Oracle Database Client Installation

Starting with Oracle Database 19c, Oracle Database Client can be installed from an image by creating an Oracle home, extracting `client_home.zip` into it, and running the Setup Wizard to register and configure the product. Image-based installation supports 32-bit and 64-bit Administrator installations, follows Oracle Optimal Flexible Architecture recommendations, and provides a simplified alternative to traditional non-image archive installations.

Read More: [About Image-Based Oracle Database Client Installation](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-database-client/about-image-based-oracle-database-client-installation.html)

## Downloading Oracle Software

Oracle Database software can be downloaded from the Oracle website or Oracle Software Delivery Cloud, subject to the applicable license terms. Download the required archives for the target platform, ensure sufficient space for both the archives and extraction, store them in product-specific directories, verify file sizes and checksums, and extract the files. The Software Delivery Cloud process additionally requires signing in, selecting the product and platform, accepting the license agreement, downloading the files, and validating their digests.

Read More: [Downloading Oracle Software](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-database-client/downloading-oracle-software.html)

## About Character Set Selection During Installation

The database character set should be selected carefully before database creation because changing it later can require extensive export and import operations. Character sets define the encoding of SQL data, identifiers, and stored source code; Oracle Database 12c Release 2 and later generally default to Unicode `AL32UTF8`, which supports global languages and technologies but may require more storage and processing than legacy single-byte sets. Legacy character sets should be chosen only for specific compatibility, storage, or performance needs, and a multitenant container database should use a character set compatible with its intended pluggable databases.

Read More: [About Character Set Selection During Installation](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-database-client/about-character-set-selection-during-installation.html)

## Running the Installer in a Different Language

The database installer language is determined by the operating system locale. Supported languages include Brazilian Portuguese, French, German, Italian, Japanese, Korean, Simplified Chinese, Spanish, and Traditional Chinese. To use one of these languages, set the operating system session locale before launching the installer; unsupported locales cause the installer to run in English.

Read More: [Running the Installer in a Different Language](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-database-client/running-the-installer-in-a-different-language.html)

## Installing the Oracle Database Client Software

Oracle Database Client 19c is available in both image-based and traditional archive formats and can be installed through the graphical installer or in silent mode. Run `runInstaller` from the Oracle home as the Oracle installation owner, not from the internal Oracle Universal Installer directory, and ensure required user, group, storage, and root-script information is available. For image installations, create a non-symbolic-link Oracle home, extract `client_home.zip` there, and launch the Setup Wizard from that directory; the image installation starts an Administrator-type client installation and requires responding to the configuration prompts.

Read More: [Installing the Oracle Database Client Software](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-database-client/installing-the-oracle-database-client-software.html)

## Using Oracle Net Configuration Assistant

After installing Oracle Database Client, run Oracle Net Configuration Assistant in standalone mode from `$ORACLE_HOME/bin` using `netca`. Use it to configure listeners, naming methods, net service names, and directory server access, and have the database host name available while completing the configuration screens.

Read More: [Using Oracle Net Configuration Assistant](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-database-client/using-oracle-net-configuration-assistant.html)

## Relinking Oracle Database Client Binaries After Installation

Oracle Database Client binaries can be relinked with the `relink as_installed` option after operating system patches or upgrades. Before relinking, shut down all executables running from the target Oracle home and applications using its shared libraries. As the client owner, set `ORACLE_HOME`, change to `$ORACLE_HOME/bin`, run `./relink as_installed`, and review the generated logs under `$ORACLE_HOME/install`.
Read More: [Relinking Oracle Database Client Binaries After Installation](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-database-client/relinking-oracle-database-client-binaries-after-installation.html)


# Installing Oracle Instant Client

## About Oracle Instant Client

Oracle Instant Client provides lightweight client-side connectivity for applications connecting to local or remote Oracle Databases on Linux x86-64 and Linux Arm (aarch64). Distributed as ZIP files or RPMs, it supports OCI, OCCI, ODBC, JDBC OCI, popular language APIs, and utilities such as SQL\_Plus, SQL\_Loader, Data Pump, genezi, and adrci, without requiring a full Oracle home. Packages include Basic, Basic Light, SDK, SQL\*Plus, Tools, ODBC, Precompilers, and JDBC-OCI Supplement, offering reduced storage requirements, simple deployment, and full client functionality for supported operations.

Read More: [About Oracle Instant Client](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-instant-client/about-oracle-instant-client.html)

## Hardware Requirements for Oracle Instant Client Installation on Linux for Arm (aarch64)

Oracle Instant Client on Linux for Arm (aarch64) requires at least 256 MB of RAM, 350 MB of available disk space, and network connectivity between the client and its network environment.

Read More: [Hardware Requirements for Oracle Instant Client Installation on Linux for Arm (aarch64)](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-instant-client/hardware-requirements-for-oracle-instant-client-installation-on-linux-for-arm-aarch64.html)

## Operating System Requirements for Linux for Arm (aarch64)

Linux for Arm (aarch64) installations must use a supported distribution, kernel, and package set. Oracle Linux 8 requires version 8.6 with Unbreakable Enterprise Kernel 7, kernel 5.15.0-6.80.3.1.el8uek.aarch64 or later, the listed development, runtime, networking, and system packages, and JDK 8; Oracle Linux 7 requires version 7.8 with Unbreakable Enterprise Kernel 5, kernel 4.14.35-1902.303.4.1.el7uek.aarch64 or later, packages including devtoolset-8 tools, glibc, libaio, and pcre, and JDK 8. The latest certification information should be checked before installation.

Read More: [Operating System Requirements for Linux for Arm (aarch64)](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-instant-client/operating-system-requirements-for-linux-for-arm-aarch64.html)

## Verifying Oracle Instant Client Code Signing

Oracle Instant Client ZIP files and RPM packages can be verified before deployment to confirm package integrity and authenticity. Use Java jarsigner with the verify option for ZIP files, optionally including verbose certificate details, and use rpm commands to inspect signatures, compare key fingerprints, and run verbose checksum and signature validation. RPM verification may report NOKEY when the signing key is absent, while an installed and matching key produces successful signature and digest checks.

Read More: [Verifying Oracle Instant Client Code Signing](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-instant-client/verifying-oracle-instant-client-code-signing.html)

## Installing Oracle Instant Client Packages

Oracle Instant Client can be installed from ZIP files, repository or manually downloaded RPMs, or the graphical setup wizard. ZIP installations require extracting packages together, installing libaio, configuring the runtime library path, optionally setting TNS\_ADMIN and PATH, and placing optional network configuration files in network/admin. RPM installations use yum or dnf and generally permit only one client version at a time, while the setup wizard installs into an Oracle home and supports later deinstallation with runInstaller.

Read More: [Installing Oracle Instant Client Packages](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-instant-client/installing-oracle-instant-client-packages.html)

## Installing Oracle Instant Client Basic Light

Basic Light is a smaller Instant Client package containing English client error messages and a limited set of Unicode, ASCII, and Western European character sets. It supports specified single-byte and Unicode client and database character sets, including US7ASCII, WE8MSWIN1252, UTF8, and AL32UTF8, and reports client-generated errors in English regardless of NLS\_LANG language settings. It can be installed from ZIP files or RPMs by using the basiclite package in place of Basic; additional packages such as SQL\*Plus require the Basic package.

Read More: [Installing Oracle Instant Client Basic Light](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-instant-client/installing-oracle-instant-client-basic-light.html)

## Instant Client Libraries for OCI

OCI applications require the Instant Client libraries to reside in the same directory. The Basic package provides libclntsh.so.19.1, libclntshcore.so.19.1, libociei.so, and libnnz19.so, while Basic Light substitutes libociicus.so for libociei.so. Applications must expose only the appropriate Instant Client library directory through ldconfig or the operating system library path, avoiding simultaneous inclusion of an Oracle home library directory, and may store Oracle Net configuration files in network/admin.

Read More: [Instant Client Libraries for OCI](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-instant-client/instant-client-libraries-for-oci.html)

## Environment Variables for Oracle Instant Client

Key environment variables include LD\_LIBRARY\_PATH for locating libraries when ldconfig or another mechanism is not used, NLS\_LANG for client language, territory, and character set behavior, TNS\_ADMIN for locating Oracle Net and Instant Client configuration files, ORA\_TZFILE for selecting an external or smaller time zone file, and ORA\_SDTZ for the default session time zone. LD\_LIBRARY\_PATH is generally unnecessary for RPM installations, and ORACLE\_HOME must not be set for Instant Client deployments.

Read More: [Environment Variables for Oracle Instant Client](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-instant-client/environment-variables-for-oracle-instant-client.html)

## About the Oracle Instant Client SDK

The Instant Client SDK supplies C and C++ headers, makefiles, demonstration programs, the Object Type Translator, and Linux build support for developing OCI and OCCI applications. It is available as ZIP or RPM packages for Linux x86-64 and Linux Arm (aarch64), and applications built with it can be deployed in compatible client environments. During Linux builds, the Instant Client directory must be available through the runtime library path, typically by setting LD\_LIBRARY\_PATH before linking or running applications.

Read More: [About the Oracle Instant Client SDK](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-instant-client/about-the-oracle-instant-client-sdk.html)

## Patching Oracle Instant Client Shared Libraries

Oracle Instant Client patching requires applying patches to a complete Oracle Database Client Administration installation with OPatch, regenerating the required data shared libraries and package files, and copying the results to the target Instant Client system. This process is not supported on Linux Arm (aarch64) and is unavailable on Microsoft Windows. Make targets can regenerate libociei.so, libociicus.so, individual package ZIPs, or all packages; regenerated content reflects the languages, character sets, and time zone files installed in the source Oracle home, and patch information can be inspected with genezi -v.

Read More: [Patching Oracle Instant Client Shared Libraries](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/installing-oracle-instant-client/patching-oracle-instant-client-shared-libraries.html)


# Oracle Database Client Postinstallation Tasks

Complete configuration tasks after you install Oracle Database Client.

You are required to complete some configuration tasks after Oracle Database Client is installed. In addition, Oracle recommends that you complete additional tasks immediately after installation. You must also complete product-specific configuration tasks before you use those products.

> **Note:**
>
> This article describes basic configuration only. Refer to product-specific administration and tuning guides for more detailed configuration and tuning information.

## Downloading Release Update Patches

After installation, download and install the appropriate quarterly Release Updates or Monthly Recommended Patches for Oracle software through My Oracle Support. Use Patch Search to locate patches by name, number, bug, product, release, platform, or language, then download, extract, and review each patch’s README for application instructions. Oracle recommends out-of-place patching with Gold images for quarterly updates in Oracle AI Database 26ai; OPatch and OPatchAuto remain available for in-place patching, while RU patching is unsupported for the Free release.

Read More: [Downloading Release Update Patches](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/oracle-database-client-postinstallation-tasks/downloading-release-update-patches.html)

## Setting Language and Locale Preferences for Client Connections

Configure client locale and character-set settings to match application preferences and the encoding of the client I/O device, because an incorrect character set can cause data loss. OCI applications use NLS\_LANG and related NLS settings, supplied through environment variables or, on Windows, the Registry, with environment variables taking precedence. Windows Oracle Universal Installer sets a default NLS\_LANG value, whereas Linux and UNIX installations do not. JDBC applications instead derive language and territory from the Java VM locale and always use Unicode for the client character set; application servers may define these settings in their configuration.

Read More: [Setting Language and Locale Preferences for Client Connections](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/oracle-database-client-postinstallation-tasks/setting-language-and-locale-preferences-for-client-connections.html)

## Creating a Backup of the root.sh Script

Back up the root.sh script after completing installation because installing additional products into the same Oracle home can modify the existing script. The backup preserves the original script contents for recovery if they are needed later.
Read More: [Creating a Backup of the root.sh Script](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/oracle-database-client-postinstallation-tasks/creating-a-backup-of-the-root.sh-script.html)


# Removing Oracle Database Software

## About Oracle Deinstallation Options

Oracle’s `deinstall` utility removes Oracle software and configuration files from an Oracle home, including Oracle Database, Grid Infrastructure, Oracle RAC, and Oracle Database Client; individual components are not supported for separate removal. The utility resides in `$ORACLE_HOME/deinstall`, can generate or use response files, and must be run from the same release as the software being removed. Failed or inactive installations require complete configuration details, while Grid Infrastructure removal additionally requires dismounting ACFS, disabling ADVM, and addressing any GNS DNS entries. Depending on the inventory and installation layout, `deinstall` may delete Oracle base directories, configuration files, database data, and recovery-area files, including user data owned by the Oracle software account, even when located outside the Oracle base.

Read More: [About Oracle Deinstallation Options](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/removing-oracle-database-software/about-oracle-deinstallation-options.html)

## Oracle Deinstallation

The `deinstall` command stops Oracle software and removes software and configuration files for a specified Oracle home. It supports interactive or silent execution, configuration inspection and response-file generation with `-checkonly`, custom response files through `-paramfile`, parameter overrides with `-params`, and configurable response, temporary, and log directories using `-o`, `-tmpdir`, and `-logdir`. In multinode environments, `-local` limits deinstallation to the local node while deconfiguring remote nodes, and Grid Infrastructure options can preserve local or remote homes with `-skipLocalHomeDeletion` or `-skipRemoteHomeDeletion`; `-help` provides option details.

Read More: [Oracle Deinstallation](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/removing-oracle-database-software/oracle-deinstallation.html)

## Deinstallation Examples for Oracle Database Client

Oracle Database Client software can be removed by running `./deinstall` from its `$ORACLE_HOME/deinstall` directory, which automatically identifies the Oracle home. For noninteractive or customized removal, provide a response file with `-paramfile`; response files can be generated using `-checkonly` or adapted from `$ORACLE_HOME/deinstall/response/deinstall.rsp.tmpl`. The example demonstrates invoking the client deinstaller from `/u01/app/oracle/product/19.0.0/client_1/deinstall` with a response file stored at `/home/usr/oracle/my_db_paramfile.tmpl`.
Read More: [Deinstallation Examples for Oracle Database Client](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/removing-oracle-database-software/deinstallation-examples-for-oracle-database-client.html)


# Response Files

## Reasons for Using Silent Mode or Response File Mode

Response files automate Oracle software installation and configuration by supplying answers to installer prompts, enabling repeatable deployments across multiple systems. Silent mode requires all responses and runs without installer screens, displaying only terminal progress, while response file mode supplies partial or complete responses but continues displaying installer screens as needed. Silent mode is suited to unattended, scheduled, GUI-less, or identical multi-system installations; response file mode is useful when default answers are provided but user interaction remains necessary.

Read More: [Reasons for Using Silent Mode or Response File Mode](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/response-files/reasons-for-using-silent-mode-or-response-file-mode.html)

## Using Response Files

Using response files involves completing all required preinstallation tasks, preparing the response file, running the Oracle installer in silent or response file mode, executing root scripts when prompted, and, for software-only installations, running Net Configuration Assistant and Oracle DBCA to configure networking and create the database. This process enables consistent, largely automated Oracle product deployment and configuration.

Read More: [Using Response Files](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/response-files/using-response-files.html)

## Preparing Response Files

Oracle supplies product-specific response file templates containing instructions and examples; database, Grid Infrastructure, and client templates are stored in their respective installation response directories. Administrators should copy and edit the appropriate template, retain the `.rsp` suffix, validate all required settings, and protect files with permission mode 600 because they may contain administrative and operating-system authentication passwords. Response files can also be recorded during an interactive OUI installation from the Summary page, although passwords are not saved; recorded files should be reviewed and adapted before reuse on other systems.

Read More: [Preparing Response Files](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/response-files/preparing-response-files.html)

## Running Oracle Universal Installer Using a Response File

Run OUI from the command line as the software owner with a fully qualified response file path, using `runInstaller` for Oracle Database or Client and `gridSetup.sh` for Grid Infrastructure. Include `-silent` for completely noninteractive execution; otherwise, response file mode requires the `DISPLAY` variable. Complete normal preinstallation checks, execute `orainstRoot.sh` as root during the first Oracle installation to establish inventory configuration, and run the product `root.sh` script after installation. Use the `-help` option to review available installer arguments.

Read More: [Running Oracle Universal Installer Using a Response File](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/response-files/running-oracle-universal-installer-using-a-response-file.html)

## Running Configuration Assistants Using Response Files

Oracle DBCA and NETCA can be automated after installation by copying and editing their response file templates, setting the appropriate Oracle home, and executing them with fully qualified response file paths. DBCA uses `dbca.rsp` and requires `-responseFile` together with `-silent` for noninteractive database creation, as well as a graphical display and `DISPLAY` setting; NETCA uses `netca.rsp` with its silent command to configure listeners, naming methods, and service names. Incorrectly configured response files cause the assistants to fail, and both tools provide help options or progress feedback during execution.
Read More: [Running Configuration Assistants Using Response Files](https://docs.oracle.com/en/database/oracle/oracle-database/19/lacli/response-files/running-configuration-assistants-using-response-files.html)