ed.stevens_at_home.com wrote:
>
> When we first stated setting up our Oracle databases, neither of our
> DBAs had any Oracle experience (I was just coming into DBA from apps,
> the other was coming to Oracle from DB2), so we were feeling our way
> along. After a few iterations and a lot of reading (and having a few
> databases already in production) we reviewed what we had done and came
> up with some standards, but they were still from a position of a lot of
> ignorance. That brings us to where we are today, and my question.
>
> While we knew to make data and index tablespaces for the application
> data, we still defaulted user SYSTEM to the system tablespace.
> Everything I'm reading is telling me that only SYS should own objects
> in the system tablespace. My partner is very much a "if it ain't
> broke, don't fix it" person, and I'm having a difficult time convincing
> him that we should make this change -- creating a TOOLS tablespace and
> moving all of SYSTEM's objects to it. Everything is saying this is
> "best" practice, but nothing is really explaining "why" well enough to
> make a convincing argument.
>
> Anyone want to help me make the case?
>
> - Ed Stevens
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Ask him if he knows what happens when the system tablespace fills
up. Then tell him that, since he is the one that doesn't want it fixed
he can be the guy that gets to come in a 3:00 AM to fix things when they
break. (I think it is Murphy's Law #39 -- The system will crash and
the
database will need rebuilding only when running very large time critical
jobs between the hours of 1:30 and 2:20 AM local time.)
--
Jerry Gitomer
Once I learned how to spell DBA, I became one.
Received on Thu Jan 27 2000 - 23:47:06 CST
