Direct connects using tnsnames.ora are used from desktop and servers.
Construct an ALTER SYSTEM KILL SESSION (‘SID’,’SERIAL#’) dynamic sql statement from joining V$SESSION and V$PROCESS with SDE.PROCESS_INFORMATION. This is how we gather information, there is a next step of constructing and executing the ALTER SYSTEM that is not shown here.
WITH sp AS ( SELECT s.audsid, s.LOGON_TIME, s.MACHINE, s.MODULE, s.OSUSER, s.PROCESS, s.PROGRAM, s.SERIAL#, s.SID, s.TERMINAL, s.USERNAME, p.PID, p.PNAME, p.SPID FROM v$session s, v$process p WHERE s.paddr = p.addr AND s.TYPE != 'BACKGROUND' AND s.program IS NOT NULL AND s.username NOT IN ('SYS', 'SYSTEM', 'DBSNMP') ), pi AS ( SELECT p.audsid, p.sde_id, p.server_id, p.start_time, p.owner, p.nodename FROM sde.process_information p ) select sp.LOGON_TIME, sp.MACHINE, sp.MODULE, sp.OSUSER, sp.PROCESS, sp.PROGRAM, sp.SERIAL#, sp.SID, sp.TERMINAL, sp.USERNAME, sp.PID, sp.PNAME, sp.SPID, pi.owner, pi.server_id from pi, sp where pi.owner = sp.username and pi.server_id = SUBSTR (sp.process, 1, INSTR (sp.process, ':') - 1) and pi.audsid = sp.audsid order by sp.logon_time;
We periodically need to update data during our maintenance window requiring all connections to be disconnected. After all sessions were disconnected, the V$SESSION and V$PROCESS tables showed no connections for SDE. But SDE.PROCESS_INFORMATION had 196 rows, and SDE.TABLE_LOCKS had over 3000 rows.
We bounced the database, but SDE.PROCESS_INFORMATION and SDE.TABLE_LOCKS returned the same.
Ultimately from SQL we deleted all rows in SDE.PROCESS_INFORMATION and SDE.TABLE_LOCKS, and update work progressed. After the maintenance window, desktop ArcMap, ARCSOC sessions came in, everything seems to be working fine.
I believe that SDE.PROCESS_INFORMATION should always have an entry for an SDE connection. Right now if I pick a USERNAME/OWNER and compare V$SESSION has 9 rows, but there are 11 rows in SDE.PROCESS_INFORMATION. I’ve also seen cases where there are entries in SDE.PROCESS_INFORMATION that don’t exist in V$SESSION.
Prior to ArcGIS 10.5 sdemon was used to clear and rectify SDE process entries with Oracle sessions, even with direct connections. There isn’t an sdemon now, or a method (that I know of) to manage connections. There is something for locks, but not connections. This is why we resort to the brute force ALTER SYSTEM KILL SESSION method.
Something is not quite right, but I don’t know why. It’s hard to test because this is production.
Why do entries persist in SDE.PROCESS_INFORMATION?
Why do sessions show in V$SESSION that are not in SDE.PROCESS_INFORMATION?
It feels dangerous to manually monkey with SDE metadata tables. I see many posts about using the ALTER SYSTEM KILL method, so it seems widely accepted and recommended by ESRI.
At this point, things are working okay, but it’s uncomfortable not to have processes and connections matched up. And I can’t guarantee this won’t happen again during the next maintenance update.
Any insights or suggestions are welcome.
Have you checked these:
To disconnect users from a geodatabase in Oracle, the geodatabase administrator must either be added to the DBA role or granted ALTER SYSTEM and SELECT_CATALOG_ROLE privileges.
Yes. The user doing the ALTER SYSTEM KILL SESSION has DBA privileges.
The issue isn't that the sid,serial# can't be killed, it's that it doesn't exist, it's already been disconnected. When the session in V$SESSION and v$PROCESS has been killed, the corresponding entry in SDE.PROCESS_INFORMATION should be deleted but it's not. It persists so it appears that there are SDE connections when there aren't.
At the time of this issue, there were NO sessions other then DBSNMP and Oracle background processes connected. However, SDE.PROCESS_INFORMATION table had 196 rows.
No, I wasn't pointing towards the permissions for the disconnecting user.
What I meant was, did you trying using the Script suggested in those links for disconnecting the connected users. Does that make any difference?
Gotcha. No, we have always used alter system kill session How To: Kill direct connect processes to the ArcSDE databaseBut we've been doing it for so long I don't remember exactly where it came from, although I'm sure it was from ESRI. We'll give Arcpy a look and see what it does. At this point, I'm way past the production issue but will keep this in mind.
We are running ArcGIS 10.6.1 and Oracle 19c (22.214.171.124) and we're seeing some similar behavior in our database which is what brought me to this topic. When viewing the Process_Information table in SQL Developer we see a large number of what appear to be stale connections. Hence my interest in your scripts above.
Interestingly enough, when I connected to the database w/ArcCatalog and ran the Administer Geodatabase tool referenced by Asrujit and viewed the connections, it only shows the active connections, none of the stale entries show. After doing so, I went back into SQL Developer and refreshed my query of the Process_Information table. At that point all of the stale connection entries had been cleared out! So it seems ESRI has built some sort of check/maintenance function into the tool. I'm wondering if it can be scripted in Python and run as a scheduled task to keep the stale connection entries and their associated locks to a minimum.
Just thought I'd share this in case anyone else runs into similar issues on their systems.