Hoping someone might be able to tell me how to kill a job that doesn't want to die:)
We had network maintenance over the weekend that interupted the connection between our app server and database. It caused a bunch of jobs to get stuck. I could kill all but one job. The last job seems to be busy reading but the session info doesn't show any sql.
BOTH OF THE COMMANDS BELOW RETURN ERROR: "ora-00030:user session id doesn't not exist" and session info continues to say "active">
ALTER SYSTEM KILL SESSION '8,46534' immediate;
alter system disconnect session '008,46534' post_transaction;
Any idea what else I can do to kill this job? Booting the database is not a possiblities.