IBM Support

5.1.1 Limitations and known issues for Tivoli Storage Productivity Center

Preventive Service Planning


Abstract

This list provides information about limitations and known issues that you might encounter when you use IBM® Tivoli® Storage Productivity Center 5.1.1. The number in parentheses at the end of the title of each issue is the IBM support reference number for that issue.

Content

This document is a list of the known issues for Tivoli Storage Productivity Center 5.1.1.

To access all of the support documentation, including alerts and APARs for previous releases, go to the IBM Support Portal.

For the list of known issues for Tivoli Storage Productivity Center 5.1, see http://www-01.ibm.com/support/docview.wss?uid=swg21576205.

For information about the devices that are supported by Tivoli Storage Productivity Center 5.1.1, see the support matrix at https://www.ibm.com/support/docview.wss?uid=swg21386446.

IMPORTANT INFORMATION

When you add an LDAP repository to Tivoli Storage Productivity Center Version 5.1, the following restriction applies:

The WebSphere® Application Server cannot resolve duplicated users or groups if these users or groups are present in more than one repository in the federated repositories framework. For example, an Administrator user exists in both the local OS and LDAP repository. You must ensure that the duplicated users (or groups) are not used during the configuration or to manage Tivoli Storage Productivity Center.

Installation images on AIX®

When you extract installation images, use the GNU tar program instead of the AIX tar program. The AIX tar program might truncate long file names, which can cause installation errors in Tivoli Storage Productivity Center and Tivoli Integrated Portal.

Go to http://www.ibm.com/systems/power/software/aix/linux/toolbox/alpha.html and install GNU 1.14 or later. You must specify this program as the default tar program in the PATH environment variable.

Obtaining a license key to install Tivoli Storage Productivity Center 5.1.1 from the installation media

The media provided for Tivoli Storage Productivity Center 5.1.1 does not include a
license key.  Follow these instructions to obtain a license key to install this version of the product.

New installation:

You will need the license key directory from the Tivoli Storage Productivity Center
Version 5.1.0 GA release.

Copy the following directory from the Tivoli Storage Productivity Center Version 5.1.0 GA
disk1 DVD or electronic image into the Tivoli Storage Productivity Center Version 5.1.1 disk 1 source installation directory:

<root_directory>/license/key/  (copy the entire key directory)

Use the modified source installation directory to perform the installation.

Upgrade from a previous version:

Follow the instructions in the installation guide. No additional action is needed.

For Tivoli Storage Productivity Center version Version 5.1.0, your license will be automatically transferred to the new version. 

For Tivoli Storage Productivity Center Version 4, your license will be migrated as explained in the information center section titled "Product licenses for Tivoli Storage Productivity
Center".

Adding an installation license using the installation wizard:

You can either follow the steps in the "New Installation" section above to copy the
license key directory from the Version 5.1.0 GA media prior to starting the "License upgrade" installation of Version 5.1.1, or you can let the installer ask where to find the license key file. It is recommended that you follow the steps in the "New Installation" section to copy the license key directory into the Version 5.1.1 source installation directory.

If you do not copy the license key directory into the Version 5.1.1 source installation
directory, you will encounter a known issue that requires you to enter the path to
the license key file twice. Follow these steps to work around this issue:

After selecting the installation language, on the "Select a License Key" panel you
must enter the path to the license key file.  Enter the path to <v5.1.0_GA_disk1>/license
/key/nodelock* where nodelock* is the name of your license file.  Click Next.

After you accept the license agreement, on the "Choose Installation Location and Type"
panel, the installation program detects that you are installing the same
version of Tivoli Storage Productivity Center Version 5.1.1 and automatically selects "License upgrade" as the installation type.  Click Next.

On the "Upgrade the License" panel, select the option to "Specify the
location of the license key file" and enter the path to the <v5.1.0_GA_disk1> license/
key/nodelock* file again.

Click Next and then click Install.

If you encounter installation issues, use the following steps to resolve the problems.

Tivoli Storage Productivity Center 5.1.1 has no license if the default nodelock file location is not used (62896)

When installing Version 5.1.1, if you specify a location other than the default location for the nodelock file (for example, <installimage>\license\key), there is no license for Tivoli Storage Productivity Center.

