oracle数据库导出ORA-39127错误解决方案

arccatalog往oracle里粘贴空间数或数据备份还原报错 当使用arccatalog往oracle里粘贴空间数据或者数据泵命令导入导出数据报ora-29861:域索引标记为loading/failed/unusab ORA-39127: unexpected error from call to local_str := SYS.DBMS_EXPORT_EXTENSION.GET_DOMAIN_INDEX_METADATA('A202_IX1','CA 阅读详情

错误类型及描述:

expdp 导出表在表分析是开始出现报错。
ORA-39127: unexpected error from call to export_string :=SYS.DBMS_AQ_EXP_QUEUE_TABLES.INSTANCE_INFO_EXP('CAPTURE_QUEUE_T_ALL1','STRMADMIN',1,1,'11.02.00.00.00',newblock) 
ORA-01403: no data found
ORA-01403: no data found
ORA-06512: at "SYS.DBMS_AQ_SYS_EXP_ACTIONS", line 123
ORA-06512: at "SYS.DBMS_AQ_EXP_QUEUE_TABLES", line 20
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 9081

错误原因

1、用户SYS用户事物处于无效状态
2、用户SYS用户的事物被删除

3、存在无效的object

4、以前做过的流复制没有清理干净,残留下来的很多垃圾导致的无效object.

解决方法:

1、DELETE FROM exppkgact$ WHERE SCHEMA='EXFSYS';

2、用TOAD登入数据库,然后删除无效的object.

3、删除残余的流复制垃圾

Object Owner Cleanup
Log in as the user who owns the queue_table. (This username will replace the <schema> value  where referred to below.)

Within sqlplus


SQL> SELECT object_name, object_type FROM user_objects WHERE object_name like '%<QUEUE_TABLE_NAME>%';
where <QUEUE_TABLE_NAME> is replaced with the appropriate value.
Depending on what parts of the queue table remain you could see a number of different objects.

SELECT object_name, object_type FROM user_objects 
WHERE object_name like '%ALL1%' or object_name like '%ALL3%' or object_name like '%ALL2%';

1. Drop any views associated with <QUEUE_TABLE_NAME> via drop view ... .
DROP VIEW AQ$CAPTURE_QUEUE_T_ALL1_R;
DROP VIEW AQ$CAPTURE_QUEUE_T_ALL1;
DROP VIEW AQ$_CAPTURE_QUEUE_T_ALL1_F;
DROP VIEW AQ$CAPTURE_QUEUE_T_ALL1_S;


DROP VIEW AQ$CAPTURE_QUEUE_T_ALL2_R;
DROP VIEW AQ$CAPTURE_QUEUE_T_ALL2;
DROP VIEW AQ$_CAPTURE_QUEUE_T_ALL2_F;
DROP VIEW AQ$CAPTURE_QUEUE_T_ALL2_S;


DROP VIEW AQ$CAPTURE_QUEUE_T_ALL3_R;
DROP VIEW AQ$CAPTURE_QUEUE_T_ALL3;
DROP VIEW AQ$_CAPTURE_QUEUE_T_ALL3_F;
DROP VIEW AQ$CAPTURE_QUEUE_T_ALL3_S;

2. Drop any sequences associated with <QUEUE_TABLE_NAME> via drop sequence ... .
drop sequence AQ$_CAPTURE_QUEUE_T_ALL1_N;
drop sequence AQ$_CAPTURE_QUEUE_T_ALL2_N;
drop sequence AQ$_CAPTURE_QUEUE_T_ALL3_N;


3. ALTER SESSION SET EVENTS '10851 trace name context forever, level 2';


4. DROP TABLE <QUEUE_TABLE_NAME> CASCADE CONSTRAINTS;
DROP TABLE CAPTURE_QUEUE_T_ALL1 CASCADE CONSTRAINTS;
DROP TABLE CAPTURE_QUEUE_T_ALL2 CASCADE CONSTRAINTS;
DROP TABLE CAPTURE_QUEUE_T_ALL3 CASCADE CONSTRAINTS;


5. Repeat for all the following tables
DROP TABLE AQ$_<QUEUE_TABLE_NAME>_<X> CASCADE CONSTRAINTS;
where <X> is replaced by the appropriate value.


DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL1_H CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL1_G CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL1_C CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL1_D CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL1_I CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL1_S CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL1_T CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL1_L CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL1_P CASCADE CONSTRAINTS;


DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL2_H CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL2_G CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL2_C CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL2_D CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL2_I CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL2_S CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL2_T CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL2_L CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL2_P CASCADE CONSTRAINTS;


DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL3_H CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL3_G CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL3_C CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL3_D CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL3_I CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL3_S CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL3_T CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL3_L CASCADE CONSTRAINTS;
DROP TABLE AQ$_CAPTURE_QUEUE_T_ALL3_P CASCADE CONSTRAINTS;

SYSTEM User Cleanup
connect as system
1. SELECT schema, name, objno FROM SYSTEM.AQ$_QUEUE_TABLES WHERE name LIKE '%<QUEUE_TABLE_NAME>%';
take a note of the schema, objno, and name, for the relevant schema, if any is returned.


SELECT schema, name, objno FROM SYSTEM.AQ$_QUEUE_TABLES WHERE name IN ('CAPTURE_QUEUE_T_ALL1','CAPTURE_QUEUE_T_ALL2','CAPTURE_QUEUE_T_ALL3')


2. SELECT oid, eventid, table_objno, name FROM SYSTEM.AQ$_QUEUES WHERE name IN ('<QUEUE_NAME_1>','<QUEUE_NAME_2>',....) ;
take a note of the oids, table_objnos and names. The oid values, i.e, OID_1, etc., eventid and names, e.g. QUEUE_NAME_1, etc., will be used in the Data Dictionary Cleanup section.


SELECT oid, eventid, table_objno, name FROM SYSTEM.AQ$_QUEUES WHERE name IN ('CAPTURE_QUEUE_ALL1','CAPTURE_QUEUE_ALL2','CAPTURE_QUEUE_ALL3','AQ$_CAPTURE_QUEUE_T_ALL1_E','AQ$_CAPTURE_QUEUE_T_ALL2_E','AQ$_CAPTURE_QUEUE_T_ALL3_E') ;


3. DELETE FROM SYSTEM.AQ$_QUEUE_TABLES where objno=<objno from above>;


DELETE FROM SYSTEM.AQ$_QUEUE_TABLES where objno IN (SELECT objno FROM SYSTEM.AQ$_QUEUE_TABLES WHERE name IN ('CAPTURE_QUEUE_T_ALL1','CAPTURE_QUEUE_T_ALL2','CAPTURE_QUEUE_T_ALL3')
)


4. DELETE FROM SYSTEM.AQ$_QUEUES WHERE table_objno=<table_objno from above>;


DELETE FROM SYSTEM.AQ$_QUEUES WHERE table_objno IN (SELECT table_objno FROM SYSTEM.AQ$_QUEUES WHERE name IN ('CAPTURE_QUEUE_ALL1','CAPTURE_QUEUE_ALL2','CAPTURE_QUEUE_ALL3','AQ$_CAPTURE_QUEUE_T_ALL1_E','AQ$_CAPTURE_QUEUE_T_ALL2_E','AQ$_CAPTURE_QUEUE_T_ALL3_E') );


commit;


Data Dictionary Cleanup
connect as sys as sysdba


Find the owner# corresponding to the relevant <schema> from


select distinct o.owner# from obj$ o, user$ u where o.owner#=u.user# and u.name='<schema>';
This result will be referred to a <owner_num> in the statements below.


select distinct o.owner# from obj$ o, user$ u where o.owner#=u.user# and u.name='STRMADMIN';


86


Then


1. (a) and (b) are valid for all versions. (c) and (d) are valid only for 
9.2.0.1 and above.






Queues (type#24)
(a) SELECT obj#,name FROM SYS.OBJ$ where type# ='24' AND owner# = <owner_num> AND name IN ('<QUEUE_NAME_1>','<QUEUE_NAME_2>',....);
where <QUEUE_NAME_1>, etc., are those found from the select of queue names. 


SELECT obj#,name FROM SYS.OBJ$ where type# ='24' AND owner#='86' 
and name in('CAPTURE_QUEUE_ALL1','CAPTURE_QUEUE_ALL2','CAPTURE_QUEUE_ALL3','AQ$_CAPTURE_QUEUE_T_ALL1_E','AQ$_CAPTURE_QUEUE_T_ALL2_E','AQ$_CAPTURE_QUEUE_T_ALL3_E')


Rule Sets (type#46)
(b) SELECT obj#,name FROM SYS.OBJ$ WHERE type#=46 AND owner# = <owner_num> AND name LIKE '%QUEUE_NAME_1%';
where <QUEUE_NAME_1>, etc., are those found from the select of queue names. 


SELECT obj#,name FROM SYS.OBJ$ where type# =46 AND owner#=86
and name in('CAPTURE_QUEUE_ALL1_N','CAPTURE_QUEUE_ALL1_R','CAPTURE_QUEUE_ALL2_N','CAPTURE_QUEUE_ALL2_R','CAPTURE_QUEUE_ALL3_N','CAPTURE_QUEUE_ALL3_R')


Rules (type#59)
(c) SELECT obj#,name FROM SYS.OBJ$ WHERE type#=59 AND owner# = <owner_num> AND name LIKE '%QUEUE_NAME_1%';
where <QUEUE_NAME_1>, etc., are those found from the select of queue names. 


SELECT obj#,name FROM SYS.OBJ$ WHERE type#=59 AND owner# = 86 AND ctime >= to_date('20131124','yyyymmdd') and ctime < to_date('20131130','yyyymmdd')
order by ctime


Evaluation Context (type#=62)
(d) SELECT obj#,name FROM SYS.OBJ$ WHERE type#=62 AND owner# = <owner_num> AND name LIKE '%QUEUE_TABLE_NAME%';
where <QUEUE_TABLE_NAME> is that found previously. 


SELECT obj#,name FROM SYS.OBJ$ WHERE type#=62 AND owner# = 86 AND name IN('AQ$_CAPTURE_QUEUE_T_ALL1_V','AQ$_CAPTURE_QUEUE_T_ALL2_V','AQ$_CAPTURE_QUEUE_T_ALL3_V');




(b) DELETE FROM SYS.OBJ$ WHERE obj# IN (<obj#1>, <obj#2>, ...);
where <obj#1>, etc are all the obj# found from Step 1 (a).


DELETE FROM SYS.OBJ$ WHERE OBJ# IN (SELECT obj# FROM SYS.OBJ$ where type# ='24' AND owner#='86' 
and name in('CAPTURE_QUEUE_ALL1','CAPTURE_QUEUE_ALL2','CAPTURE_QUEUE_ALL3','AQ$_CAPTURE_QUEUE_T_ALL1_E','AQ$_CAPTURE_QUEUE_T_ALL2_E','AQ$_CAPTURE_QUEUE_T_ALL3_E')
)


Using the name values for Step 1 (c) above
execute DBMS_RULE_ADM.DROP_RULE('<schema>.<rule_name>',TRUE);


SELECT 'execute DBMS_RULE_ADM.DROP_RULE(''' || 'STRMADMIN.'  || name || ''',TRUE);' FROM SYS.OBJ$ WHERE type#=59 AND owner# = 86 AND ctime >= to_date('20131124','yyyymmdd') and ctime < to_date('20131130','yyyymmdd')
order by ctime
类似:
execute DBMS_RULE_ADM.DROP_RULE('STRMADMIN.CWREPORT_NAME74761',TRUE);




Using the name values for Step 1 (d) above
--如果无法清除,报错ORA-24170的错误,则执行下面的语句后再清除:
--ALTER SESSION SET EVENTS = '25475 TRACE NAME CONTEXT FOREVER, LEVEL 2';


execute DBMS_RULE_ADM.DROP_EVALUATION_CONTEXT('STRMADMIN.AQ$_CAPTURE_QUEUE_T_ALL1_V',TRUE);
execute DBMS_RULE_ADM.DROP_EVALUATION_CONTEXT('STRMADMIN.AQ$_CAPTURE_QUEUE_T_ALL2_V',TRUE);
execute DBMS_RULE_ADM.DROP_EVALUATION_CONTEXT('STRMADMIN.AQ$_CAPTURE_QUEUE_T_ALL3_V',TRUE);




3. DELETE FROM SYS.EXPACT$ WHERE owner='<schema>' AND name LIKE '%<QUEUE_TABLE_NAME>%';
4. DELETE FROM SYS.EXPACT$ WHERE owner='<schema>' AND name LIKE '%<QUEUE_NAME>%';
5. DELETE FROM SYS.NOEXP$ WHERE owner='<schema>' AND name LIKE '%<QUEUE_TABLE_NAME>%';
6. DELETE FROM SYS.NOEXP$ WHERE owner='<schema>' AND name LIKE '%<QUEUE_NAME>%';


commit;


select * from SYS.NOEXP$ WHERE owner='STRMADMIN' AND NAME IN ('AQ$_CAPTURE_QUEUE_T_ALL1_D','AQ$_CAPTURE_QUEUE_T_ALL1_P','AQ$_CAPTURE_QUEUE_T_ALL2_D','AQ$_CAPTURE_QUEUE_T_ALL2_P','AQ$_CAPTURE_QUEUE_T_ALL3_D','AQ$_CAPTURE_QUEUE_T_ALL3_P')


DELETE from SYS.NOEXP$ WHERE owner='STRMADMIN' AND NAME IN ('AQ$_CAPTURE_QUEUE_T_ALL1_D','AQ$_CAPTURE_QUEUE_T_ALL1_P','AQ$_CAPTURE_QUEUE_T_ALL2_D','AQ$_CAPTURE_QUEUE_T_ALL2_P','AQ$_CAPTURE_QUEUE_T_ALL3_D','AQ$_CAPTURE_QUEUE_T_ALL3_P')
commit;


Propagation Cleanup [Optional]
1. DELETE FROM SYS.AQ$_SCHEDULES WHERE oid IN ('<OID_1>', ....);
where the <OID_1> values are those obtained from the SYSTEM Cleanup stage.


SELECT * FROM SYS.AQ$_SCHEDULES WHERE oid IN (SELECT oid FROM SYSTEM.AQ$_QUEUES WHERE name IN ('CAPTURE_QUEUE_ALL1','CAPTURE_QUEUE_ALL2','CAPTURE_QUEUE_ALL3','AQ$_CAPTURE_QUEUE_T_ALL1_E','AQ$_CAPTURE_QUEUE_T_ALL2_E','AQ$_CAPTURE_QUEUE_T_ALL3_E') );


DELETE FROM SYS.AQ$_SCHEDULES WHERE oid IN (SELECT oid FROM SYSTEM.AQ$_QUEUES WHERE name IN ('CAPTURE_QUEUE_ALL1','CAPTURE_QUEUE_ALL2','CAPTURE_QUEUE_ALL3','AQ$_CAPTURE_QUEUE_T_ALL1_E','AQ$_CAPTURE_QUEUE_T_ALL2_E','AQ$_CAPTURE_QUEUE_T_ALL3_E') );




2. DELETE FROM SYS.AQ$_MESSAGE_TYPES WHERE queue_oid IN ('<OID_1>', ....);
where the <OID_1> values are those obtained from the SYSTEM Cleanup stage.


SELECT * FROM SYS.AQ$_MESSAGE_TYPES WHERE queue_oid IN (SELECT oid FROM SYSTEM.AQ$_QUEUES WHERE name IN ('CAPTURE_QUEUE_ALL1','CAPTURE_QUEUE_ALL2','CAPTURE_QUEUE_ALL3','AQ$_CAPTURE_QUEUE_T_ALL1_E','AQ$_CAPTURE_QUEUE_T_ALL2_E','AQ$_CAPTURE_QUEUE_T_ALL3_E') );


DELETE FROM SYS.AQ$_MESSAGE_TYPES WHERE queue_oid IN (SELECT oid FROM SYSTEM.AQ$_QUEUES WHERE name IN ('CAPTURE_QUEUE_ALL1','CAPTURE_QUEUE_ALL2','CAPTURE_QUEUE_ALL3','AQ$_CAPTURE_QUEUE_T_ALL1_E','AQ$_CAPTURE_QUEUE_T_ALL2_E','AQ$_CAPTURE_QUEUE_T_ALL3_E') );


3. SELECT MIN(sequence), MAX(sequence) from SYS.AQ$_PROPAGATION_STATUS WHERE queue_id IN ('eventid', ....);
where the <eventid> values are those obtained from the SYSTEM Cleanup stage.


SELECT * from SYS.AQ$_PROPAGATION_STATUS WHERE queue_id IN (SELECT  eventid FROM SYSTEM.AQ$_QUEUES WHERE name IN ('CAPTURE_QUEUE_ALL1','CAPTURE_QUEUE_ALL2','CAPTURE_QUEUE_ALL3','AQ$_CAPTURE_QUEUE_T_ALL1_E','AQ$_CAPTURE_QUEUE_T_ALL2_E','AQ$_CAPTURE_QUEUE_T_ALL3_E'));


SELECT MIN(sequence), MAX(sequence) from SYS.AQ$_PROPAGATION_STATUS WHERE queue_id IN (SELECT  eventid FROM SYSTEM.AQ$_QUEUES WHERE name IN ('CAPTURE_QUEUE_ALL1','CAPTURE_QUEUE_ALL2','CAPTURE_QUEUE_ALL3','AQ$_CAPTURE_QUEUE_T_ALL1_E','AQ$_CAPTURE_QUEUE_T_ALL2_E','AQ$_CAPTURE_QUEUE_T_ALL3_E'));


4. DELETE FROM SYS.AQ$_PROPAGATION_STATUS WHERE queue_id IN ('<eventid>', ....);
where the <eventid> values are those obtained from the SYSTEM Cleanup stage.


DELETE FROM SYS.AQ$_PROPAGATION_STATUS WHERE queue_id IN (SELECT  eventid FROM SYSTEM.AQ$_QUEUES WHERE name IN ('CAPTURE_QUEUE_ALL1','CAPTURE_QUEUE_ALL2','CAPTURE_QUEUE_ALL3','AQ$_CAPTURE_QUEUE_T_ALL1_E','AQ$_CAPTURE_QUEUE_T_ALL2_E','AQ$_CAPTURE_QUEUE_T_ALL3_E'));


5. DELETE FROM SYS.AQ$_PENDING_MESSAGES WHERE sequence BETWEEN (<MIN>,<MAX);
where <MIN>, <MAX> are the minimum and maximum sequence values found in step 3.




commit;


EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_0_GA1');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_1_GY1');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_1_GY2');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_1_GY3');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_2_LPS1');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_2_LPS2');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_2_LPS3');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_4_TR1');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_4_TR2');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_4_TR3');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_8_QDN1');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_8_QDN2');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_8_QDN3');
EXEC DBMS_PROPAGATION_ADM.DROP_PROPAGATION('PROPAGATION_9_QN1');


exec  DBMS_RULE_ADM.DROP_RULE_SET(rule_set_name =>'CAPTURE_QUEUE_ALL2_R' ,delete_rules =>true );
exec  DBMS_RULE_ADM.DROP_RULE_SET(rule_set_name =>'CAPTURE_QUEUE_ALL2_N' ,delete_rules =>true );


    ALTER SESSION SET EVENTS '10046 trace name context forever, level 8';


 Event 10046 trace is disabled at session level using 
    ALTER SESSION SET EVENTS '10046 trace name context off';
 
ALTER SESSION SET EVENTS '10851 trace name context off';
ALTER SESSION SET EVENTS '25475 trace name context off';

进过以上处理后,expdp就不会出错了。

【全开源】旅游系统源码(Uniapp+FastAdmin+ThinkPHP) 通过源码的灵活配置和定制开发,我们可以根据旅游企业的实际需求,快速构建出符合其业务特点的旅游系统。旅游系统源码,作为这一变革的基石,为旅游业的数字化转型提供了强有力的支撑。通过深入研究和应用旅游系统源码,我们能够构建出更加智能、便捷、个性化的旅游服务平台,满足游客日益增长的旅游需求。国际化发展:随着全球化的深入发展,旅游系统源码也将迎来国际化的发展机遇,为国内外游客提供更加便捷、高效的旅游服务。跨界融合:旅游系统源码将与更多领域进行跨界融合,如与交通、餐饮、购物等行业的结合,为游客提供更加丰富的旅游体验。 阅读详情

相关推荐

手把手教你用Microsoft AEC Challenge数据集训练自己的回声消除模型(附完整代码)

本文详细介绍了如何使用Microsoft AEC Challenge数据集训练专业的回声消除模型,包括环境准备、数据清洗、模型架构设计、训练流程和实际部署注意事项。通过完整的代码示例和实战指南,帮助开发者快速掌握AEC技术,提升语音通信系统的回声消除效果。

weixin_27697385的博客 461

EXPDP导出ORA-39127错误

错误如下: ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('SCOTT',1,1,'11.02.00.00.00',newblock)  ORA-04063: package body "EXFSYS.DBMS_EXPFIL_EXP" ha

另类清晨 6575

图像去噪实战:Noise2Noise与Noise2Void在医学影像中的应用(附代码)

本文深入探讨了Noise2Noise与Noise2Void在医学影像去噪中的革命性应用,通过自监督学习技术有效解决临床数据配对难题。文章提供详细的代码实现和临床部署方案,展示如何提升低剂量CT、MRI等影像的诊断质量,特别适用于辐射敏感场景和急诊快速处理。

weixin_29092579的博客 243

ORA-39127 ORA-01502 ORA-06512

版本:ORACLE 10R2.0.1.0 做数据泵导出的时候出现如下错误: Processing object type SCHEMA_EXPORT/DEFAULT_ROLEORA-39127: unexpected err...

cldnu44288的专栏 546

YOLOv12改进策略【损失函数篇】| 替换Powerful-IoU(PIoU),增强对中等质量锚框的关注力,引导锚框更直接、高效地回归

本文针对现有基于IoU的损失函数在目标检测任务中存在的问题,提出了利用Powerful-IoU(PIoU)及其升级版PIoU v2改进YOLOv12的损失函数,以提高模型精度。文章详细介绍了PIoU和PIoU v2的结构原理,并提供了在YOLOv12中实现这些损失函数的具体步骤和代码修改方法。

Limiiiing的博客 932

《QGIS快速入门与应用基础》230:添加图例工具

本文系统讲解QGIS图例制作的核心方法与优化技巧。首先强调图例与地图框的绑定逻辑,提出三种绑定状态及适用场景。详细拆解三种图例添加方法:布局工具栏一键添加法(新手首选)、菜单栏添加法和右键快捷创建法,并给出单地图框和多地图框两种典型场景的规范技巧。重点解决新手常见的图例杂乱、样式不规范、内容脱节等问题,帮助用户从基础图例制作进阶到符合行业标准的专业图例设计。通过分步操作图示和实用技巧,使读者能够快速掌握图例创建的核心流程与优化方法。

LuckyHanMo的博客 556

ORA-20083: No ST_SRID supplied in PARAMETERS clause.

ORA-39127: unexpected error from call to local_str := SYS.DBMS_EXPORT_EXTENSION.GET_DOMAIN_INDEX_METADATA('A116_IX1','US_KZSJZHYYXT','ST_DOMAIN_METHODS','SDE',11.02.00.04.00,newblock,0)  ORA-20083: N

逝鸿的博客 1514

29、集成电路测试技术解析

本文深入解析了集成电路测试技术,涵盖定制电路测试资源与策略、混合模拟/数字电路测试方法、数字测试模式生成难点与解决方案,以及可控性和可观测性的核心概念。同时详细讨论了固定故障、桥接故障和开路故障等主要故障模型及其检测方法。在测试技术的综合应用与优化方面,提出了合理配置测试资源、优化测试模式和设计测试流程的策略。最后展望了测试技术的发展趋势,包括集成化测试、自动化测试和智能化测试。通过全面掌握这些测试技术,可以有效提高集成电路的质量和可靠性,推动集成电路产业的发展。

work3的博客 207

mysql expdp gtid_expdp导出报错ORA-39127

处理对象类型 SCHEMA_EXPORT/TABLE/TRIGGERORA-39127: 调用 export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.SCHEMA_INFO_EXP('ECOLOGY8',1,1,'11.02.00.04.00',newblock) 时发生意外错误ORA-04063: package body "EXFSYS.DBMS_EXPFIL...

weixin_31767787的博客 375

redhawk:avgTW maxTW minTW minWC的区别

分析dynamic ir drop报告时会遇到这几个值,avgTW maxTW minTW minWC,如下图。我正在「拾陆楼」和朋友们讨论有趣的话题,你⼀起来吧?

m0_61544122的博客 696

腾讯滑块验证码防水墙 tdc.js 补环境实录

腾讯滑块验证码破解研究摘要 本文记录了破解腾讯防水墙滑块验证码(tdc.js)的全过程。研究重点包括: 流程分析:通过抓包分析验证码完整链路,识别出关键参数collect和eks需从tdc.js虚拟机获取 环境模拟:采用渐进式补环境方法,针对字节码虚拟机特性构建完整的window对象,包括navigator、screen、canvas等API的精确模拟 核心破解:成功调用TDC.getData()和TDC.getInfo()获取关键参数,解决POW计算和滑块缺口识别问题 优化调整:针对errorCode 5

码王吴彦祖的博客 235

php导出oracle数据库,oracle数据库导出ORA

错误类型及描述: expdp 导出表在表分析是开始出现报错。 ORA-39127: unexpected error from call to export_string :=SYS.DBMS_AQ_EXP_QUEUE_TABLES.INSTANCE_INFO_EXP('CAPTURE_QUEUE_T_ALL1','STRMADMIN',1,1,'11.02.00.00.00',newblock)...

weixin_39824801的博客 188

3. LangGraph快速入门

本示例中,我们将使用 Claude Sonnet 4.5 模型,并定义加法、乘法、除法工具。# 定义工具@toolArgs:"""@toolArgs:"""@toolArgs:"""# 为大模型绑定工具图的状态用于存储消息和大模型调用次数。LangGraph 中的状态在整个智能体执行过程中保持持久化。使用带的Annotated类型可以确保新消息追加到现有列表,而不是替换列表。模型节点用于调用大模型,并决定是否调用工具。return {],

Long_像风一样自由 842

expdp报错:ora-39127“WMSYS”

错误信息: ORA-39127: unexpected error from call to "WMSYS"."LT_EXPORT_PKG"."SCHEMA_INFO_EXP" ORA-44002: invalid object name ORA-06512: at "SYS.DBMS_ASSERT", line 383 ORA-06512: at "SYS.DBMS_METADATA", li

u011214505的专栏 2630

VB摄像头监控

该VB模块可对摄像头捕获的画面进行录像等,可在创建的窗口进行控制

visio安装包

Microsoft Office Visio 是一款专业的制图软件。利用经过更新的形状、协作工具和数据链接图表,创建专业级图表以简化复杂的信息。

ORA-39127: 调用 "WMSYS"."LT_EXPORT_PKG"."SCHEMA_INFO_EXP" 时发生意外错误

expdp 告警提示: Export: Release 11.2.0.4.0 - Production on 星期日 4月 28 12:14:51 2019....ORA-39127: 调用 "WMSYS"."LT_EXPORT_PKG"."SCHEMA_INFO_EXP" 时发生意外错误ORA-44002: 对象名无效ORA-06512: 在 "SYS.DBMS_ASSERT", line 3...

weixin_33924220的博客 632

Statistics and Machine Learning Toolbox

Statistics and Machine Learning Toolbox(带书签),MATLAB统计学习工具

【转】Oracle 9i客户端导出10g数据库时报ora-33262错误

Bug 号 7155407 已归档 05-JUN-2008 已更新 25-JUL-2008 产品 Oracle OLAP 产品版本 10.2.0.3 平台 Linux x86 平台版本 无数据 数据库版本...

240

19c-expdp-ORA-39127: unexpected error from call to TAG: SCHEDULER Calling: SYS.DBMS_SCHED_JOB_EXPORT

使用具有dba权限的用户expdp导出全库报错,报错如下。方法2:--授予调度器包的执行权限。方法1:使用sys用户导出。

kevinyu998的博客 55

expdp时候遇到ORA-04067

做一次expdp时候,显示出以下错误信息ORA-39127: unexpected error from call to export_string :=WMSYS.LT_EXPORT_PKG.schema_info_exp('...

congdiku5262的博客 1309

AWR导出过程中报ORA-04063

错误日志: ORA-20115: datapump export encountered error: ORA-39127: unexpected error from call to export_string ...

crcz16618的博客 296

Database Data Pump Export fails with PLS-00201 identifier must be declared

出现问题如下: ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('HNM...

cuanbiane8209的博客 562

oracle 表结构导不出来,exp报错与exp为何导不出某些表结构原因

11G中有个新特性,当表无数据时,不分配segment,以节省空间解决方法:设置deferred_segment_creation 参数修改配置参数sqlplus /nologSQL>connect system/password as sysdba;SQL>show parameter deferred_segment_creation;你会看到它默认为true,修改。SQL>...

weixin_39580042的博客 293

数据泵导出数据报错处理

在创建数据库实例的时候未采用loltp模板,在后期做数据泵备份数据时报错如下: oracle@zderpppad01:/home/oracle$expdp \'/ as sysdba\' dumpfile=guijian....

cqq1799的博客 872

expdp输出信息出现乱码

采用expdp导出的时候,显示信息出现了很多???, 应该是字符集设置有问题[oracle@db ~]$ expdp justin/justin directory=pump dumpfile=full_justin_11021...

congdiku5262的博客 767

Exp出这个错

Exp出这个错PLS-00201: 必须宣告识别项 'DMSYS.DBMS_DM_MODEL_EXP' 即将汇出设定的使用者 ... . 正在汇出预先纲要程序对象与动作 EXP-00008: ORACLE 错误 6550 发生 ORA-06550: 第 1 行, 第 13 个字段: PLS-00201: 必须宣告识别项 'DMSYS.DBMS_DM_MODEL_EXP' ORA-...

weixin_30278237的博客 141
上一篇: 模板和异常处理
下一篇: #define UNREFERENCED_PARAMETER(P) (P)
天天向上zb
博客等级 码龄16年 34粉丝 43原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值