Looking for tips and best practices for upgrading OEM 10.2.0.1 to
10.2.0.5 on an 8 core Sun v490. It's currently monitoring about 60 hosts
and 140 databases, some of which are critical production systems. I also
have about 30g of data in the repository. I want to keep the down time
to a minimum. Does anyone have an idea of how much down time is
necessary to perform such an upgrade?

Looking for tips and best practices for upgrading OEM 10.2.0.1 to
10.2.0.5 on an 8 core Sun v490. It's currently monitoring about 60 hosts
and 140 databases, some of which are critical production systems. I also
have about 30g of data in the repository. I want to keep the down time
to a minimum. Does anyone have an idea of how much down time is
necessary to perform such an upgrade?

I've thought about installing anew on a 2nd host and migrating the
monitored hosts one by one to the new OEM but there are *very* many
firewall considerations in my environment and that itself will become a
large project. Do you think this is the best approach?

TIA

Are there people at your site who put the 10.2.0.1 solution into place
that you can work with?

If you google around for "grid control upgrade 10.2.0.5" there's a
bunch of stuff written.

It looks like a long complicated bug infested undertaking from a quick
look.

hpuxrac wrote:

If you google around for "grid control upgrade 10.2.0.5" there's a
bunch of stuff written.

It looks like a long complicated bug infested undertaking from a quick
look.


That's been my impression too. The few folks I've spoken to who went
through the upgrade all said the same. One the one hand I'd like to do
an in-place upgrade because if it works I could be done in an hour or
two. On the other hand if my experience follows that of others I've read
about I could hit lots of snags and have all my DB monitoring down for
an extended period. Potentially days.

Even though it's much more work I'm leaning towards installing a
completely new OMS and repository on a new host and migrating each agent
one at a time. It buys me the confidence of knowing that I'm still
monitoring all my targets througout the migration, but I will undoubetly
lose any historical metric data from the original repository, and will
have hundreds of firewall rules that potentially need updating.

If you google around for "grid control upgrade 10.2.0.5" there's a
bunch of stuff written.

It looks like a long complicated bug infested undertaking from a quick
look.

That's been my impression too. The few folks I've spoken to who went
through the upgrade all said the same. One the one hand I'd like to do
an in-place upgrade because if it works I could be done in an hour or
two. On the other hand if my experience follows that of others I've read
about I could hit lots of snags and have all my DB monitoring down for
an extended period. Potentially days.

Even though it's much more work I'm leaning towards installing a
completely new OMS and repository on a new host and migrating each agent
one at a time. It buys me the confidence of knowing that I'm still
monitoring all my targets througout the migration, but I will undoubetly
lose any historical metric data from the original repository, and will
have hundreds of firewall rules that potentially need updating.

If you are thinking of 10.2.0.5 is it worth it instead to think of the
11.2 equivalent? Why put yourself thru so much work when you have yet
another set of upgrades just around the corner?

Tried the upgrade on AIX (64bit). After several attempts, SR's,
consultants etc. installed a new repository.

Shakespeare wrote,on my timestamp of 22/10/2009 5:25 AM:



Tried the upgrade on AIX (64bit). After several attempts, SR's,
consultants etc. installed a new repository.

Aye!  Just going through the pain right now.
We have a fresh install but the stupid TZ problem is an issue at the moment.
Why on earth is Oracle still forcing folks to install first 10.2.0.1 and THEN
upgrade to 10.2.0.5 totally defies description.
This, on a supposedly "widespread use" product.
Yeah! Right...

On Oct 22, 4:17 am, Noons <wizofo... at (no spam) yahoo.com.au> wrote:

Shakespeare wrote,on my timestamp of 22/10/2009 5:25 AM:

Tried the upgrade on AIX (64bit). After several attempts, SR's,
consultants etc. installed a new repository.

Aye!  Just going through the pain right now.
We have a fresh install but the stupid TZ problem is an issue at the moment.
Why on earth is Oracle still forcing folks to install first 10.2.0.1 and THEN
upgrade to 10.2.0.5 totally defies description.
This, on a supposedly "widespread use" product.
Yeah! Right...

Because it's even worse to change procedures in the middle of a patch
sequence.  Oh wait, they've already done that with this cpu stuff...
is it 3 times now?  Never mind.