Fixes are available
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
<TPC_HOME>\web\tpctrace.log will show the following error: SQLCODE=-119, SQLSTATE=42803, SQLERRMC=UNIQUE_ID: 2015-09-15 12:59:45.691+02:00 -6588401540043626902 com.ibm.tpc.internal.api.services.impl.ServerManagerServiceImpl getServers Entry Thread[WebContainer : 8,5,main] 2015-09-15 12:59:45.691+02:00 -6588401540043626902 com.ibm.tpc.internal.api.services.impl.ServerDetails getServers Entry Thread[WebContainer : 8,5,main] 2015-09-15 12:59:45.705+02:00 -6588401540043626902 com.ibm.tpc.internal.api.services.impl.ServerDetails getServers Exception in querying the database: DB2 SQL Error: SQLCODE=-119, SQLSTATE=42803, SQLERRMC=UNIQUE_ID, DRIVER=3.65.77 {prepstmnt 533127045 WITH DISK_TEMP AS ( SELECT COMPUTER_ID, SUM(CAPACITY) * 512 AS TOTAL_DISK_SPACE FROM (SELECT DISTINCT HOST.HOST_NAME AS NAME, HOST.COMPUTER_ID AS COMPUTER_ID, PHYSICAL_VOLUME.PHYSICAL_VOLUME_ID, CASE WHEN HIST.CAPACITY > 0 THEN HIST.CAPACITY ELSE CASE WHEN PHYSICAL_VOLUME.CAPACITY > 0 THEN PHYSICAL_VOLUME.CAPACITY ELSE 0 END END AS CAPACITY FROM T_RES_HOST AS HOST INNER JOIN T_RES_SHARE AS DISK_SHARE ON DISK_SHARE.COMPUTER_ID = HOST.COMPUTER_ID AND DISK_SHARE.RESOURCE_TYPE = 10 AND YEAR(DISK_SHARE.REMOVED_TIME) <= 1970 INNER JOIN T_RES_PHYSICAL_VOLUME AS PHYSICAL_VOLUME ON DISK_SHARE.RESOURCE_ID = PHYSICAL_VOLUME.PHYSICAL_VOLUME_ID INNER JOIN T_STAT_DISK_HIST HIST ON HIST.STATISTIC_TYPE = '3' AND
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * TPC 5.2.x users who manage Servers and Hypervisors. * **************************************************************** * PROBLEM DESCRIPTION: * * TPC Web logs displays * * IM11: Servers L2 panel shows -> "An internal error has * * occurred: {0}." is displayed caused by * * <openjpa-2.2.1-r422266:1396819 fatal general error> * * org.apache.openjpa.persistence.PersistenceException: DB2 SQL * * Error: SQLCODE=-119, SQLSTATE=42803, SQLERRMC=UNIQUE_ID * * * * The issue happens only for TPC installed with Db2 10.1 FP 5 * * and a DB2 PMR was opened * **************************************************************** * RECOMMENDATION: * * Apply fix maintenance when available. * ****************************************************************
Problem conclusion
TPC code changed in order to get over the DB2 issue. The fix for this APAR is targeted for the following maintenance package: | refresh pack | 5.2-TIV-TPC-RP0008 - target December 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.
Temporary fix
Comments
APAR Information
APAR number
IT11433
Reported component name
TPC
Reported component ID
5608TPC00
Reported release
523
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-09-28
Closed date
2015-10-26
Last modified date
2015-10-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
WEBUI
Fix information
Fixed component name
TPC
Fixed component ID
5608TPC00
Applicable component levels
R523 PSY
UP
R524 PSY
UP
R525 PSY
UP
R526 PSY
UP
R527 PSY
UP
R520 PSY
UP
Document Information
Modified date:
22 February 2022