CRJAZ0252I The JAZZ_DEADLOCKS deadlock monitor does not exist so no extra detail s are available.
Frank Ning (500●25●119●133)
| asked Apr 04 '13, 12:01 p.m.
retagged Apr 04 '13, 1:21 p.m. by Laura W. Hinson (161●2●6)
The server is on Linux RHEL 5.8 with DB2 9.7 FP6 and WAS 8.0.3.
In jts.log, I see the CRJAZ0252I message. What do I do to avoid it? Part of the jts.log: 2013-04-04 11:45:11,649 [ jts: AsynchronousTaskRunner-0] ERROR sqlExceptionLogger - CRJAZ1318I A database connection error occurred. Serialization failure CRJAZ0252I The JAZZ_DEADLOCKS deadlock monitor does not exist so no extra details are available. SQL: SELECT MAX("SCALAR_COUNTER_ID") FROM "RICALM"."SCALAR_COUNTER" SQL Exception #1 SQL Message: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=2, DRIVER=4.14.88 SQL State: 40001 Error Code: -911 com.ibm.db2.jcc.am.SqlTransactionRollbackException: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=2, DRIVER=4.14.88 at com.ibm.db2.jcc.am.ed.a(ed.java:664) 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:2713) at com.ibm.db2.jcc.t4.ab.p(ab.java:853) at com.ibm.db2.jcc.t4.ab.h(ab.java:144) at com.ibm.db2.jcc.t4.ab.b(ab.java:41) at com.ibm.db2.jcc.t4.p.a(p.java:32) at com.ibm.db2.jcc.t4.qb.i(qb.java:135) at com.ibm.db2.jcc.am.oo.ib(oo.java:2103) at com.ibm.db2.jcc.am.po.tc(po.java:3613) at com.ibm.db2.jcc.am.po.b(po.java:4403) at com.ibm.db2.jcc.am.po.gc(po.java:750) at com.ibm.db2.jcc.am.po.executeQuery(po.java:719) at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.PreparedStatementStatWrapper.executeQuery(PreparedStatementStatWrapper.java:60) at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.PreparedStatementErrLogWrapper.executeQuery(PreparedStatementErrLogWrapper.java:78) at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.PreparedStatementLeakWrapper.executeQuery(PreparedStatementLeakWrapper.java:57) at com.ibm.team.datawarehouse.service.repository.internal.etlbuild.ScalarCounter.insertRecord(ScalarCounter.java:136) at com.ibm.team.datawarehouse.service.repository.internal.etlbuild.ScalarCounter.execute(ScalarCounter.java:87) at com.ibm.team.datawarehouse.service.repository.internal.LicenseRemoteSnapshotService.updateSnapshot(LicenseRemoteSnapshotService.java:80) at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService$1.run(AbstractRemoteSnapshotService.java:200) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$5.run(RemoteDatabaseService.java:254) at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:381) at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:244) at sun.reflect.GeneratedMethodAccessor1885.invoke(Unknown Source) 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 $Proxy2645.write(Unknown Source) at com.ibm.team.datawarehouse.service.internal.RemoteDataWarehouseProvider.write(RemoteDataWarehouseProvider.java:29) at sun.reflect.GeneratedMethodAccessor1884.invoke(Unknown Source) 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 $Proxy4420.write(Unknown Source) at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService.updateData(AbstractRemoteSnapshotService.java:195) at sun.reflect.GeneratedMethodAccessor1702.invoke(Unknown Source) 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 $Proxy2919.updateData(Unknown Source) at com.ibm.team.datawarehouse.service.AbstractSnapshotTask.run(AbstractSnapshotTask.java:88) at com.ibm.team.datawarehouse.service.AbstractExclusiveTask.runTask(AbstractExclusiveTask.java:38) at com.ibm.team.repository.service.async.AbstractAutoScheduledTask.executeTask(AbstractAutoScheduledTask.java:88) at sun.reflect.GeneratedMethodAccessor1267.invoke(Unknown Source) 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 $Proxy2920.executeTask(Unknown Source) at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.runTask(AsynchronousTaskRunner.java:153) at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:116) at java.lang.Thread.run(Thread.java:769) |
One answer
Hello Frank,
It seems that the data required by CLM application cannot be retrieved due to the lock. One of possible causes of this situation is that you are performing any maintanance tasks on your database. Could you check if there are running already such tasks. You can also use any gui tool to see what application is locking "RICALM"."SCALAR_COUNTER" table. |
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.