System requirements for IBM InfoSphere Optim Performance Manager for DB2 for Linux, UNIX, and Windows V5.1.0

Product documentation


Abstract

This document describes the system requirements for IBM® InfoSphere® Optim™ Performance Manager for DB2® for Linux®, UNIX®, and Windows® Version 5.1.0.

Content

Tab navigation

Tab navigation


Outline


Hardware Requirements
Group Applicable Component Notes
Disk Space InfoSphere Optim Performance Manager server

Permanent space for the program files and log files:

  • /opt directory: 3.5 GB
  • /var directory: 1 MB
  • /home directory: 2 GB

By default, the database log files are stored in the /home directory. The log files location can be changed when you configure the repository database.

Note that more space might be needed for the log files if secondary logs need to be allocated during runtime, or if you increase the size or number of primary log files manually when you configure the repository database.

The additional disk space for the collected data of the monitored databases depends on the type of information that is collected for history data and Performance Warehouse.

For more information about capacity planning, see the Capacity planning for InfoSphere Optim Performance Manager document.

InfoSphere Optim Performance Manager server

1,500 MB of temporary space for running the installation program
 

Memory InfoSphere Optim Performance Manager server

1 GB free RAM

The minimum memory requirements that are needed to run InfoSphere Optim Performance Manager when monitoring a small number of non-partitioned databases.

The total amount of memory consumption depends on:

  • The number of monitored DB2 databases
  • The number of partitions on your monitored DB2 databases
  • The number of DB2 objects on your monitored DB2 databases
  • The number of monitoring functions that are activated in InfoSphere Optim Performance Manager

In general, the memory consumption consists of memory that the InfoSphere Optim Performance Manager process consumes and of memory that DB2 processes consume. For more information about capacity planning, see the Capacity Planning for InfoSphere Optim Performance Manager document.

Operating Systems
Operating System Attributes Applicable Component Notes
AIX Platform listing of supported OS
AIX 5.3 TL11 POWER System and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: POWER System
InfoSphere Optim Performance Manager server

Requires APAR IZ74749 or 5300-11-05 or later.

AIX 5.3 TL12 POWER System and future OS fix packs Bitness: 64 Bit Tolerate
Deployment Role: Server
Hardware platform: POWER System
InfoSphere Optim Performance Manager server

Requires APAR IZ76228 or 5300-12-02 or later.

AIX 6.1 TL4 POWER System and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: POWER System
InfoSphere Optim Performance Manager server

Requires APAR IZ74508 or 6100-04-06 or later.

AIX 6.1 TL5 POWER System and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: POWER System
InfoSphere Optim Performance Manager server

Requires APAR IZ76227 or 6100-05-02 or later.

AIX 6.1 TL6 POWER System and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: POWER System
InfoSphere Optim Performance Manager server

Requires APAR IZ74932 or 6100-06-00 or later.

AIX 7.1 POWER System and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: POWER System
InfoSphere Optim Performance Manager server
Software Requirements
Group Product Applicable Component Notes
Databases DB2 Enterprise Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

DB2 Enterprise Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

DB2 Enterprise Server Edition 9.7.0.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

Java Technology IBM Runtime Environment, Java Technology Edition 6.0.9.1 InfoSphere Optim Performance Manager server
Web Browsers Microsoft Internet Explorer 9.0 All Applicable Components

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Mozilla Firefox 4.0 All Applicable Components

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

Optional Supported Software
Group Product Applicable Component Notes
Monitored Databases DB2 Advanced Enterprise Server Edition 9.7 and future fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
DB2 Enterprise Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

For Extended Insight, DB2 Version 9.1, Fix Pack 6 is required to get information about data server time.

DB2 Enterprise Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

If you monitor a DB2 9.5 database on Linux on xSeries and if you have the DB2 Administrative Task Scheduler enabled on this database, ensure that one of the following APARS is installed:

  • DB2 APAR IC77911 on the monitored DB2 instance
  • APAR PK99986 on Optim Performance Manager
DB2 Enterprise Server Edition 9.7 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
DB2 pureScale Feature for Enterprise Server Edition 9.8 and future fix packs InfoSphere Optim Performance Manager server

