OEM Agent Issues after Upgrade 10.2.0.4

  • From: "Arnold, Sandra" <ArnoldS@xxxxxxxx>
  • To: "oracle-l@xxxxxxxxxxxxx" <Oracle-L@xxxxxxxxxxxxx>
  • Date: Mon, 21 Jul 2008 15:22:21 -0400

I am having some major issues with the OEM Agent after I upgraded it to
10.2.0.4 on my production server.  The OS is Solaris 64-bit version
5.10.  I had this same issue on my Sandbox which is 5.10 and my DEVTEST
server which is 5.9.  I applied patch 6276119 which fixed the problem on
those two servers.  However on this server that is not the case.  I
don't know whether all the errors are caused by one problem or whether I
have multiple issues.  Here are some of the errors I am getting and the
files they are in.  I have removed any port #, server name, ip address,
or sid name since that informationis considered to be sensitive
information.  I think I have provided all the errors.  One thing I
haven't done is to delete everything in the OMS server for the
production server and rediscover it.
 
Any help that I can get would be greatly appreciated.  I know Oracle
support is going to want log files, configuration files, etc.
Unfortunately because of security policies here I can not send those
files.
 
Thanks,

Sandra Arnold
 
 
 
emagent.trc:
 
2008-07-21 14:49:12,086 Thread-1703 ERROR engine:
[oracle_database,<sid>,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.
2008-07-21 14:49:12,086 Thread-1703 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.
2008-07-21 14:49:13,066 Thread-1704 ERROR fetchlets.healthCheck:
GIM-00105: file not found

 
emagent_perl.trc:
 
storage_report_metrics.pl: Mon Jul 21 13:20:32 2008: WARN:
STORAGE_REPORTS:ERROR:Failed to read all the required field positions
from veritas vxprint
 
emagentfetchlet.trc:
 
2008-07-21 13:19:09,761 [main] WARN  track.OracleInventory
createLiveSnapshotComponent.454 - ECM: unknown external name for the
following patchset: Patchset: internal name: <oracle.patchset.db>;
external name: <UNKNOWN>; version: <10.2.0.3.0>; install time: <>;
description: <>
2008-07-21 13:20:18,796 [main] WARN  trk.BasePatchSet validate.209 -
ECM: unknown external name for the following patchset: Patchset:
internal name: <oracle.patchset.db>; external name: <UNKNOWN>; version:
<10.2.0.3.0>; install time: <>; description: <>

emdctl.trc:
 
2008-07-21 13:18:34,492 Thread-1 WARN  http: snmehl_connect: connect
failed to (<sid>:<port>): Connection refused (error = 146)
2008-07-21 13:18:34,501 Thread-1 ERROR main: nmectla_agentctl: Error
connecting to https://<sid>:<port>/emd/main/. Returning status code 1
 
emagent.nohup:
 
(pid=24547): signal handler called due to abnormal condition; dumping
core due to signal SIGSEGV
----- Mon Jul 21 13:18:34 2008::Checking status of EMAgent : 24547 -----
----- Mon Jul 21 13:18:34 2008::EMAgent exited at Mon Jul 21 13:18:34
2008 with signal 6 -----
----- Mon Jul 21 13:18:34 2008::EMAgent has exited due to an internal
error -----
----- Mon Jul 21 13:18:34 2008:: - checking for corefile at <path for
core file> -----
----- Mon Jul 21 13:18:34 2008::EMAgent coredump found at <path for core
file>
----- Mon Jul 21 13:18:34 2008::Core file moved to <where core file
moved to>
----- Mon Jul 21 13:18:35 2008::EMAgent will be restarted due to core
dump(via signal 6). -----
----- Mon Jul 21 13:18:35 2008::Restarting EMAgent. -----
----- Mon Jul 21 13:18:35 2008::Agent Launched with PID 4845 at time Mon
Jul 21 13:18:35 2008 -----
(pid=4845): starting emagent version 10.2.0.4.0
(pid=4845): emagent started successfully


Other related posts: