当前位置:操作系统 > Unix/Linux >>

ORA-39126: 在KUPW$WORKER.PUT_DDLS [TABLE_STATISTICS]错误解决

ORA-39126: 在KUPW$WORKER.PUT_DDLS [TABLE_STATISTICS]错误解决
 
SQL> select * from v$version;
 
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production
CORE        11.2.0.1.0        Production
TNS for 32-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
 
详细错误如下:
impdp system/passwd direcotry=DATA_PUMP_DIR dumpfile=optdumpfile.dmp schemas=xxx remap_schema=xxx:yyy
 
Import: Release 11.2.0.1.0 - Production on 星期五 7月 1 16:10:51 2011
 
Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
;;; 
连接到: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
已成功加载/卸载了主表 "HOHHOTNMG"."SYS_IMPORT_SCHEMA_01" 
启动 "HOHHOTNMG"."SYS_IMPORT_SCHEMA_01":  hohhotnmg/******** dumpfile=nmg350627.DMP schemas=hohhot remap_schema=hohhot:hohhotnmg 
处理对象类型 SCHEMA_EXPORT/USER
ORA-31684: 对象类型 USER:"HOHHOTNMG" 已存在
处理对象类型 SCHEMA_EXPORT/SYSTEM_GRANT
处理对象类型 SCHEMA_EXPORT/ROLE_GRANT
处理对象类型 SCHEMA_EXPORT/DEFAULT_ROLE
处理对象类型 SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
处理对象类型 SCHEMA_EXPORT/TYPE/TYPE_SPEC
ORA-39083: 对象类型 TYPE 创建失败, 出现错误:
ORA-02304: 无效的对象标识符文字
失败的 sql 为:
CREATE TYPE "HOHHOTNMG"."TYPE_SPLIT"   OID 'E5FE032391B54FF19E15645AB2954C52' as table of varchar2(50)
处理对象类型 SCHEMA_EXPORT/SEQUENCE/SEQUENCE
处理对象类型 SCHEMA_EXPORT/TABLE/TABLE
处理对象类型 SCHEMA_EXPORT/TABLE/TABLE_DATA
. . 导入了 "HOHHOTNMG"."TAPP_RESOURCE"                 26.30 MB    1408 行
. . 导入了 "HOHHOTNMG"."TAPP_INFO_FILE"                17.67 MB      94 行
. . 导入了 "HOHHOTNMG"."TAPP_SCHEMA_BUTTON"            6.484 MB     782 行
 
              .................................................................
ORA-39126: 在 KUPW$WORKER.PUT_DDLS [TABLE_STATISTICS] 中 Worker 发生意外致命错误
ORA-06502: PL/SQL: 数字或值错误 
LPX-00225: end-element tag "HIST_GRAM_LIST_ITEM" does not match start-element tag "EPVALUE"
ORA-06512: 在 "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: 在 "SYS.KUPW$WORKER", line 8165
----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
33ACF770     18990  package body SYS.KUPW$WORKER
33ACF770      8192  package body SYS.KUPW$WORKER
33ACF770     15575  package body SYS.KUPW$WORKER
33ACF770      3945  package body SYS.KUPW$WORKER
33ACF770      8875  package body SYS.KUPW$WORKER
33ACF770      1649  package body SYS.KUPW$WORKER
2B712238         2  anonymous block
ORA-39126: 在 KUPW$WORKER.PUT_DDLS [TABLE_STATISTICS] 中 Worker 发生意外致命错误
ORA-06502: PL/SQL: 数字或值错误 
LPX-00225: end-element tag "HIST_GRAM_LIST_ITEM" does not match start-element tag "EPVALUE"
ORA-06512: 在 "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: 在 "SYS.KUPW$WORKER", line 8165
----- PL/SQL Call Stack -----
  object      line  object
  handle    number  name
33ACF770     18990  package body SYS.KUPW$WORKER
33ACF770      8192  package body SYS.KUPW$WORKER
33ACF770     15575  package body SYS.KUPW$WORKER
33ACF770      3945  package body SYS.KUPW$WORKER
33ACF770      8875  package body SYS.KUPW$WORKER
33ACF770      1649  package body SYS.KUPW$WORKER
2B712238         2  anonymous block
作业 "HOHHOTNMG"."SYS_IMPORT_SCHEMA_01" 因致命错误于 16:12:32 停止
 
 
 
FYI:mos
Applies to:
Oracle Server - Standard Edition - Version: 10.1.0.3 to 11.1.0.7 - Release: 10.1 to 11.1
Information in this document applies to any platform.
 
DataPump Import Including Statistics Terminates With Fatal Error ORA-39126, ORA-6502, LPX-225 End-Element Tag "HIST_GRAM_LIST_ITEM" [ID 878626.1]
 
Symptoms
 
DataPump import terminates with the following errors captured in the import log:
 
    ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS
                           [TABLE_STATISTICS]
    ORA-06502: PL/SQL: numeric or value error
    LPX-00225: end-element tag "HIST_GRAM_LIST_ITEM" does not match start-element tag
                        "EPVALUE"
    ORA-06512: at "SYS.DBMS_SYS_ERROR"
    ORA-06512: at "SYS.KUPW$WORKER"
Cause
The statistics included in the import may be malformed.
Solution
 
To work around this issue, repeat either the expdp task or the impdp task using the EXCLUDE=STATISTICS parameter.  After import, regenerate the statistics for the imported objects on the target database using the DBMS_STATS package.
 
CopyRight © 2022 站长资源库 编程知识问答 zzzyk.com All Rights Reserved
部分文章来自网络,