CA Spectrum reports not loading in CABI Jaspersoft screen

Products

• CA Spectrum
• CA eHealth

Issue/Introduction

CABI reports are not working due to current data not present in the reporting database. In the OneClick log file the
  following MySql Error is seen and event collection stops.

uncategorized SQLException for SQL [DELETE FROM security_string_accessibility_by_landscape]; SQL state [HY000]; error code [14]; Can't change size of file (Errcode: 22 - Invalid argument [OS Error Code : 0x4c8]); nested exception is java.sql.SQLException: Can't change size of file (Errcode: 22 - Invalid argument [OS Error Code : 0x4c8])

Environment

Release : 10.3.x

Component : CA BUSINESS INTELLIGENCE

Cause

The problem seems to be a possible resource issue with mysql.

Feb 13, 2020 08:36:07.708 (SRM/SecurityHandler/bucketReader) (com.aprisma.spectrum.app.repmgr.dc.event.handler.SecurityHandler) - (ERROR) - Error occurred while processing Security event bucket
Caused by: org.springframework.jdbc.UncategorizedSQLException: StatementCallback; uncategorized SQLException for SQL [DELETE FROM security_string_accessibility_by_landscape]; SQL state [HY000]; error code [14]; Can't change size of file (Errcode: 22 - Invalid argument [OS Error Code : 0x4c8]); nested exception is java.sql.SQLException: Can't change size of file (Errcode: 22 - Invalid argument [OS Error Code : 0x4c8])
 at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:84)
 at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81)
 at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81)
 at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:416)
 at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:549)
 at com.aprisma.spectrum.app.repmgr.dc.db.dao.jdbc.JdbcSecurityStringDAO.update_security_string_accessibility_by_landscape(JdbcSecurityStringDAO.java:235)
 at com.aprisma.spectrum.app.repmgr.dc.event.handler.SecurityEventReader.processBucketRecords(SecurityEventReader.java:229)
 at com.aprisma.spectrum.app.repmgr.dc.event.handler.AbstractBucketReader.readBucket(AbstractBucketReader.java:133)
 at com.aprisma.spectrum.app.repmgr.dc.event.handler.BucketReaderScheduler$ScheduledReader.run(BucketReaderScheduler.java:118)
 at com.aprisma.util.thread.JobQueue.runJobThread(JobQueue.java:221)
 at com.aprisma.util.thread.JobQueue.access$000(JobQueue.java:15)
 at com.aprisma.util.thread.JobQueue$JobRunnable.run(JobQueue.java:24)
 at java.lang.Thread.run(Thread.java:748)
Caused by: java.sql.SQLException: Can't change size of file (Errcode: 22 - Invalid argument [OS Error Code : 0x4c8])
 at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1075)
 at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3562)
 at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3494)
 at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1960)
 at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2114)
 at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2690)
 at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1648)
 at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1567)
 at org.apache.commons.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:225)
 at org.springframework.jdbc.core.JdbcTemplate$1UpdateStatementCallback.doInStatement(JdbcTemplate.java:538)
 at org.springframework.jdbc.core.JdbcTemplate$1UpdateStatementCallback.doInStatement(JdbcTemplate.java:535)
 at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:405)
 ... 9 more

Feb 13, 2020 08:36:07.710 (SRM/SecurityHandler/bucketReader) (com.aprisma.spectrum.app.repmgr.dc.event.handler.SecurityHandler) - (ERROR) - Critical failure with events; processing halted for all servers.
  Handler Name: SecurityHandler

Resolution

In this instance stopping OneClick, stopping processd (which in turn stops MySql) and restarting
  corrected the problem and SRM was again able to process events normally

Additional Information

More information would be needed about this error should it occur again in the future. This specific
  error has not been encountered before in Spectrum and might be tied to specific activities on the
  machine.