Re: IOT - Tablespace

From: Howard J. Rogers <howardjr2000_at_yahoo.com.au>
Date: Sat, 23 Nov 2002 07:47:06 +1100
Message-ID: <MAwD9.81853$g9.230911@newsfeeds.bigpond.com>

It's blank because it doesn't actually exist.

When you say

create table blah (
col1 number constraint blah_col_pk primary key, col2 etc etc)
organization index...

...then what you've actually created is an index (in this case called blah_col1_pk) which is visible in user_indexes (or dba_indexes etc). The table 'blah' appears in user_tables, sure enough, because it exists logically. But physically, the only thing that exists is the index structure.

The null value for tablespace_name in user_tables is trying to tell you all of that.

Regards
HJR "RK" <rajXesh_at_hotmail.com> wrote in message news:548b9514.0211220648.24a390f_at_posting.google.com...
> Is there any reason why the tablespace_name in user_tables and
> all_tables is blank (empty) for an Index Organized Table.
>
> It shows up blank for partitioned tables too, but thats because each
> partition can be stored in different tablespaces. I can query
> user_segments with segment_name = <partitioned_table_name> to get the
> tablespace, but not for IOT
>
> Thanks
>
> -- rajXesh
Received on Fri Nov 22 2002 - 14:47:06 CST