Re: Sessions Won't Die When Killed

Hi Tim,

Lookup the parameter PROCESSES in your init<sid>.ora file. Probably you didn't specify this parameter which would result in Oracle taking the default setting. Adjusting (or Adding including a value) this parameter could
solve the first problem concerning maximum number of processes. The answer is ye%s, there should be a number there.

Won't Die question:

Probably this session is "marked for kill". This means that backgroundprocesses
of Oracle will take care of really killing this process, once they get the chance.
Most likely they didn't kill the sessions directly (killing includes cleaning op memory
used by the session) due to heavy work this session was performing when it got the kill-command. ("Marked for kill" should be visible in the v$session view,
look for "*").

Hope this helps.
Jan Vissers

Tim Romano wrote in message <35DC9A25.A78F63F4_at_ot.com>...
>We received this error:
>
>"unable to make connection ORA-00020: maximum number of processes
>(%s) exceeded"
>
>(Why "%s" ? should there be a number here?)
>
>When I attempt to kill the sessions:
>
>ALTER SYSTEM KILL SESSION 'SID,SERIAL#'
>
>Oracle returns:
>
>SYSTEM ALTERED
>
>But when I list v$session afterwards, the "killed" sessions are
>still there. Any suggestions or hints on why these sessions are
>so persistent would be appreciated. Also, how to increase the
>number of processes?
>
>Thanks,
>Tim
>
>
>
>
>
Received on Thu Aug 20 1998 - 17:26:11 CDT