ORA-30 Received When Trying To Kill Session
(Doc ID 1011386.6)
Last updated on FEBRUARY 02, 2022
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
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
2. The user reboots the client machine without logging off, leaving a shadow
3. That session is holding onto a lock that needs to be released.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!