Preventive Service Planning
This list provides information about limitations and known issues for Tivoli® Storage Productivity Center and Tivoli® Storage Productivity Center for Replication V4.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:
*** Note: Changes to this flash since initially published are indicated by asterisks (***).
Before you install Tivoli Storage Productivity Center, read the information about issue IC79141.
This is a list of APARs that were fixed in Version 4.2.2:
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.
The Tivoli Storage Productivity Center for Replication installation fails while installing the WebSphere Application Server when Japanese is chosen as the language.
When monitoring NetApp NAS and other NAS devices for the same probe job, the probe causes the Data server to consume excessive memory.
Users with the Disk Operator role should not be able to stop the performance monitoring job.
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 (.).
Tivoli Storage Productivity Center is unable to create a zone when the Tivoli Provisioning Manger workflow calls the Tivoli Storage Productivity Center API.
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.
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
See doc_corrections_v422.pdf below.
See doc_corrections_v422.pdf below.
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
The New detected filesystem alert is not displayed on the Filesystem page. The filesystem is green but there is no alert.
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.
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.
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.
The SAN Planner with Replication using Metro Global Mirror displays error message HWNLM0744E when only two subsystems are provided as input.
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.
The Storage Optimizer analysis does not take the performance monitor values provided into the Analysis - Performance Time Interval.
Enter a value of minutes plus 1 for generating a Storage Optimizer analysis for the performance monitor report samples.
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.
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.
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.
Do not refresh the job management page frequently when a job is running.
When using Tivoli Storage Productivity Center with IBM Systems Director, the Tivoli Storage Productivity Center server crashes or looses communication with DB2.
See doc_corrections_v422.pdf below.
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.
In Tivoli Storage Productivity Center Version 4.2.1 (or later), if you change your LDAP password, you may not be able to upgrade to Tivoli Storage Productivity Center Version 5.2 because your LDAP credentials cannot be validated.
To resolve this issue, see the doc_corrections_v422.pdf attachment.
If a Windows domain user account is used to install Tivoli® Storage Productivity Center, the user account might not have the DB2® SYSADM authority, because DB2 goes to the domain controller computer to list the groups. Before you install Tivoli Storage Productivity Center, you must grant the Windows domain user accounts the DB2 SYSADM authority.
To enter the commands, and grant DB2 SYSADM authority, complete the following steps:
- Click Start > Command Prompt.
- Right-click Command Prompt and select Run as administrator.
- Enter these commands:
db2set -g DB2_GRP_LOOKUP=local,TOKENLOCAL
db2 force application all
After you run the commands, you can log in to Tivoli Storage Productivity Center by using a user account that has DB2 SYSADM authority.
If you are logged in with your Windows domain user account, you might not have the authorization to run the db2 force application all command.
Important: When you grant DB2 SYSADM authority, and the db2 force application all command does not work, you can enter the db2stop command instead of the db2 force application all command.
When you add a NAS filer, you must enter the Administrator user ID for the Storage Resource agent service on which it runs.
To manually add a NAS filer, complete the following steps in the Tivoli Storage Productivity Center stand-alone GUI:
- Expand Administrative Services > Configuration > Manual NAS Server Entry.
- Click Add NAS Server.
- On the Add NAS Server window, enter the Administrator user ID in the Login ID field.
You cannot log in to Tivoli Intergrated Portal and Tivoli Storage Productivity Center after you modify the authentication and try to restore Tivoli Storage Productivity Center.
To resolve this situation, complete the following tasks:
- Before you change the user authentication configuration by adding or removing an LDAP repository in the federated repositories framework, back up the existing WebSphere Application Server configuration files.
- After you add an LDAP repository to the user authentication configuration and want to later change the LDAP authentication settings, back up the WebSphere configuration files.
- In the TIP_installation_directory, back up, and if necessary, restore the isc.ear file.
On Windows operating systems:
If you completed a default installation on the Windows operating system, the isc.ear directory is located here:
On AIX or Linux operating systems:
If you completed a default installation on the AIX or Linux operating systems, the isc.ear directory is located here:
Known issues for Tivoli Storage Productivity Center for Replication
When upgrading from Tivoli Storage Productivity Center for Replication 18.104.22.168 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.
|Storage Management||Tivoli Storage Productivity Center Basic Edition||Not Applicable||Windows, Solaris, AIX, HP-UX, Linux||4.2.2||All Editions|
|Storage Management||Tivoli Storage Productivity Center for Data||Not Applicable||AIX, HP-UX, Linux, Solaris, Windows, NetWare||4.2.2||All Editions|
|Storage Management||Tivoli Storage Productivity Center for Disk||Not Applicable||AIX, Linux, Windows, HP-UX, Solaris||4.2.2||All Editions|
|Storage Management||Tivoli Storage Productivity Center for Disk Select||Not Applicable||AIX, HP-UX, Linux, NetWare, Solaris, Windows||4.2.2||All Editions|
|Storage Management||Tivoli Storage Productivity Center for Replication||TPC for Replication||AIX, Linux, Windows, z/OS||4.2.2||All Editions|