求助：很多perl.exe进程占用大量CPU

LoveWinter

9楼提供的Note 很有用.

我再多说两句: 这些perl 进程是干什么用的呢? 一般来说,分为三种:
1. Agent自身的watchdog, 检测agent的健康状况. dbconsole 的agent是embedd的.
2. 后台收集Metric信息,并且上传到repository
3. 一些数据库操作是用perl 脚本(调用DBI模块)实现的,因为这些操作都需要和OS交互,
而perl正好是跨平台应用的.

如果其中一个或多个操作很费时,就会出现CPU占用过高的问题.

[ 本帖最后由 LoveWinter 于 2008-5-9 21:28 编辑 ]

lotus1024

http://forums.oracle.com/forums/ ... art=15&tstart=0
我刚才碰到我的机器是300多个perl进程，cpu 100%使用。
可能是oem的bug，据说打补丁可以解决！

haoyuanfen

我的是10203的, win2000中系統盤C:改成了G:后,出現Perl.exe的CUP 100%
按下面的方法解決了

謝謝了

有問題我修正下：
四個文件正確路徑是
%ORACLE_HOME%sysman/admin/scripts/db/db_common.pl
%ORACLE_HOME%sysman/admin/scripts/db/db_instance.pl
%ORACLE_HOME%sysman/admin/scripts/db/net/listenerUtil.pl
%ORACLE_HOME%sysman/admin/scripts/db/net/netAdmin.pl

原帖由 cc59 于 2008-5-7 11:20 发表
楼主可以参考一下这个方法,


from metalink:


PERL Perl.Exe using too much Cpu Resources
  Doc ID:  Note:392059.1 Type:  PROBLEM
  Last Revision Date:  19-SEP-2006 Status:  REVIEW_READY

In this Document
  Symptoms
  Cause
  Solution
  References



--------------------------------------------------------------------------------

@ (AuthWiz 2.4) Created from SR 16659628.600 with ODM
@ Click here to edit in wizard.   


Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.2.0
This problem can occur on any platform.
Symptomsperl. exe program that is launched with the EM DBConsole is eating up all of their cpu resources -
50% processing and all RAM.


.
Verified the issue by the customer problem description, which shows that when the customer stop or
kill the EM DBConsole Service, the high CPU usage disappers.








CauseThere are system files that reference the c: drive when setting variables. There is no c: drive on
the system.

Bug 5005739 specified that the following files reference the c: drive which must be present:

%ORACLE_HOME%sysmanadminscriptsdbdb_common.pl
%ORACLE_HOME%sysmanadminscriptsdbdb_instance.pl
%ORACLE_HOME%sysmanadminscriptsdb
etlistenerUtil.pl
%ORACLE_HOME%sysmanadminscriptsdb
et
etAdmin.pl

Also chacke to make sure the TMP and TEMP system varialbes are set to a location where the drive exists






SolutionIf the c: drive does not exist then to implement the solution, please execute the following steps:

1. Change all references of c: over to e: (or a drive that exists) in the following files:

%ORACLE_HOME%sysmanadminscriptsdbdb_common.pl
%ORACLE_HOME%sysmanadminscriptsdbdb_instance.pl
%ORACLE_HOME%sysmanadminscriptsdb
etlistenerUtil.pl
%ORACLE_HOME%sysmanadminscriptsdb
et
etAdmin.pl

2. Make sure the TMP and TEMP system variables are set to a location that exists with at least
125Mb of free space. In this case TMP and TEMP should reference a temp directory on the e: drive.

Start Menu -> Settings -> Control Panel -> System -> Advanced -> Environment Variables

[ 本帖最后由 haoyuanfen 于 2008-9-19 15:48 编辑 ]

PUB-CEO

看看