【MOS】Why an Object Not Be Exported? ORA-39166 or ORA-31655 (文档 ID 2114233.1)

【MOS】Why Can an Object Not Be Exported? Expdp of SYSTEM User's Table Returns ORA-39166 or ORA-31655 (文档 ID 2114233.1)

In this Document

Goal
Solution
References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Oracle Database - Standard Edition - Version 12.1.0.2 and later
Information in this document applies to any platform.

GOAL

This document explains why certain objects cannot be exported, and how to find those objects.

There are certain system generated schemas that are not exportable using exp or expdp because they contain Oracle-managed data and metadata. SYS, MDSYS, and ORDSYS are some examples.

In addition, there are other tables owned by users such as SYS or APEX_040200 which are automatically skipped during export, nor can those be exported intentionally. 

For example, certain tables owned by SYSTEM user like below cannot be exported:

% expdp system/manager directory=my_dir tables='REDO_DB'

Export: Release 12.1.0.2.0 - Production on Thu Mar 3 20:39:27 2016

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

Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_TABLE_01": system/******** directory=my_dir tables=REDO_DB
Estimate in progress using BLOCKS method...
Total estimation using BLOCKS method: 0 KB
Processing object type TABLE_EXPORT/TABLE/STATISTICS/MARKER
ORA-39166: Object SYSTEM.REDO_DB was not found or could not be exported or imported.
ORA-31655: no data or metadata objects selected for job
Job "SYSTEM"."SYS_EXPORT_TABLE_01" completed with 2 error(s) at Thu Mar 3 20:39:31 2016 elapsed 0 00:00:03

 

SOLUTION

Objects (tables, views, schemas, etc) which fall under either of below conditions are not exported with expdp because they are regarded as system maintained objects.

  • Object is listed in ku_noexp_view. 
    This view is a union of ku_noexp_tab and noexp$ tables. 
    Objects that are listed in this view are not exported.
  • Object is ORACLE_MAINTAINED='Y' in ALL_OBJECTS (and DBA_OBJECTS).

 

REFERENCES

NOTE:1912162.1 - 12.1.0.1 EXPDP Does Not Export APEX Schema
BUG:17373592 - EXPDP DOES NOT EXPORT APPLICATION EXPRESS OBJECTS CORRECTLY

About Me


...............................................................................................................................

● 本文来自于MOS转载文章(文档 ID  2114233.1)

● 小麦苗云盘地址:http://blog.itpub.net/26736162/viewspace-1624453/

● QQ群:230161599     微信群:私聊

● 联系我请加QQ好友(642808185),注明添加缘由

● 版权所有,欢迎分享本文,转载请保留出处

...............................................................................................................................

手机长按下图识别二维码或微信客户端扫描下边的二维码来关注小麦苗的微信公众号:xiaomaimiaolhr,免费学习最实用的数据库技术。

 

时间: 2024-10-11 18:00:24

【MOS】Why an Object Not Be Exported? ORA-39166 or ORA-31655 (文档 ID 2114233.1)的相关文章

【MOS】在不同版本和平台之间进行还原或复制 (文档 ID 1526162.1)--跨版本恢复

[MOS]关于在不同版本和平台之间进行还原或复制的常见问题 (文档 ID 1526162.1)--跨版本恢复 Questions and Answers    1) 我能用更高版本的 Oracle 还原或复制旧版本的数据库吗?    2) 我能在两个不同的补丁程序集之间进行还原或复制吗?    3) 我能在同一操作系统的不同版本之间进行还原或复制吗?    4) Oracle 的位(bit)级别(32 位或 64 位)不匹配时,可以进行还原或复制吗?    5) 可以将更高版本的备份还原到较早版

【MOS】为何在查询中索引未被使用 (文档 ID 1549181.1、英文文档为67522.1)

