Hello,

We are running java applications which uses DB2 as the data store.
But sometimes we get the following exception:

2004-04-25 22:51:39,478 FATAL [VBJ ThreadPool Worker]
LogService.logFatal(LogSer
vice (?:?) - JavaException: Error 11070 Collaboration exception at
step 3 in VBJ
ThreadPool Workerjava.lang.Object@692a4004CxCom...t@6954c004.mai
n:, Error 11070 Java exception
encountered:COM.ibm.db2.jdbc.DB2Exception: [IBM][
CLI Driver][DB2/6000] SQL0964C The transaction log for the database
is full. S
QLSTATE=57011

at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_S QLException(SQLExce
ptionGenerator.java(Compiled Code))
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_S QLException(SQLExce
ptionGenerator.java(Inlined Compiled Code))
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_r eturn_code(SQLExcep
tionGenerator.java(Compiled Code))

It seems that the problem is caused by some uncommitted transactions.
For DB2, how to find out which SQL command is not committed? Thanks a
lot.

The problem is not in an uncommitted transaction by itself; it is in a transaction that updates a lot of rows before committing.

You would need to take a series of application snapshots while your suspect transactions are running. At your database server issue:

db2 attact to <node name>
db2 update monitor switches using statement on uow on table on

and then few times:

db2 get snapshot for applications on <your db name>

Look at the number of rows inserted/updated/written and at the uow log usage. This should give you an idea.