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

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.

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

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.

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

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

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

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

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

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

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

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

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

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.

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

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

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.

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.

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

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

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.

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

• Linux on xSeries 32-bit and 64-bit: 390 MB

Temporary space for running the installation program:

•     Linux on xSeries 32-bit: 260 MB
•     Linux on xSeries 64-bit: 500 MB

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.

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

512 MB free RAM

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.

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

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

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

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

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.

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

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

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.

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

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

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.

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.

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

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.

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

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

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

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

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

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.

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

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

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.

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

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

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.

Temporary space for running the installation program:

• Windows 32-bit and 64-bit: 150 MB

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

• Windows 32-bit: 290 MB
• Windows 64-bit: 390 MB

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.

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

512 MB free RAM

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.

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

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

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

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Requires Adobe Flash Player 10.0 or higher.

Recommended screen resolution: 1280x1024

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

Requires Adobe Flash Player 10.1.53.64 or higher.

Recommended screen resolution: 1280x1024

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.

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

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

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.

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

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

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.