My Oracle Support Banner

DataPump Import (IMPDP) Reports ORA-1 When Processing SCHEMA_EXPORT/STATISTICS/MARKER (Doc ID 2277109.1)

Last updated on JULY 27, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.1.0.2 [Release 12.1]
Oracle Database - Standard Edition - Version 12.1.0.1 to 12.1.0.2 [Release 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

DataPump import fails due to violation of unique constraint when:

...
Processing object type SCHEMA_EXPORT/STATISTICS/MARKER
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.STATS_LOAD [MARKER]
ORA-00001: unique constraint (SYS.PK_COL_GROUP_USAGE$) violated
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 11265
...

The generated trace file shows the error is raised for a merge into sys.col_group_usage$ data dictionary table:

----- Error Stack Dump -----
ORA-00001: unique constraint (SYS.PK_COL_GROUP_USAGE$) violated
----- Current SQL Statement for this session (sql_id=dv4y5yuq0q8tu) -----
merge into sys.col_group_usage$ m
using (
select * from (
select dbms_stats_internal.get_objnum(c5, c1, null, null,'TABLE') obj#,
s.flags, d1, to_char(cl1) cl1
from "SYS"."IMPDP_STATS" s, (select distinct object_type, base_object_schema, base_object_name from "<SCHEMA_NAME>"."SYS_IMPORT_FULL_01" where process_order > 0 and duplicate = 0
and object_type in ('TABLE_STATISTICS', 'INDEX_STATISTICS')
and processing_status = 'C' and processing_state in ('R','W') ) l
where object_type = 'TABLE_STATISTICS' and
s.type = 'G' and
s.c5 = l.base_object_schema and
s.c1 = l.base_object_name ) where obj# > 0)src
on (src.obj# = m.obj#)
when matched then
update set m.flags = src.flags, timestamp = d1, cols = cl1
when not matched then
insert (obj#, flags, timestamp, cols)
values (src.obj#, src.flags, src.d1, src.cl1)
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0x6f517d88 16349 package body SYS.DBMS_STATS_INTERNAL
0x7063d170 49566 package body SYS.DBMS_STATS
0x7063d170 49665 package body SYS.DBMS_STATS
0x706c2ee8 24270 package body SYS.KUPW$WORKER
0x706c2ee8 20690 package body SYS.KUPW$WORKER
0x706c2ee8 4545 package body SYS.KUPW$WORKER
0x706c2ee8 12063 package body SYS.KUPW$WORKER
0x706c2ee8 2081 package body SYS.KUPW$WORKER
0x6c534240 2 anonymous block

Call stack looks like:

 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.