The PureScale feature is only supported as a monitored instance or database. The PureScale feature cannot be used as a repository database for an InfoSphere Optim Performance Manager server.

DB2 Workgroup Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

For Extended Insight, DB2 Version 9.1, Fix Pack 6 is required to get information about data server time.

DB2 Workgroup Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

If you monitor a DB2 9.5 database on Linux on xSeries and if you have the DB2 Administrative Task Scheduler enabled on this database, ensure that one of the following APARS is installed:

  • DB2 APAR IC77911 on the monitored DB2 instance
  • APAR PK99986 on Optim Performance Manager
DB2 Workgroup Server Edition 9.7 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
Problem Determination Tools Optim Query Tuner for DB2 for Linux, UNIX and Windows 3.1 and future fix packs InfoSphere Optim Performance Manager server
Optim Query Tuner for DB2 for Linux, UNIX and Windows 2.2.0.2 and future fix packs InfoSphere Optim Performance Manager server
Virtualization IBM PowerVM Hypervisor (LPAR, DPAR, Micro-Partition) any supported version and future fix packs InfoSphere Optim Performance Manager server


Hardware Requirements
Group Applicable Component Notes
Disk Space DB2 Performance Expert client

Permanent space in the installation directory for the program files and log files:

  • Linux on xSeries 32-bit and 64-bit: 390 MB
DB2 Performance Expert client

Temporary space for running the installation program:

  •     Linux on xSeries 32-bit: 260 MB
  •     Linux on xSeries 64-bit: 500 MB
InfoSphere Optim Performance Manager server

Permanent space for the program files and log files:

  • /opt directory: 3.5 GB
  • /var directory: 1 MB
  • /home directory: 2 GB

By default, the database log files are stored in the /home directory. The log files location can be changed when you configure the repository database.

Note that more space might be needed for the log files if secondary logs need to be allocated during runtime, or if you increase the size or number of primary log files manually when you configure the repository database.

The additional disk space for the collected data of the monitored databases depends on the type of information that is collected for history data and Performance Warehouse.

For more information about capacity planning, see the Capacity planning for InfoSphere Optim Performance Manager document.

InfoSphere Optim Performance Manager server

1,500 MB of temporary space for running the installation program
 

Memory DB2 Performance Expert client

512 MB free RAM

InfoSphere Optim Performance Manager server

1 GB free RAM

The minimum memory requirements that are needed to run InfoSphere Optim Performance Manager when monitoring a small number of non-partitioned databases.

The total amount of memory consumption depends on:

  • The number of monitored DB2 databases
  • The number of partitions on your monitored DB2 databases
  • The number of DB2 objects on your monitored DB2 databases
  • The number of monitoring functions that are activated in InfoSphere Optim Performance Manager

In general, the memory consumption consists of memory that the InfoSphere Optim Performance Manager process consumes and of memory that DB2 processes consume. For more information about capacity planning, see the Capacity Planning for InfoSphere Optim Performance Manager document.