To update the product with a license, complete the following steps:

1. Open the silent_SingleServerTypical.properties file.
2. Edit the following values:

  • LICENSE_ACCEPTED=true
  • CHOSEN_INSTALL_TYPE="License Upgrade"
  • varUseLicenseKeyOnImage=1
  • varLicenseKeyFile=<location of nodelock file>
3. Navigate to the root directory of the installation image.
4. Run the setup (bat/bin) -i silent -f <FullPath>\silent_SingleServerTypical.properties command.
5. Review the lax*out.txt file to verify the status of the update.

You can track the status and resolution of this problem by checking APAR IC89068.

Migrating Tivoli Storage Productivity Center from Version 5.1 to Version 5.1.1 fails if Version 5.1 uses a customized DB schema (60990)

If you installed Tivoli Storage Productivity Center Version 5.1 with a custom DB2 schema, when you upgrade to Version 5.1.1 or later, the upgrade will fail. (The standard DB2 schema is called TPC.)

The following DB2 SQL exception is displayed:

DB2 SQL Error: SQLCODE=-454, SQLSTATE=42723, SQLERRMC=TPC.EPOCH_TO_TS.

To resolve this issue, contact IBM software support to get the script file that must be executed before you migrate to Version 5.1.1 or later. You can track the status and resolution of this problem by checking APAR IC88366.

Hover text for data points in charts do not display correctly (39134)

The web-based GUI provides a number of charts that show information about monitored resources. You can view these charts on the details page for a specific resource. For example, to view charts for a storage system, go to the Storage Resources > Storage Systems page, right-click a storage system, and select View Details.

Charts that show information about historical storage usage contain data points. You can hover the mouse pointer over these data points to view additional information about storage usage at a point in time. On some charts, the hover text does not display correctly or the data point appears to flicker on and off.

To correct the problem, move the mouse pointer away from the data point and then return it.

Progress bar does not display correct percentage when uninstalling Tivoli Storage Productivity Center (39939)

When you uninstall Tivoli Storage Productivity Center, the progress bar for each feature or component jumps from 50 percent to 100 percent.

PDF files do not export correctly in languages and locations with non-Latin 1 code pages (40194)

In Tivoli Storage Productivity Center web-based and stand-alone GUIs, PDF files do not export correctly in languages and locations where non-Latin 1 code pages are used. When you try to export the file, the non-Latin 1 characters are stripped from the output.

The affected languages are:
  • Japanese
  • Chinese (Simplified)
  • Chinese (Traditional)
  • Korean
  • Polish
  • Czech
  • Hungarian
  • Russian

When you export to CSV and HTML, the correct output is generated in all languages and locations.

You must use Tivoli Common Reporting to generate reports and export these reports as PDF files. For more information about exporting reports as PDF files, see Export Data in PDF Format.

Description column in the Jobs log file does not display in browser language (41802)

In the web-based GUI, the text in the Description column for the jobs log file is displayed in the language specified by the Tivoli Storage Productivity Center server, regardless of the language that is specified in the browser.

IBM Scale Out Network Attached Storage error when using the Cloud API (44473)

When using the Cloud API to create a delivery unit with a numeric-only name, IBM Scale Out Network Attached Storage (IBM SONAS) error EFSSG0002C occurs.

To avoid this issue, do not use numeric-only delivery unit names.

Note: This issue only applies to versions of IBM SONAS before Version 1.4.

Information message in jobs log require no action (44672)

On the panel to view job logs, some informational messages do not have a valid link to messages help. When you click on the message link, you may see a help page that states:

The topic that you have requested is not available. The link may be wrong, or you may not have the corresponding product feature installed. This online help only includes documentation for features that are installed.

This problem occurs on all platforms, and is an information message that requires no further action.

