Re: Question on Installing Oracle.

One thing that got lost here was that IF you do use the database creation assistant at install, or afterwards, you can change quite a bit about the system tablespace. It's probably a bad idea but you can do it.

Van

"Kev.-" <java2e_at_yahoo.com> wrote in message news:3b01a03b.3228282_at_ns1.nothingbutnet.net...
> Hello Howard,
>
> >Who cares if it's too small? Autoextend is set to on by default (for
> >SYSTEM), and so when it needs more space, you get it. You haven't been
 daft
> >enough to stop it autoextending, have you? SYSTEM must never run out of
> >space.
> No I am not daft enough to do that. BUt when I query to see the
> extents it shows that the system and catalog are well over 300
> extents. This just seems like alot of extents to me and it is getting
> worse by the day.
>
>
> The system has its own tablespace and nothing is sharing it. I do
> know that TextMedia is being used and massive inserts and deletions
> are being done on a daily basis. The system has become much slower
> than when installed about 5 months ago.
>
>
> >You *do* know about tablespace default storage clauses and how to assign
> >tables to any named tablespace, don't you?
> Of course.
>
> next, pctincrease, initial etc... Set the tablespace, nologging,
> nocaching, etc...
>
> Look I am not a complete idiot and again the system tablespace has
> nothing in it except system.
>
> Also remember that when database are fragmented that you can lose 20+%
> in performance.
>
> Again thank you very much for you reply.
>
> On Tue, 15 May 2001 23:01:37 +1000, "Howard J. Rogers"
> <howardjr_at_www.com> wrote:
>
> >"Kev.-" <java2e_at_yahoo.com> wrote in message
> >news:3b007d89.13855863_at_ns1.nothingbutnet.net...
> >> Hello All,
> >>
> >> I need to re-install oracle without the installer as it makes the
> >> database pretty much useless except for playing around with it. Where
> >> can I find dierctions on how to do it by hand.
> >>
> >
> >First off, what the rest of your post indicates that it is not a
> >reinstallation of Oracle that you need, but that you dislike the way the
> >Installer bungs a default database on whose setup and settings you
 dislike.
> >You *can* disable the installation of said database at the installation,
 and
> >create your own. You just have to read the wizard screens carefully,
 that's
> >all.
> >
> >> What files to run, etc...
> >>
> >> For example witht the installer the system tablspace is too small and
> >> it always gets fragmented due to the initial and next are set just to
> >> small.
> >>
> >
> >Oh Lord. Another one that thinks they know more about organising the
 SYSTEM
> >tablespace than Oracle does.
> >
> >Who cares if it's too small? Autoextend is set to on by default (for
> >SYSTEM), and so when it needs more space, you get it. You haven't been
 daft
> >enough to stop it autoextending, have you? SYSTEM must never run out of
> >space.
> >
> >"It always gets fragmented". There's only one thing that causes
> >fragmentation, and that's dropping objects from a tablespace (Oh, ok
 then,
> >and odd sized extents, too). What on earth are you dropping from SYSTEM?
> >There should be minimal activity of that sort on SYSTEM, and hence
> >fragmentation should be minimal.
> >
> >Yes, immediately after install, SYSTEM does show evidence of
 fragmentation.
> >It's minor, but it's there. Do you care?? What's the issue with
> >fragmentation anyway. OK, I'll tell you. It's a waste of space, that's
> >what. How big is the biggest SYSTEM tablespace I've ever seen?? 400Mb.
 If
> >even 10% of that was fragmented, that would be a whole massive 40 Mb
 you'd
> >save by curing/preventing fragmentation. Like I say: why on Earth
 bother?
> >
> >"Initial and next are set just to[o] small". Who says? Since the only
> >thing that should be in SYSTEM are the data dictionary tables etc, are
 you
> >utterly confident that you can say that the extent sizes for those tables
> >are too small? I doubt it.
> >
> >> Please help anyone as I am in dire need of doing this ASAP.
> >>
> >
> >No you're not. Trust me. What you are in dire need of is understanding
> >what SYSTEM is for, and (I think more importantly) what SYSTEM is NOT
 for.
> >If you are seriously worried about fragmentation in SYSTEM with good
 cause,
> >it suggests to me that you have allowed a million and one things to
 reside
> >in SYSTEM which should never, ever see the insides of that particular
> >tablespace in the first place. So what you *really* need is to learn how
 to
> >protect SYSTEM from invasion by objects which belong elsewhere.
> >
> >Otherwise, forget it. Oracle knows best how to deal with SYSTEM, and
 I've
> >yet to see anyone make a noticeable improvement on database performance
 by
> >hacking it around in the way you suggest might be appropriate.
> >
> >It isn't appropriate at all.
> >
> >You *do* know about tablespace default storage clauses and how to assign
> >tables to any named tablespace, don't you?
> >
> >Regards
> >HJR
> >
> >
> >
> >
> >
> >
> >
> >> Thanks,
> >>
> >> Kev.-
> >
> >
>
Received on Tue May 15 2001 - 17:00:00 CDT