I am unable to kill two sessions that iimonitor marks them as:

cs_state: CS_COMPUTABLE cs_mask: CS_DEAD_MASK,CS_IRPENDING_MASK

I have tried:

- Kill them with ipm. After it, ipm informed that session was removed,
but it was not. Still appeared in the session list.

- Kill the process (in the remote machine) that created them. In this
case a JDBC server. No change.

- Kill them with iimonitor. No result. I also tried the
suspend,remove,resume trick with no results.

I suspect that they perhaps are comsuming quite CPU in a indefinite
loop or something as the system is quiet but CPU is unusually high.

(iimonitor shows that the query is "open ~Q cursor for INGSTMT0 for
readonly using ~V , ~V , ~V , ~V , ~V , ~V")

Any ideas?

Thanks in advance


Carlos

Have you try to use lartool command to abort the transaction?

i... (AT) mixmail (DOT) com wrote:

Hi again,

Sorry for replying so late. About the way of removing these kind of
sessions, we had some replies saying that the only way is to recycle
the instalation or stop-start server through iimonitor. It has been
confirmed by CA support.

Fortunatelly, for this case, we finally found what it seems the root
cause of the problem. The issue was related with the statistics of one
table. This table has an index with a field that was not part of the
key. With optimizedb -zk this field was used. A very simple query and
in a concrete where case (no records for the concrete value of the
field) issued with isql or jdbc freezed and the program that launched
it as well. The db session got trapped and there was no way of removing
it. A copy of the same db, without statistics showed no problem with
the same query and data.

We have rebuilt and reloaded the table and made this field part of the
key (it was reasonable) and now there are no problem with the same
query and statistics.

Thanks to all the replies

Carlos

Thai ha escrito: