2012/05/24 17:11:58.415 Purge GLS4_TOK_REC_REP - Purge Thread - Table : 'GLS4_TOK_REC_REP_Trends' : error in purge loop. com.sybase.jdbc3.jdbc.SybSQLException: Arithmetic overflow occurred.
2012/05/24 17:11:58.416 Purge GLS4_TOK_REC_REP - Purge Thread - Closing connection
2012/05/24 17:11:58.417 Purge GLS4_TOK_REC_REP - Purge Thread : error in loop. java.sql.SQLException: JZ0C0: Connection is already closed.
java.sql.SQLException: JZ0C0: Connection is already closed.
at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source)
at com.sybase.jdbc3.jdbc.SybConnection.checkConnection(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.checkDead(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.checkStatement(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.executeUpdate(Unknown Source)
at com.sybase.jdbc3.jdbc.SybStatement.executeUpdate(Unknown Source)
at asemon_logger.PurgeThread.run(PurgeThread.java:69)
2012/05/24 17:11:58.418 Purge GLS4_TOK_REC_REP - Purge Thread - Closing connection
Anonymous
Can you execute the query :
select TrendID, count(*) from GLS4_TOK_REC_REP_Trends group by TrendID order by TrendID
and send me the result. this will help me diagnose on which trend is the problem
(20 rows affected)
New version of RSTrends.xml
Can you use the new RSTrends.xml file, attached to this
(Replace the old RSTrends.xml file in conf dir and restart asemon_logger)