Shulou(Shulou.com)06/01 Report--

1. What is a SNIPED session?

When a session is INACTIVE and the duration of the INACTIVE exceeds a certain limit, such as the IDLE_TIME specified in PROFILE, the state of the session changes from INACTIVE to SINPED.

In your case, when an inactive session is idle for more than 360 minutes, the state of the session becomes SNIPED. Instead of cleaning up SNIPED's session in 360 minutes.

2. When will the SNIPED session be cleaned up?

When the client of the session marked SNIPED issues the SQL statement again, the client receives an error prompt, such as ORA-02396: exceeded maximum idle time, please connect again. At this point, the database will completely clean up the session and the connections on the operating system.

But this means that if the client does not issue SQL, the sessions of the SNIPED and the connections it uses cannot be cleaned up, and they will still take up resources, which may cause errors due to insufficient resources, such as the problem of reaching the maximum number of connections. At this point, you need to manually clean up these SINPED sessions and the connections they use.

3. Script to manually clean up the SNIPED session

The command to query spid with the status of SNIPED:

SELECT P.SPID from V$PROCESS Precinct Vendor session S

WHERE S.PADDR=P.ADDR

And s.STATUS = 'SNIPED'

The command to query spid with a status of SNIPED or INACTIVE:

SELECT P.SPID from V$PROCESS Precinct Vendor session S

WHERE S.PADDR=P.ADDR

And s.STATUS in ('SNIPED','INACTIVE')

Query the above two states and locate the user:

SELECT P.SPID from V$PROCESS Precinct Vendor session S

WHERE S.PADDR=P.ADDR

And S.STATUS = 'SNIPED'

And S.USERNAME = 'TTT'

Content of the script:

Snfile=/tmp/tmp.txt

Sqlplus system/oracle

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.