How to move Oracle Spatial objects from SYSAUX tablespace to a user defined tablespace
(Doc ID 1119758.1)
Last updated on APRIL 01, 2020
Applies to:Oracle Spatial and Graph - Version 10.2.0.4 and later
Information in this document applies to any platform.
***Checked for relevance on 01-Aug-2012***
Starting in Oracle 10g, a new default tablespace was added to the Oracle database.
The SYSAUX tablespace is used to store Oracle components that are not considered part of
the Oracle database internal engine, but that are considered as additional components.
These 'add ons' include Oracle options such as Streams, Ultrasearch, and Oracle Spatial.
Prior to Oracle 10g, some of these components were either stored in their own tablespaces,
or were stored in the SYSTEM tablespace.
From Oracle 10g on, the SYSAUX tablespace became the default location for all component
installations, including Oracle Spatial objects.
More information on the SYSAUX tablespace can be found here:
<Note 243246.1> SYSAUX Tablespace in Oracle 10g and higher
In Oracle 10g, Oracle Spatial objects used such a small amount of space that having the
objects in the SYSAUX tablespace did not present any issues.
In Oracle 11g, Oracle Spatial added the ability to manipulate DICOM objects which could result in a larger amount of space now being used by the Oracle Spatial objects.
With this change, a user might want to move the Oracle Spatial objects to a different tablespace.
A procedure has been created to move Spatial objects from SYSAUX to a user defined tablespace.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document