Flash (Alert)
Abstract
The Tivoli Storage Manager patch 6.1.2.1 is available and recommended for use by all customers.
Content
The Tivoli Storage Manager patch 6.1.2.1 is available and recommended for use by all customers. It is strongly recommended that all customers using 6.1.0.x, 6.1.1.x, or 6.1.2.0 apply this patch.
This flash also includes information about known issues not fixed in 6.1.2.1, and about sizing the active and archive logs.
Patch 6.1.2.1
The patch 6.1.2.1 delivers fixes that are considered to be either high impact or pervasive. High impact problems are those that, if encountered, result in a server crash or server hang, or that otherwise compromise server availability. Pervasive problems are those that many customers are encountering.
The table shows a partial list of the fixes that are included in 6.1.2.1. See the README that is included with the 6.1.2.1 patch for a complete list of the fixes.
| APAR | ABSTRACT |
| IC62978 | ARCHIVE LOGS GROW RAPIDLY AND CAN CAUSE THE SERVER TO KEEP CRASHING DUE TO THE DB2 REORG OPERATION RUNNING TOO FREQUENTLY. |
| IC63162 | TIVOLI STORAGE MANAGER 6.1 MAY CRASH DUE TO A SEGMENTATION FAULTWITH (MEMTREEDEMOTE__FPP8SMEMNODE). |
| IC63841 | MOVE DATA/NODEDATA COMMAND WITH RECONSTRUCT=NO CAN CAUSE DATA INTEGRITY ISSUES IN DEDUPLICATED STORAGEPOOLS. |
| IC62884 | TIVOLI STORAGE MANAGER V6.1 MIGRATION HANG |
| IC62304 | BACKUPS CAN FAIL IF DESTINATION DISK STORAGE POOL IS FULL OF CACHED DATA |
| IC63331 | PERFORMANCE WHEN READING DATA FROM DISK OR FILE POOLS IS ABNORMALLY LOW |
| IC64163 | TIVOLI STORAGE MANAGER 6.1 SERVER MAY GET INTO A HANG SITUATION |
All the fixes provided in the 6.1.2.1 patch will also be delivered in the 6.1.3.0 server fix-pack at a future date. Install and use the 6.1.2.1 patch until the 6.1.3.0 fix-pack becomes available.
Patch 6.1.2.1 Download Link
The patch is available at the FTP downloads site for Tivoli Storage Manager server:
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/server/
From this site, select the appropriate platform and then the 6.1.2.1 version subdirectory.
Known issues not fixed in 6.1.2.1
In addition to the fixes delivered in 6.1.2.1, there are a few known issues with workarounds described below:
| Symptom | Description | APAR | Circumvention |
| Server crash | The server might crash while performing offsite reclamation if the requested input volume is not available to be mounted. | IC63727 | Monitor server operations, especially MOVE DRMEDIA processing, to ensure that all volumes being processed are successfully moved and available when offsite reclamation is subsequently performed. |
| Hang | On some AIX and Solaris platforms where there are issues with the NIS configuration, the TSM server might experience what appear to be hangs because underlying system calls for authentication are taking many minutes to complete. | None | Using the same login ID as is used to run the server, issue the following while the server is halted: On AIX, set the following DB2 registry value: db2set DB2_ALTERNATE_GROUP_LOOKUP= GETGRSET On Solaris, set the following DB2 registry value: db2set FASTGROUPS=YES |
Important information about sizing the active and archive logs
Whether planning for deployment of a new server or evaluating the setup and configuration of an existing server, it is important to appropriately size the active and archive logs to minimize disruption and get the most out of TSM. Useful information can be found in the following flash on this topic:
http://www.ibm.com/support/docview.wss?uid=swg21389352
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
