适用于：
RDBMS企业管理器--版本：10.2.0.1到10.2.0.4—发行号：10.2到10.2
企业管理器网格控制器—版本：10.2.0.1到10.2.0.4【发行号：10.2到10.2】
HP-UX PA-RISC（64位）
HP-UX 安腾处理器
***相关性的检查于2010年5月28日***
症状
警告：
本说明的范围仅限于代理10.2.x监测Oracle数据库上运行HP-UX服务器。
默认情况下，代理10.2.x每15秒钟收集一次健康检查度量数据。这个度量是基于一个被监测的正在运行的数据库给定的迹象。在一些环境中，这些健康检查度量不能被收集。这些结果每15秒被加入到以下目录中的日志文件：$AGENT_HOME/sysman/log/emagent.trc。
2007-05-09 09:21:36 线程-81 错误获取。健康检查：错误：进程上下文没有初始化。
2007-05-09 09:21:36 线程-81 错误引擎：
【oracle数据库，EMI10104_rmtdchp4，健康检查】：nmeegd_度量数据取得失败：
由于下列原因之一引起的数据库实例健康检查初始化失败：EM代理进程的所有者和oracle实例进程的所有者不一样；EM代理进程的所有者不是dba组中的一部分；数据库不是10g（10.2.0.2）以上的版本。
2007-05-09 09:27:04 Thread-27 ERROR fetchlets.healthCheck: GIM-00104: file not found
LEM-00031: file not found; arguments: [lempgmh] [lmserr]
LEM-00033: file not found; arguments: [lempgfm] [Couldn't open message file]
LEM-00031: file not found; arguments: [lempgmh] [lmserr]
2007-05-09 09:27:04 Thread-27 ERROR engine:
[oracle_database,EMI10104_rmtdchp4,health_check] : nmeegd_GetMetricData failed :
实例健康检查初始化失败是因为下列原因之一：
EM代理进程的所有者和oracle实例进程的所有者不一样；EM代理进程的所有者不是dba组中的一部分；数据库不是10g（10.2.0.2）以上的版本。
2007-05-09 09:27:04 Thread-27 WARN collector: <nmecmc.c> Error exit. Error message:
实例健康检查初始化失败是因为下列原因之一：
EM代理进程的所有者和oracle实例进程的所有者不一样；EM代理进程的所有者不是dba组中的一部分；数据库不是10g（10.2.0.2）以上的版本。
或者
GIM-00090: OS-dependent operation:mmap failed with status: 12
GIM-00091: OS failure message: Not enough space
GIM-00092: OS failure occurred at: sskgmsmr_13
2007-05-09 09:49:09 Thread-44 ERROR engine: [oracle_database,EMI10104_rmtdchp4,health_check] : nmeegd_GetMetricData failed : Instance Health Check initialization failed due to one of the following causes: the owner of the EM agent process is not same as the owner of the Oracle instance processes; the owner of the EM agent process is not part of the dba group; or the database version is not 10g (10.1.0.2) and above.
2007-05-09 09:49:09 Thread-44 WARN collector: <nmecmc.c> Error exit. Error message: Instance Health Check initialization failed due to one of the following causes: the owner of the EM agent process is not same as the owner of the Oracle instance processes; the owner of the EM agent process is not part of the dba group; or the database version is not 10g (10.1.0.2) and above.
原因：
这里是三个内部缺陷原因的结合（内部缺陷在METALINK中是不可见的）
BUG 5854190 - SKGP.C NEEDS TO BE COMPILED WITH -D_PSTAT64 FOR HP-UX 32BIT EMAGENT
这个bug修复一个关于注意读取健康检查数据的DBMS客户端问题库的问题。这个修复在代理端被消耗，并且需要适用于Agent Oracle Home。
BUG 5868695 - HEALTH CHECK METRICS FAILS FOR 10.1.0.4 DATABASE
这个bug也是修复RDBMS服务器端的库，但是只在10.2数据库版本中才有用。
解决：
There are several steps to solve this problem:
1． 如果代理发行版本是10.2.0.1或者10.2.0.2，升级代理到10.2.0.3或者10.2.0.4，跟随如下步骤：
2． 对于HP-UX10.2.0.3 / 10.2.0.4，这是修复这个问题的指令，然而保持健康检查度量可用。这部分发生在Agent Oracle Home中。
2.1. Download Patch 5854190 from Metalink.
For 10.2.0.3 / 10.2.0.4 Agent on HP-UX PA-RISC, download the version 10.2.0.3 of Patch 5854190
For 10.2.0.3 Agent on HP-UX Itanium, download the version 10.2.0.2 of Patch 5854190
For 10.2.0.4 Agent on HP-UX Itanium, download the version 10.2.0.3 of Patch 5854190
2.2. Setup the Agent environment and shutdown the Agent by doing:
emctl stop agent
2.3. Because OCCI is not installed in an Agent Oracle Home, backup and edit the file $AGENT_HOME/rdbms/lib/ins_rdbms.mk and comment the line GENOCCISH so that the content of the makefile looks like:
client_sharedlib:
$(GENCLNTSH)
# $(GENOCCISH)
$(GENAGTSH) $(LIBAGTSH) 1.0
2.4. Apply the Patch 5854190 in the Agent Oracle Home by following the instructions given in the README
2.5. Relink the Agent by following
Note 273189.1 How to relink the EM 10g Grid Control Central Management Agent on Unix
2.6. Restart the Agent by doing:
emctl start agent
3． 我们现在需要聚焦在被监控的数据库端。这部分发生在被监控RDBMS Oracle Home：
如果被监控的数据库是10gR1（10.1.x）
*10.1.0.4,10.1.0.5：你需要在RDBM Oracle Home上适用补丁5868695 ，
![北京联动北方科技有限公司]()
otherwise the Healthcheck metric will still fail, despite the code fix applied on the Agent side.
![北京联动北方科技有限公司]()
Patch 5868695 is available only for HP-UX PA-RISC.
![北京联动北方科技有限公司]()
The equivalent issue for HP-UX Itanium is tracked by internal BUG 5881249 for which there is no backport available yet. Contact Oracle Support is such a backport is required for 10.1.x databases on HP-UX Itanium.
![北京联动北方科技有限公司]()
10.1.0.3, 10.1.0.2: consider patching / upgrading
![北京联动北方科技有限公司]()
If the monitored database is 10gR2 (10.2.x):
![北京联动北方科技有限公司]()
10.2.0.3 (and above): nothing to be done. The fix is already included.
Please pay special attention if the monitored database is 10.2.0.4. 10.2.0.4 RDBMS has the code fixes mentioned in this note, however some other Healthcheck issues have been found. Please check Note 602633.1 for more details.
![北京联动北方科技有限公司]()
10.2.0.2: Apply the Patch 4559294 in the RDBMS Oracle Home by following instructions given in the README.
![北京联动北方科技有限公司]()
As this patch was uploaded several times on Metalink, please make sure you download the patch dated from 25-JUL-2007 (or later).
![北京联动北方科技有限公司]()
This patch is only available for HP-UX PA-RISC. The equivalent issue for HP-UX Itanium is tracked by internal BUG 4990549, which is fixed in 10.2.0.1 RDBMS already. In other words, 10.2.0.x databases on HP-UX Itanium already have this fix.
![北京联动北方科技有限公司]()
10.2.0.1: consider patching / upgrading to 10.2.0.2 at least and follow the options above.
Note:
This step might also apply to the Grid Control repository database, provided it runs on HP-UX.
4. It is highly recommended to recreate the healthcheck file on the monitored database side, in order to make sure that the healthcheck file is fully in sync with the memory structures used by the Oracle RDBMS processes. To do so:
4.1. Shutdown the monitored database.
4.2. Rename / Delete the healthcheck file $RDBMS_HOME/dbs/hc_<SID>.dat file
4.3. Restart the monitored database. This will recreate the $RDBMS_HOME/dbs/hc_<SID>.dat file
Although this step is optional, it is highly recommended as it solved several Healthcheck issues.
5. If you cannot upgrade to Agent 10.2.0.3 / 10.2.0.4, or cannot follow one of the steps above, then the workaround is to disable the Healthcheck metric, as described in
Note 379423.1 How to edit or disable the Health Check Metric Collection in Grid Control 10.2
This means that the database availability will rely on the Response metric, which is collected by default every 5 minutes
当前位置：
论坛首页 »
自由讨论区 »
MySQL, Oracle及数据库讨论区
»
发起投票
技术讨论
加好友
发消息
2012-2-10 9:32:07 |
赞(
操作