Operating Systems
Operating System Attributes Applicable Component Notes
Linux Platform listing of supported OS
Red Hat Enterprise Linux (RHEL) 5 Advanced Platform POWER System and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: POWER System
InfoSphere Optim Performance Manager server See Note #1
Red Hat Enterprise Linux (RHEL) 5 Advanced Platform System z and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: System z
InfoSphere Optim Performance Manager server
Red Hat Enterprise Linux (RHEL) 5 Advanced Platform x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client
Red Hat Enterprise Linux (RHEL) 5 Advanced Platform x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Red Hat Enterprise Linux (RHEL) 5 Desktop editions x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client See Note #1
Red Hat Enterprise Linux (RHEL) 5 Desktop editions x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components See Note #1
Red Hat Enterprise Linux (RHEL) 5 Server POWER System and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: POWER System
InfoSphere Optim Performance Manager server See Note #1
Red Hat Enterprise Linux (RHEL) 5 Server System z and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: System z
InfoSphere Optim Performance Manager server See Note #1
Red Hat Enterprise Linux (RHEL) 5 Server x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client See Note #1
Red Hat Enterprise Linux (RHEL) 5 Server x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components See Note #1
Red Hat Enterprise Linux (RHEL) Desktop 6 x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client See Note #2
Red Hat Enterprise Linux (RHEL) Desktop 6 x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components See Note #2
Red Hat Enterprise Linux (RHEL) Server 6 POWER System and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: POWER System
InfoSphere Optim Performance Manager server See Note #2
Red Hat Enterprise Linux (RHEL) Server 6 System z and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: System z
InfoSphere Optim Performance Manager server See Note #2
Red Hat Enterprise Linux (RHEL) Server 6 x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client See Note #2
Red Hat Enterprise Linux (RHEL) Server 6 x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components See Note #2
SUSE Linux Enterprise Desktop (SLED) 10.0 SP1 x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client
SUSE Linux Enterprise Desktop (SLED) 10.0 SP1 x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
SUSE Linux Enterprise Desktop (SLED) 11.0 x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client
SUSE Linux Enterprise Desktop (SLED) 11.0 x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
SUSE Linux Enterprise Server (SLES) 10 SP1 POWER System and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: POWER System
InfoSphere Optim Performance Manager server
SUSE Linux Enterprise Server (SLES) 10 SP1 System z and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: System z
InfoSphere Optim Performance Manager server
SUSE Linux Enterprise Server (SLES) 10 SP1 x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client
SUSE Linux Enterprise Server (SLES) 10 SP1 x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
SUSE Linux Enterprise Server (SLES) 11 POWER System and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: POWER System
InfoSphere Optim Performance Manager server
SUSE Linux Enterprise Server (SLES) 11 System z and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: System z
InfoSphere Optim Performance Manager server
SUSE Linux Enterprise Server (SLES) 11 x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client
SUSE Linux Enterprise Server (SLES) 11 x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Software Requirements
Group Product Applicable Component Notes
Databases DB2 Enterprise Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

DB2 Enterprise Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

DB2 Enterprise Server Edition 9.7.0.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

Java Technology IBM Runtime Environment, Java Technology Edition 6.0.9.1 InfoSphere Optim Performance Manager server
Web Browsers Microsoft Internet Explorer 9.0 All Applicable Components

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Mozilla Firefox 3.6 All Applicable Components

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

Mozilla Firefox 4.0 All Applicable Components

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

Optional Supported Software
Group Product Applicable Component Notes
JDBC Drivers IBM Data Server Runtime Client 9.5 and future fix packs DB2 Performance Expert client
IBM Data Server Runtime Client 9.7 and future fix packs DB2 Performance Expert client
DB2 Connect Application Server Edition 9.7 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Enterprise Edition 9.1 and future releases, mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Enterprise Edition 9.5 and future fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Enterprise Edition 9.7 and future fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Personal Edition 9.1 and future releases, mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Personal Edition 9.5 and future fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Personal Edition 9.7 and future fix packs (overview) (support) DB2 Performance Expert client
DB2 Run-time Client 9.1 FP 2 DB2 Performance Expert client
Monitored Databases DB2 Advanced Enterprise Server Edition 9.7 and future fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
DB2 Enterprise Server Edition 9.1 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Enterprise Server Edition 9.5 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Enterprise Server Edition 9.7 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Enterprise Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

For Extended Insight, DB2 Version 9.1, Fix Pack 6 is required to get information about data server time.

DB2 Enterprise Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

If you monitor a DB2 9.5 database on Linux on xSeries and if you have the DB2 Administrative Task Scheduler enabled on this database, ensure that one of the following APARS is installed:

  • DB2 APAR IC77911 on the monitored DB2 instance
  • APAR PK99986 on Optim Performance Manager
DB2 Enterprise Server Edition 9.7 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
DB2 Personal Edition 9.1 and future fix packs DB2 Performance Expert client
DB2 Personal Edition 9.5 and future fix packs DB2 Performance Expert client
DB2 Personal Edition 9.7 and future fix packs DB2 Performance Expert client
DB2 Workgroup Server Edition 9.1 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Workgroup Server Edition 9.5 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Workgroup Server Edition 9.7 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Workgroup Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

For Extended Insight, DB2 Version 9.1, Fix Pack 6 is required to get information about data server time.

DB2 Workgroup Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

