SAP Oracle Agent: System Requirements

The following requirements are for the SAP Oracle Agent:

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

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.

  • For Oracle 18c, you must install BR*Tools 7.40 patch level 37 or higher. For information on additional SAP requirements with Oracle 18c, see SAP Notes 2705272, 2763733, and 2660020.

  • For Oracle 19c, you must install BR*Tools 7.40 patch level 40 or higher . For information on additional SAP requirements with Oracle 19c, see SAP Note 2799900, 2817074, and 2763733.

Application

Operating System

Architecture

AIX

AIX 7.2 64-bit

TL 09 SP 1, TL05

PowerPC

AIX 7.1 64-bit

TL03 SP4

PowerPC

AIX 6.1 64-bit

TL09 SP4

PowerPC

HP-UX

HP-UX 11i v3 (11.31)

Itanium

Linux

Oracle Linux

Oracle Linux 7.x with glibc 2.17.x or a more recent version

  • x86

  • x64

  • Compatible processors

Red Hat Enterprise Linux

Red Hat Enterprise Linux 7.x

  • x86

  • x64

  • Compatible processors

Red Hat Enterprise Linux 6.4

  • x86

  • x64

  • Compatible processors

SuSE Linux (SLES)

SuSE Linux 12 SP1 Enterprise Server

  • x86

  • x64

  • Compatible processors

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

  • x86

  • x64

  • PowerPC

  • 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

Microsoft Windows Server 2019 (Standard, Datacenter) (64-bit only)

Microsoft Windows Server 2019 Editions

Windows 2016

Microsoft Windows Server 2016 x64 Editions

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 (46), 7.40(14) for Oracle 12c (V12.1), 11g(R1, R2 or higher)

Application

Operating System

Architecture

AIX

AIX 7.2 64-bit

PowerPC

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 v1 (11.23)

Itanium

Linux

Oracle Linux

Oracle Linux 7.x with glibc 2.17.x or a more recent version

  • x86

  • x64

  • Compatible processors

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 7.x with glibc 2.17.x or a more recent version

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

  • x86

  • x64

  • PowerPC

  • Compatible processors

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

  • PowerPC

  • Compatible processors

SuSE Linux (SLES)

SuSE Linux 12 (Initial Release/SP1/SP2/SP3/SP4/SP5) with glibc 2.19.x

  • x86

  • x64

  • PowerPC

  • Compatible processors

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

  • x86

  • x64

  • PowerPC

  • 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

Server Core installations are not supported.

Windows Server 2008

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

Server Core installations 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

PowerPC

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 v1 (11.23)

Itanium

Linux

Oracle Linux

Oracle Linux 7.x with glibc 2.17.x or a more recent version

  • 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

  • PowerPC

  • Compatible processors

SuSE Linux (SLES)

SuSE Linux 12 (Initial Release/SP1/SP2/SP3/SP4/SP5) with glibc 2.19.x

  • x86

  • x64

  • PowerPC

  • Compatible processors

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

  • x86

  • x64

  • PowerPC

  • 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. For more information, see Considerations for Microsoft Windows Server 2016.

Windows Server 2012

Microsoft Windows Server 2012 R2 Editions

Microsoft Windows Server 2012 Editions

Server Core installations are not supported.

Windows 2008

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

Server Core installations are not supported.

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.

Solaris Containers and Zones

You can back up and restore data in both global and non-global zones.

For a list of supported components, see Unix Virtualization.

AIX LPAR/WPAR

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++ Redistributable 2017 is Automatically Installed

Starting in Service Pack 18, Microsoft Visual C++ Redistributable 2017 (vcredist2017.exe) is automatically installed. If a computer does not have the latest Windows updates, the installation of Microsoft Visual C++ Redistributable 2017 will fail in installing Universal C Runtime.

The following Windows updates must be installed to prevent the installation failure:

KB2919355

KB2939087

KB2975061

KB2999226

Updates are not required on latest Windows operating system versions, such as Microsoft Windows 10 and Microsoft Windows Server 2016, as these versions come with the Universal C Runtime already installed.

Connect String Considerations

The software uses the Connect String that you specify for the instance for browse operations and to view the instance status. Depending on your configuration, the SAP for Oracle agent uses “/” or “//” for data protection and recovery operations. If you want to use “//”, then you must configure the SAP secure store on Commvault and on SAP. For more information on SSFS, go to the SAP support site and see SAP Note 1611877 Support for ABAP SSFS during database connect.

To use “system” as the user, the password must be "manager" and you need to set the following additional setting. To the SAP Oracle client, add the additional setting as shown in the following table.

For instructions on how to add additional settings from the CommCell Console, see Adding or Modifying Additional Settings from the CommCell Console.

Property

Value

Name

sCVSAPNOSLASH

Category

OracleSapAgent

Type

String

Value

Y

Note:

If you disabled OS authentication, and the system user password is not "manager" and you do not have the SSFS feature enabled, you can use the Oracle connect string specified in the SAP Oracle instance properties to run the brbackup, brarchive, brrestore, and rerecover commands.

To use the connect string, set the bUseConnectStringForBRTools additional setting. To the SAP Oracle client, add the additional setting as shown in the following table.

For instructions on how to add additional settings from the CommCell Console, see Adding or Modifying Additional Settings from the CommCell Console.

Property

Value

Name

bUseConnectStringForBRTools

Category

OracleSapAgent

Type

Boolean

Value

True

DISCLAIMER

Certain third-party software and service releases (together, “Releases”) may not be supported by Commvault. You are solely responsible for ensuring Commvault’s products and services are compatible with any such Releases.

Loading...