ORA-30 Received When Trying To Kill Session (Doc ID 1011386.6)

Last updated on DECEMBER 06, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 7.0.16.0 and later
Information in this document applies to any platform.
***Checked for relevance on 01-Jul-2016***

Symptoms

After issuing ALTER SYSTEM KILL SESSION (sid,serial#);

an ORA-30 may occur.


ORA-00030, 00000, "user session ID does not exist"
// *Cause: The user session id no longer exists, probably because the
// session was logged out.
// *Action: Use a valid session ID.


The command may have been issued for one or more of the following reasons:

1. The process no longer exists at the os level, but does show up as active in
v$session.

 

2. The user reboots the client machine without logging off, leaving a shadow
process.

 

3. That session is holding onto a lock that needs to be released.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms