RE: OEM Agent 10.2.0.4 on Solaris 64-bit
- From: "Arnold, Sandra" <ArnoldS@xxxxxxxx>
- To: "Roman Podshivalov" <roman.podshivalov@xxxxxxxxx>
- Date: Mon, 23 Jun 2008 13:22:23 -0400
I have downloaded this patch, applied it, and have restarted my agent.
I have taken the host it was monitoring out of blackout mode and we will
see what happens. It is encouraging because I can at least go to the DB
Console page and see what I am supposed to see. I wasn't able to do
that before.
Thanks for your help.
Sandra
________________________________
From: Roman Podshivalov [mailto:roman.podshivalov@xxxxxxxxx]
Sent: Monday, June 23, 2008 12:30 PM
To: Arnold, Sandra
Cc: Elliott, Patrick; oracle-l@xxxxxxxxxxxxx
Subject: Re: OEM Agent 10.2.0.4 on Solaris 64-bit
Hi,
You should apply patch #7031906 to your MA agent installation.
--romas
On 6/23/08, Arnold, Sandra <ArnoldS@xxxxxxxx> wrote:
The agent is at 10.2.0.4 <http://10.2.0.4/> . The OMS and
Repository database are at 10.2.0.4 <http://10.2.0.4/> . The target
databases are 10.2.0.4 <http://10.2.0.4/> .
Sandra
________________________________
From: Elliott, Patrick [mailto:patrick.elliott@xxxxxxxxxxxxx]
Sent: Monday, June 23, 2008 11:19 AM
To: Arnold, Sandra; oracle-l@xxxxxxxxxxxxx
Subject: RE: OEM Agent 10.2.0.4 <http://10.2.0.4/> on Solaris
64-bit
Did you say the agent is at 10.2.0.3 <http://10.2.0.3/> ? I
just had an SR open with Oracle, and they say that you need to have the
agents at 10.2.0.4 <http://10.2.0.4/> to monitor and administer
10.2.0.4 <http://10.2.0.4/> databases.
Pat
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Arnold, Sandra
Sent: Monday, June 23, 2008 9:32 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: OEM Agent 10.2.0.4 <http://10.2.0.4/> on Solaris
64-bit
I am having problems with my OEM Agent on Solaris 64-bit since I
have upgraded to 10.2.0.4 <http://10.2.0.4/> . I am seeing the
following in my log files:
2008-05-16 08:37:06,778 Thread-21594 ERROR upload: rawdata.dat
rename failed
2008-05-16 08:37:06,778 Thread-21594 ERROR upload: rawdata.dat
deleted, it will not be merged
2008-05-16 08:37:06,778 Thread-21594 ERROR upload: ERROR:
nmehursf_Rowset_write - lf
iopn failed -2 rawdata.dat
2008-05-16 08:37:09,820 Thread-21596 ERROR
fetchlets.healthCheck: GIM-00105: file not found
2008-05-16 08:37:09,820 Thread-21596 ERROR engine:
[oracle_database,dubt.osti.gov <http://dubt.osti.gov/> ,health_check] :
nmeegd_GetMetricData fa
iled : Instance Health Check initialization failed due to one of
the following c
auses: 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 gro
up; or the database version is not 10g (10.1.0.2
<http://10.1.0.2/> ) and above.
2008-05-16 08:37:09,820 Thread-21596 WARN collector: <nmecmc.c>
Error exit. Error message: Instanc
e Health Check initialization failed due to one of the following
causes: the own
er of the EM agent process is not same as the owner of the
Oracle instance proce
sses; the owner of the EM agent process is not part of the dba
group; or the dat
abase version is not 10g (10.1.0.2 <http://10.1.0.2/> ) and
above.
2008-05-16 08:37:10,830 Thread-21597 ERROR
fetchlets.healthCheck: GIM-00105: file not found
2008-05-16 08:37:10,830 Thread-21597 ERROR engine:
[oracle_database,stit.osti.gov <http://stit.osti.gov/> ,health_check] :
nme
egd_GetMetricData failed : Instance Health Check initialization
failed due to on
e 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 <http://10.1.0.2/> ) and above.
2008-05-16 08:37:10,830 Thread-21597 WARN collector: <nmecmc.c>
Error exit. Error message: Instance Health Check initialization failed
due to one of the follo
wing causes: the owner of the EM agent process is not same as
the owner of the O
racle instance processes; the owner of the EM agent process is
not part of the d
ba group; or the database version is not 10g (10.1.0.2
<http://10.1.0.2/> ) and above
The OMS and repository databases are on Red Hat Linux and have
been upgraded to 10.2.0.4 <http://10.2.0.4/> . The OEM Agent on that
server is not having any problems. Also, my current 10.2.0.3
<http://10.2.0.3/> OEM agent is not having any problems reporting to
the 10.2.0.4 <http://10.2.0.4/> OMS processes.
I have reported this to Oracle but they are unable to proceed
because they need additional information from RDA which I am unable to
send them because of Security policies here. This is going to force me
to have to rollback my upgrades on both the OEM Agent and the target
databases being monitored which were also upgraded to 10.2.0.4
<http://10.2.0.4/> . Unless the problem is fixed it also means that I
cannot upgrade past 10.2.0.3 <http://10.2.0.3/> on my databases if I
still want to use OEM.
Has anyone else had this problem?
Thanks,
Sandra
Arnold
[CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by
this email is proprietary to Medtronic and is intended for use only by
the individual or entity to which it is addressed, and may contain
information that is private, privileged, confidential or exempt from
disclosure under applicable law. If you are not the intended recipient
or it appears that this mail has been forwarded to you without proper
authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
delete this mail from your records. To view this notice in other
languages you can either select the following link or manually copy and
paste the link into the address bar of a web browser:
http://emaildisclaimer.medtronic.com
<http://emaildisclaimer.medtronic.com/>
Other related posts:
