My Oracle Support Banner

LPX-00225 Element Tag Error When Import An Interval partitioned Table Using Datapump (Doc ID 959119.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 and later
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

Create Interval Partitioned Table Can Insert Bad Dictionary Interval Data During Datapump Import.
LPX-00225 element tag error occurs when impdp a partition table.

For example : -

$ impdp <user_name>/<password> directory=<dir_name> tables=<table_name> dumpfile=exp.dmp table_exists_action=append
...
Processing object type TABLE_EXPORT/TABLE/TABLE
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS []
ORA-6502: PL/SQL: numeric or value error
LPX-00225: end-element tag "CTIME" does not match start-element tag "INTERVAL_STR"
ORA-6512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-6512: at "SYS.KUPW$WORKER", line 7704
----- PL/SQL Call Stack -----
object line object
handle number name
0x329541a0 18051 package body SYS.KUPW$WORKER
0x329541a0 7736 package body SYS.KUPW$WORKER
0x329541a0 15263 package body SYS.KUPW$WORKER
0x329541a0 3766 package body SYS.KUPW$WORKER
0x329541a0 8370 package body SYS.KUPW$WORKER
0x2ce15d28 1 anonymous block
0x2fe3d000 1501 package body SYS.DBMS_SQL
0x329541a0 8201 package body SYS.KUPW$WORKER
0x329541a0 1477 package body SYS.KUPW$WORKER
0x2fe80078 2 anonymous block

ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS []
ORA-6502: PL/SQL: numeric or value error
LPX-00225: end-element tag "CTIME" does not match start-element tag
"INTERVAL_STR"
ORA-6512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-6512: at "SYS.KUPW$WORKER", line 7704

----- PL/SQL Call Stack -----
object line object
handle number name
0x329541a0 18051 package body SYS.KUPW$WORKER
0x329541a0 7736 package body SYS.KUPW$WORKER
0x329541a0 15263 package body SYS.KUPW$WORKER
0x329541a0 3766 package body SYS.KUPW$WORKER
0x329541a0 8370 package body SYS.KUPW$WORKER
0x2966acfc 1 anonymous block
0x2fe3d000 1501 package body SYS.DBMS_SQL
0x329541a0 8201 package body SYS.KUPW$WORKER
0x329541a0 1477 package body SYS.KUPW$WORKER
0x2fe80078 2 anonymous block
.
Job "EHATTA"."SYS_IMPORT_TABLE_01" stopped due to fatal error at 20:54:35


==> Here SQL like the following could cause trailing 0x00 in PARTOBJ$.INTERVAL_STR which can lead to subsequent errors during export / import etc..

create table <TABLE_NAME>
(<COLUMN_NAME1> number(12),
<COLUMN_NAME2> date
)
partition by range(<COLUMN_NAME2>)
interval(numtoyminterval(1, 'month'))
(partition p1 values less than (to_date('2000-01-01', 'YYYY-MM-DD')),
partition p2 values less than (to_date('2001-01-01', 'YYYY-MM-DD')),
partition p3 values less than (to_date('2001-07-01', 'YYYY-MM-DD')),
partition p4 values less than (to_date('2002-01-01', 'YYYY-MM-DD'))
);
insert into <TABLE_NAME> values(1000, to_date('2000-01-01', 'YYYY-MM-DD')) ;
commit ;

Changes

This issue is related with interval partitioning, which is introduced in 11g. It is not there in 10g or prior releases.

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.