RE: Grid Control upgrade

Sorry List for being late in updating you how it went. Here it is now;

As I said in my earlier email, Oracle Support said it's impossible to upgrade and move the repository db at the same time and there isn't much in it anyways, so I took the easy path to install 10gR2 OMS with a new 10104 db from scratch. I was planning to use a new 9206 db, the OS software packages required for 9206 on RHEL 3 and those required for OMS 10gR2 conflict with each other. Also, one required (I say required, because without it OUI wont even start) package isn't available for RHEL3, its available in RHEL4, which we are not running. So I just went ahead with just out-of-box install. After a few glitches (EMCA failures, OPMN failures etc), it's up and running, I am happy with it.

So now I have

OMS 10.2.0.1
Repo db 10.1.0.4
Agent 10.2.0.1

Moving databases from old OMS to new one was easy; just change the emd.properties file to reflect the new REPOSITORY_URL on the target node. Wait 5-15 mins, you will see the target (host and agent only) automatically discovered in the new OMS. Rediscover other targets such as dbs and listeners manually.

HTH,
-Amit.

Amit Verma
Senior Oracle DBA
University of Michigan ITCS
Ph: 734-647-5790

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Alex Gorbachev Sent: Wednesday, April 19, 2006 5:16 PM
To: averma_at_umich.edu
Cc: joseph.armstrong-champ_at_tufts.edu; oracle-l_at_freelists.org Subject: Re: Grid Control upgrade

I tried to upgrade 10.1.0.4 to 10.2.0.1 following official procedure. After a week of pain and feedling with all possible fixes for upgrade actions done during installation I finally couldn't do anything else as to recreate repository from scratch. Upgrade from 10.1 to 10.2 is done via new oracle home and I couldn't make it working. Maybe it's our HP-UX platform so if you are on Linux - you might be lucky.

If you need to keep you old repository than you will need to upgrade it. There is tool how to do it - newer got it 100% working. If you decide to do it - backup your repository (well, you do it anyway, right?) - I restored it few times over the course of upgrade attemtps. I also use 9.2.0.6.

Upgrading agents - perhaps it will work as in official installation guide. If not - consider installing 10.2 agent from scratch and copy over targets.xml file.

Good luck. Would be great if you share in the end what was the path you took and how successful it was.

2006/4/14, averma_at_umich.edu <averma_at_umich.edu>:
> Joe,
>
> I spoke with Oracle Support this evening and they suggested the
> following plan:
>
> 1. Install 10gR2 EM on new hardware.
> 2. Install 10gR2 agent.
> 3. Install and create a 9206 db(My choice over a 10.1.0.4 buggy db).
> 4. Change the agent configuration on target nodes to point to the new OMS.
>
> You may be correct that sysman store information about jobs, events,
> blackouts etc, but since I am not using any of these(I mean
> user-defined, my current installation is out-of-the-box OMS), I am
> going to go ahead with this plan and not worry about moving the repo
> db. Also, the support guys told me was the repo db has information
> about the hostname the oms is running on, so the exp/imp wouldn't work.
>
> I hope this works. I am gonna try this tmrw and will let you know if
> this works.
>
> Thanks
>
> -Amit.
>
> Quoting Joe Armstrong-Champ <joseph.armstrong-champ_at_tufts.edu>:
>
> > Amit,
> >
> > Look at the sysman schema in the repository. It contains all the info
> > about the jobs, events, blackouts, etc for every monitored target
> > (db, listener, app server, etc). The data in the target db (AWR) is
> > the performance metrics for that particular db.
> >
> > If you install R2 with a new db you'll lose everything in your
> > current sysman schema and you'll have to recreate it all. This may
> > actually be easier than converting all the data from R1 depending on
> > how much data there is and how reliable the upgrade (R1 to R2)
> > process is. We will be upgrading to R2 when it is released for
> > windows and may take this approach since we don't have many targets
> > currently.
> >
> > Joe
> >
> > Amit Verma wrote:
> >> Okay, another question:
> >>
> >> Since EM 10gR2 (Grid Control) stores all the information inside the
> >> target database (AWR), is it worth upgrading and copying the old
> >> repository database to the new hardware and database? Or can I just
> >> install GC with new database option? What does it contain? Does
> >> anyone know?
> >>
> >> Amit Verma
> >> Senior Oracle DBA
> >> University of Michigan ITCS
> >> Ph: 734-647-5790
> >>
> >> ------------------------------------------------------------------------
> >>
> >> *From:* Amit Verma [mailto:averma_at_umich.edu]
> >> *Sent:* Thursday, April 13, 2006 11:05 AM
> >> *To:* 'oracle-l_at_freelists.org'
> >> *Subject:* Grid Control upgrade
> >>
> >> I have OMS Grid control 10.1.0.3.0, with a repository database on
> >> Oracle Version 9.0.1.5.0 running on RHEL 3. I want to upgrade the
> >> OMS to 10.2.0.1 and move the OMS to a new hardware running the same
> >> OS platform and version RHEL3.
> >>
> >> I am thinking the following upgrade plan should work;
> >>
> >> 1. Install 10.2.0.1 GC on new hardware.
> >>
> >> 2. Keep auto discovery off.
> >>
> >> 3. Export/import data from old database to new database.
> >>
> >> 4. Turn auto discovery on.
> >>
> >> 5. Shutdown OMS on old machine and start on the new one.
> >>
> >> Does this sound reasonable? Has anyone any experience of this sort?
> >> Can anyone suggest any documents available that I can refer?
> >>
> >> -Amit.
> >>
> >> Amit Verma
> >> Senior Oracle DBA
> >> University of Michigan ITCS
> >> Ph: 734-647-5790
> >>
> >>
> > --
> > http://www.freelists.org/webpage/oracle-l
> >
> >
> >
> >
> >
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
Best regards,
Alex Gorbachev
--
http://www.freelists.org/webpage/oracle-l





--
http://www.freelists.org/webpage/oracle-l