Re: Materialized Views

Actually the object should be I_SNAP$_<MVName>. This is NOT the MV log. It is an unique index created by ORACLE when you create you MV with "ROWID". Specifying the tablespace for the index is easy, simply use the "using index" clause in your MV creation SQL. You can also specify storage clause if you wish.

The tricky part is the partitioning. According to ORACLE, you can simply drop this index and replace it with a partitioned one. The process is not very clear, to me, however. And I am not at all convinced that it is a good idea. I would think that since ORACLE uses the index internally to refresh MV, the partitioning of the index, if it is indeed beneficial to do so, should also be done internally.

skvaish_at_mybluelight.com (Shailandra) wrote in message news:<1a8bd3be.0209040855.1de90b98_at_posting.google.com>...
> When I am creating a Meterialized view it creates my MV and one
> ISNAP$_MVname object in the default tablespace. I am not creating
> materialized log myself. Is this the same as materialzed log? How do I
> specify its tablespace location in my create materialized view
> statement.
>
> My materialized view is partitioned. Can this object be partitioned as
> well and how to specify its tablespace location for each partitions.
>
> Thanks
Received on Thu Sep 05 2002 - 12:18:24 CEST