Limitations and known issues for Tivoli Storage Productivity Center and Tivoli Storage Productivity Center for Replication for Version 4.2.2

This section lists known issues when using Tivoli Storage Productivity Center and Tivoli Storage Productivity Center for Replication. Also check the following website for other Tivoli Storage Productivity Center and Tivoli Storage Productivity Center for Replication issues:

http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Productivity_Center_Standard_Edition

*** Note: Changes to this flash since initially published are indicated by asterisks (***).

Important notice

Before you install Tivoli Storage Productivity Center, read the information about issue IC79141.

Fixed APARs

This is a list of APARs that were fixed in Version 4.2.2:

IC77528
IC77601
IC77791
IC77793
IC77871
IC78208
IC78254
IC78319
IC78424
IC78896

For a complete list of APARs that were fixed in the Version 4.2 fix packs, see https://www-304.ibm.com/support/docview.wss?&uid=swg21454276.

Known issues for Tivoli Storage Productivity Center

This is a list of known issues that have not been fixed.

*** Disk space requirements

In the Tivoli Storage Productivity Center information center, these updates have been made to the Hardware requirements topic:

Disk space for AIX and Linux:

• For installations on AIX, 10 GB of free disk space is required.
• For installations on AIX or Linux, the following free disk space is required:
  • 2.25 GB for the /tmp directory
  • 3 GB for the /opt directory
  • 250 MB in the /home directory
  • 10 KB in the /etc directory
  • 1.4 GB in the /usr directory (for Tivoli Integrated Portal)

*** Memory requirements

This update has been made to the Hardware requirements topic in the Tivoli Storage Productivity Center information center:

For memory, if you are running in an environment with less than 8 GB of RAM, do not install Tivoli Common Reporting on the Tivoli Storage Productivity Center server. You can install Tivoli Common Reporting on a separate server.

IC78320

The Tivoli Storage Productivity Center for Replication installation fails while installing the WebSphere Application Server when Japanese is chosen as the language.

IC78428

When monitoring NetApp NAS and other NAS devices for the same probe job, the probe causes the Data server to consume excessive memory.

IC78484

Users with the Disk Operator role should not be able to stop the performance monitoring job.

IC78494

This condition causes Tivoli Storage Productivity Center to fail: You try to create a performance monitor alert and have the Regional setting set to a language that has a comma (,) as the decimal separator instead of a period (.).

IC78617

Tivoli Storage Productivity Center is unable to create a zone when the Tivoli Provisioning Manger workflow calls the Tivoli Storage Productivity Center API.

IC78771

After applying the Chinese language pack, the Tivoli Storage Productivity Center GUI displays information in English if you start the Tivoli Storage Productivity Center GUI through Tivoli Integrated Portal. If you open the Tivoli Storage Productivity Center GUI directly through Java Web Start, the Chinese language is displayed correctly.

IC79141

When running a Data agent scan, the agent fails with the following error message:

10/6/11 1:28:57 PM GEN0323E: Failed to read data from host xxx.xxx.xxx.
10/6/11 1:28:57 PM GEN0008E: Cannot read from host <xxx.xxx.xxx>
java.io.InvalidClassException: com.tivoli.itsrm.TStorm.common.STimeDist; incompatible types for field tdAverageAge

*** IC80420

See doc_corrections_v422.pdf below.

*** IC80608

See doc_corrections_v422.pdf below.

53413

The Consumed volume space/Available Volume Space are wrong for some XIV volumes assigned to hosts in the following reports:

Disk Manager>Reporting>Storage subsystem>Computer Views>by Computer - relate Computers to SS
Disk Manager>Reporting>Storage subsystem>Computer Views>by Computer - relate Computers to Volumes
Disk Manager>Reporting>Storage subsystem>Computer Views>by Computer Group - relate Computers to SS
Disk Manager>Reporting>Storage subsystem>Computer Views>by Computer Group - relate Computers to Volumes
Disk Manager>Reporting>Storage subsystem>SS Views>by SS - relate SS to Computers
Disk Manager>Reporting>Storage subsystem>SS Views>by SS Groups - relate SS to Computers
Disk Manager>Reporting>Storage subsystem>SS Views>by Volumes - relate Volumes to Computers

54478

The New detected filesystem alert is not displayed on the Filesystem page. The filesystem is green but there is no alert.

54823

There are corrupted strings in the Tivoli Storage Productivity Center dashboard for the Russian and Polish locales. The corrupted strings appear in the User Consuming the Most Space window in the dashboard when the user ID is in the Russian or Polish language.

No workaround is available, if possible, define the user IDs in English.

54833

In the Subsystem Alerts page, the Computer column contains the subsystem name. This is a known issue. The Computer column should contain the name of the computer that triggered the alert, or to a volume or disk that is assigned from the subsystem which triggered the alert.

55222

After you download the installation images, run the checksum utility to verify that the installation images have not been corrupted. For information about the checksum utility, see https://www.ibm.com/support/docview.wss?uid=swg21515288.

55231

The SAN Planner with Replication using Metro Global Mirror displays error message HWNLM0744E when only two subsystems are provided as input.

Workaround:
The Metro Global Mirror session requires at least three supported subsystems to be specified for the SAN Planner. If only one or two supported subsystems are provided to the SAN Planner, this error message is displayed.

55322

The Storage Optimizer analysis does not take the performance monitor values provided into the Analysis - Performance Time Interval.

Workaround:
Enter a value of minutes plus 1 for generating a Storage Optimizer analysis for the performance monitor report samples.

55378

The SAN Planner fails to create VDisks if the VDisk name prefix specified is greater than 64 characters.
The SAN Planner informs you that the name specified is too long and prompts you to provide a new name prefix. However, if the name provided is already in use, the SAN Planner uses the original name provided, which is greater than 64 characters. The VDisk is not created.

Workaround:
Provide a name prefix that is less than 64 characters, or, when the SAN Planner prompts you for a new name prefix, cancel the request and enter a valid name prefix.

55424.NF

The SAN Planner job fails with an invalid job status. When a SAN Planner job is running and executes the plan, the job might fail with the message: invalid job status. There is a timing issue with the job status checking. If you are in the Tivoli Storage Productivity Center GUI refreshing the job page, the job might fail to return a valid status, even if the job run is successful.

Workaround:
Do not refresh the job management page frequently when a job is running.

55474

When using Tivoli Storage Productivity Center with IBM Systems Director, the Tivoli Storage Productivity Center server crashes or looses communication with DB2.

***55958

See doc_corrections_v422.pdf below.

56741

After a Tier 3 or 4 recovery procedure is performed on an SVC or Storwize system (V7000, V7000U, V3700, etc.) that was previously probed by Tivoli Storage Productivity Center, the cluster data is no longer available in the Tivoli Storage Productivity Center UI. During these
recovery procedures, the storage system is given a new cluster ID. Tivoli Storage Productivity Center is not aware of the new cluster ID associated with this device and cannot locate and gather data from the storage system.

To resolve this issue, remove the affected storage system from Tivoli Storage Productivity Center and then add the device again. Run a discovery job and probe job to gather data on the storage system.

Known issues for Tivoli Storage Productivity Center for Replication

30666

When upgrading from Tivoli Storage Productivity Center for Replication 3.4.1.0 to 4.2.2, you might get the following error during the Tivoli Storage Productivity Center for Replication installation:

An error occurred and product update failed. Look at the log file TPCRMInstall.log for details.

Search the log for the message ADMC0016E: The system cannot create a SOAP connector to host localhost at port 41185.

If this is the error, the upgrade completed. This issue is automatically resolved at runtime.

doc_corrections_v422.pdf