If you monitor a DB2 9.5 database on Linux on xSeries and if you have the DB2 Administrative Task Scheduler enabled on this database, ensure that one of the following APARS is installed:

  • DB2 APAR IC77911 on the monitored DB2 instance
  • APAR PK99986 on Optim Performance Manager
DB2 Workgroup Server Edition 9.7 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
Problem Determination Tools Optim Query Tuner for DB2 for Linux, UNIX and Windows 3.1 and future fix packs InfoSphere Optim Performance Manager server
Optim Query Tuner for DB2 for Linux, UNIX and Windows 2.2.0.2 and future fix packs InfoSphere Optim Performance Manager server
Virtualization z/VM 5.4 and future mod levels and fix packs (overview) InfoSphere Optim Performance Manager server

Tab navigation


Outline


Hardware Requirements
Group Applicable Component Notes
Disk Space InfoSphere Optim Performance Manager server

Permanent space for the program files and log files:

  • /opt directory: 3.5 GB
  • /var directory: 1 MB
  • /home directory: 2 GB

By default, the database log files are stored in the /home directory. The log files location can be changed when you configure the repository database.

Note that more space might be needed for the log files if secondary logs need to be allocated during runtime, or if you increase the size or number of primary log files manually when you configure the repository database.

The additional disk space for the collected data of the monitored databases depends on the type of information that is collected for history data and Performance Warehouse.

For more information about capacity planning, see the Capacity planning for InfoSphere Optim Performance Manager document.

InfoSphere Optim Performance Manager server

1,500 MB of temporary space for running the installation program
 

Memory InfoSphere Optim Performance Manager server

1 GB free RAM

The minimum memory requirements that are needed to run InfoSphere Optim Performance Manager when monitoring a small number of non-partitioned databases.

The total amount of memory consumption depends on:

  • The number of monitored DB2 databases
  • The number of partitions on your monitored DB2 databases
  • The number of DB2 objects on your monitored DB2 databases
  • The number of monitoring functions that are activated in InfoSphere Optim Performance Manager

In general, the memory consumption consists of memory that the InfoSphere Optim Performance Manager process consumes and of memory that DB2 processes consume. For more information about capacity planning, see the Capacity Planning for InfoSphere Optim Performance Manager document.

Operating Systems
Operating System Attributes Applicable Component Notes
Solaris Platform listing of supported OS
Solaris 10 SPARC and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server
Hardware platform: SPARC
InfoSphere Optim Performance Manager server

Required patches: 111711-12, 111712-12.
If raw devices are used, also requires 125100-07.

Software Requirements
Group Product Applicable Component Notes
Databases DB2 Enterprise Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

DB2 Enterprise Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

DB2 Enterprise Server Edition 9.7.0.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

Java Technology IBM Runtime Environment, Java Technology Edition 6.0.9.1 InfoSphere Optim Performance Manager server
Web Browsers Microsoft Internet Explorer 9.0 All Applicable Components

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Mozilla Firefox 4.0 All Applicable Components

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

Optional Supported Software
Group Product Applicable Component Notes
Monitored Databases DB2 Advanced Enterprise Server Edition 9.7 and future fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
DB2 Enterprise Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

For Extended Insight, DB2 Version 9.1, Fix Pack 6 is required to get information about data server time.

DB2 Enterprise Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

If you monitor a DB2 9.5 database on Linux on xSeries and if you have the DB2 Administrative Task Scheduler enabled on this database, ensure that one of the following APARS is installed:

  • DB2 APAR IC77911 on the monitored DB2 instance
  • APAR PK99986 on Optim Performance Manager
DB2 Enterprise Server Edition 9.7 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
DB2 Workgroup Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

For Extended Insight, DB2 Version 9.1, Fix Pack 6 is required to get information about data server time.

DB2 Workgroup Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

If you monitor a DB2 9.5 database on Linux on xSeries and if you have the DB2 Administrative Task Scheduler enabled on this database, ensure that one of the following APARS is installed:

  • DB2 APAR IC77911 on the monitored DB2 instance
  • APAR PK99986 on Optim Performance Manager
