 |
Support & downloads > |
 |
 |
 |
History configuration setup failure in Summarization and Pruning agent
|
| | This document applies only to the following language version(s): UK English, US English | | | | Problem(Abstract) | An error similar to the following appears in the *sy_java* logs:
Error SQL State = 42622 , SQL Error Code = -107
EXCEPTION: Failed to setup history config in sy_java logs.
No summarisation and prunning at scheduled time. | | | | | | Cause | | The S&P agent is configured incorrectly. | | | | | Environment | | ITM 6.2 and DB2 version 9.1 FP 1 or FP3 and higher. | | | | | Diagnosing the problem | Check the current schedule at which the Summarization and Pruning agent is scheduled to run.
Make sure that the S&P Agent is started at that scheduled time, and check the following logs 30 minutes after scheduled time has passed: <hostname>_sy_java_nnnnnnnnnn-xx.log where "nnnnnnnnnn" is a hexadecimal timestamp, and "xx" is a sequential number (01, 02, . . . ). These logs can be found in CANDLE_HOME/logs for both Windows and Unix operating systems. Check these logs for the presence of errors like this: == 145 t=Thread-1 SQL IN ERROR :
statement name : .Alt1 SQL : ALTER TABLE "ITMUSER"."KPX_SYSTEM_IO" ADD
"Logical_Blk_Buffer_Cache_Reads_per_Sec" INTEGER
template SQL :
== 146 t=Thread-1 SQLException occured. SQL State = 42622 , SQL Error
Code = -107 == 147 t=Thread-1 com.ibm.db2.jcc.b.SqlException: DB2 SQL error:
SQLCODE: -107, SQLSTATE: 42622, SQLERRMC:
Logical_Blk_Buffer_Cache_Reads_per_Sec;30
== 148 t=Thread-1 EXCEPTION: Failed to setup history config
== 149 t=Thread-1 EXCEPTION: Failed to get parameters
== 150 t=Thread-1 Summarization and pruning agent ended with errors Note that the table "KPX_SYSTEM_IO", the attribute "Logical_Blk_Buffer_Cache_Reads_per_Sec", and the statement numbers (145 to 150) can be different. But the SQL state and error codes, number 30, and exceptions at the end should match. | | | | | Resolving the problem | | 1) According to the Link:
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.msg.doc/doc/r0sttmsg.htm error Code 42622 occurs when the name label is too long.
2)There is one DB2 APAR :http://www-01.ibm.com/support/docview.wss?uid=swg1IY89812.
According to this APAR the fix for this error is included in almost all Fix Packs 1 to 6a (latest)
ITM 6.2 supports FP1 or FP3 and higher.
Therefore check whether DB2 v9.1 has been upgraded properly or not.
3)Lastly check whether S&P points to a correct, updated version of the jdbc driver .jar or .zip files.
If not, reconfigure the S&P agent to use the correct jdbc files. | | | | | | | | |
 |
| 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. |
 |
 |
 |
| Please take a moment to complete this form to help us better serve you. |
 |
 |
 |
|
|
|
 |
 |
| Product categories: |
 |
| | Software |  |
| | Systems and Asset Management |  |
| | Application Performance & Availability |  |
| | IBM Tivoli Monitoring |  |
 |
| Operating system(s): |
| |
AIX, AIX 64bit, HP-UX, Linux, Linux Red Hat - iSeries, Linux Red Hat - pSeries, Linux SUSE - iSeries, Linux SUSE - pSeries, Solaris, Windows, Windows 2003 server
|
 |
| Software version: |
| |
6.2
|
 |
| Reference #: |
| |
1378192
|
 |
| IBM Group: |
| | Software Group |
 |
| Modified date: |
| | 2009-10-26 |
 |
|