Bill,

I think it should be separated to 2 parts - mass upgrade of agents and
upgrade of OMS itself
First part can be handled through mass agent deployment: you should
provide software
accessible on hosts (either through upload from oms web server or scp
to the host
or thought NFS) and after that you can upgrade the agent using silent
installation
Those operations can be scheduled and here emcli or execution of hosts command
(available in GC) can help

Since they are already configured agents there will be no need to configure them
again and they should just change version of protocol they speak with
oms (from 10.2.0.4 to 10.2.0.5)

After agents upgrade you can upgrade the oms itself where the main
downtime is - but it is at one place
(just on Grid Control server)


Please let me know if you need more information on that

Cheers,
Andrey

On 24 June 2010 21:04, Bill Shi <[address removed]> wrote:
> Hi Guys,
>
> I am working on a project that upgrading OMS and OEM Agent both from
> 10.2.0.4 to 10.2.0.5 on 400+ servers. Could anyone please suggest a solution
> to facilitate this operation? The main purpose is to minimise mornitoring
> down time, as there are a large amount of databases are monitoring by OEM GC
> at the moment.
>
> Sorry to disturb you and thanks for your help.
>
> Thanks in advance & Best Regards,
>
> Bill
>
>
>
>
> --
> Please Note: If you hit "REPLY", your message will be sent to everyone on
> this mailing list ([address removed])
> This message was sent by Bill Shi ([address removed]) from Sydney
> Oracle Meetup.
> To learn more about Bill Shi, visit his/her member profile
> To unsubscribe or to update your mailing list settings, click here
>
> Meetup, PO Box 4668 #37895 New York, New York 10163-4668 |
> [address removed]



-- 
Sincerely,
Andrey Goryunov.