maxextents unlimited - value in dba_tables, dba_indexes

From: Cunningham, Gerald <Gerald.Cunningham_at_usi.net>
Date: Wed, 28 May 2003 08:15:29 -0800
Message-ID: <F001.005A453C.20030528081529@fatcity.com>

Hi all,  

I have a database where all tables and indexes have maxextents set to unlimited. Why, in dba_tables, do some tables have a null value for maxetents and some have a value of 2147483645?  

An index I just modified (previous value of maxextents was 249) now has a null value for maxextents:  

SQL> alter index app_owner.index1 storage (maxextents unlimited);

Index altered.

SQL> select owner, index_name, max_extents from dba_indexes   2 where owner = 'APP_OWNER' and index_name = 'INDEX1';

OWNER                          INDEX_NAME

MAX_EXTENTS

------------------------------ ------------------------------
-----------
APP_OWNER                       INDEX1

 

It seems that some of the objects that have maxextents = null are partitioned, but not all. Anybody have an explanation??  

Thanks!  

• Jerry

Jerry Cunningham
Principal Database Engineer
Enterprise Applications
USi
gerald.cunningham_at_usi.net  

Office 410.897.3084

Cell      443.994.7359
SMS       4439947359_at_mobile.att.net
AIM       cunninghamjerryc
 
 

--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author: Cunningham, Gerald
  INET: Gerald.Cunningham_at_usi.net

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Wed May 28 2003 - 11:15:29 CDT