Re: Index Corruption ??

Try

MAXEXTENTS UNLIMITED

                   specifies that extents should automatically be
                   allocated as needed. You should not use this option
                   for rollback segments.

This is per Oracle's help facility in SQL*Plus.

Oracleguru
www.oracleguru.net
oracleguru_at_mailcity.com

stuco_at_mailcity.com wrote in article <6u69et$j62$1_at_nnrp1.dejanews.com>...
> 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
> 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
>
Received on Mon Sep 21 1998 - 16:41:24 CDT