Oracle Archive: System Requirements

The following requirements are for Oracle Archiving:

Oracle 12c, 11g (R1, R2 or higher), 10g Databases (Enterprise Edition)

Operating System

Operating System Version

Architecture

AIX

AIX 7.1 64-bit

PowerPC

AIX 6.1 TL 02 SP00 or higher, 64-bit

PowerPC

HP-UX

HP-UX 11i v3 (11.31)

Itanium

HP-UX 11i v2 (11.23)

Itanium

Linux

Oracle Linux

Oracle Linux 6.x with glibc 2.12.x or a more recent version

  • x86

  • x64

  • Compatible processors

Oracle Linux 5.x with glibc 2.5.x

  • x86

  • x64

  • Compatible processors

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12.x

  • x86

  • PowerPC

  • Compatible processors

Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12-1.25.x or a more recent version

x64

Red Hat Enterprise Linux/CentOS 5.x with glibc 2.5.x

  • x86

  • x64

  • Compatible processors

SuSE Linux (SLES)

SuSE Linux 11 (Initial Release/SP1 and later SPs) with glibc 2.9.x and higher

  • x86

  • x64

  • PowerPC

  • Compatible processors

SuSE Linux 10 (Initial Release/SP1/SP2/SP3/SP4) with glibc 2.4.x

  • x86

  • x64

  • PowerPC

  • Compatible processors

Solaris

Solaris 11.x

  • x64

  • Sparc T/M series

Solaris 10 Update 6 or equivalent

  • x64

  • Sparc T/M series

Cluster Support

You can install the software on a cluster, if clustering is supported by the operating system. For information about supported cluster types, see Support for Cluster Configuration.

Hard Drive

2 GB of minimum disk space is required for software installation.

256 MB of free disk space is required for the job result directory.

256 MB of free disk space is required for the log directory.

Miscellaneous

SELinux

If you have SELinux enabled on the client computer, create the SELinux policy module as a root user before performing a backup. The SELinux Development package must be installed on the client.

To create an SELinux policy module, perform the following steps as user "root":

  1. Create the following files in the /usr/share/selinux/devel directory:

    File Name

    Content of the File

    <directory>/<file_name>.te

    where:

    <directory> is /usr/share/selinux/devel

    <file_name> is the name of the UNIX file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

    For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.te

    The content of the file should be as follows:

    policy_module(<name>,<version>)

    ##############################

    where:

    <name> is the name of the policy module. You can give any unique name to the policy module, such as a process or application name.

    <version> is the version of the policy module. It can be any number, such as 1.0.0.

    For Example: While creating a policy module for the backup_IDA application, you can use the following content.

    policy_module(backup_IDA,1.0.0)

    <directory>/<file_name>.fc

    where:

    <directory> is /usr/share/selinux/devel

    <file_name> is the name of the UNIX file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

    For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.fc

    The content of the file should be as follows:

    Note that the following list of files is not exhaustive. If the process fails to launch, check /var/log/messages. Also, if required, add it to the following list of files.

    /opt/<software installation directory>/Base/libCTreeWrapper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libCVMAGuiImplgso -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libdb2locale.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libdb2osse.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libDb2Sbt.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libdb2trcapi.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libDrDatabase.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libIndexing.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

    /opt/<software installation directory>/Base/libSnooper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

  2. Create the policy file from command line. Use the following command. Ensure that you give the following commands in the /usr/share/selinux/devel directory.

    [root]# make backup_IDA.pp

    Compiling targeted backup_IDA module

    /usr/bin/checkmodule: loading policy configuration from tmp/backup_IDA.tmp

    /usr/bin/checkmodule: policy configuration loaded

    /usr/bin/checkmodule: writing binary representation (version 6) to tmp/backup_IDA.mod

    Creating targeted backup_IDA.pp policy package

    rm tmp/backup_IDA.mod tmp/backup_IDA.mod.fc

    [root]# semodule -i backup_IDA.pp

    [root]#

  3. Execute the policy module. Use the following command:

[root]# restorecon -R /opt/<software installation directory>

SELinux is now configured to work with this application.

The File System Agent will be automatically installed during installation of this software, if it is not already installed. For System Requirements and install information specific to the File System Agents, see:

The operating system must have been installed with at least the user level software option selected.

DISCLAIMER

Third-party maintenance (minor) releases or service packs that are supported by the Commvault software may not be listed in our System Requirements. When possible, Commvault provides information on any known issues related to these minor releases or service packs. In some cases, these minor releases or service packs affect how the Commvault software works. Commvault software may experience changes in functionality as the result of the third-party minor release or service pack. These changes are beyond the control of Commvault. Platforms that are supported in the current version of Commvault software may not be supported in earlier versions of the software. Contact your software provider to ensure that third-party minor releases or service packs are compatible with the Commvault software. Additional considerations regarding minimum requirements and End-of-Life policies from third-party vendors also apply.

Loading...