Orphan rows in the PROCESS_INFORMATION table accumulate regularly. All of our user are using Arcmap direct connections. ArcSDE is only used to do geodatabase operations so typically there is no ArcSDE running. If I query the number of rows in PROCESS_INFORMATION I get a count that�??s much higher than is realistic. I�??ve noticed by experience that the command: sdemon �??o info �??I users �??i instance_name causes orphan rows to be cleaned out of PROCESS_INFORMATION so after I run it, I see an instant decrease in the number of rows and then I have a number that equals the number of database connections. Most, if not all, of The rows that get cleaned out are from abnormally terminated sessions due to i.e. power outage, network goes offline for a minute or two and freezes the session, the desktop freezes on a failed operation or just seems to freeze on a long operation and the user terminates their software session .... the things that happen in every company.
Is there a fix or workaround that stops this constant accumulation of orphan connections?
Our db is Oracle 11.2.0.3 Our SDE DB version is 9.3.1 sp2 with GUP patch
The only information on this issue is this post: http://forums.esri.com/thread.asp?c=158&f=2284&t=300145 The responder doesn't acknowlege acknowledge that the software leaves orphans of dead sessions but assumes that all the sessions are valid live connections.
