Index Corruption ??

From: <stuco_at_mailcity.com>
Date: Mon, 21 Sep 1998 19:30:06 GMT
Message-ID: <6u69fs$j7l$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

[Quoted] -----== 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 - 21:30:06 CEST

Original text of this message