Cluster data for a Storwize device is not available in Tivoli Storage Productivity Center after a Tier 3 or 4 recovery procedure (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 GUI. 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.

Inconsistent display of disks with multipath aliases (57863)

When a multipath disk is added to Tivoli Storage Productivity Center, the asset report displays a parent node using one alias, for example, /dev/sdb.  All partitions of that device display correctly as children nodes (for example, /dev/sdb1, /dev/sdb2, and so on), except the last partition, which uses another multipath alias device name such as /dev/sde3.

Untranslated drop-down lists in Data Path Views (58351)

In the globalized versions of Tivoli Storage Productivity Center 5.1.1, some elements in drop-down lists for the data path layout algorithm in Data Path Views are not translated from English.

Cannot install or upgrade the Russian or Czech versions of Tivoli Storage Productivity Center (58532)

Installing or upgrading the Russian or Czech versions of Tivoli Storage Productivity Center 5.1.1 fails because of DB2 Version 9.7 Fix Pack 6 compatibility problems. These problems will be resolved in a future fix pack of DB2. You can track the status and resolution of this problem by checking DB2 APAR IC87668.

Data is not collected for hypervisors in VMware vCenter despite a successful probe status (58794)

In VMware vCenter, when a hypervisor displays an alarm, the isOverallStatusRed(mHypervisor variable returns true. The probe status is successful, but data was not collected.

To avoid this issue, you must accept the alarm in VMware vCenter.

IBM® Tivoli® Common Reporting cannot find virtual machines on a hypervisor (58864)

On a hypervisor, if an ESX administrator removes the hard disks from a virtual machine, by clicking Remove on the Hardware tab, Tivoli Common Reporting cannot display information that the virtual machine was created on this hypervisor because the probe cannot collect information about the .vmdk file.

To avoid this issue, do not remove the virtual machine that you plan to use in a report.

TPCInstallProgress.log file does not update to 100% after a successful silent mode installation (58929)

After you successfully install Tivoli Storage Productivity Center in a multiple-server environment by using the silent mode, the TPCInstallProgress.log file continues to display 99.55%, rather than updating to 100%.

However, the installation is complete, and you can ignore this message in the log file.

Known issues for IBM SONAS (59528)

The following is a list of known issues in IBM SONAS:
  • The mkfs command causes IBM Storwize® V7000 to fail
    If you use the Tivoli Storage Productivity Center command-line interface (CLI) to
    issue the mkfs command on an Storwize V7000 storage system, the command
    might fail with one of the following errors:
    • EFSSG0962C
      If you issue the mkfs command and specify a value for the number of
      inodes that exceeds the number of available inodes, the following output is
      returned:
      EFSSG0962C
      The specified number of inodes 256M:100M exceeds the amount of available inodes.
    • EFSSG0486C
      If you issue the mkfs command and specify a value for the -pool option, the command might fail with the following message:

      EFSSG0486C One or more disks found in pool system that are not tagged for
      file system masvrdisk6.
    • EFSSG0962C
      If the mkfs command failed with error EFSSG0962C, issue the command
      again specifying a lower number of inodes and use the -noverify option.
    • EFSSG0486C

    • If the mkfs command failed with error EFSSG0486C, to create file systems
      issue the command again specifying either the -disks option or the -discoverdisks option.
  • The runprepop command causes IBM SONAS to fail
    If you use the Tivoli Storage Productivity Center command-line interface (CLI) or
    the IBM SONAS Version R1.3.0.0-74j CLI to issue the runprepop command, the
    command fails. For example, if you issue the Tivoli Storage Productivity Center
    runprepop command, IBM SONAS fails with error HWNEP0193E and returns the
    following output:

    HWNEP0193E The run prepop command failed because the following command
    executed on the NAS device failed with the return code 8:
    cli runprepop gpfs0 ma53550cache ma53550polcy -c tpcsonas3.storage.tucson.
    ibm.com returned: EFSSG0630C PANACHE : Error occurred in prepop task
    Execution of command cli_chkpolicy failed on the host 9.11.92.144 output
    till failure is ERRORREFSSP0008c CLI parser: No valid cluster has been
    specified.
  • The lsprepop command reports mmafmctl failed
    When you issue the Tivoli Storage Productivity Center lsprepop command, the
    command fails and an error message is displayed that states that the GPFS™
    mmafmctl command failed. The lsprepop command fails if the IBM SONAS cache
    source directory is empty.

    If you use the Tivoli Storage Productivity Center command-line interface (CLI) or the IBM SONAS CLI Version R1.3.0 or earlier to issue the runprepop command against an empty cache source directory, and you later issue the lsprepop command, IBM SONAS might return an error. For example, if you issue the lsprepop command, fails and IBM SONAS returns the following output:

    mmafmctl - Performing prefetching of fileset -mumfsetcacheB.
    Error is mmafmctl- Failed to stat /ibm/gpfs0/mumfsetcacheB/.afm/.afmctl

    Avoid issuing the runprepop command on an empty cache source directory.

The mkwcache command does not fail when an invalid value is specified for the number of inodes (60119)

If you use the Tivoli Storage Productivity Center command-line interface (CLI) to
issue the mkwcache command and specify an invalid value for the number of
inodes, IBM SONAS does not return an error message. For example, the following
mkwcache command does not return an error message:

tpctool> mkwcache -name mumfsetcacheE -path ’/ibm/gpfs0/mumtsetcacheE’
-filesystem gpfs0+tpcsonas3.storage.tucson.ibm.com+tpcsonas3a.storage.
tucson.ibm.com+0 -numInodes 1K:500M

The -numInodes parameter defines the inode limits for the file set created for the
WAN cache. The max_num_inodes variable specifies the maximum number of
inodes that can be allocated to the file set, 1,000 in the example. The
num_inodes_preallocate variable specifies the number of inodes that the system
immediately preallocates, 500,000,000 in the example. These values are not valid,
however, the command returns a status of success.

You must reissue the command and enter valid values for -numInodes. Specify values for -numInodes where the value for the max_num_inodes variable is greater than the value for the num_inodes_preallocate variable.

The following text is an example of this command:

tpctool> mkwcache -name mumfsetcacheE -path ’/ibm/gpfs0/mumtsetcacheE’
-filesystem gpfs0+tpcsonas3.storage.tucson.ibm.com+tpcsonas3a.storage.
tucson.ibm.com+0 -numInodes 200M:100M

The chwcache command fails to disable the expirationtimeout option (60120)

If you use the Tivoli Storage Productivity Center Command Line Interface (CLI)
chwcache command and specify the -expirationtimeout option with a value of -1,
the command fails and the expirationtimeout option cannot be disabled.

To disable the expiration timeout for an IBM SONAS cache, log in to the IBM
SONAS system. Issue the IBM SONAS CLI chwcache command and specify the
-expirationtimeout option with a value of -1.

Cannot reauthenticate to Tivoli Storage Productivity Center after the authentication token has expired (60140)

When you use Tivoli Storage Productivity Center that is installed on a Windows domain, and you are logged in as a local Administrator, if the authentication token expires, you are prompted to reenter your Tivoli Storage Productivity Center credentials.

To resolve this issue, complete one of the following steps:
  • Change the user password and log in as domain\Administrator.
  • Stop and restart the stand-alone GUI.

Known issues with Tivoli Common Reporting when using DB2 9.5
  • Multiple columns added to the same report causes an error (61115)
    If the Storage Virtualizer Volume Grain Size, Storage Virtualizer Volume Warning Level, and Storage Virtualizer Volume Physical Allocation Percentage columns are added to the same custom report, due to a DB2 Version 9.5 limitation, an SQL error UDA-SQL-0144 is displayed.
  • Storage System - Most Active Volume report fails in a DB2 9.5 environment (61131)


  • Error UDA-SQL-0353 appears for the following reasons:
    • In the Storage Systems - Most Active Volumes report, the name field is incorrectly spelled as volume utilization in the IBM® DS6000® storage system and IBM® DS8000® storage system queries, but this field is correctly spelled in the IBM® XIV Storage System and BSP queries.
      This mismatch creates an error.
    • The order of the fields in the DS6000 and the DS8000 storage systems daily query is incorrect.
  • No information about the Run Storage Server System Credential Migration Tool is provided during an upgrade (62098)
    When you upgrade from TPC Version 4.1.1 to Version 5.1.1, if you select the Run Storage Server System Credential Migration Tool checkbox, no additional about this tool is displayed.

These issues will be resolved with a Tivoli Storage Productivity Center Fix Pack. You can track the status and resolution of this problem by checking DB2 APAR IC89070.

Upgrading to Tivoli Storage Productivity Center Version 5.1.1 fails when installing Tivoli Common Reporting Version 2.1.1.0 Fix Pack 6 (62124)

When installing or upgrading to Tivoli Storage Productivity Center Version 5.1.1, if the installation of Tivoli Common Reporting Version 2.1.1.0 Fix Pack 6 fails, the Tivoli Storage Productivity Center installation or upgrade will fail.

To resolve this issue, complete the steps in one the following scenarios:
  • Resume the Tivoli Storage Productivity Center Version 5.1.1 installation after rolling back Tivoli Integrated Portal, if you are not reusing an existing Tivoli Integrated Portal.
  • Resume the upgrade after acknowledging the error, if you are upgrading Tivoli Storage Productivity Center 4 to Tivoli Storage Productivity Center Version 5.1.1.

To resolve this issue when you upgrade from Tivoli Storage Productivity Center Version 5.1 to Version 5.1.1, contact IBM software support.

When upgrading to Tivoli Storage Productivity Center Version 5.1.1, an error message appears in the Upgrade Complete window (62379)

After you upgrade to Tivoli Storage Productivity Center Version 5.1.1, the following error message is displayed in the Upgrade Complete window:

Errors occurred during the upgrade of Tivoli Storage Productivity Center.
See the installation log “C\Program files\IBM\TPC\logs\msgTPCInstall.log” for details.

The log file shows that all components have installed successfully. You must review the ShutdownServersAction renameJREFolder Fail to rename JRE folder? file and search for the BPCIN0153E key. The installation program could not rename the JRE folder.

To resolve this issue, complete the following steps in a Windows command window:
  1. Navigate to the C:\Program files\IBM\TPC\jre directory.
  2. Enter the following command: rmdir /s/q include java15 java16 _uninst.
  3. Enter the following command: del JVMCount *tmp.

Names column in the Jobs window is empty (62407)

In the web-based GUI, if the USER_PROVIDED_NAME variable for a storage subsystem is an empty string, then the Name column in Jobs window appears empty. You cannot determine which log belongs to which storage subsystem unless you open the log file.

To avoid this issue, set the Label in the Storage Subsystem detail panel.
    Upgrading Tivoli Storage Productivity Center could fail if Tivoli Storage Productivity Center for Replication is running (62733)

    If your Tivoli Storage Productivity Center upgrade fails, it could be because Tivoli Storage Productivity Center for Replication is running. To resolve this issue, stop Tivoli Storage Productivity Center for Replication and try to upgrade Tivoli Storage Productivity Center again.

    SQL error UDA-SQL-0353 is displayed due to a DB2 Version 9.5 limitation (62802)

    If the Storage Virtualizer Volume Grain Size, Storage Virtualizer Volume Warning Level, and Storage Virtualizer Volume Physical Allocation Percentage columns are added to the same custom report, due to a DB2 Version 9.5 limitation, SQL error UDA-SQL-0144 is displayed. You can track the status and resolution of this problem by checking DB2 APAR IC89070.

    This limitation will be resolved with a Tivoli Storage Productivity Center Fix Pack.

    "Changing the HOSTS file" information center topic updated

    The Changing the HOSTS file topic has been updated in the information center to provide a more clear example of how to add entries to the HOSTS file on a system managed by Tivoli Storage Productivity Center. The same topic in the IBM Tivoli Storage Productivity Center Version 5.1.1 Installation and Configuration Guide will be updated in a Tivoli Storage Productivity Center Fix Pack.

    Installation wizard does not allow host names that begin with a numeric character (70564)

    When you install Tivoli Storage Productivity Center using the installation wizard, entering a server host name that begins with a numeric character will cause error message BPCIN0009E to display and the installation will fail. To resolve this, specify a server host name that does not begin with a numeric character.

    Starting the DB2 Control Center on the AIX operating system (70565)

    In DB2® 9.5, to start the DB2 Control Center on the AIX operating system, run the db2cc command in a command window.

    Installation hangs during Tivoli Integrated Portal installation if a reference to IBM Java Version 7 is found in the Windows path statement (70709)

    If you have references to IBM Java Version 7 in your Windows path statement, the Tivoli Storage Productivity Center installer will hang while installing Tivoli Integrated Portal. IBM Java 7 is not supported by Tivoli Storage Productivity Center Version 5.1.

    To work around this:

    1. Uninstall Tivoli Storage Productivity Center using the instructions in this information center topic:

    Uninstalling Tivoli Storage Productivity Center

    2. Temporarily remove the reference to IBM Java Version 7 from your Windows path statement.

    3. Run the Tivoli Storage Productivity Center installation program again.

    4. Add the IBM Java Version 7 reference back to your Window path statement.

    5. Restart your Tivoli Storage Productivity Center server.

    Always run the setenv command before running the srmcp command (72382)

    The setenv command must be run before you run the srmcp command. Several information center and User's Guide topics do not include the instructions for running the setenv command before running the srmcp command.

    To run the setenv command:

    On the Windows operating system:

    1. Go to the following directory: C:\Program Files\IBM\TPC\device\bin\w32-ix86.
    2. Run this command: setenv.
    3. Run the srmcp command from the same location.

    On the AIX or Linux operating systems:

    1. Go to one of the following default directories:
    • On the AIX operating system:

    • /opt/IBM/TPC/device/bin/aix
    • On the Linux operating system:

    • /opt/IBM/TPC/device/bin/linux

    2. Run this command: ./setenv.sh.

    3. Run the srmcp command from the same location.

    Antivirus software can prevent Tivoli Storage Productivity Center from installing (72544)

    Some antivirus software can interfere with the Tivoli Storage Productivity Center installation process. To avoid this, disable all antivirus software on the target system and restart before you install Tivoli Storage Productivity Center.

    For more information, see this IBM Software Support technote: http://www-01.ibm.com/support/docview.wss?uid=swg21633867.

    You can track the status and resolution of this problem by checking APAR IC91365.

    Information center specifies an incorrect location for the stand-alone GUI logs (72692)

    The information center topic Default log file locations specifies an incorrect location for the stand-alone GUI log files.

    The correct location is:
    • Windows operating systems:

    • TPC_installation_directory\data\log
    • UNIX or Linux operating systems:

    • TPC_installation_directory/data/log

    You can track the status and resolution of this problem by checking APAR IC90097.

    Updated command for changing the DB2 password on the Data server (72706)

    The command to change the DB2 password on the Data server has changed. TSRMsrv.zip has been replaced by TPC_Common.jar.

    These are the updated commands:

    On the Windows operating system:

    C:\Program Files\IBM\TPC\data\config>\"program files"\ibm \tpc\jre\bin\java -classpath "\program files\ibm\tpc\data\server\lib\TPC_Common.jar" com.tivoli.itsrm.repository.Transform -p <new_password> repository.config

    On AIX/Linux operating systems:

    /opt/IBM/TPC/jre/bin/java -classpath "/opt/IBM/TPC/data/server/lib/TPC_Common.jar" com.tivoli.itsrm.repository.Transform -p <new_password> repository.config

    This change affects the information center topic Changing the DB2 password for the Data server, which is on page 216 in the IBM Tivoli Storage Productivity Center 5.1.1 User's Guide.

    You can track the status and resolution of this problem by checking APAR IC91133.

    Incorrect reference to Limited Edition in information center and IBM Tivoli Storage Productivity Center 5.1.1 User's Guide (72708)

    The Product overview topic on page 11 of the IBM Tivoli Storage Productivity Center 5.1.1 User's Guide and information center incorrectly references Tivoli Storage Productivity Center Limited Edition. This version of the product is no longer available.

    Logging in to the Tivoli Storage Productivity Center stand-alone GUI by using a Windows domain account (76078)

    To log in to the Tivoli Storage Productivity Center Version 5.1.1 stand-alone GUI by using a Windows domain account, complete the following steps:

    1. Verify that your Windows domain user ID belongs to a Windows domain group (for example, Domain Administrator or Domain Users) by completing the following steps:
      1. Log in to the Windows domain controller computer and click Start > Active Directory users and computers > Domain DNS > Users.
      2. Right-click the Windows domain user ID and select Properties.
      3. On the Member of tab, if the Windows domain group is not listed, click Add.
      4. Add the Windows domain group and click OK.

    2. Assign roles to the Windows domain group by completing the following steps:
      1. Log in to the Tivoli Storage Productivity Center stand-alone GUI by using a local administrator user ID (for example, Administrator).
      2. Click Administrative services > Configuration > Role-To-Group mappings.
      3. On the role (for example, Productivity Center administrator or Tivoli Storage Productivity Center tape operator) that you want to assign, enter the Windows domain group (for example, Domain Administrator or Domain Users).

    Restriction: Do not enter the domain_name (for example, TPC\) in front of the Windows domain group name.

    Information center topic incorrectly lists embedded TPC as a valid license type (86534)

    In the IBM Tivoli Storage Productivity Center Installation and Configuration Guide, the Adding an installation license topic states that an embedded version of Tivoli Storage Productivity Center is available as part of IBM® Systems Director. This is not correct for Tivoli Storage Productivity Center Versions 5.1 and later.

    Unable to log on to the stand-alone GUI by using a Windows domain user name (APAR IC92438)

    If a Windows domain user name belongs to a local group that is mapped to a Tivoli Storage Productivity Center role, you cannot use this user name to log in to Tivoli Storage Productivity Center. To log in to Tivoli Storage Productivity Center, the domain user name must belong to a domain group that is mapped to a Tivoli Storage Productivity Center role.

    Specifying locations for saving IBM Cognos reports to your local file system (APAR IC92488)

    You can configure reports to save the report output to your local file system. For instructions, see the attached doc_corrections.pdf file.

    You can track the status and resolution of this problem by checking APAR IC92488.

    Update to the "Cleaning up a failed installation or uninstallation on Windows" information center topic (APAR IC92840)

    Step 2 in the information center topic incorrectly specifies how to remove the Common Agent.

    The correct text for step 2 is:

    2. Remove the Storage Resource agent entries from the Windows registry by using
    the instructions in the following information center topic:

    Deleting Storage Resource agent registry entries after a failed installation or uninstallation.

    Unable to add a NAS filer if the Storage Resource Agent service that runs under the Administrator user ID is not used to add a NAS filer (APAR IC92894)

    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:
    1. Expand Administrative Services > Configuration > Manual NAS Server Entry.
    2. Click Add NAS Server.
    3. On the Add NAS Server window, enter the Administrator user ID in the Login ID field.

    The back up and restore procedures fail to recover from an authentication change (APAR IC93534)

    You cannot log in to Tivoli Integrated 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:

    TIP_installation_directory\profiles\TIPProfile\installedApps\TIPCell\isc.ear

    If you completed a default installation on the Windows operating system, the isc.ear directory is located here:

    C:\ProgramFiles\IBM\tipv2\profiles\TIPProfile\installedApps\TIPCell\isc.ear\

    On AIX or Linux operating systems:

    TIP_installation_directory/profiles/TIPProfile/installedApps/TIPCell/isc.ear

    If you completed a default installation on the AIX or Linux operating systems, the isc.ear directory is located here:

    C:/ProgramFiles/IBM/tipv2/profiles/TIPProfile/installedApps/TIPCell/isc.ear\

    Update to process for changing the authentication method from local OS to LDAP (APAR IC96172)

    In the information center topic Changing the authentication method from local operating system to LDAP federated repositories, step 15 requires an additional verification when you restart the Tivoli Storage Productivity Center-related servers after you change the authentication method. This update applies to Tivoli Storage Productivity Center Version 4.2.x and Version 5.1.x.

    This additional verification involves logging in to the Tivoli Integration Portal server to verify that it is fully functional before you start the other Tivoli Storage Productivity Center services.

    For more information about this documentation update, see technote IC96172: Update to process for changing authentication method from local OS to LDAP.

    For more information about this APAR, see APAR IC96172.

    Starting and stopping Tivoli Storage Productivity Center for Replication from a command line (APAR IC98593)

    When you start or stop Tivoli Storage Productivity Center for Replication from a command line, use the following parameter. This parameter is case sensitive:

    replicationServer

    This replaces the previous parameter, which is no longer valid:
    ReplicationServer

    On Windows, the command to start the Replication server is now:
    WAS_HOME/profiles/ReplicationServerProfile/bin/startServer.bat
    replicationServer

    On AIX and Linux, the command to start the Replication server is now:
    WAS_HOME/profiles/ReplicationServerProfile/bin/ startServer.sh –
    username user_name –password password replicationServer

    For more information about this APAR, see APAR IC98593.

    Stop all jobs and reboot servers before upgrading Tivoli Storage Productivity Center
    (APAR IC99222)

    Follow these steps before upgrading Tivoli Storage Productivity Center:

    1. Stop all jobs including performance monitor jobs, system and fabric probe jobs, scan jobs, and other probe jobs.

    2. If possible, reboot the Tivoli Storage Productivity Center servers. This action will stop any remaining Tivoli Storage Productivity Center Java processes that might not stop in a timely manner. If a reboot is not possible, stop and restart the Tivoli Storage Productivity Center server service. It is important for the Tivoli Storage Productivity Center Device server to stop and restart cleanly. If this does not occur, a server reboot might be indicated.

    To track the status and resolution of this APAR, see APAR IC99222.

    Error SRV0853E is displayed when you try to log in to the stand-alone GUI

    In some cases, when you try to log in to the stand-alone GUI, you get a SRV0853E error message. You see an error similar to the following error in the Data Server log file (<TPC_installation_directory>\data\log\ServerTrace.log):

    2016-10-18 13:14:23.931+0200 EXCEPTION
      java.lang.reflect.UndeclaredThrowableException
    at com.sun.proxy.$Proxy5.authenticate(Unknown Source)
    at com.tivoli.itsrm.server.SingleSignonHndlr.authenticateUserOrToken(SingleSignonHndlr.java:409)
    at com.tivoli.itsrm.server.SingleSignonHndlr.handle(SingleSignonHndlr.java:141)
    at com.tivoli.itsrm.server.RequestManager$RmThread.run(RequestManager.java:501)
    Caused by: [SOAPException: faultCode=SOAP-ENV:Server; msg=java.lang.IllegalArgumentException: Illegal daylight saving value: 0]
    at org.apache.soap.providers.RPCJavaProvider.invoke(Unknown Source)
    at com.tivoli.sanmgmt.middleware.data.RPCSecureJavaProvider.invoke(RPCSecureJavaProvider.java:172)
    at org.apache.soap.server.http.RPCRouterServlet.doPost(Unknown Source)
    at com.tivoli.sanmgmt.middleware.TSNMServiceManager.doPost(TSNMServiceManager.java:469)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1275)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:766)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:472)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1101)
    at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:81)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:912)
    at com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVirtualHost.java:262)
    at com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$TaskWrapper.run(HttpDispatcherLink.java:938)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
    at java.lang.Thread.run(Thread.java:798)  com.tivoli.itsrm.server.RequestManager$RmThread run RequestHandler0

    This error occurs because the Java Runtime Environment (JRE) does not comply with Daylight Saving Time (DST). To fix this problem, do one of the following actions:

    Incorrect configuration instructions for Storwize V7000 Unified (APAR IT08072)
    For Storwize V7000 Unified, the instructions in the topic "Configure storage subsystem connections page" are incorrect in the following documentation:

    IBM Tivoli Storage Productivity Center Knowledge Center V5.1.1
    http://www-01.ibm.com/support/knowledgecenter/SSNE44_5.1.1/com.ibm.tpc_V511.doc/fqz0_r_storagesystems_connections.html?cp=SSNE44_5.1.1%2F0-8-5-0-0&lang=en

    IBM Tivoli Storage Productivity Center User's Guide V5.1.1, pages 313 and 315-317:
    To view, go to http://www-01.ibm.com/support/knowledgecenter/SSNE44_5.1.1/com.ibm.tpc_V511.doc/fqz0_r_printable_pdf_files.html and click the link for the IBM Tivoli Storage Productivity Center User's Guide.

    The correct instructions are in the following PDF. Ignore passages of strikethrough text.
    IT08072.pdfIT08072.pdf

    To track the status and resolution of this APAR, see APAR IT08072.


    References to PowerHA® should be PowerHA® System Mirror for AIX

    References to PowerHA in the Tivoli Storage Productivity Center documentation should specify PowerHA System Mirror for AIX. Other PowerHA versions are not supported by Tivoli Storage Productivity Center.

    [{"Product":{"code":"SS5R93","label":"IBM Spectrum Control"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"5.1.1","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}}]

    Document Information

    Modified date:
    22 February 2022

    UID

    swg21609438