ORA-00030 User session ID does not exist when killing an oracle session

[Former Member]

When using alter system kill session, I have the ora-00030 alert as per subject.

Therefore I am not able to kill it, is there any other method to kill an oracle session?

Why is this happening? When executing "select serial# from v$session where sid=.....", I do get an output

Thanks.

Edited by: e.castro on Jun 25, 2011 4:29 PM

[Former Member · Accepted solution]

Hi Orkun,

Thanks.

I didn't get to check the alert log, however the problem was solved.

One of the contractor actually killed a hanging job in another SID.

I'm just wondering, where do I check this oracle session belongs which job in which SID?

Sorry, I'm new to Basis.

Thanks.

[Former Member · Accepted solution]

Hi Castro,

You can find these values by executing an SQL statement, but the easiest way to match Oracle SID# and thread# is using ST04 transaction. You can find the path, below;

ST04 -> Performance -> Wait Event Analysis -> Session Monitor

On the screen, you can find Orale SID# and Client proc. and SQL statement. For example;

SID: 1210

Client proc: <SAP rocess ID>:<Oracle thread/process>#

SQL statement: SELECT .....

I hope that I clarified the issue.

Best regards,

Orkun Gedik

[Former Member]

Thanks. It's a helpful tips for me as an SAP newbie

[Former Member]

Hi Castro,

Could you check, alert<SID>.log, after you executed the statement? You should be able to see the detailed info about the problem, in it.

Additionally, you can use "orakill" command at the OS level. Please find the sample, below;

orakill <SID> <thread #>

for example;

orakill PRD 3352

Best regards,

Orkun Gedik