The other day I was installing 10.2.0.5 Grid on Windows 2003, during 10.2.0.5 upgrade it failed, reported problem and the workaround is: - restore ssl.conf.smibak to ssl.conf Because ssl.conf was truncated to 2KB instead of 7KB so I wonder, anyone in Oracle QA tried to installed this in windows Server before release to the public? On Wed, Nov 11, 2009 at 1:39 PM, Niall Litchfield < niall.litchfield@xxxxxxxxx> wrote: > With Grid Control.... > > So I generally rather like Grid Control (so shoot me). We have had fun > though with bugs in older agents trying to monitor newer > databases (specifically a 10.2.0.2 agent will hit 100% cpu constantly when > trying to monitor a 10.2.0.4 db and higher if the health check metric is > enabled). So we've updated the agents to 10.2.0.5. > > Now I'm trying to add a new monitored database instance. However the add > new database page displays incorrectly and cannot be used to add new > database targets. I'd say this was fairly serious. This turns out to be a > known bug > > > CauseThe oms 10.2.0.2 is too old and its not able to parse the response of > the 10.2.0.5 agent > > > backward compatibility, who needs backward compatibility. Or testing for > that matter. > > -- > Niall Litchfield > Oracle DBA > http://www.orawin.info > >