System requirements

The following table indicates the combinations of operating systems and DB2 UDB that are supported by version 9.6.00 of BMC PATROL for DB2 Universal Database. Support for a version of DB2 UDB on a particular operating system is designated by a + symbol. A blank cell indicates no support.

Supported operating systems

(for PATROL Agent only)

Supported IBM DB2 versions

DB2 UDB
ESE 9.7
(64-bit)

DB2 UDB
ESE 10.1
(64-bit)

DB2 UDB
ESE 10.5
(64-bit)
DB2 UDB
ESE 11.1
(64-bit)
DB2 UDB ESE 11.5 (64-bit)
CentOS 5.6, x86-64 ++++
HP-UX 11.31i, Itanium 64 ++++
IBM AIX 7.1, 64-bit +++
Oracle Solaris 10, 64-bit, SPARC+++
Oracle Solaris 10, x86-64 +++
Oracle Solaris 11, x86-64  +++
Oracle Solaris 11, SPARC +++
Red Hat Enterprise Linux 6a, x86-64b+++
Red Hat Enterprise Linux 6a, zSeries, 64-bit +++

Red Hat Enterprise Linux 7.x, 64-bit 

Note: Red Hat Enterprise Linux Server 7.x is supported till 7.6.

This support is available in PATROL for DB2 version 9.6.10 and later.

+++++
Red Hat Enterprise Linux 8.x, 64-bit+++++
SUSE Linux Enterprise Server 11, x86-64b+++

Microsoft Windows Server 2012, x64

+
Microsoft Windows Server 2012 R2, x64+
Microsoft Windows Server 2016, x64 +
Microsoft Windows Server 2019, x64+++++


Includes support for all updates of Red Hat Enterprise Linux 5 and 6, x86, x86-64, and zSeries.

References to x86-64 include AMD64 (which includes Opteron) and Intel 64 architecture (formerly known as Intel Extended Memory 64 Technology, or Intel EM64T).


Resource

Requirements

Microsoft .Net Framework (remote computer with Microsoft Windows OS).NET Framework 4.0 or later is required on the PATROL Agent system and the remote DB2 system
PowerShell (remote computer with Microsoft Windows OS)PowerShell 2.0 or later is required on the PATROL Agent system and the remote DB2 system

PATROL Agent

9.6.00 or later

Other PATROL products

PATROL Installation Utility version 10.7 or later

BMC TrueSight Presentation Server
  • 11.x
  • 10.x
BMC ProactiveNet Performance Management9.6.00
Java

Supports any of the following Java versions:

  • Oracle Java 8.x
  • OpenJDK 8.x
  • OpenJDK 11.x

Note: For the latest announcement on BMC’s Java Support policies for TrueSight monitoring solutions, see Java support for TrueSight monitoring solutions

Ports

If you are migrating a PATROL Agent or console with PATROL for DB2 UDB, you must specify the port number to connect to all the agent computers.

The default port number is 3181.

Minimum hardware requirements2 CPUs, 4 GB RAM
 OS accounts on UNIX

PATROL account for UNIX (used for PATROL for DB2 installation)

Use the following guidelines when setting up the PATROL UNIX account:

  • Create a dedicated user account before you install PATROL. This default account for PATROL can be a local account or a domain account.
  • The account .login, .profile.cshrc, and.kshrc files should not contain any customizations such as aliases, nondefault prompts, or unmask settings other than 022.
  • Do not use the root account.
  • The account must have permission to create directories and write the installation logs to the $HOME and*/tmp* directories on the computer where you are installing products.
  • The account must have access to a root account on the computer where PATROL will be installed.
  • (recommended ) Install PATROL on local partitions. If PATROL is installed on NFS-mounted partitions, the root account must have root access permissions on the NFS server.
  • If you are installing PATROL to monitor DB2 UDB in a UNIX environment with a large number of physical nodes, you can install on NFS-mounted partitions to reduce the number of installations.
OS accounts on Windows

PATROL account for Windows (used for PATROL for DB2 installation)

Use the following guidelines when setting up the PATROL Windows account:

  • Create a dedicated user account before you install PATROL. This default account for PATROL can be a local account or a domain account.
  • The account must be a member of the local Administrators group of the computer where the agent will reside.
  • The account on a domain controller must be a member of the domain Administrators group.
  • Do not use a built-in Administrator account.
  • If you are using a domain account, you must specify the Windows NT domain with the user name.
  • Stand-alone workgroup servers must use a local user account.
  • Servers that are trusted members of a domain can use a local or domain account.
  • If an Access Control List (ACL) is used to control access to the PATROL Agent, the default accounts must have C-configure privileges.

OS account for PATROL for DB2 UDB (used for configuration of the instances to be monitored by PATROL). For more information, see User account requirements.

SecurityDo not use Security level 3 or higher if you are using Enterprise Configuration or the PATROL Advisor. These security levels require passwords to be entered every time the host is accessed.
LicenseYou must have a valid demonstration license (typically good for 30 days) or a permanent license to run your PATROL products. If you do not have a permanent license, contact your BMC Software sales representative or the BMC Software Contract Administration department for licensing information.

Note

BMC products are certified for use on supported operating system versions. BMC does not explicitly test for OS patches/updates that are released after a BMC product is released.

BMC products should work fine with minor updates to these supported operating systems. For assistance, please contact BMC Customer Support.

Was this page helpful? Yes No Submitting... Thank you

Comments