According to to administrator's guide for ORACLE 7.3, when you kill a
session it is terminated, rolled back if active, and the resources freed up.
The status in V$SESSION is "KILLED", but the row for the terminated session
is not removed from V$SESSION until the user atttemps to use the session
again. In our environment, we occasionally have users connecting from PC's
that reboot their PC or abnormally terminate their ORACLE
connection by some other means. Those sessions generally remain in
V$SESSION until the instance is shutdown and restarted.
To increase the maxinum number of processes, simply increase the "processes"
parameter in the initSID.ora file.
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 Mon Aug 24 1998 - 16:11:50 CDT
