[Sh] & lt; defunct & gt; and other zombie processes, resulting in very slow System (ORA-00445)

Source: Internet
Author: User

During lunch break today, I received a request. The system is very slow. From the top view, most processes are zombie processes.

Oracle version 11.2.3.x

Linux5.6 x86-64


First, we suspect the problems in cron.

Use crontab-l, crontab-u oracle-l

No tasks found

Similar to this problem, you can add one after each row in crontab>/dev/null 2> & 1

Reference http://blog.sina.com.cn/s/blog_6226824c01014ee8.html

Then use pstree-ap

We can see that these botnets are caused by psp0, cjq0, mmon, and smco.

Search for defunct processes in metalink and compare the information in alert. Locate a document

ORA-00445: Background Process "xxxx" Did Not Start After 120 Seconds (Document ID 1345364.1) Go to the bottom
Modification time:2014-2-9Type:PROBLEM

In this Document

  Symptoms
  Changes
  Cause
  Solution


Applies to: Oracle Database-Enterprise Edition-Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to 12.1]
CRM On Demand-Version N/A to N/
IBM: Linux on System z
Linux x86-64
Linux x86
SYMPTOMS

Errors are seen in the alert log relating to spawning of processes such:

@ Checked for relevance on 17th Jan 2012
ORA-00445: background process "m001" did not start after 120 seconds
Incident details in:/opt/u01/app/oracle/diag/rdbms/incident/incdir_3721/db1_mmon_71__i3721.trc
ERROR: Unable to normalize symbol name for the following short stack (at offset 2 ):
Tue Jun 21 03:03:06 2011
ORA-00445: background process "J003" did not start after 120 seconds


Or

Waited for process W002 to initialize for 60 seconds



The system appears to be running very slowly and defunct processes can appear.

CHANGES

REDHAT 5 kernel 2.6.18-194. el5 #1 SMP Tue Mar 16
Oracle 11.2.0.2 Single Instance
IBM: Linux on System z

CAUSE

Recent linux kernels have a feature called Address Space Layout Randomization (ASLR ).
ASLR is a feature that is activated by default on some of the newer linux distributions.
It is designed to load shared memory objects in random addresses.
In Oracle, multiple processes map a shared memory object at the same address within ss the processes.

With ASLR turned on Oracle cannot guarantee the availability of this shared memory address.
This conflict in the address space means that a process trying to attach a shared memory object to a specific address may not be able to do so, resulting in a failure in shmat subroutine.

However, on subsequent retry (using a new process) the shared memory attachment may work.
The result is a "random" set of failures in the alert log.

 

SOLUTION

It shoshould be noted that this problem has only been positively diagnosed in Redhat 5 and Oracle 11.2.0.2.
It is also likely, as per unpublished BUG: 8527473, that this issue will reproduce running on Generic Linux platforms running any Oracle 11.2.0.x. or 12.1.0.x on Redhat/OEL kernels which have ASLR.

This issue has been seen in both Single Instance and RAC environments.

ASLR also exists in SLES10 and SLES 11 kernels and by default ASLR is turned on. To date no problem has been seen on SuSE servers running Oracle but Novell confirm ASLR may cause problems. Please refer

Http://www.novell.com/support/kb/doc.php? Id = 7004855 mmap occasionally infringes on stack

You can verify whether ASLR is being used as follows:

#/Sbin/sysctl-a | grep randomize
Kernel. randomize_va_space = 1

If the parameter is set to any value other than 0 then ASLR is in use.

On Redhat 5 to permanently disable ASLR.

Add/modify this parameter in/etc/sysctl. conf
Kernel. randomize_va_space = 0
Kernel.exe c-shield = 0

You need to reboot for kernel.exe c-shield parameter to take effect.

Note that both kernel parameters are required for ASLR to be switched off.

 

There may be other reasons for a process failing to start, however, by switching ASLR off, you can quickly discount ASLR being the problem. more and more issues are being identified when ASLR is in operation.





By setting two kernel parameters, we disabled a new linux feature named ASLR, restarted the server, and now the system is back to normal. To be observed

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.