DB2 Workgroup Server Edition 9.7 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
Problem Determination Tools Optim Query Tuner for DB2 for Linux, UNIX and Windows 3.1 and future fix packs InfoSphere Optim Performance Manager server
Optim Query Tuner for DB2 for Linux, UNIX and Windows 2.2.0.2 and future fix packs InfoSphere Optim Performance Manager server


Hardware Requirements
Group Applicable Component Notes
Disk Space DB2 Performance Expert client

Temporary space for running the installation program:

  • Windows 32-bit and 64-bit: 150 MB
DB2 Performance Expert client

Permanent space in the installation directory for the program files and log files:

  • Windows 32-bit: 290 MB
  • Windows 64-bit: 390 MB
InfoSphere Optim Performance Manager server

3,000 MB of permanent space for the program files and log files.

The additional disk space for the collected data of the monitored databases depends on the type of information that is collected for history data and Performance Warehouse.

For more information about capacity planning, see the Capacity planning for InfoSphere Optim Performance Manager document.

InfoSphere Optim Performance Manager server

1,500 MB of temporary space for running the installation program
 

Memory DB2 Performance Expert client

512 MB free RAM

InfoSphere Optim Performance Manager server

3.5 GB free RAM

The minimum memory requirements that are needed to run InfoSphere Optim Performance Manager when monitoring a small number of non-partitioned databases.

The total amount of memory consumption depends on:

  • The number of monitored DB2 databases
  • The number of partitions on your monitored DB2 databases
  • The number of DB2 objects on your monitored DB2 databases
  • The number of monitoring functions that are activated in InfoSphere Optim Performance Manager

In general, the memory consumption consists of memory that the InfoSphere Optim Performance Manager process consumes and of memory that DB2 processes consume. For more information about capacity planning, see the Capacity Planning for InfoSphere Optim Performance Manager document.

Operating Systems
Operating System Attributes Applicable Component Notes
Windows Platform listing of supported OS
Windows 7 Professional x86-32 Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows 7 Professional x86-64 Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows 7 Ultimate x86-32 Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows 7 Ultimate x86-64 Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2003 R2 Datacenter Edition x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Server 2003 R2 Datacenter Edition x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2003 R2 Enterprise Edition x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Server 2003 R2 Enterprise Edition x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2003 R2 Standard Edition x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Server 2003 R2 Standard Edition x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2003 SP1 Datacenter Edition x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Server 2003 SP1 Datacenter Edition x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2003 SP1 Enterprise Edition x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Server 2003 SP1 Enterprise Edition x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2003 SP1 Standard Edition x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Server 2003 SP1 Standard Edition x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2008 Datacenter Edition x86-32 Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Server 2008 Datacenter Edition x86-64 Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2008 Enterprise Edition x86-32 Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Server 2008 Enterprise Edition x86-64 Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2008 R2 Datacenter Edition x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2008 R2 Enterprise Edition x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2008 R2 Standard Edition x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Server 2008 Standard Edition x86-32 Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Server 2008 Standard Edition x86-64 Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Vista Business x86-32 Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Vista Business x86-64 Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Vista Enterprise with FDCC x86-32 Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client
Windows Vista Enterprise x86-32 Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Vista Enterprise x86-64 Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows Vista Ultimate x86-32 Bitness: 32 Bit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-32
All Applicable Components
Windows Vista Ultimate x86-64 Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows XP Professional with FDCC x86-32 Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client
Windows XP SP2 Professional x86-64 and future OS fix packs Bitness: 64 Bit Exploit
Deployment Role: Server, Agent/End-point
Hardware platform: x86-64
All Applicable Components
Windows XP SP3 Professional x86-32 and future OS fix packs Bitness: 32 Bit
Deployment Role: Agent/End-point
Hardware platform: x86-32
DB2 Performance Expert client
Software Requirements
Group Product Applicable Component Notes
Databases DB2 Enterprise Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

DB2 Enterprise Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

DB2 Enterprise Server Edition 9.7.0.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Repository database.
The DB2 instance may not run in Oracle compatibility mode.

Java Technology IBM Runtime Environment, Java Technology Edition 6.0.9.1 InfoSphere Optim Performance Manager server
Web Browsers Microsoft Internet Explorer 7.0 All Applicable Components

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Microsoft Internet Explorer 8.0 All Applicable Components

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Microsoft Internet Explorer 9.0 All Applicable Components

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Mozilla Firefox 3.6 All Applicable Components

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

