Re: New DB vs Sample?

Go ahead and create the new database get it to the state you are happy with it then get rid of the 'SAMPLE' one. Its all good practice.

I personally don't like having a Sample database around for anything other than playing with.

You don't have to have all the services running concurrently for both instances.

Regards
--
Kevin A Lewis (BOCM PAULS LTD - Animal Feed Manufacturer - Ipswich England)

                        <KevinALewis_at_HotMail.com>

The views expressed herein by the author of this document are not necessarily those of BOCM PAULS Ltd. Paul Woods <paulwoods_at_inter-intelli.com> wrote in message news:hW8C3.858$e4.1810_at_news1.iquest.net...
> I'm working with Oracle 8i on NT. When I installed, I allowed the sample
> database to be created. Then when I installed the Enterprise Manager, I
put
> the repository in this sample database.
>
> Now, after doing some experimenting with the sample database (nothing
> drastic, mind you), I'm ready to start setting up a "real" database to be
> put into production eventually. However, I've read that it's a good idea
to
> limit things to one instance per machine.
>
> So my questions are:
>
> 1. Should I simply use the sample database as is instead of creating a
new
> one? The problem here is that the db_block_size is 2K, and I'd like to
make
> it 8K, which I understand can only be done at creation.
>
> 2. Should I create a new database, and try to move my OEM repository? I
> would then remove the sample database. I guess my fear with this option
> would be that the sample database seems to have a lot of "goodies"-
> packages, etc. that I don't know if I would get automatically in the new
> one. Also, I have no idea how to move the OEM repository.
>
> 3. Or should I just go ahead and create the new database and stop
worrying
> about nothing?
>
> Thanks,
>
> Paul
>
>
>
>
Received on Mon Sep 13 1999 - 10:51:54 CDT