为何在查询中索引未被使用 (文档 ID 1549181.1)   "为什么索引没有被使用"是一个涉及面较广的问题.有多种原因会导致索引不能被使用.首要的原因就是统计信息不准,第二原因就是索引的选择度不高,使用索引比使用全表扫描效率更差.还有一个比较常见的原因,就是对索引列进行了函数.算术运算或其他表达式等操作,或出现隐式类型转换,导致无法使用索引.还有很多其它原因会导致不能使用索引,这个问题在MOS(MOS即My Oracle Support)"文档1549181.1为何在查

【MOS】Top Ten Performance Mistakes Found in Oracle Systems. (文档 ID 858539.1)

In this Document Purpose Troubleshooting Steps References APPLIES TO: Oracle Database - Enterprise Edition - Version 9.2.0.8 and laterInformation in this document applies to any platform.RDBMS PURPOSE The purpose of this note is to inform reader abou

【MOS】TNSPING TNS-12543: TNS:destination host unreachable (文档 ID 1556918.1)

In this Document Symptoms Cause Solution APPLIES TO: Oracle Net Services - Version 11.2.0.3 and laterInformation in this document applies to any platform. SYMPTOMS When attempting to tnsping a remote server,  the following error occurs. ERROR -------

【MOS】EVENT: DROP_SEGMENTS - cleanup of TEMPORARY segments (文档 ID 47400.1)

[MOS]EVENT: DROP_SEGMENTS - Forcing cleanup of TEMPORARY segments (文档 ID 47400.1) ***Checked for relevance on 14-Jun-2012*** The DROP_SEGMENTS event ~~~~~~~~~~~~~~~~~~~~~~~ Available from 8.0 onwards. DESCRIPTION Finds all the temporary segments in a

【MOS】中文文档列表 - Oracle Database (文档 ID 1533057.1)

中文文档列表 - Oracle Database (文档 ID 1533057.1) 类型: 状态: 上次主更新: 上次更新: ANNOUNCEMENT PUBLISHED 2017-2-23 2017-2-23     文档内容 详细信息 操作   Oracle 数据库技术支持通讯   安装/升级/降级/迁移相关     日常管理相关   性能相关     集群及存储相关   高可用相关   TimesTen 内存数据库 联系人 参考 适用于: Oracle Database - Enterp

【MOS】OCR/Vote disk 维护操作: (添加/删除/替换/移动) (文档 ID 1674859.1)

[MOS]OCR/Vote disk 维护操作: (添加/删除/替换/移动) (文档 ID 1674859.1) 文档内容 目标 解决方案   准备磁盘   1. 磁盘大小   2. 裸设备或者块设备 (pre 11.2)   3. ASM disks (11.2+)   4. 集群文件系统   5. 权限   6. 冗余   添加/删除/替换/移动 OCR device   1. 当只有一个 OCR 设备时,添加一个 OCRMIRROR 设备:   2. 删除一个 OCR 设备   3. 替换

【MOS】Troubleshooting Performance Issues (文档 ID 1377446.1)

[MOS]Troubleshooting Performance Issues (文档 ID 1377446.1) In this Document Purpose   Best Practices   Pro-Active Problem Avoidance and Diagnostic Collection   Performance Service Request Diagnostic Collection (SRDC) documents Troubleshooting Steps  

【MOS】Cluster Health Monitor (CHM) FAQ (文档 ID 1328466.1 ID 2062234.1)

11gR2 新特性:Oracle Cluster Health Monitor(CHM)简介 Cluster Health Monitor(以下简称CHM)是一个Oracle提供的工具,用来自动收集操作系统的资源(CPU.内存.SWAP.进程.I/O以及网络等)的使用情况.CHM会每秒收集一次数据.    这些系统资源数据对于诊断集群系统的节点重启.Hang.实例驱逐(Eviction).性能问题等是非常有帮助的.另外,用户可以使用CHM来及早发现一些系统负载高.内存异常等问题,从而避免产生更严