Mozilla Firefox 4.0 All Applicable Components

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

Optional Supported Software
Group Product Applicable Component Notes
JDBC Drivers IBM Data Server Runtime Client 9.5 and future fix packs DB2 Performance Expert client
IBM Data Server Runtime Client 9.7 and future fix packs DB2 Performance Expert client
DB2 Connect Application Server Edition 9.7 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Enterprise Edition 9.1 and future releases, mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Enterprise Edition 9.5 and future fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Enterprise Edition 9.7 and future fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Personal Edition 9.1 and future releases, mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Personal Edition 9.5 and future fix packs (overview) (support) DB2 Performance Expert client
DB2 Connect Personal Edition 9.7 and future fix packs (overview) (support) DB2 Performance Expert client
DB2 Run-time Client 9.1 FP 2 DB2 Performance Expert client
Monitored Databases DB2 Advanced Enterprise Server Edition 9.7 and future fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
DB2 Enterprise Server Edition 9.1 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Enterprise Server Edition 9.5 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Enterprise Server Edition 9.7 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Enterprise Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

For Extended Insight, DB2 Version 9.1, Fix Pack 6 is required to get information about data server time.

DB2 Enterprise Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

If you monitor a DB2 9.5 database on Linux on xSeries and if you have the DB2 Administrative Task Scheduler enabled on this database, ensure that one of the following APARS is installed:

  • DB2 APAR IC77911 on the monitored DB2 instance
  • APAR PK99986 on Optim Performance Manager
DB2 Enterprise Server Edition 9.7 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
DB2 Personal Edition 9.1 and future fix packs DB2 Performance Expert client
DB2 Personal Edition 9.5 and future fix packs DB2 Performance Expert client
DB2 Personal Edition 9.7 and future fix packs DB2 Performance Expert client
DB2 Workgroup Server Edition 9.1 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Workgroup Server Edition 9.5 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Workgroup Server Edition 9.7 and future mod levels and fix packs (overview) (support) DB2 Performance Expert client
DB2 Workgroup Server Edition 9.1 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

For Extended Insight, DB2 Version 9.1, Fix Pack 6 is required to get information about data server time.

DB2 Workgroup Server Edition 9.5 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

If you monitor a DB2 9.5 database on Linux on xSeries and if you have the DB2 Administrative Task Scheduler enabled on this database, ensure that one of the following APARS is installed:

  • DB2 APAR IC77911 on the monitored DB2 instance
  • APAR PK99986 on Optim Performance Manager
DB2 Workgroup Server Edition 9.7 and future mod levels and fix packs (overview) (support) InfoSphere Optim Performance Manager server

Important:

  • If you upgrade from DB2 Version 9.7 to a later version, you must run the db2updv97 tool for all DB2 V9.7 databases to update the DB2 catalogs. Otherwise, you cannot work with extended insight monitoring data.

Restrictions:

  • Only if you have DB2 Version 9.7, you will be alerted for lock wait events and lock wait timeout events.
  • For Extended Insight, DB2 Version 9.7 Fix Pack 1 or later is required to get layers for time that is spent in locking, sort, logging, queue time, and so on. DB2 V9.7 below Fix Pack 1 will only provide one layer that indicates DB2 data server time.
Problem Determination Tools Optim Query Tuner for DB2 for Linux, UNIX and Windows 3.1 and future fix packs InfoSphere Optim Performance Manager server
Optim Query Tuner for DB2 for Linux, UNIX and Windows 2.2.0.2 and future fix packs InfoSphere Optim Performance Manager server
Virtualization VMware ESXi 3.5 and future fix packs All Applicable Components

Notes

  • Note #1:

    Red Hat Enterprise Linux (RHEL) v5.0-5.5

  • Note #2:

    Red Hat Enterprise Linux (RHEL) v6.0-6.1

Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere Optim Performance Manager

Software version:

5.1

Operating system(s):

AIX, Linux, Solaris, Windows

Software edition:

Content Manager, Enterprise, Extended, Workgroup

Reference #:

7023046

Modified date:

2012-10-11

Translate my page

Machine Translation

Content navigation