Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Index Corruption ??
A copy of this was sent to stuco_at_mailcity.com
(if that email address didn't require changing)
On Mon, 21 Sep 1998 19:28:59 GMT, you wrote:
>I wanted to check the validity of something an old Oracle guru once told me.
>
>He says, "... in very large database indexing, be sure that your MAXEXTENTS
>parameter is not more than what the index tablespace will actually hold when
>full. This will corrupt your indexes based on how the b-tree indexing works"
>
> Example: 100MB Index Tablespace
> 10 MB Initial
> 5 MB Next
> 19 MAXEXTENTS (not 255 or 999)
>
>Is this true or is it just bunk?!?! If it is true, why? I'm trying to set my
bunk. also, in a 100m tablespace you won't get 100m -- there is overhead for segment management and such
SQL> create tablespace demo datafile '/user2/ora7321/oradata/o7321/demo.dbf' size 10m;
Tablespace created.
SQL>
SQL> create table demo_tbl ( x int ) tablespace users;
Table created.
SQL> create index demo_idx on demo_tbl(x) 2 storage ( initial 1m next 1m pctincrease 0 minextents 10 ) tablespace demo; create index demo_idx on demo_tbl(x)
*
So, it created the index with 9 extents because it could not make that 10'th one in there...
>maxextents and I'm wondering how much calculation needs to go into this
>process.
>
>Thanks again, People of the Oracle Underworld!
>
>Stuart Cowen
>Paladin Consulting - Dallas
>
>-----== Posted via Deja News, The Leader in Internet Discussion ==-----
>http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum
Thomas Kyte
tkyte_at_us.oracle.com
Oracle Government
Herndon VA
--
http://govt.us.oracle.com/ -- downloadable utilities
Anti-Anti Spam Msg: if you want an answer emailed to you, you have to make it easy to get email to you. Any bounced email will be treated the same way i treat SPAM-- I delete it. Received on Mon Sep 21 1998 - 14:53:39 CDT
![]() |
![]() |