In particular I'd look at *.log,emagent.nohup, and emagent.trc - these should be in $AGENT_HOME/sysman/log or $AGENT_HOME/<hostname>/sysman/log if it's a clustered agent. There may also be an agabend.log if the agent has crashed. On Tue, Sep 28, 2010 at 11:07 AM, Marcin Przepiorowski <pioro1@xxxxxxxxx>wrote: > Hi > > Did you try to do a agent clear state ? > > $ emctl clearstate > > Definitely checking agent logs will help to find a root cause. > > regards, > Marcin > > On Tue, Sep 28, 2010 at 8:09 AM, Niall Litchfield > <niall.litchfield@xxxxxxxxx> wrote: > > I must confess I've only ever upgraded an agent by replacing it so the > > removal of the targets wouldn't directly apply there,but like Kellyn I'd > be > > interested in what the actual crash is. 11.1 databases are a supported > > target for 10.2.0.5 grid control. > > > https://supporthtml.oracle.com/ep/faces/secure/km/DocumentDisplay.jspx?id=412431.1 > > . > > > > On Tue, Sep 28, 2010 at 12:55 AM, J. Dex <cemail_219@xxxxxxxxxxx> wrote: > >> > >> If you remove databases from Grid Control, does that mean the agent on > the > >> target will no longer try to discover them? The reason that I ask is > that > >> we added some 11.1 databases to our target server and did an upgrade to > >> 10.2.0.5 agent. Agent keeps crashing because of the 11.1 databases. > It > >> used to work fine with 10g databases. Would like to at least make sure > the > >> 10g databases are being monitored some way. > > > > > > > > -- > > Niall Litchfield > > Oracle DBA > > http://www.orawin.info > > > > > > -- > Marcin Przepiorowski > http://oracleprof.blogspot.com > -- Niall Litchfield Oracle DBA http://www.orawin.info