Skip to Main Content
Forums

Enterprise Manager

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

12c management agent on repository server doesn't start following a system crash

sridhartempalleFeb 16 2015 — edited Feb 17 2015

My environment architecture for 12c Cloud Control (Used for personal practice purpose) can be explained as follows:

@DBSERVER: (OEL6.5, x86-64)

     - 12c Enterprise Manager Cloud Control (EMCC)

     - 11.2.0.4 database that acts as a repository for 12c EMCC

Monitored host is on a virtual machine (VM12) that is currently in the DBSERVER:

VM12: (OEL6.5, x86-64)

     - 12c Management Agent that monitors the host and the database (12.1.0.1)

The server was running fine for the last few months until recently when the computer had rebooted abruptly. Abrupt rebooting occurred a few times in the past, but this time it had an issue at the time of rebooting. The DBSERVER at the time of a startup starts the OMS and the AGENT. The OMS starts perfectly, but the AGENT does not start. Upon trying to start the agent, it shows the following error message:

[orcl11204g@dbserver bin]$ ./emctl start agent

Oracle Enterprise Manager Cloud Control 12c Release 3 

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

Starting agent ................. failed.

Target Manager failed at Startup: targets.xml was rejected: loaded with a wrong agent token

Consult emctl.log and emagent.nohup in: /home/u01/oemrel3/agent/agent_inst/sysman/log

[orcl11204g@dbserver bin]$

The targets.xml file contains the following information which doesn't seem to be of any help:

[orcl11204g@dbserver emd]$ cat targets.xml

<?xml version = "1.0"?>

<Targets>

</Targets>

[orcl11204g@dbserver emd]$

Can anybody provide the help during such circumstances?

The DBSERVER repository database, listener and oms are up and running while the agent is down. The VM12 database, listener and agent is up and running. Is there any other file that needs to be checked for additional information?
This post has been answered by Krishnan_venkat on Feb 16 2015
Jump to Answer

Comments

Krishnan_venkat
Answer

--> $/AGENT_INST/bin/emctl stop agent

If agent does not shutdown gracefully then kill all agent background processes by first grepping for agent perl and java processes only

--> Move your existing target.xml file

mv target.xml target.xml.old

--> Create an empty targets.xml file under /AGENT_INST/sysman/emd with the below content

<Targets>

</Targets>

--> Start the agent

$AGENT_INST/bin/emctl start agent

This starts agent but without any targets populated in targets.xml

To discover targets perform agent resynchronization operation from console

Regards

Krishnan

Marked as Answer by sridhartempalle · Sep 27 2020
1 person found this helpful
sridhartempalle

Thank you Krishnan_Venkat

After creating the empty targets.xml I started the agent, but the agent was still unreachable. I restarted the agent manually by stopping and starting in the subsequent steps and the agent is now up and communicating. That was the perfect solution to the problem I faced here.

1 - 2
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Mar 17 2015
Added on Feb 16 2015
2 comments
3,299 views