oracle ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout

Mon Jun 11 21:59:52 2018
LNS: Standby redo logfile selected for thread 2 sequence 132997 for destination LOG_ARCHIVE_DEST_10
Mon Jun 11 21:59:55 2018
Archived Log entry 465126 added for thread 2 sequence 132996 ID 0x92570693 dest 1:
Mon Jun 11 22:00:00 2018
Setting Resource Manager plan SCHEDULER[0x32D9]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Mon Jun 11 22:00:00 2018
Starting background process VKRM
Mon Jun 11 22:00:00 2018
VKRM started with pid=609, OS id=39289
Mon Jun 11 22:00:09 2018
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
Mon Jun 11 22:00:21 2018
DBMS_STATS: GATHER_STATS_JOB encountered errors.  Check the trace file.
Errors in file /u01/app/oracle/diag/rdbms/bapdb/bapdb2/trace/bapdb2_j001_39449.trc:
ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout
KUP-11024: This external table can only be accessed from within a Data Pump job.
Mon Jun 11 22:03:38 2018
LGWR: Standby redo logfile selected for thread 2 sequence 132998 for destination LOG_ARCHIVE_DEST_3
Thread 2 advanced to log sequence 132998 (LGWR switch)
  Current log# 10 seq# 132998 mem# 0: +SAS_DATA/bapdb/redo10a.log
  Current log# 10 seq# 132998 mem# 1: +SAS_DATA/bapdb/redo10b.log

ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout KUP-11024: This external table can only be accessed from within a Data Pump job.

*** 2018-06-11 22:00:21.096 DBMS_STATS: GATHER_STATS_JOB: GATHER_TABLE_STATS(‘"SYS"‘,‘"ET$032682FB0001"‘,‘""‘, ...) DBMS_STATS: ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout KUP-11024: This external table can only be accessed from within a Data Pump job.

--------support.oracle.com 找到文章 1274653.1

select OWNER,OBJECT_NAME,OBJECT_TYPE, status, to_char(CREATED,‘dd-mon-yyyy hh24:mi:ss‘) created ,to_char(LAST_DDL_TIME , ‘dd-mon-yyyy hh24:mi:ss‘) last_ddl_time from dba_objects where object_name like ‘ET$%‘;

---查询结果

SYS ET$032682FB0001 TABLE VALID 07-jun-2018 17:30:39 07-jun-2018 17:30:39

select owner, TABLE_NAME, DEFAULT_DIRECTORY_NAME, ACCESS_TYPE from dba_external_tables order by 1,2

---删除---原因是导出有 LOB

drop table SYS.ET$032682FB0001 purge;

---其他相关链接

https://blog.csdn.net/www_xue_xi/article/details/79031702

原文地址:https://www.cnblogs.com/ss-33/p/9171674.html

时间: 2024-10-14 06:46:56

oracle ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout的相关文章

关于oracle 11g导出数据时 报 ORA 1455错误的处理

由于导出的该用户的表可能存在空数据表,那么可能就会出现此其异常. 首先: 查看: SQL>show parameter deferred_segment_creation; 如果为TRUE,则将该参数改为FALSE: 在sqlplus中,执行如下命令: SQL>alter system set deferred_segment_creation=false; 然后: 可以针对数据表.索引.物化视图等手工分配Extent SQL>Select 'alter table '||table_n

Oracle Study之--Oracle 11g RAC故障(Failed to create or upgrade OLR)

Oracle Study之--Oracle 11g RAC故障(Failed to create or upgrade OLR) 系统环境:       操作系统: RedHat EL5.5       Cluster:   Oracle Grid 11.2.0.1.0       Oracle:     Oracle 11g  11.2.0.1.0 故障现象:             在Oracle 11gR2  RAC添加新节点的过程中,在new node上运行root.sh时出现以下故障:

Mongodb中经常出现的错误(汇总)child process failed, exited with error number

异常处理汇总-服 务 器 http://www.cnblogs.com/dunitian/p/4522983.html 异常处理汇总-数据库系列  http://www.cnblogs.com/dunitian/p/4522990.html 情况不唯一,这边只能当参考,大致就是这么几种解决思路 child process failed, exited with error number 1 child process failed, exited with error number 48 chi

hive分区导致FAILED: Hive Internal Error: java.lang.NullPointerException(null)

写了一条hive sql ,其中条件中存在 dt>=20150101 and dt<=20150228 这样的条件,原来执行没问题,今天就抛出 FAILED: Hive Internal Error: java.lang.NullPointerException(null)java.lang.NullPointerException at org.apache.hadoop.hive.ql.optimizer.pcr.PcrExprProcFactory.opAnd(PcrExprProcFa

[Firmware Warn]: GHES: Failed to read error status block address for hardware error source

Firmware Warn 问题描述: 系统版本:Ubuntu 12.04 LTS. 系统启动后dmesg打印大量Firmware Warn告警信息到syslog文件中.信息如下: [Firmware Warn]: GHES: Failed to read error status block address for hardware error source: 1. [Firmware Warn]: GHES: Failed to read error status block address

ERROR: child process failed, exited with error number 51

1.ERROR: child process failed, exited with error number 51 异常的关闭再次重启时容易产生这样的错误,首先删除mongod.lock 文件  修复  再次启动 . 2.Error parsing INI config file: unrecognised option 'configdb' 仔细看下图操作,mongos启动时用mongos而不是mongod 原文地址:https://www.cnblogs.com/tszc/p/856819

zabbix报错listener failed: zbx_tcp_listen() fatal error: unable to serve on any address

I'm trying to install zabbix on a new (virtual) server. But i have troubles with the zabbix_agentd on the zabbix server. I get the error below and don't know how to fix it... Can someone help me out or point me in the correct direction? Error logging

liunx启动mongodb报错 mongodb child process failed, exited with error number 14

mongodb启动报错:mongodb child process failed, exited with error number 14,查看mongodb.cnf日志,发现其中有一条:Too many open files at src/mongo/db/storage/wiredtiger/wiredtiger_session_cache.cpp 79. 设置ulimit -n 10000.完美! 原文地址:https://www.cnblogs.com/shilang/p/1019748

mongodb启动报错,child process failed, exited with error number 1

error: child process failed, exited with error number 1 第一次安装mongodb,随后启动一般不会出现上面的错误,出现这种错误的原因一般是mongodb进程非正常关闭导致的(例如用kill关闭mongo),导致出现mongod.lock这个文件 解决方案一: # find / -name "mongod.lock" 找到对应的文件,删除即可 解决方案二: 查看mongodb.conf的配置,检查 dbpath 和 logpath