Direct links to fixes
Tivoli Storage Productivity Center 5.2.7 (select fixes from group)
IBM Spectrum Control V5.2.8 (December 2015)
IBM Spectrum Control V5.2.9 (February 2016)
IBM Spectrum Control V5.2.10 (May 2016)
IBM Spectrum Control V5.2.10.1 (July 2016)
IBM Spectrum Control V5.2.11 (August 2016)
IBM Spectrum Control V5.2.12 (November 2016)
IBM Spectrum Control V5.2.13 (March 2017)
IBM Spectrum Control V5.2.14 (May 2017)
IBM Spectrum Control V5.2.15 (August 2017)
IBM Spectrum Control V5.2.15.2 (November 2017)
IBM Spectrum Control V5.2.16 (March 2018)
IBM Spectrum Control V5.2.17 (May 2018)
APAR status
Closed as program error.
Error description
Tivoli Storage Productivity Center 5.2.x users monitoring large environments may encounter DB2 transaction log full errors if small values for the DB2 parameters LOGFILSIZ, LOGPRIMARY, LOGSECOND, LOGBUFSZ are used, particularly when performance monitors are scheduled to run every minute. The problem can surface in Tivoli Storage Productivity Center in a variety of ways. It may be a failed upgrade, a failed action (e.g. deleting a storage system), a failed probe, or a variety of other issues. Investigation into the Tivoli Storage Productivity Center and DB2 logs provides confirmation of this condition. The Tivoli Storage Productivity Center logs will display the SQL errors: SQLCODE=-964, SQLSTATE=57011 The db2diag log file will show: "Log File has reached its saturation point" DIA8309C Log file was full.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * TPC 5.2.0 through 5.2.6 users monitoring large environments * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION. * **************************************************************** * RECOMMENDATION: * * Apply fix maintenance when available or set these DB * * parameters as specified on your current TPC 5.2.x * * installation. * ****************************************************************
Problem conclusion
Users experiencing this should upgrade to Tivoli Storage Productivity Center 5.2.7 or higher or modify the values for the following DB2 parameters: LOGFILSIZ, LOGPRIMARY, LOGSECOND, LOGBUFSZ Steps to check and modify the DB2 parameters: 1. Open a DB2 command window: 2. Run the following command to verify that the current values of the mentioned DB2 parameters are lower than the ones indicated at step 3. db2 get db cfg for tpcdb > tpcdb_cfg_current.txt 3. Open file tpcdb_cfg_current.txt and search for LOGFILSIZ, LOGPRIMARY, LOGSECOND, LOGBUFSZ 4. If they are smaller than 20000, 100, 150, 512 then run step 5. 5. Issue the following commands, one by one in this specific order, to increase the DB2 parameters: db2 update db cfg for tpcdb using LOGFILSIZ 5000 db2 update db cfg for tpcdb using LOGSECOND 240 db2 update db cfg for tpcdb using LOGPRIMARY 16 db2 update db cfg for tpcdb using LOGBUFSZ 512 The fix for this APAR is targeted for the following maintenance package: | refresh pack | 5.2-TIV-TPC-RP0007 - target August 2015 http://www-01.ibm.com/support/docview.wss?&uid=swg21320822 The target dates for future refresh packs do not represent a formal commitment by IBM. The dates are subject to change without notice. Note: You must ensure there is adequate disk or file system space before you modify the LOGFILSIZ, LOGPRIMARY, and LOGSECOND parameters. These values will result in approximately 5 GB of log file space. The values suggested here will be the default values with Tivoli Storage Productivity Center 5.2.7 If the DB2 transaction log full errors continue after increasing these parameters as suggested or upgrading to Tivoli Storage Productivity Center 5.2.7 or higher, contact IBM Support for further investigation.
Temporary fix
Comments
APAR Information
APAR number
IT09754
Reported component name
TPC
Reported component ID
5608TPC00
Reported release
525
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-29
Closed date
2015-06-29
Last modified date
2015-06-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
DB
Fix information
Fixed component name
TPC
Fixed component ID
5608TPC00
Applicable component levels
Document Information
Modified date:
05 October 2023