Professional Documents
Culture Documents
Telecordia - Iconnectiv - Database Max Processes Warning
Telecordia - Iconnectiv - Database Max Processes Warning
Summary: This document is dedicated for handling the Incident ticket triggered when the no of
spawn process associated with the database instances reached to the threshold limit. There are two
monitoring process threshold limit set in the Sitescope :
Case 3- If threshold reached 100% (Monitoring not set in the sitescope), this case is just a
reference if such an incident took place when we have 100% threshold.
Root Cause- Due to customer apps getting out of control and flooding processes by creating new
connections.
Impact Statement – New Connection request to the database will get failed if it threshold reached
100%. Existing connection will keep on working as usual.
1. Notify customer in any case with the current process utilization along with the user’s
sessions via email, phone call.
2. Do not recycle the instance without customer confirmation.
3. Do not kill any process in case 1, 2 without customer confirmation.
4. Kill only few process in case 3 so that you are able to login to the database and gather info
to notify customer with the details.
Case 1 –
Steps to follow: -
user_session.sql
5. Update the ticket with the detail information and sent notification mail to the customer
(Philippe Nguyen-Tan) pnguyentan@iconectiv.com including sessions and process details.
6. Call the customer. If notification matrix does not include customer phone number then ask
service desk.
Steps to follow: -
1. Logged in the database.
SQL> select (case NVL (a.username,'Background') when 'Background' then 'Background Instance
processes' else a.username end) "Users", count(b.spid) "Processes" from v$session a ,v$process
b where a.paddr=b.addr group by a.username;
user_session.sql
5. Update the ticket with the detail information and sent notification mail to the customer
(Philippe Nguyen-Tan) pnguyentan@iconectiv.com including sessions and process details.
Case 3 –
Steps to follow: -
2. As the user oracle execute the following command and filter the records with older
timestamp–
ps -ef|grep LOCAL=NO
4. Exclude the processes from the process list obtained in the step 2 if the same process is in
the list obtained in the step 2.
(Note - The reason of excluding the processes are to make sure that high CPU utilized
processes should not be killed)
5. Kill few process (from the list of processes obtained from step 4) as per understanding
so that you are able to login to the database.
SQL> select (case NVL (a.username,'Background') when 'Background' then 'Background Instance
processes' else a.username end) "Users", count (b.spid) "Processes" from v$session a ,
v$process b where a.paddr=b.addr group by a.username;
user_session.sql
10. Update the ticket with the detail information and sent notification mail to the customer
(Philippe Nguyen-Tan) pnguyentan@iconectiv.com including sessions and process details.
12. If customer says recycle the instance and then only we can recycle the instance. Without
customer confirmation we will not kill any process and not even recycle the instances.