Is This Content Helpful?
We're glad to know this article was helpful.
The spatial index segments for a feature class, using ESRI's spatial type for Oracle, do not use the storage parameters from the DBTUNE table.
The spatial index creates the following objects in the database:
This is a known limitation.
When the Index Organized Table and index are created, the storage parameters in the DBTUNE are ignored; therefore, each object is created in the user's default tablespace.
** This has been fixed in ArcSDE 9.2 Service Pack 4. **
Use Oracle to alter the storage parameters for these objects, or use the MOVE command to move the objects to a different tablespace.
SELECT table_name, geom_id
FROM sde.st_geometry_columns WHERE table_name = '<table_name_wanted>';
ALTER TABLE s<n>_idx$ MOVE TABLESPACE <tablespace>;
ALTER INDEX s<n>$_ix2 REBUILD TABLESPACE <tablespace>;