It's all about the answers!

Ask a question

Data Warehouse Collection Jobs failure - Quality Management


Chaitra Elanjickal (31820) | asked Jul 02 '14, 10:02 a.m.

When we execute the datawarehouse collection job - Quality Management. It runs for about 7 mins and then fails with the below error.

2014-07-02 09:26:19,886 [WebContainer : 10 @@ 09:18  /qm/service/com.ibm.team.reports.common.internal.service.IReportRestService/updateSomeSnapshotData] ERROR sqlExceptionLogger                                  - CRJAZ1318I A database connection error occurred.
CRJAZ0265I The virtual storage or database resource is not available.
SQL: DELETE FROM RIODS.TESTSCRIPT WHERE EXTERNAL_KEY2 IN (SELECT EXTERNAL_KEY2 FROM RIODS.TESTSCRIPT GROUP BY EXTERNAL_KEY2 HAVING COUNT(TESTSCRIPT_ID) > 1)  AND TESTSCRIPT_ID NOT IN (SELECT MIN(TESTSCRIPT_ID) FROM RIODS.TESTSCRIPT WHERE EXTERNAL_KEY2 IN (SELECT EXTERNAL_KEY2 FROM RIODS.TESTSCRIPT GROUP BY EXTERNAL_KEY2 HAVING COUNT(TESTSCRIPT_ID) > 1) GROUP BY EXTERNAL_KEY2)
Parameter 0: DELETE FROM RIODS.TESTSCRIPT WHERE EXTERNAL_KEY2 IN (SELECT EXTERNAL_KEY2 FROM RIODS.TESTSCRIPT GROUP BY EXTERNAL_KEY2 HAVING COUNT(TESTSCRIPT_ID) > 1)  AND TESTSCRIPT_ID NOT IN (SELECT MIN(TESTSCRIPT_ID) FROM RIODS.TESTSCRIPT WHERE EXTERNAL_KEY2 IN (SELECT EXTERNAL_KEY2 FROM RIODS.TESTSCRIPT GROUP BY EXTERNAL_KEY2 HAVING COUNT(TESTSCRIPT_ID) > 1) GROUP BY EXTERNAL_KEY2)
SQL Exception #1
SQL Message: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=4.14.121
SQL State: 57011
Error Code: -964

com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-964, SQLSTATE=57011, SQLERRMC=null, DRIVER=4.14.121
 at com.ibm.db2.jcc.am.ed.a(ed.java:682)
 at com.ibm.db2.jcc.am.ed.a(ed.java:60)
 at com.ibm.db2.jcc.am.ed.a(ed.java:127)
 at com.ibm.db2.jcc.am.oo.c(oo.java:2715)
 at com.ibm.db2.jcc.am.oo.d(oo.java:2703)
 at com.ibm.db2.jcc.am.oo.b(oo.java:2070)
 at com.ibm.db2.jcc.t4.ab.i(ab.java:226)
 at com.ibm.db2.jcc.t4.ab.c(ab.java:48)
 at com.ibm.db2.jcc.t4.p.b(p.java:38)
 at com.ibm.db2.jcc.t4.qb.h(qb.java:114)
 at com.ibm.db2.jcc.am.oo.hb(oo.java:2065)
 at com.ibm.db2.jcc.am.oo.a(oo.java:3237)
 at com.ibm.db2.jcc.am.oo.c(oo.java:740)
 at com.ibm.db2.jcc.am.oo.executeUpdate(oo.java:723)
 at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.StatementStatWrapper.executeUpdate(StatementStatWrapper.java:225)
 at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.StatementErrLogWrapper.executeUpdate(StatementErrLogWrapper.java:240)
 at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.StatementLeakWrapper.executeUpdate(StatementLeakWrapper.java:95)
 at com.ibm.team.datawarehouse.service.rqmmigration4.internal.etlbuild.RQM4TestScriptCleanUpETL.cleanUpDuplicateTestScripts(RQM4TestScriptCleanUpETL.java:475)
 at com.ibm.team.datawarehouse.service.rqmmigration4.internal.etlbuild.RQM4TestScriptCleanUpETL.execute(RQM4TestScriptCleanUpETL.java:147)
 at com.ibm.team.datawarehouse.service.rqm.internal.RemoteRQMSnapshotService.cleanupDuplicateTestScripts(RemoteRQMSnapshotService.java:1461)
 at com.ibm.team.datawarehouse.service.rqm.internal.RemoteRQMSnapshotService.updateSnapshot(RemoteRQMSnapshotService.java:209)
 at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService$1.run(AbstractRemoteSnapshotService.java:199)
 at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$6.run(RemoteDatabaseService.java:523)
 at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:434)
 at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:485)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
 at java.lang.reflect.Method.invoke(Method.java:611)
 at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
 at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
 at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
 at $Proxy118.write(Unknown Source)
 at com.ibm.team.datawarehouse.service.internal.RemoteDataWarehouseProvider.write(RemoteDataWarehouseProvider.java:29)

2 answers



permanent link
Benjamin Silverman (4.1k610) | answered Jul 02 '14, 10:27 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
This message means that your DB2 transaction log has run out of space.  I'd suggest asking the DBA to increase the size of the log file on the data warehouse database as well as the number of logs using something like what you see below.

UPDATE DB CFG FOR <DBALIAS> USING LOGFILSIZ 2000
UPDATE DB CFG FOR <DBALIAS> USING LOGPRIMARY 50
UPDATE DB CFG FOR <DBALIAS> USING LOGSECOND 200

Hope it helps,

permanent link
Ara Masrof (3.2k15) | answered Jul 02 '14, 10:26 a.m.
JAZZ DEVELOPER
These error messages are most likely a result of running out of space in the transaction log. 

This link may be of help

http://www-01.ibm.com/support/docview.wss?uid=swg21472442

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.