After Migration To Oatm R-tree Index Tables Remain In Old Tablespaces
Last updated on FEBRUARY 08, 2017
Applies to:Oracle Spatial and Graph - Version 10.2.0.4 and later
Information in this document applies to any platform.
This problem can occur on any platform.
Checked for relevance on 24-Dec-2013
After an OATM tablespace migration, the following tables remain in the old tablespaces:
These objects do not appear in the SDO_INDEX_METADATA_TABLE, and appear to be orphan objects.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms