Re: Oracle Enterprise Data Repository - Help!

Thankyou, I see whats going on now.....think it must just have been black box syndrome!

cheers for the help.

"Quarkman" <quarkman_at_nowhere> wrote in message news:<3efe8de0$0$30823$afc38c87_at_news.optusnet.com.au>...
> "amani" <amanclark_at_yahoo.co.uk> wrote in message
> news:ddbedb82.0306260708.a3419d7_at_posting.google.com...
> > Hi there,
> >
> > Can anyone give me advice on what i need to do to set up the data
> > repository for oracle enterprise? I'm afraid i am something of a
> > novice to this and for various reasons have been given this.
> >
> > I have four databases at the moment and my tnsnames.ora is configured
> > as i can use the visual studio with no problems. I just can't seem to
> > get my head around this repository thing, can it be set up on a
> > workstation or does it need to be a server? Any help would be
> > appreciated..... I'm not familiar with most of this stuff.
> >
> > Thanks
> >
> > amani
>
>
> What's not to understand?
>
> The repository for Enterprise Manager is just a bunch of tables stored in a
> database somewhere, in which details of what jobs/events have been scheduled
> are stored.
>
> If you run the Enterprise Manager configuration assistant, it will actually
> propose to create you a working database into which this repository can be
> dropped (or, in plain English, within which the necessary tables can be
> created).
>
> Otherwise, you can persuade the EMCA that you've already created an
> appropriate database (use Database Configuration Assistant and select any of
> the templates) and have the repository created in that.
>
> So I'm afraid I don't understand the confusion.
>
> The idea of the repository is that it is in a database to which you have
> ready access, so it's probably more appropriate to create it on a
> workstation than on a server... unless you have half a dozen DBAs who all
> want to access EM simultaneously.
>
> As for how you get started, and thus eliminate the confusion you're
> suffering, fire up EMCA on a workstation to which you have easy access and
> which has had the complete Oracle stuff (not just the Client) installed.
> Select to create a new database, call it OEMREP, and let te wizard do its
> stuff. Since you are creating a bunch of tables, someone needs to own them
> (the 'repository owner' or the OEM schema owner). Pick a username such as
> REPOWNER... you'll never actually log in as this user any way: it's merely
> an account to own the repository tables.
>
> Then you need to start the Management Server process (or, Management Server
> service on NT/W2K/WXP): on Unix, you do oemctl start and on windows you
> click the "play" button for the Management Server service (hint: mentioning
> an O/S would help whenever you post).
>
> With the Server started, you can log in to it. Username = SYSMAN,
> password=OEM_TEMP.
>
> With that done, click Navigate- Discover Nodes, type in the name of your
> server that has the real database you want to manage, and you're off (or
> should be: the Agent needs to be running on the node you specify, and the
> LISTENER.ORA needs to have a static SID_LIST, rather than rely on just
> automatic instance registration).
>
> ~QM
Received on Mon Jun 30 2003 - 02:46:37 CDT