暂无图片
19c 数据泵导出失败 ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CONFIGURE_METADATA_UNLOAD
我来答
分享
 祁
2024-10-31
19c 数据泵导出失败 ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CONFIGURE_METADATA_UNLOAD

19c 19.9.0.0 数据泵导出失败 NOCDB 模式,有INVALID的对象。找遍全网都无正确解决方案,

sys@ONELAB 23:13:28> SELECT NAME,cdb FROM v$database;

NAME CDB
-------------------------------------------------------------------------------- ------
ONELAB NO

Elapsed: 00:00:00.01


[oracle@QZLIMSDB:/home/oracle]$ expdp zwdba/***@10.199.11.108/ONELAB DUMPFILE=LIMS16.dmp logfile=LIMS16.log DIRECTORY=DATA_PUMP_DIR schemas=HUB PARALLEL=2

Export: Release 19.0.0.0.0 - Production on Thu Oct 31 23:08:34 2024
Version 19.9.0.0.0

Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.

Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Starting "ZWDBA"."SYS_EXPORT_SCHEMA_35": zwdba/********@10.130.11.108/ONELAB DUMPFILE=LIMS16.dmp logfile=LIMS16.log DIRECTORY=DATA_PUMP_DIR schemas=HUB PARALLEL=2
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CONFIGURE_METADATA_UNLOAD []
ORA-04063: package body "SYS.DBMS_METADATA" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_METADATA"

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 12617
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 9749

----- PL/SQL Call Stack -----
object line object
handle number name
0x184041e80 33543 package body SYS.KUPW$WORKER.WRITE_ERROR_INFORMATION
0x184041e80 12651 package body SYS.KUPW$WORKER.DETERMINE_FATAL_ERROR
0x184041e80 10244 package body SYS.KUPW$WORKER.CONFIGURE_METADATA_UNLOAD
0x184041e80 3838 package body SYS.KUPW$WORKER.UNLOAD_METADATA
0x184041e80 13746 package body SYS.KUPW$WORKER.DISPATCH_WORK_ITEMS
0x184041e80 2439 package body SYS.KUPW$WORKER.MAIN
0x142b8a8b0 2 anonymous block

DBMS_LOB.CREATETEMPORARY v_dml_xml_clob
KUPW: In UNLOAD_METADATA
KUPW: Flags: 128
KUPW: Start sequence number:
KUPW: End sequence number:
KUPW: **NOT** Doing Parallel metadata
KUPW: In procedure CONFIGURE_METADATA_UNLOAD
KUPW: Phase: Filter Name: BEGIN_AFTER Filter Value:
DBMS_METADATA.OPEN19.0.0.0.0
KUPW: In procedure DETERMINE_FATAL_ERROR with ORA-04063: package body "SYS.DBMS_METADATA" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_METADATA"

ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CONFIGURE_METADATA_UNLOAD []
ORA-04063: package body "SYS.DBMS_METADATA" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_METADATA"

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 12617
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 9749

----- PL/SQL Call Stack -----
object line object
handle number name
0x184041e80 33543 package body SYS.KUPW$WORKER.WRITE_ERROR_INFORMATION
0x184041e80 12651 package body SYS.KUPW$WORKER.DETERMINE_FATAL_ERROR
0x184041e80 10244 package body SYS.KUPW$WORKER.CONFIGURE_METADATA_UNLOAD
0x184041e80 3838 package body SYS.KUPW$WORKER.UNLOAD_METADATA
0x184041e80 13746 package body SYS.KUPW$WORKER.DISPATCH_WORK_ITEMS
0x184041e80 2439 package body SYS.KUPW$WORKER.MAIN
0x142b8a8b0 2 anonymous block

DBMS_LOB.CREATETEMPORARY v_dml_xml_clob
KUPW: In UNLOAD_METADATA
KUPW: Flags: 129
KUPW: Start sequence number:
KUPW: End sequence number:
KUPW: **NOT** Doing Parallel metadata
KUPW: In procedure CONFIGURE_METADATA_UNLOAD
KUPW: Phase: Filter Name: BEGIN_AFTER Filter Value:
DBMS_METADATA.OPEN19.0.0.0.0
KUPW: In procedure DETERMINE_FATAL_ERROR with ORA-04063: package body "SYS.DBMS_METADATA" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_METADATA"

Job "ZWDBA"."SYS_EXPORT_SCHEMA_35" stopped due to fatal error at Thu Oct 31 23:08:38 2024 elapsed 0 00:00:03

[oracle@QZLIMSDB:/home/oracle]$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Thu Oct 31 23:13:25 2024
Version 19.9.0.0.0

Copyright (c) 1982, 2019, Oracle. All rights reserved.


Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.9.0.0.0


select owner,object_name,object_type,status from dba_objects where status = 'INVALID';
"SYS" "KU$_PRIM_COLUMN_VIEW" "VIEW" "INVALID"
"SYS" "KU$_COLUMN_VIEW" "VIEW" "INVALID"
"SYS" "KU$_PCOLUMN_VIEW" "VIEW" "INVALID"
"SYS" "KU$_P2TPARTCOL_VIEW" "VIEW" "INVALID"
"SYS" "KU$_SP2TPARTCOL_VIEW" "VIEW" "INVALID"
"SYS" "KU$_P2TCOLUMN_VIEW" "VIEW" "INVALID"
"SYS" "KU$_SP2TCOLUMN_VIEW" "VIEW" "INVALID"
"SYS" "KU$_HTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_PHTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_FHTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_2_FHTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_PFHTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_ACPTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_PARTITION_VIEW" "VIEW" "INVALID"
"SYS" "KU$_SUBPARTITION_VIEW" "VIEW" "INVALID"
"SYS" "KU$_IOTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_PIOTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_XMLSCHEMA_VIEW" "VIEW" "INVALID"
"SYS" "KU$_EXP_XMLSCHEMA_VIEW" "VIEW" "INVALID"
"SYS" "KU$_NT_PARENT_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_1_HTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_1_PHTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_1_FHTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_1_PFHTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_1_IOTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_1_PIOTABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_VIEW_VIEW" "VIEW" "INVALID"
"SYS" "KU$_11_2_VIEW_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_VIEW_H_VIEW" "VIEW" "INVALID"
"SYS" "KU$_ZM_VIEW_H_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_VIEW_PH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_ZM_VIEW_PH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_VIEW_FH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_ZM_VIEW_FH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_VIEW_PFH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_ZM_VIEW_PFH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_VIEW_IOT_VIEW" "VIEW" "INVALID"
"SYS" "KU$_ZM_VIEW_IOT_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_VIEW_PIOT_VIEW" "VIEW" "INVALID"
"SYS" "KU$_ZM_VIEW_PIOT_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_ZONEMAP_H_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_ZONEMAP_PH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_ZONEMAP_FH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_ZONEMAP_PFH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_ZONEMAP_IOT_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_ZONEMAP_PIOT_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_VIEW_LOG_H_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_VIEW_LOG_PH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_VIEW_LOG_FH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_M_VIEW_LOG_PFH_VIEW" "VIEW" "INVALID"
"SYS" "KU$_CLUSTER_VIEW" "VIEW" "INVALID"
"SYS" "KU$_QTAB_STORAGE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_QUEUE_TABLE_VIEW" "VIEW" "INVALID"
"SYS" "KU$_HISTGRM_VIEW" "VIEW" "INVALID"
"SYS" "KU$_COL_STATS_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_1_TAB_COL_STATS_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_1_PTAB_COL_STATS_VIEW" "VIEW" "INVALID"
"SYS" "KU$_TAB_ONLY_STATS_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_1_TAB_ONLY_STATS_VIEW" "VIEW" "INVALID"
"SYS" "KU$_PTAB_STATS_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_1_PTAB_STATS_VIEW" "VIEW" "INVALID"
"SYS" "KU$_11_2_TAB_STATS_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_2_TAB_STATS_VIEW" "VIEW" "INVALID"
"SYS" "KU$_10_1_TAB_STATS_VIEW" "VIEW" "INVALID"
"SYS" "DBMS_METADATA" "PACKAGE BODY" "INVALID"
"XDB" "XDB_PV_TRIG" "TRIGGER" "INVALID"
"SYS" "DBMS_CUBE_ADVISE" "PACKAGE BODY" "INVALID"

我来答
添加附件
收藏
分享
问题补充
1条回答
默认
最新
aknight

参照https://www.modb.pro/db/52186 试试

以SYS用户的身份运行以下脚本以验证包并重新运行DataPump导入作业

SQL> $ORACLE_HOME/rdbms/admin/prvtmeti.plb

SQL> $ORACLE_HOME/rdbms/admin/prvtmetu.plb

SQL> $ORACLE_HOME/rdbms/admin/utlrp.sql

暂无图片 评论
暂无图片 有用 0
打赏 0
回答交流
Markdown


请输入正文
提交
相关推荐
Goldengate同步表delete从Oracle到Oracle但不同步每天定时清理源库过期数据delete的方案?
回答 4
已采纳
ogg可以过滤特定用户的操作,定时任务设置单独用户就可以了
expdp导出数据问题
回答 2
已采纳
expdp是服务端进程,断开了ssh连接也会在后台运行的
Oracle 11g 如何设置内存参数?
回答 6
已采纳
各位大佬,我添加了墨值悬赏,虽然没有多少,但是我希望回答这个问题的人能够言之有物
ogg的initload问题
回答 1
表上有主键或者唯一索引吗
ORACLE没有开审计可以从哪获取存储过程的调用记录?
回答 4
查ASH或logminor应该都可以吧。当然如果一步到位,方便查询,肯定是在procedure里写代码记录到日志表。
Oracle数据库 要在rac环境下处理dg的gap问题,已经把缺失的归档放到节点1的文件目录下了 ,是直接注册,还是需要把文件放到asm里?
回答 1
已采纳
如果放在备库的归档目录不用注册,自己会apply.其他目录则需要注册。
ORACLE用DB_LINK连接PG数据库,报错:ORA-28500,ORA-02063
回答 3
已采纳
pg中的表名,创建的时候,不加双引号时默认是小写;oracle中的查询sql,不加双引号时,默认会转换为大写。所以,就报这个错了
alert日志不更新
回答 2
Windows有很多未知问题,可以重启下操作系统(这是很多客户的常规操作)
telnet 服务器IP 1521端口是通的,但是访问不了Oracle数据库?
回答 1
已采纳
看一下监听,是不是设置IP黑/白名单
Oracle impdp按照用户导入,没有数据表的用户导入不了吗?
回答 3
可以的,他会自动创建的。
问题信息
请登录之后查看
邀请回答
暂无人订阅该标签,敬请期待~~