Upgrade agent?

Hi experts,
I have problems with OEM, every day, appear the agent like "agent unreachable" and I have not information in OEM.
When try to know what happend, I go to "emctl status agent" and appear the error:
Collection Status : Disabled by Upload Manager
when I try to "emctl upload agent", appear the error:
.... disk full
Teh disk is not full and it has more than 50% free,
So, I need to recreate the repository again.
Some strange is:
My Oracle version is 11.2.0.3, why the Agent, OMS and Procotol appear with 10.2.0.4.4? Could be a problem? how can upgrade it?
Thanks in advance,
Regards,

Hi Victor,
OEM is delivered with Oracle, but you need to install and configure it to use.
As you must have upgrade from 10g to 11g, and OEM was configured before the upgrade, so you are getting old version of it.
You need to check the package delivered for OEM and may have to re-install and configure for version 11.
http://docs.oracle.com/cd/E11857_01/install.111/e15838/upgrade_em.htm#CHDEJGAH
Oracle Enterprise Manager Documentation</title><meta name="Title" content="Oracle Enterprise Man…
As, i have installed and configure this long ago on 10g, I can't really say about 11g.
Regards,

Similar Messages

Upgrade agents from OEM 10.2.0.5 from 12c not using Upgrade Console

Hi,
As we have to upgrade more than 100 agents from OEM 10.2.0.5 to OEM 12.1.0.3, don't have oracle account passwords (OEM 10g agents are runing as the oracle accout), and PAM authentification is not working for our environnement (SR open) we want to know if there is a workaround for upgrading agents and not using the upgrade console.
Regards,
Nicolas

Hi, the response from the support is upgrading all our agents to 11g and then upgrading to 12c it seems a bit complicated isn't it (more than 100 agents to migrate) ?
And as the migrate from 10g to 12c is nothing more than many automated actions I can believe that it can't be done manualy (just the install and configure agants).
Regards,
Nicolas

Question re upgrading agents to 12cR3

Hopefully I can ask this question clearly.
I upgraded my OEM installation from 12cR1 to 12cR3 and have also successfully upgraded most of the agents. My question -
The Agent Upgrade console shows a couple of agents which are not upgradable because the latest agent software is missing. They are Oracle Solaris on SPARC (64-bit) and the agent version is 12.1.0.1. The remedy is to go to the Self Update Screen. When I get there under Agent Software I see that the Oracle Solaris on SPARC (64-bit) is there with a status of applied. I believe I must download the 12.1.0.3 agent, is that correct?
When I choose the Oracle Solaris on SPARC (64-bit) the download button is greyed out so I do not have the option of downloading it. Must I first remove it in order to download the 12.1.0.3 agent? If I must do that is there anything I must be wary of or are there ramifications?
Thank you.
Bill Wagman

Hi Bill,
I have no idea why the download button would be greyed out, but I do know from experience that when you download updated agent software you do not need to do anything with the old software first -- that is, having the 12.1.0.1 agent sitting there in "Applied" status is normal and correct and shouldn't be causing you problems.
Is there any chance your software library is full? That's the only reason I can think of that the download button would be unavailable.
One thing to try might be to toggle OEM to offline mode for MOS, then return to self update and see if the download button is available. If it is, it should give you a link you can use to download the software manually along with instructions on how to import it to OEM using emcli. If that doesn't work, toggle back to MOS online mode and check the download button again.
-Brian

Upgrade agent using agentDownload.solaris -u

Hello,
Has anyone being able to upgrade the OEM agent from version 10.2.0.1.0 to 10.2.0.2.0
using agentDownload.solaris script and the -u option?
OMS version is 10.2.0.1.0
The command I ran was
./agentDownload.solaris -b $AGENT_HOME -o $OLD_AGENT_HOME -u
./agentDownload.solaris -b /opt/oracle/10Agent -o /opt/oracle/10Agent -u
Then it fails at
Initializing Java Virtual Machine from /tmp/OraInstall2007-05-28_09-47-38PM/jre/1.4.2/bin/java. Please wait...
Completed with Status=255
I have used the agentDownload script to install 10.2.0.1.0 in the past.

