<SPAN
class=882210316-03072001>Hi All...
<SPAN
class=882210316-03072001>
<SPAN
class=882210316-03072001>I need to add my 2-cent's worth to this thread.
At the 8i (8.1.5) level,
<SPAN
class=882210316-03072001>we noticed that some SYSTEM tables were throwing lots
(really...LOTS) of
<SPAN
class=882210316-03072001>extents. I know..I know...lots of extents aren't
necessarily a bad thing.
<SPAN
class=882210316-03072001>But when I look at the SYSTEM tablespace and see
objects with 2,000-3,000
<SPAN
class=882210316-03072001>extents I just can't stand it!
<SPAN
class=882210316-03072001>
<SPAN
class=882210316-03072001>So, we stepped back and through trial and error (and
this is a secret!
<SPAN
class=882210316-03072001>Don't tell Oracle!) we modified SQL.BSQ. Now our
8i databases all look
<SPAN
class=882210316-03072001>'normal'. Yes, they still add extents, but now
the NEXTEXTENT size is
<SPAN
class=882210316-03072001>larger so I get fewer extents even with PCTINCREASE
0.
<SPAN
class=882210316-03072001>
<SPAN
class=882210316-03072001>I figure what we've done here would <FONT
color=#0000ff face="Courier New" size=2>not
necessarily work the same for
<SPAN
class=882210316-03072001>some of the places I've worked before because the
application <FONT color=#0000ff face="Courier New"
size=2>mix is
<SPAN
class=882210316-03072001>different. <FONT color=#0000ff face="Courier New"
size=2>Hey...it works for us. Build a
sandbox. Try it. YMMV.
<SPAN
class=882210316-03072001>
<SPAN
class=882210316-03072001>Mike
---
<FONT color=#0000ff face="Courier New"
size=2>===========================================================================
Michael P.
Vergara
| I’ve got a PBS mind in an MTV world
Oracle
DBA
|
Guidant
Corporation
|
<FONT face=Tahoma
size=2>-----Original Message-----From: Koivu, Lisa
[mailto:lisa.koivu_at_efairfield.com]Sent: Tuesday, July 03, 2001 9:12
AMTo: Multiple recipients of list ORACLE-LSubject: RE:
Extent size for system tablespace
Justin,
Do not change the way Oracle sets up
the system tablespace. Let it do it's thing. I have never had a
problem with it other than to resize next extents for certain objects from
time to time, but that's rare.
HTH <FONT color=#0000ff
face=Arial size=2>Lisa Koivu <FONT color=#0000ff face=Arial
size=2>Extreeeeeemely Bored Janitor (aka dba) <FONT color=#0000ff
face=Arial size=2>Ft. Lauderdale, FL, US
-----Original Message----- <FONT
face=Arial size=1>From: <FONT face=Arial
size=1>Justin Coleman [SMTP:jd_coleman_ora1_at_hotmail.com] <FONT
face=Arial size=1>Sent: <FONT face=Arial
size=1>Tuesday, July 03, 2001 11:51 AM <FONT face=Arial
size=1>To: <FONT face=Arial
size=1>Multiple recipients of list ORACLE-L <FONT face=Arial
size=1>Subject: <FONT
face=Arial size=1>Extent size for system tablespace
Experts,
From an earlier e-mail, I found out that LMT was
not possible with the SYSTEM
tablespace. Thanks for that info. So if using Data Dictionary
managed tablespaces for the SYSTEM
tablespace, when setting up a new <FONT face=Arial
size=2>database, should you change the default extent size for the system
space and change pctincrease from 50%
down to 0%?
Cheers for any help in advance. <FONT
face=Arial size=2>Justin
Received on Tue Jul 03 2001 - 11:22:26 CDT
