G
George Potemkin
Guest
A session died 3 days ago after memory violation. It logged out from 3 of 4 databases it was connected to. Right now the process does not exist but one database still has a remote connection opened by the dead session. "Usrtodie" flag (a.k.a. _Connect-Disconnect) is on. Session had an active transaction in this database but transaction was rather small (5266 records were created). A remote client server is still doing approximately 30 db accesses per sec (_UserIO-DbAccess) on behalf of the dead session but the _UserTableStat/_UserIndexStat are not changing. promon/User Control reports dbkey: Type Wait Table Dbkey Trans REMC/ABL -- 29 3700543 17687823 Dbkey belongs to an index that was updated by transaction (though I don't know if exactly this dbkey was updated by transaction - aimage scan is not yet ready). Dbkey is not locked according to promon/Status: Buffer Lock Queue. I guess it's just a last dbkey the dead session was waiting for. How can I find what the remote client server is doing right now on behalf of the dead session? Note: it also serves to another 4 sessions. The customer needs to close the transaction. We can try to stop the server of the dead session but I'm not sure if the server will stop. We can kill the server but it might crash a database. Waiting for db restart is also a bad option. Suggestions?
Continue reading...
Continue reading...