You need to apply the 10202 agent patch on 10202 agent oh
-u option use if u want to upgrade 10.1.0.X-->10.2.0.X

Upgrade Agent to 11g to run on 10.2.05 repository

Hello.
I want to upgrade our 10.2.0.5 agent to 11.1.0.1.0 and have confirmed that this is supported via Certifications on Metalink.
Does anyone have experience of this procedure?
Regards,
DA.

Steps for the upgrade are thus:
Upgrade Procedure, as per Upgrading Oracle Management Agent Using a Response File from Oracle® Enterprise Manager Grid Control Advanced Installation and
Configuration Guide
11g Release 1 (11.1.0.1.0)
Part Number E16847-10
http://download.oracle.com/docs/cd/E11857_01/install.111/e16847/upgrade_agent_usng_rsp.htm#CEGIDJFC
To upgrade an existing Management Agent using a response file, follow these steps:
1.
Backup Agent Home and set Registration Password.
Backup the exisiting Agent Home
cp -R /oraoem/agent10g /oraoem/pre_upgrade_agent10g
set a Registration Password in Grid Control
In oraoem’s bash shell, set an environment variable for $AGENT_INSTALL_PASSWORD
2.
Prepare Response File.
Navigate to and edit the response file upgrade_agent.rsp as described here:
edit rsp file, as per Oracle doc, and set 2 values:
OLD_BASE_DIR
If you have the default name for the Oracle home of your existing Management Agent, that is, agent10g, then specify the path to the old installation base
directory where the Management Agent to be upgraded is residing.
For example, if the Management Agent is residing in /john/OracleHomes/10.2/agent10g, then specify only /john/OracleHomes/10.2/
ORACLE_AGENT_HOME_LOCATION
Specify the location where the Oracle home of the Management Agent (agent11g) can be created.
Therefore:
The old installation base directory where the Management Agent to be upgraded is residing =
OLD_BASE_DIR = /oraoem
ORACLE_AGENT_HOME_LOCATION = /oraoem/agent10g
3.
Stop the Agent and Invoke installation.
Stop the Management Agent you want to upgrade.
as oraoem emctl stop agent
Invoke the installer:
If you have the default name for the Oracle home of your existing Management Agent, that is, agent10g, then: run the following command:
./runInstaller -silent -responseFile /<path to upgrade_agent.rsp>
4.
Post upgrade tasks.
After you upgrade verify the installation:
emctl status agent
Run the following command to see a message that confirms that EMD upload completed successfully:
$<ORACLE_HOME>/bin/emctl upload
manually run the root.sh script as a root user from the Oracle home of the Management Agent:
as oraoem stop the agent
emctl stop agent
as root run the root.sh
<Oracle_Home>/root.sh
start agent
emctl start agent
DA

NAC - upgrade agent

Hello,
Can I upgrade NAC agent for switchs cisco 2950 and 3560 to 4.9.4.3 without upgrading the CAM without any problems ?
the NAC version is 4.5.1.0
Big thanks in advance!
ILIAS

You can directly download the nac agent 4.9.4.3 from the below download link
http://software.cisco.com/download/release.html?mdfid=283801620&softwareid=283802505&release=1.2&flowid=26081

Database Upgrade Agent not working for upgrading Oracle 9i DB to Oracle 10i

Hi All,
Presently I have completed my Oracle 10i installation on Solaris Server but I am facing an issue during the upgrade process of Oracle 9i to 10g. Whenever I try to upgrade the 9i databases to 10g using DBUA(Database Upgrade assistant) I am facing an issue that Data base not running from oracle home or pfile not found. The exact error message says:-
The upgrade assistant failed in bringing up the database XIPCOTS. Oracle Home /opt/apps/home/oracle9i/product/releases/92/92 obtained from file /var/opt/oracle/oratab was used to connect to the database. Either the database is not running from Oracle Home /opt/apps/home/oracle9i/product/releases/92/92 or the correct Initialisation parameter file (pfile) was not found. To start the database , Oracle needs the pfile. Provide the full path name of the init file for the database XIPCOTS.
In reality the XIPCOTS database is running fine in Oracle 9i and we can connect it using PL/SQL developer in windows.I have also provided the path of pfile but it is still not accepting the same.
Path of pfile I provided :- /XIP/ofaroot/XIPCOTS/pfile/initXIPCOTS.ora
Any help or suggestions would be greately appreciated.
Our both Oracle 9i and 10g are installed on same Solaris server where solaris version is 9
Installation path for 9i :- /opt/apps/home/oracle9i/product/releases/92/92
Installation path for 10g :- /opt/apps/home/oracle/product/releases/10201
Oracle 9i version :- 9.2.0.7
Oracle 10g version :- 10.2.01
Thanks in advance.
Best Regards,
Gourav Banerjee

