After Migration To Oatm R-tree Index Tables Remain In Old Tablespaces (Doc ID 957815.1)

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

Symptoms

After an OATM tablespace migration, the following tables remain in the old tablespaces:

'MDRT_8BEA39$';
'MDRT_8BEA40$'
'MDRT_8C29EE$'
'MDRT_8C29ED$'

These objects do not appear in the SDO_INDEX_METADATA_TABLE, and appear to be orphan objects.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms