Forum Stats

  • 3,751,473 Users
  • 2,250,366 Discussions


Can a Materialized View's primary key be moved to a different tablespace?

Donbot Member Posts: 97
edited Aug 29, 2012 12:18PM in General Database Discussions
I created a materialized view with REFRESH FAST WITH PRIMARY KEY, which I assume generated its own PK for the materialized view (well, something certainly did, and it wasn't me); however, I did not include USING INDEX TABLESPACE <tablespace>, so the PK was generated in the same tablespace as the materialized view itself. The "problem" is, this particular database has a separate tablespace into which all of the indexes are supposed to go.

Is there any way, short of dropping and recreating the materialized view (which took 24 hours in the first place), to move the system-generated PK to a different tablespace?

For that matter, is there a reason why I wouldn't want to do this?


This discussion has been closed.