V11 Service Pack 11
Loading...

SAP Oracle Agent System Requirements

The following requirements are for the SAP Oracle Agent:

SAP BR*Tools 7.40 for Oracle 12c (V12.2)

Note For Oracle 12.2, you must install BR*Tools 7.40 patch level 32 or higher. For information on additional SAP requirements with Oracle 12.2, see SAP Note 2470660.

Application

Operating System

Architecture

AIX

AIX 7.2 64-bit

TL 09 SP 1

Power PC

 

AIX 7.1 64-bit

TL03 SP4

Power PC

 

AIX 6.1 64-bit

TL09 SP4

Power PC

HP-UX

HP-UX 11i v3 (11.31)

Itanium

Z-Linux

Red Hat Enterprise Linux

 

 

Red Hat Enterprise Linux 7.x

x86, x64 or compatible processors

 

Red Hat Enterprise Linux 6.4

x86, x64 or compatible processors

 

SuSE Linux (SLES)

 

 

SuSE Linux 12 SP1 Enterprise Server

x86, x64 or compatible processors

Oracle Solaris

Oracle Solaris 11.2 SRU 5.5

x64, Sparc T/M series

 

Oracle Solaris 10 Update 11

x64, Sparc T/M series

Windows

Windows 2016

 

 

Microsoft Windows Server 2016 x 64Editions

 

 

Windows Server 2012

 

 

Microsoft Windows Server 2012 R2 Editions

 

 

Microsoft Windows Server 2012 x64 Edition

 

SAP BR*Tools 7.20 (42), 7.20(40), 7.40(14) for Oracle 12c (V12.1), 11g(R1, R2 or higher)

Application

Operating System

Architecture

AIX

AIX 7.2 64-bit

Power PC

 

AIX 7.1 64-bit

Power PC

 

AIX 6.1 TL 02 SP00 64-bit or higher

Power PC

HP-UX

HP-UX 11i v3 (11.31)

Itanium

 

HP-UX 11i v1 (11.23)

Itanium

Linux

Red Hat Enterprise Linux/CentOS

 

 

Red Hat Enterprise Linux/CentOS 7.x with glibc 2.17.x

You must have Oracle v11.2.0.4 or higher with BR*Tools v7.20(40), v7.40(14).

x86, x64, Power PC or compatible processors

 

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

x86, Power PC or compatible processors

 

Red Hat Enterprise Linux/CentOS 6.x with a minimum of glibc 2.12-1.25.x

x64

 

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

x86, x64, Power PC or compatible processors

 

SuSE Linux (SLES)

 

 

SuSE Linux 12.x with glibc 2.19.x

x86, x64, Power PC or compatible processors

 

SuSE Linux 11.x with glibc 2.9.x and later

x86, x64, Power PC or compatible processors

Solaris

Solaris 11.x

x64, Sparc T/M series

 

Solaris 10 Update 6 or equivalent

Sparc T/M series

 

Solaris 10 Update 6 or equivalent

x64

Windows

Windows 2016

 

 

Microsoft Windows Server 2016 Editions

 

 

Windows Server 2012

 

 

Microsoft Windows Server 2012 R2 Editions

 

 

Microsoft Windows Server 2012 Editions*

*Core Editions are not supported.

 

 

Windows Server 2008

 

 

Microsoft Windows Server 2008 Editions with a minimum of Service Pack 1

*Core Editions are not supported.

 

SAP BR*Tools 7.40, 7.20, 7.10 and 7.00 for Oracle 10g (R1, R2 or higher) Databases

Application

Operating System

Architecture

AIX

AIX 7.2 64-bit

Power PC

 

AIX 7.1 64-bit

Power PC

 

AIX 6.1 TL 02 SP00 64-bit or higher

Power PC

HP-UX

HP-UX 11i v3 (11.31)

Itanium

 

HP-UX 11i v1 (11.23)

Itanium

Linux

Red Hat Enterprise Linux/CentOS

 

 

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

x86, Power PC or compatible processors

 

Red Hat Enterprise Linux/CentOS 6.x with a minimum of glibc 2.12-1.25.x

x64

 

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

x86, x64, Power PC or compatible processors

 

SuSE Linux (SLES)

 

 

SuSE Linux 12.x with glibc 2.19.x

x86, x64, Power PC or compatible processors

 

SuSE Linux 11.x with glibc 2.9.x and later

x86, x64, Power PC or compatible processors

 

SuSE Linux 10.x with glibc 2.4.x

x86, x64, Power PC or compatible processors

Solaris

Solaris 11.x

x64, Sparc T/M series

 

Solaris 10 Update 6 or equivalent

x64

 

Solaris 10 Update 6 or equivalent

Sparc T/M series

Windows

Windows 2016

 

 

Microsoft Windows Server 2016 Editions

*Nano Servers are not supported. See Considerations for Microsoft Windows Server 2016 for more information.

 

 

Windows Server 2012

 

 

Microsoft Windows Server 2012 R2 Editions

 

 

Microsoft Windows Server 2012 Editions*

*Core Editions are not supported.

 

 

Windows 2008

 

 

Microsoft Windows Server 2008 Editions with a minimum of Service Pack 1

*Core Editions are not supported.

 

Cluster - Support

The software can be installed on a Cluster if clustering is supported by the above-mentioned operating systems.

For information on supported cluster types, see Clustering - Support.

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.

Solaris Zones/Containers Support

For a comprehensive list of supported components, see Unix Virtualization.

AIX LPAR/WPAR Support

Data protection on Logical Partitioning (LPAR) and Workload Partitioning (WPAR) is supported.

Miscellaneous

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:

On Solaris computers, the operating system must have been installed with at least the user level software option selected.

SE Linux

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.

.NET Framework

.NET Framework 4.0 is automatically installed. Note that .NET Framework 4.0 can co-exist with other versions of this software.

Microsoft Visual C++

The following Redistributable Package is installed automatically. Note that the Redistributable Package can co-exist with other versions of this software.

Microsoft Visual C++ 2010 Redistributable Package

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.

Last modified: 5/4/2018 7:35:09 PM