Can you please mention the specific folder name under oracle home where we need to put this pfile because there are two folder dbs and ds I have allready tried putting it inside dbs its not working. And my home path is correct I hope and is set for oracle 9i directories in the .oraenv file do we need to set it for oracle 10g before the DBUA upgrade.

DPM 2012 R2 Update rollup 3 - unable to upgrade agent from 4.2.1217 to 4.2.1254

Fully updated DPM 2k12 R2. Have some protection groups with total of 11 servers in it (mainly w2k12 r2 servers and w2k8 r2 servers). After update rollup 3 try to update agents on protected servers. All agents excluding one were updated.
Update can't be performed on one w2k12 r2 server, which is also used as hypervisor. Hw is X3650_m2, common config. When try to update via DPM console (od manually), still same error.
Scenario: try to install agent update manualy. On protected server, copied agent install files (DPMAgentInstaller_KB2966014_AMD64.exe + 3 other files) to local drive. Run as domain admin user from elevated prompt. Install fail with error 0x80070643.
Does not matter how level of magic I try to put on it.
So, I studied log files (%windir%\temp\msdpm*.log, particulary MSDPMAgentPatchInstall.LOG. This is a long file, so I extract interesting parts, where installer indicated error:
MSI (s) (E4:D0) [09:55:31:963]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI85E7.tmp, Entrypoint: InstallProvider
InstallProvider entered.
UnInstallProviderCatalogAndDLL entered.
StopServiceAndChangeStartType returned Error code = 0x00000000
Error in UnInstallProviderCatalogAndDLL. hr=0x8004e00f
CustomAction _InstallProvider.E785582E_DD9D_4A85_B866_3A1BC05C6110 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
After that, rollback starting, so next part of log is not as interesting. Another interesting file is file named MSDPMAgentBootstrap0Curr.errlog, also in temp directory. File contained some (maybe) interesting infos,
try to past all of them because is not too long:
1C44   1F90   09/24   07:55:31.932   10   setupdpmfltr.cpp(860)           NORMAL   dpmfltr driver path [C:\Windows\system32\drivers\dpmfilter.sys]
1C44   1F90   09/24   07:55:31.932   10   setupdpmfltr.cpp(1045)           NORMAL   versionBufferSize returned
by GetFileVersionInfoSize = 2292
1C44   1F90   09/24   07:55:31.932   10   setupdpmfltr.cpp(1071)           NORMAL   Hr: = [0x00000000] QueryFileVersion
returning
1C44   1F90   09/24   07:55:31.932   10   setupdpmfltr.cpp(883)           NORMAL   The dpmfltr is present and driver
version is [4.2.1176.0]
1C44   1F90   09/24   07:55:31.947   10   setupdpmfltr.cpp(1045)           NORMAL   versionBufferSize returned
by GetFileVersionInfoSize = 2292
1C44   1F90   09/24   07:55:31.947   10   setupdpmfltr.cpp(1071)           NORMAL   Hr: = [0x00000000] QueryFileVersion
returning
1C44   25E4   09/24   07:55:31.979   10   main.cpp(1958)           WARNING   Failed: Hr: = [0x80070426] StopService
failed for service[vss] and returned
1C44   25E4   09/24   07:55:31.979   10   main.cpp(1848)           WARNING   Trying to open windows service failed
for Service = [VssNullProvider]
1C44   25E4   09/24   07:55:31.979   10   main.cpp(1849)           WARNING   Failed: Hr: = [0x80070424] : Encountered
Failure: : lVal : hr
1C44   25E4   09/24   07:55:31.979   10   main.cpp(2007)           WARNING   Failed: Hr: = [0x80070424] : Encountered
Failure: : lVal : GetServiceHandle(schSCManager, lpService, hService)
1C44   25E4   09/24   07:55:32.041   10   main.cpp(6876)           WARNING   Failed: Hr: = [0x8004e00f] : Encountered
Failure: : lVal : pCOMAdminCatalog->GetCollection(bsApplications, (IDispatch**)&pAppsCatalogCollection)
1C44   38D8   09/24   07:55:34.588   10   main.cpp(1958)           WARNING   Failed: Hr: = [0x80070426] StopService
failed for service[vss] and returned
1C44   38D8   09/24   07:55:34.588   10   main.cpp(1848)           WARNING   Trying to open windows service failed
for Service = [VssNullProvider]
1C44   38D8   09/24   07:55:34.588   10   main.cpp(1849)           WARNING   Failed: Hr: = [0x80070424] : Encountered
Failure: : lVal : hr
1C44   38D8   09/24   07:55:34.588   10   main.cpp(2007)           WARNING   Failed: Hr: = [0x80070424] : Encountered
Failure: : lVal : GetServiceHandle(schSCManager, lpService, hService)
1C44   38D8   09/24   07:55:34.775   10   main.cpp(6876)           WARNING   Failed: Hr: = [0x8004e00f] : Encountered
Failure: : lVal : pCOMAdminCatalog->GetCollection(bsApplications, (IDispatch**)&pAppsCatalogCollection)
1C44   3340   09/24   07:55:34.994   10   main.cpp(6623)           NORMAL   AccountName for WinLocalSystemSid =
NT AUTHORITY\SYSTEM
1C44   3340   09/24   07:55:34.994   10   main.cpp(6636)           NORMAL   AccountName for WinBuiltinAdministratorsSid
= BUILTIN\Administrators
1C44   3340   09/24   07:55:35.213   10   main.cpp(6647)           WARNING   Failed: Hr: = [0x8004e00f] : Encountered
Failure: : lVal : pCOMAdminCatalog->GetCollection(bsApplications, (IDispatch**)&pAppsCatalogCollection)
Please note, that time in thist file is UTC and is shifted 2 hours against MSDPMAgentPatchInstall.log. Then, I begun to study event viewer.
There are also some track of this failed install. Especially EventID 1000 - Application Error from MsiEXEC:
Faulting application name: MsiExec.exe, version: 5.0.9600.16384, time stamp: 0x5215f49e
Faulting module name: MSI91B2.tmp, version: 4.2.1254.0, time stamp: 0x53ce7a5f
Exception code: 0xc0000005
Fault offset: 0x000000000004bfc6
Faulting process id: 0x1c44
Faulting application start time: 0x01cfd7cce8e8f583
Faulting application path: C:\Windows\System32\MsiExec.exe
Faulting module path: C:\Windows\Installer\MSI91B2.tmp
Report Id: 29d33452-43c0-11e4-80de-02215ecc909f
Faulting package full name:
Faulting package-relative application ID:
Another steps allready tryed:
- uninstall agent 4.2.1217 - OK
- restart server
- install agent 4.2.1254 from scratch - same error
- install 4.2.1217 again - OK
- restart server
- install 4.2.1254 again - same error
I'm clueless.
Kamil Ondrus

After long fight I find out, that problem is MS DTC failing on this server, because message about MSDTC (Distributed Transaction Coordinator - in services) was right before installer fail.
So root cause was that service MSDTC was not able to start. Start digging out, event viewer contains cca 4 messages from MSDTC, and one of them pointet me to log file. Seems MSDTC service have not proper right to log file under %WINDIR%\System32\MsDtc\MsDtc.log
Because service runs under "NetworkService" account, I granted rights for it using "icacls /grant %WINDIR%\System32\MsDtc\MsDtc.log 'Networkservice':F
Maybe command is not written ok, sorry for that - did it very late yesterday, but many posts on net talks about it, look:
http://www.progtown.com/topic376230-msdtc-error.html
http://stackoverflow.com/questions/10461354/msdtc-encountered-an-error-hr-0x80000171-while-attempting-to-establish-a-secur
Kamil Ondrus

New Oracle By examples available on OTN (Install, upgrade,agent patching ..

Hi,
The following OBEs are now available on 10.2.0.2 Enterprise Manager OBE page (http://www.oracle.com/technology/obe/obe10gemgc_10202/index.html) on OTN:
Installing Oracle Enterprise Manager 10g Grid Control Release 2 (10.2.0.1.0)
Patching Grid Control 10.2.0.1 to 10.2.0.2
Deploying Oracle Management Agent using the Agent Push Application
Patching 10.2.0.1 Management Agents to 10.2.0.2 Using Patch Wizard
Thanks and Regards,
Rajat

Nice one. Thanks

Agent upgradation

To upgrade agent from 10202 to 10203, do we have to do the same way to upgrade through GUI, is it posssible to upgrade agent in silent mode by apolying patches? I am having agents for diffrent OS and wants to upgrade to 10203 (existing 10202).

The Upgrade release note has a section "Upgrading Management Agent - Multiple Hosts at a Time".
So it is good to go through both Readme and release note before you start
See
Enterprise Manager Upgrade Hints

EM12cR2 - how to clean up old agent core directories after upgrade?

Running EM12cR2+PSU1 on Linux x86-64.
Does anybody know the recommended/supported/correct way to remove old versions of the EM12c agent core directories on managed servers after the agents have been upgraded to EM12cR2? This isn't a huge issue, but I've been setting up my agents on small (2GB) dedicated volumes and I won't have enough space available for the next round of upgrades unless I get the old stuff cleared out.
I have one server that was added to the environment after my EM12cR2 upgrade, and several servers that were already being monitored before the upgrade. The servers where I upgraded the agents after installing EM12cR2 all still have copies of the agent base core/12.1.0.1.0 directory along with the new agent base core/12.1.0.2.0 directory. I've tried removing this directory and bouncing the agent, but the agent gets blocked since it apparently cannot locate some files it expects to find. Other than being rejected by the OMS, the agent appears to function fine. I can only unblock the agent successfully if I put the 12.1.0.1.0 directory back in place.
Here's what I'm seeing on an upgraded agent:
/oraagent> du -sh agent12c
1.5G    agent12c
/oraagent> ls agent12c/core
12.1.0.1.0 12.1.0.2.0
/oraagent> du -sh agent12c/core/*
626M    agent12c/core/12.1.0.1.0
534M    agent12c/core/12.1.0.2.0
/oraagent> emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
Agent Version     : 12.1.0.2.0
OMS Version       : 12.1.0.2.0
Protocol Version : 12.1.0.1.0
Agent Home        : /oraagent/agent12c/agent_inst
Agent Binaries    : /oraagent/agent12c/core/12.1.0.2.0On a host that never had the EM12cR1 agent installed, I see:
/oraagent> du -sh agent12c
631M    agent12c
/oraagent> ls agent12c/core
12.1.0.2.0
/oraagent> du -sh agent12c/core/*
534M    agent12c/core/12.1.0.2.0
/oraagent> emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
Agent Version     : 12.1.0.2.0
OMS Version       : 12.1.0.2.0
Protocol Version : 12.1.0.1.0
Agent Home        : /oraagent/agent12c/agent_inst
Agent Binaries    : /oraagent/agent12c/core/12.1.0.2.0Interestingly the inventory.xml in the oraInventory on the upgraded server still contains references to the 12.1.0.1.0 directory that seem useless:
<HOME NAME="agent12c2" LOC="/oraagent/agent12c/core/12.1.0.2.0" TYPE="O" IDX="1">
   <REFHOMELIST>
      <REFHOME LOC="/oraagent/agent12c/sbin"/>
      <REFHOME LOC="/oraagent/agent12c/plugins/oracle.sysman.db.discovery.plugin_12.1.0.2.0"/>
      <REFHOME LOC="/oraagent/agent12c/core/12.1.0.1.0/../../plugins/oracle.sysman.db.agent.plugin_12.1.0.2.0"/>
      <REFHOME LOC="/oraagent/agent12c/plugins/oracle.sysman.oh.discovery.plugin_12.1.0.2.0"/>
      <REFHOME LOC="/oraagent/agent12c/plugins/oracle.sysman.oh.agent.plugin_12.1.0.2.0"/>
      <REFHOME LOC="/oraagent/agent12c/plugins/oracle.sysman.emas.discovery.plugin_12.1.0.3.0"/>
      <REFHOME LOC="/oraagent/agent12c/plugins/oracle.sysman.xa.discovery.plugin_12.1.0.3.0"/>
   </REFHOMELIST>
</HOME>
<HOME NAME="OraHome6" LOC="/oraagent/agent12c/core/12.1.0.1.0/../../plugins/oracle.sysman.db.agent.plugin_12.1.0.2.0" TYPE="O" IDX="8">
   <DEPHOMELIST>
      <DEPHOME LOC="/oraagent/agent12c/core/12.1.0.2.0"/>
   </DEPHOMELIST>
</HOME>The agent upgrades were all performed through the agent upgrade console without incident. The OMS server itself also contains both 12.1.0.1.0 and 12.1.0.2.0 in the agent base core directory. The fact that the agent on the server that never had 12.1.0.1.0 installed is working fine would seem to indicate that the 12.1.0.1.0 binaries aren't required for proper functionality, but I'm just not clear on how to remove them. I would like to avoid losing the targets monitored by these agents and having to recreate them and their jobs and so on.
Any thoughts? Has anybody else had the same issue occur in their environment?

If you are talking about the target agent upgrade to 12.1.0.2 and there is core dir left behind then you can delete only the contents of the $AGENT_BASE_DIR/core/12.1.0.1.0 directory and make sure that
the directory $AGENT_BASE_DIR/core/12.1.0.1.0 exists
Just FYI: for next EM release, we have a proper feature: sign off process where all dangling old oracle homes, their disk foot pints plus oms side artifacts, for upgraded agents can be removed.
The Upgrade guide is also getting updated with same information, should be live in next 2-3 days. We have told the same to come of our customer like AT&T, Fedility ..etc
I would also like to share information on the thread:
Re: How to delete 12.1.0.1 OMS Home when it contains the 12.1.0.2 agent s/w?
The script/steps to move the agent home from old middleware home to new one while doing the Oms upgrade from 12.1.0.1 to 12.1.0.2 is also ready. We also provided this script to one of our customer and they verified this script ( works for them :) )
How to Migrate the AGENT BASE DIRECTORY under Middleware Home to another location outside the Middleware Home? (Doc ID 1520010.1)
Again upgrade guide is getting updated with this note number

UCCX RECORDING STOP WORKING AFTER AGENT´S PC UPGRADE FROM XP TO WINDOWS 7

Dears, We have a customer with UCCX 8.0(2) already working, some agents upgrade per company policy theirs PC´s to Windows 7, After that, supervisor are unable to monitoring/recording the upgrade agent´s PCs.
We installed Ethereal in those PCs and see that the Agent PC did not generate the "copy" RTP packet to Supervisor desktop, as in XP machines where you can see both packet, from phone to phone, and from agent´s PC to supervisor´s PC.
We disable antivirus software and Windows firewall and make everything in troubleshooting documentation, even the registry setting changes.
We did not change hardware, only OS.
We are running Windows 7 Enterprisse edition.
Does anybody stuck with this problem?
Regards
Gustavo Chiarelli

If you are sure that Postinstall is pointing to the right NIC (IP address for which you see G.711 packets when you run NICQ.exe), that’s good. But most of the times, I see problems like this or Span to PC port problem.
I think you can have a look on this doc https://supportforums.cisco.com/docs/DOC-13223 before requesting again to get response from TAC.

Agent cannot be upgraded

Hi !!
I've used patch 6810189 to upgrade database (OS : windows server 2003 SP2 ) 10.2.0.1 to 10.2.0.4.
Database version and Enterprise Manager are both upgraded successfully . But when I run ' emctl agent status ' to check agent version , it shows that agent version is 10.1.0.6 .
Besides , when I check on Oracle Universal Installer ---> Installed Products .There are 2 parts :
+ Oracle database 10g 10.2.0.1
+ Oracle Database 10g Release 2 Path Set 3 10.2.0.4
While I was upgrading Database and Enterprise Manager , no error occured
I don't know what I'll have to do to upgrade Agent version .
Can you give me some advices ?
Thanks

Tien Lai wrote:
Hi !!
I've used patch 6810189 to upgrade database (OS : windows server 2003 SP2 ) 10.2.0.1 to 10.2.0.4.
Database version and Enterprise Manager are both upgraded successfully . But when I run ' emctl agent status ' to check agent version , it shows that agent version is 10.1.0.6 .
Besides , when I check on Oracle Universal Installer ---> Installed Products .There are 2 parts :
+ Oracle database 10g 10.2.0.1
+ Oracle Database 10g Release 2 Path Set 3 10.2.0.4
While I was upgrading Database and Enterprise Manager , no error occured
I don't know what I'll have to do to upgrade Agent version .
Can you give me some advices ?
ThanksYour upgrade was an overall upgrade of the database. That does not mean that every component was (or needed to be) upgraded. Each component will report it's own level.

SCOM : Issues while upgrading SCOM agent from 2012SP1 to R2

Hi,
We have upgraded SCOM setup from SP1 to R2 but facing issues with agent upgrade.
We were able to view only ~70% agents in pending management (Agent requires update).
Further, when I tried to upgrade agents through console, some are successfully upgraded but rest are giving
error.
Can someone help me to understand why all agents are not appearing in pending management for upgrade?
I also tried to upgrade agent manually but no luck. It gives error "The path 'C:\Windows\.........\monagent.msi'
can not be found. Verify that you have access to location and try again or try to find installation package.........". , though I had logged into server with admin access.
Also most of servers are remotely manageable but unable to upgrade through console.
Thanks,
Priya

Hi Priya,
I understand you require the Agent data. How ever the events clearely say the issue is because of the old installation files.
I was looking a a article on updating an agent to SCOM 2012 R2 from the below link.
https://technet.microsoft.com/en-us/library/dn249715.aspx
So the link says:
When you upgrade an agent, the Operations Manager installer service runs and is not removed until after the completion of the upgrade.
If the agent upgrade fails, you might have to re-install the agent because the installer service was not properly removed. If you attempt to upgrade the agent again and it fails, you should re-install the agent after you have completed upgrading all features
of Operations Manager.
So i would suggest you is you try the below on only 1 agent.
1. Download the Agent Dump from the below link and try updating it. (This is my copy of MOM Agent.msi from my installation media of SCOM
2012 R2)
https://www.dropbox.com/s/wv7y37moyd04209/MOMAgent.msi?dl=0
If the above does not success and gives you the same error then try the below
1. Select an agent and pull all the perfmon data / Alerting data required for it using SQL Query or Reporting.
2. Uninstall the Old SP1 Agent setup.
3. Install the Agent via Discovery Wizard or do a manual installation and see if the issue resolves.
I think either from both the steps will solve the issue.
Gautam.75801

Upgrade to SCOM 2012 Agent - 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameters is incorrect)

I have seen this behavior on multiple servers. I receive this error when upgrading from a 2007 Agent to SCOM 2012.
Event ID: 10005
Product: System Center 2012 - Operations Manager Agent -- Error 25211.Failed to install performance counters.. Error Code: -2147024809 (The parameter is incorrect.).
Event ID: 1008
The Open Procedure for service "HealthService" in DLL "C:\Program Files\System Center Operations Manager 2007\HealthServicePerformance.dll" failed. Performance data for this service will not be available. The Status code returned is the
first DWORD in the attached data.
Any idea why I receive this error?
Thanks
Mike

Hi,
Please refer to this article:
SCOM 2012 – Unable to upgrade agent after upgrade from SCOM 2007
http://www.phits.nl/wordpress/2013/02/01/scom-2012-unable-to-update-agent-after-upgrade-from-scom-2007/
Alex Zhao
TechNet Community Support

Upgrade agent?

Similar Messages

Maybe you are looking for