OATM migration leaves WF_CONTROL objects in the old tablespace (Doc ID 418238.1)

Last updated on JANUARY 12, 2016

Applies to:

Oracle Application Object Library - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]
Information in this document applies to any platform.
***Checked for relevance on 10-April-2013***

Symptoms

OATM migration terminates successfully, but some AQ object related to WF_CONTROL was left in the old tablespace. That can be checked running:

select segment_name, segment_type from dba_segments where tablespace_name ='APPLSYSD';
SEGMENT_NAME                       SEGMENT_TYPE
------------------------------         ------------------
SYS_IL0002889820C00006$$     LOBINDEX
SYS_LOB0002889820C00006$$ LOBSEGMENT

select OWNER, TABLE_NAME from dba_lobs  where SEGMENT_NAME in  ('SYS_LOB0002889820C00006$$', 'SYS_IL0002889820C00006$$')
OWNER              TABLE_NAME 
-----------------  ------------------------------
APPLSYS            AQ$_WF_CONTROL_D

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