expdp导出表结构_【数据泵】EXPDP导出表结构

我会带着你远行 2022-12-31 11:28 149阅读 0赞

【数据泵】EXPDP导出表结构(真实案例)

BLOG文档结构图

![Image 1][]

因工作需要现需要把一个生产库下的元数据(表定义，索引定义，函数定义，包定义，存储过程)导出到测试库上，本来以为很简单的，可是做的过程发现很多的问题，现记录如下，希望有同样需要的朋友不要再走弯路了。

导读

各位技术爱好者，看完本文后，你可以掌握如下的技能，也可以学到一些其它你所不知道的知识，~O(∩\_∩)O~：

① EXPDP和IMPDP如何导出导入元数据，包括表定义，索引定义，函数定义，包定义，存储过程(重点)

② 表的初始化定义参数initial，及如何批量修改该参数

③ 如何导出DMP文件中的DDL语句(重点)

④ 10g和11g默认情况下有哪些用户及其作用

⑤ linux中的批量替换sed命令

⑥ sqlldr和spool命令

本文如有错误或不完善的地方请大家多多指正，ITPUB留言或QQ皆可，您的批评指正是我写作的最大动力。实验环境介绍

源库：10.2.0.1 AIX

目标库：11.2.0.3 RHEL6.5

执行导出工作确定需要导出的用户

oracle安装好后有很多的系统默认用户，比如sys和system，对于这2个用户里的元数据我们就没有必要再重新导出嘛，不然导入的时候还提示错误，看着实在不好。

官网信息：

All databases created by the Database Configuration Assistant (DBCA) include the SYS, SYSTEM, SYSMAN, and DBSNMP database accounts. In addition, Oracle Database provides several other administrative accounts. Before using these accounts, you must unlock them and reset their passwords.

11g默认用户比较多：

User NameDescriptionSee Also

ANONYMOUSEnables HTTP access to Oracle XML DB.

APEX\_030200The account owns the Application Express schema and metadata.

APEX\_PUBLIC\_USERThe minimally privileged account used for Application Express configuration with Oracle HTTP Server and mod\_plsql.

APPQOSSYSUsed for storing and managing all data and metadata required by Oracle Quality of Service Management.None

BIThe account that owns the Business Intelligence schema included in the Oracle Sample Schemas. It is available only if you loaded the sample schemas.

CTXSYSThe Oracle Text account.

DBSNMPThe account used by the Management Agent component of Oracle Enterprise Manager to monitor and manage the database.Oracle Enterprise Manager Grid Control Installation and Basic Configuration

DIPThe account used by the Directory Integration Platform (DIP) to synchronize the changes in Oracle Internet Directory with the applications in the database.None

DVSYSThere are two roles associated with this account. The Database Vault owner role manages the Database Vault roles and configurations. The Database Vault Account Manager is used to manage database user accounts.

Note: Part of Oracle Database Vault user interface text is stored in database tables in the DVSYS schema. By default, only the English language is loaded into these tables. You can use Oracle Database Vault Configuration Assistant to add more languages to Oracle Database Vault. For the necessary steps, see Appendix C in Oracle Database Vault Administrator's Guide

EXFSYSThe account owns the Expression Filter schema.None

FLOWS\_FILESThe account owns the Application Express uploaded files.

HRThe account that owns the Human Resources schema included in the Oracle Sample Schemas. It is available only if you loaded the sample schemas.

IXThe account that owns the Information Transport schema included in the Oracle Sample Schemas. It is available only if you loaded the sample schemas.

LBACSYSThe Oracle Label Security administrator account.

MDDATAThe schema used by Oracle Spatial for storing geocoder and router data.

MDSYSThe Oracle Spatial and Oracle Multimedia Locator administrator account.

MGMT\_VIEWAn account used by Oracle Enterprise Manager Database Control.None

OEThe account that owns the Order Entry schema included in the Oracle Sample Schemas. It is available only if you loaded the sample schemas.

ORDPLUGINSThe Oracle Multimedia user. Plug-ins supplied by Oracle and third-party plug-ins are installed in this schema.

ORDSYSThe Oracle Multimedia administrator account.

ORDDATAThis account contains the Oracle Multimedia DICOM data model.

OUTLNThe account that supports plan stability. Plan stability enables you to maintain the same execution plans for the same SQL statements. OUTLN acts as a role to centrally manage metadata associated with stored outlines.

ORACLE\_OCMThis account contains the instrumentation for configuration collection used by the Oracle Configuration Manager.

OWBSYSThe account used by Oracle Warehouse Builder as its default repository. You must unlock this account after installing the Oracle Database and before launching the Warehouse Builder Repository Assistant.

OWBSYS\_AUDITThis account is used by the Warehouse Builder Control Center Agent to access the heterogeneous execution audit tables in the OWBSYS schema.

PMThe account that owns the Product Media schema included in the Oracle Sample Schemas. It is available only if you loaded the sample schemas.

SCOTTAn account used by Oracle sample programs and examples.

SHThe account that owns the Sales History schema included in the Oracle Sample Schemas. It is available only if you loaded the sample schemas during an Enterprise Edition installation.

SI\_INFORMTN\_SCHEMAThe account that stores the information views for the SQL/MM Still Image Standard.

SPATIAL\_CSW\_ADMIN\_USRThe Catalog Services for the Web (CSW) account. It is used by the Oracle Spatial CSW cache manager to load all record type metadata, and record instances from the database into the main memory for the record types that are cached.

SPATIAL\_WFS\_ADMIN\_USRThe Web Feature Service (WFS) account. It is used by the Oracle Spatial WFS cache manager to load all feature-type metadata, and feature instances from the database into main memory for the feature types that are cached.

SYSThe account used to perform database administration tasks.

SYSMANThe account used to perform Oracle Enterprise Manager database administration tasks.Oracle Enterprise Manager Grid Control Installation and Basic Configuration

SYSTEMAnother account used to perform database administration tasks.

WMSYSThe account used to store the metadata information for Oracle Workspace Manager.

XDBThe account used for storing Oracle XML DB data and metadata.

10g下比较少：

CTXSYSCTXSYSThe Oracle Text account

DBSNMPDBSNMPThe account used by the Management Agent component of Oracle Enterprise Manager to monitor and manage the database

LBACSYSLBACSYSThe Oracle Label Security administrator account

MDDATAMDDATAThe schema used by Oracle Spatial for storing Geocoder and router data

MDSYSMDSYSThe Oracle Spatial and Oracle interMedia Locator administrator account

DMSYSDMSYSThe Oracle Data Mining account.

OLAPSYSMANAGERThe account used to create OLAP metadata structures. It owns the OLAP Catalog (CWMLite).

ORDPLUGINSORDPLUGINSThe Oracle interMedia user. Plug-ins supplied by Oracle and third party format plug-ins are installed in this schema.

ORDSYSORDSYSThe Oracle interMedia administrator account

OUTLNOUTLNThe account that supports plan stability. Plan stability enables you to maintain the same execution plans for the same SQL statements. OUTLN acts as a role to centrally manage metadata associated with stored outlines.

SI\_INFORMTN\_SCHEMASI\_INFORMTN\_SCHEMAThe account that stores the information views for the SQL/MM Still Image Standard

SYSCHANGE\_ON\_INSTALLThe account used to perform database administration tasks

SYSMANCHANGE\_ON\_INSTALLThe account used to perform Oracle Enterprise Manager database administration tasks. Note that SYS and SYSTEM can also perform these tasks.

SYSTEMMANAGERAnother account used to perform database administration tasks.

确定需要导出的用户在哪些表空间，及其表初始化时占用的表空间大小

SELECTD.tablespace\_name, SUM(D.initial\_extent)/1024/1024initial\_extent

FROMDBA\_SEGMENTS D

WHERED.owner IN

(SELECTa.username

FROMDBA\_USERS A

WHEREA.account\_status = 'OPEN'

ANDA.username NOTIN

('SYS', 'SYSTEM', 'MGMT\_VIEW', 'SYSMAN', 'DBSNMP'))

GROUPBYD.tablespace\_name

ORDERBYinitial\_extent desc;

![Image 1][]

SELECTSUM(D.initial\_extent)/1024/1024initial\_extent

FROMDBA\_SEGMENTS D

WHERED.owner IN

(SELECTa.username

FROMDBA\_USERS A

WHEREA.account\_status = 'OPEN'

ANDA.username NOTIN

('SYS', 'SYSTEM', 'MGMT\_VIEW', 'SYSMAN', 'DBSNMP'))

;

![Image 1][]

由此可以知道，创建这些元数据大约需要49G的空间，如果涉及到数据的话，还需要判断数据占用空间，这里一定需要判断这个，不然执行导入的时候会因为表空间不足而不能导入，我第一次导入的时候就是因为这里没有判断导致花费了很长的时间，我一直扩展表空间，但是就是就表空间不足的错误(ORA-01659),想想建表不会花这么大的空间的吧，最后查看了表的定义才知道，原来表初始化的时候就很大，这个问题后边还需要再处理一下的，不然测试库没法导入，当然存储够的话就另当别论了。

ORA-39171: Job is experiencing a resumable wait.

ORA-01659: unable to allocate MINEXTENTS beyond 4 in tablespace DWII\_SOR\_F\_01

确定需要导出的用户中有哪些无效的对象、及总共需要导出的对象数量

这一步也很重要，决定着最终导出结果的正确性验证。

SELECTd.OWNER,count(1)

FROMdba\_objects d

WHEREd.OWNER in(SELECTa.username

FROMDBA\_USERS A

WHEREA.account\_status = 'OPEN'

ANDA.username NOTIN

('SYS', 'SYSTEM', 'MGMT\_VIEW', 'SYSMAN', 'DBSNMP'))

group byd.OWNER;

SELECTd.OWNER,

d.status,count(1)

FROMdba\_objects d

WHEREd.OWNER in(SELECTa.username

FROMDBA\_USERS A

WHEREA.account\_status = 'OPEN'

ANDA.username NOTIN

('SYS', 'SYSTEM', 'MGMT\_VIEW', 'SYSMAN', 'DBSNMP'))

group byd.OWNER, d.status;

SELECTd.OWNER,

d.OBJECT\_NAME,

d.OBJECT\_TYPE,

d.status

FROMdba\_objects d

WHEREd.status =

'INVALID'

and d.owner in(SELECTa.username

FROMDBA\_USERS A

WHEREA.account\_status = 'OPEN'

ANDA.username NOTIN

('SYS', 'SYSTEM', 'MGMT\_VIEW', 'SYSMAN', 'DBSNMP'));

expdp数据泵利用content=metadata\_only导出元数据

导出命令，注意这里不导出数据只导出定义我们采用content=metadata\_only来处理：

expdp lhr/lhr directory=DATA\_PUMP\_DIR dumpfile=lhrsql20150515.dmp logfile=lhrsql20150515.log content=metadata\_only schemas=TEST,SQCHECK,DWUSER,DPA,CNYDM,ONL1,LHR,TEST1,FXDM,DWII\_ETL,DWUSER1,SOR,DW\_ETL,NRDM,NRDM\_ETL,FXDM\_ETL,LCM2,CNY\_ETL

由于是事后写文档，所以这里只贴出导出元数据的日志：

;;;

Export: Release 10.2.0.1.0 - 64bit Production on Friday, 15 May, 2015 13:05:54

;;;

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production

With the Partitioning, OLAP and Data Mining options

Starting "LHR"."SYS\_EXPORT\_SCHEMA\_01": lhr/\*\*\*\*\*\*\*\* directory=DATA\_PUMP\_DIR dumpfile=lhrsql20150515.dmp logfile=lhrsql20150515.log content=metadata\_only schemas=TEST,SQCHECK,DWUSER,DPA,CNYDM,ONL1,LHR,TEST1,FXDM,DWII\_ETL,DWUSER1,SOR,DW\_ETL,NRDM,NRDM\_ETL,FXDM\_ETL,LCM2,CNY\_ETL

Processing object type SCHEMA\_EXPORT/USER

Processing object type SCHEMA\_EXPORT/SYSTEM\_GRANT

Processing object type SCHEMA\_EXPORT/ROLE\_GRANT

Processing object type SCHEMA\_EXPORT/DEFAULT\_ROLE

Processing object type SCHEMA\_EXPORT/PRE\_SCHEMA/PROCACT\_SCHEMA

Processing object type SCHEMA\_EXPORT/DB\_LINK

Processing object type SCHEMA\_EXPORT/SEQUENCE/SEQUENCE

Processing object type SCHEMA\_EXPORT/TABLE/TABLE

Processing object type SCHEMA\_EXPORT/TABLE/GRANT/OWNER\_GRANT/OBJECT\_GRANT

Processing object type SCHEMA\_EXPORT/TABLE/INDEX/INDEX

Processing object type SCHEMA\_EXPORT/TABLE/CONSTRAINT/CONSTRAINT

Processing object type SCHEMA\_EXPORT/TABLE/INDEX/STATISTICS/INDEX\_STATISTICS

Processing object type SCHEMA\_EXPORT/TABLE/COMMENT

Processing object type SCHEMA\_EXPORT/PACKAGE/PACKAGE\_SPEC

Processing object type SCHEMA\_EXPORT/FUNCTION/FUNCTION

Processing object type SCHEMA\_EXPORT/FUNCTION/GRANT/OWNER\_GRANT/OBJECT\_GRANT

Processing object type SCHEMA\_EXPORT/PROCEDURE/PROCEDURE

Processing object type SCHEMA\_EXPORT/PROCEDURE/GRANT/OWNER\_GRANT/OBJECT\_GRANT

Processing object type SCHEMA\_EXPORT/PACKAGE/COMPILE\_PACKAGE/PACKAGE\_SPEC/ALTER\_PACKAGE\_SPEC

Processing object type SCHEMA\_EXPORT/FUNCTION/ALTER\_FUNCTION

Processing object type SCHEMA\_EXPORT/PROCEDURE/ALTER\_PROCEDURE

Processing object type SCHEMA\_EXPORT/VIEW/VIEW

Processing object type SCHEMA\_EXPORT/VIEW/GRANT/OWNER\_GRANT/OBJECT\_GRANT

Processing object type SCHEMA\_EXPORT/VIEW/COMMENT

Processing object type SCHEMA\_EXPORT/TABLE/CONSTRAINT/REF\_CONSTRAINT

Processing object type SCHEMA\_EXPORT/TABLE/STATISTICS/TABLE\_STATISTICS

Master table "LHR"."SYS\_EXPORT\_SCHEMA\_01" successfully loaded/unloaded

\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

Dump file set for LHR.SYS\_EXPORT\_SCHEMA\_01 is:

/oracle/product/10.2.0/db\_1/rdbms/log/lhrsql20150515.dmp

Job "LHR"."SYS\_EXPORT\_SCHEMA\_01"successfullycompleted at 13:09:49

接下来就是把导出来的文件利用ftp工具或scp传递到目标端，我这里就直接传到我的虚拟机上吧。

执行导入工作先建立相应的表空间

根据上边的工作我们知道需要在测试库上建立以下的表空间，我这里都设置的是20M，实际情况下应该根据上边查询出来的结果来设置相应的大小，表空间应用包含用户的默认表空间及用户下对象所在的表空间：

create tablespace DWII\_CNY\_BK\_F\_01 datafile '+DATA' size 20M;

create tablespace DWII\_DPA\_F\_01 datafile '+DATA' size 20M;

create tablespace DWII\_DPA\_I\_01 datafile '+DATA' size 20M;

create tablespace DWII\_DPA\_S\_01 datafile '+DATA' size 20M;

create tablespace DWII\_SOR\_F\_01 datafile '+DATA' size 20M;

create tablespace DWII\_SOR\_I\_01 datafile '+FRA' size 20M;

create tablespace DW\_USER datafile '+FRA' size 20M;

create tablespace SQCHECK datafile '+FRA' size 20M;

create tablespace SD\_CNY\_D\_01 datafile '+FRA' size 20M;

create tablespace SD\_CNY\_F\_01 datafile '+FRA' size 20M;

create tablespace SD\_DPA\_D\_01 datafile '+FRA' size 20M;

create tablespace SD\_DPA\_F\_01 datafile '+FRA' size 20M;

create tablespace SD\_SORT\_T\_01 datafile '+FRA' size 20M;

create tablespace DWII\_FXDM\_F\_01 datafile '+FRA' size 20M;

create tablespace SD\_SOR\_T\_01 datafile '+FRA' size 20M;

如果空间不够，我们可以追加数据文件：alter tablespace DWII\_DPA\_F\_01 add datafile '+FRA' size 50M;

执行导入语句

一般情况下，如果存储够的话，我们把相应的表空间设置大一点之后这里直接执行导入语句就可以了，但是我是在本机的虚拟机里执行的，由前边的情况我们可以知道大约需要49G的空间，这个显然不太合适，哪该怎么办呢？我能想到的办法只有如下2种，如果大家还有好的办法可以给我留言。

① 在源库上修改表的定义后然后再执行导出命令

② 从已经导出来的dmp文件中抽取其中的DDL语句，然后将DDL语句导入到数据库中，update掉其中的STORAGE(INITIAL 参数后再将语句导出到sql文本中执行sql语句，这样可以解决表的定义问题。

③从已经导出来的dmp文件中抽取其中的DDL语句，然后利用linux的sed批量替换功能替换掉不正确的参数。

显然，第一种比较方便，也比较快，但是不实用，由于是生产库，参数不能随便修改，我们就采用第二或第三种办法，也可以多演示一种impdp的用法。

导出DMP文件中的DDL语句

我们在impdp的导入命令中添加sqlfile参数后执行导入并不会真正将数据导入到数据库，而会抽取出dmp文件中的DDL语句，如下：

\[oracle@rhel6\_lhr dpdump\]$impdp lhr/lhr directory=DATA\_PUMP\_DIR dumpfile=lhrsql20150515.dmp logfile=imp\_exptest.log sqlfile=lhrsql20150515.sql

Import: Release 11.2.0.3.0 - Production on Fri May 15 15:08:03 2015

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning, Automatic Storage Management, OLAP, Data Mining

and Real Application Testing options

Master table "LHR"."SYS\_SQL\_FILE\_FULL\_01" successfully loaded/unloaded

Starting "LHR"."SYS\_SQL\_FILE\_FULL\_01": lhr/\*\*\*\*\*\*\*\* directory=DATA\_PUMP\_DIR dumpfile=lhrsql20150515.dmp logfile=imp\_exptest.log sqlfile=lhrsql20150515.sql

Processing object type SCHEMA\_EXPORT/USER

Processing object type SCHEMA\_EXPORT/SYSTEM\_GRANT

Processing object type SCHEMA\_EXPORT/ROLE\_GRANT

Processing object type SCHEMA\_EXPORT/DEFAULT\_ROLE

Processing object type SCHEMA\_EXPORT/PRE\_SCHEMA/PROCACT\_SCHEMA

Processing object type SCHEMA\_EXPORT/DB\_LINK

Processing object type SCHEMA\_EXPORT/SEQUENCE/SEQUENCE

Processing object type SCHEMA\_EXPORT/TABLE/TABLE

Processing object type SCHEMA\_EXPORT/TABLE/GRANT/OWNER\_GRANT/OBJECT\_GRANT

Processing object type SCHEMA\_EXPORT/TABLE/INDEX/INDEX

Processing object type SCHEMA\_EXPORT/TABLE/CONSTRAINT/CONSTRAINT

Processing object type SCHEMA\_EXPORT/TABLE/INDEX/STATISTICS/INDEX\_STATISTICS

Processing object type SCHEMA\_EXPORT/TABLE/COMMENT

Processing object type SCHEMA\_EXPORT/PACKAGE/PACKAGE\_SPEC

Processing object type SCHEMA\_EXPORT/FUNCTION/FUNCTION

Processing object type SCHEMA\_EXPORT/FUNCTION/GRANT/OWNER\_GRANT/OBJECT\_GRANT

Processing object type SCHEMA\_EXPORT/PROCEDURE/PROCEDURE

Processing object type SCHEMA\_EXPORT/PROCEDURE/GRANT/OWNER\_GRANT/OBJECT\_GRANT

Processing object type SCHEMA\_EXPORT/PACKAGE/COMPILE\_PACKAGE/PACKAGE\_SPEC/ALTER\_PACKAGE\_SPEC

Processing object type SCHEMA\_EXPORT/FUNCTION/ALTER\_FUNCTION

Processing object type SCHEMA\_EXPORT/PROCEDURE/ALTER\_PROCEDURE

Processing object type SCHEMA\_EXPORT/VIEW/VIEW

Processing object type SCHEMA\_EXPORT/VIEW/GRANT/OWNER\_GRANT/OBJECT\_GRANT

Processing object type SCHEMA\_EXPORT/VIEW/COMMENT

Processing object type SCHEMA\_EXPORT/TABLE/CONSTRAINT/REF\_CONSTRAINT

Processing object type SCHEMA\_EXPORT/TABLE/STATISTICS/TABLE\_STATISTICS

Job "LHR"."SYS\_SQL\_FILE\_FULL\_01" successfullycompleted at 15:21:50

\[oracle@rhel6\_lhr dpdump\]$ ll lhrsql20150515.sql

\-rw-r--r-- 1 oracle asmadmin 65707967 May 15 15:21 lhrsql20150515.sql

\[oracle@rhel6\_lhr dpdump\]$ more lhrsql20150515.sql

\-- CONNECT LHR

ALTER SESSION SET EVENTS '10150 TRACE NAME CONTEXT FOREVER, LEVEL 1';

ALTER SESSION SET EVENTS '10904 TRACE NAME CONTEXT FOREVER, LEVEL 1';

ALTER SESSION SET EVENTS '25475 TRACE NAME CONTEXT FOREVER, LEVEL 1';

ALTER SESSION SET EVENTS '10407 TRACE NAME CONTEXT FOREVER, LEVEL 1';

ALTER SESSION SET EVENTS '10851 TRACE NAME CONTEXT FOREVER, LEVEL 1';

ALTER SESSION SET EVENTS '22830 TRACE NAME CONTEXT FOREVER, LEVEL 192 ';

\-- new object type path: SCHEMA\_EXPORT/USER

\-- CONNECT SYSTEM

CREATE USER "CNY\_ETL" IDENTIFIED BY VALUES '4686A1050F638F44'

DEFAULT TABLESPACE "DW\_USER"

TEMPORARY TABLESPACE "TEMP";

CREATE USER "LCM2" IDENTIFIED BY VALUES '48BCFDF435352212'

DEFAULT TABLESPACE "DWII\_SOR\_F\_01"

TEMPORARY TABLESPACE "TEMP";

CREATE USER "FXDM\_ETL" IDENTIFIED BY VALUES 'EA010AEA839BFA14'

DEFAULT TABLESPACE "DW\_USER"

TEMPORARY TABLESPACE "TEMP";

CREATE USER "NRDM\_ETL" IDENTIFIED BY VALUES '54A4A046AEE8B31E'

DEFAULT TABLESPACE "DW\_USER"

TEMPORARY TABLESPACE "TEMP";

CREATE USER "NRDM" IDENTIFIED BY VALUES '1AE3DF7368DF560D'

DEFAULT TABLESPACE "SD\_CNY\_F\_01"

TEMPORARY TABLESPACE "TEMP";

CREATE USER "DW\_ETL" IDENTIFIED BY VALUES '91635F9C0744E7EC'

DEFAULT TABLESPACE "DW\_USER"

TEMPORARY TABLESPACE "TEMP";

CREATE USER "SOR" IDENTIFIED BY VALUES 'BA3A6C912E6BFF14'

DEFAULT TABLESPACE "DWII\_SOR\_F\_01"

TEMPORARY TABLESPACE "TEMP";

。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。。省略

\[oracle@rhel6\_lhr dpdump\]$ tail -n 50 lhrsql20150515.sql

c := 'SPOT\_EXCHNG\_RATE\_SRC';

EXECUTE IMMEDIATE stmt USING 'C',t,p,sp,c,s,

2,.5,2,156,0,2.65784513562818E+35,2.65784513872303E+35,5,0,nv,nv,

TO\_DATE('2015-05-14 22:00:18',df),'33303031','33303032',nv,2,nv;

c := 'SPOT\_EXCHNG\_RATE\_SRC\_NM';

EXECUTE IMMEDIATE stmt USING 'C',t,p,sp,c,s,

2,.5,2,156,0,1.18758942587854E+36,1.20817519861257E+36,12,0,nv,nv,

TO\_DATE('2015-05-14 22:00:18',df),'E4B8ADE997B4E4BBB7','E8AFA2E4BBB7E59D87E580BC',nv,2,nv;

c := 'FLEG\_SWAP\_PNT';

EXECUTE IMMEDIATE stmt USING 'C',t,p,sp,c,s,

14,.0714285714285714,14,156,0,-64.01,16.5,4,0,nv,nv,

TO\_DATE('2015-05-14 22:00:18',df),'3E256466','C11133',nv,2,nv;

c := 'SRC\_SYS\_LBL';

EXECUTE IMMEDIATE stmt USING 'C',t,p,sp,c,s,

1,1,1,156,0,3.44097282552972E+35,3.44097282552972E+35,5,0,nv,nv,

TO\_DATE('2015-05-14 22:00:18',df),'42454E4D','42454E4D',nv,2,nv;

END;

DECLARE

c varchar2(60);

nv varchar2(1);

df varchar2(21) := 'YYYY-MM-DD:HH24:MI:SS';

s varchar2(60) := 'DPA';

t varchar2(60) := 'BNCHMK\_OPTN\_DLT\_PARAM\_F';

p varchar2(1);

sp varchar2(1);

stmt varchar2(300) := 'INSERT INTO "SYS"."IMPDP\_STATS" (type,version,c1,c2,c3,c4,c5,n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,d1,r1,r2,ch1,flags,cl1) VALUES (:1,6,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11,:12,:13,:14,:15,:16,:17,:18,:19,:20,:21,:22,:23)';

BEGIN

NULL;

c := 'CRT\_TMST';

EXECUTE IMMEDIATE stmt USING 'C',t,p,sp,c,s,

1,1,1,156,0,2457157.57244213,2457157.57244213,11,0,nv,nv,

TO\_DATE('2015-05-14 22:00:18',df),'7873050E0E2D14','7873050E0E2D14',nv,2,nv;

c := 'PPLN\_WKDT';

EXECUTE IMMEDIATE stmt USING 'C',t,p,sp,c,s,

1,1,1,156,0,20150422,20150422,6,0,nv,nv,

TO\_DATE('2015-05-14 22:00:18',df),'C415100517','C415100517',nv,2,nv;

c := 'PPLN\_TMST';

EXECUTE IMMEDIATE stmt USING 'C',t,p,sp,c,s,

1,1,1,156,0,2457157.57244213,2457157.57244213,11,0,nv,nv,

TO\_DATE('2015-05-14 22:00:18',df),'7873050E0E2D14','7873050E0E2D14',nv,2,nv;

DBMS\_STATS.IMPORT\_TABLE\_STATS('"DPA"','"BNCHMK\_OPTN\_DLT\_PARAM\_F"',NULL,'"IMPDP\_STATS"',NULL,NULL,'"SYS"');

DELETE FROM "SYS"."IMPDP\_STATS";

END;

\[oracle@rhel6\_lhr dpdump\]$

可以看到生成的SQL语句开始部分是ddl的建用户语句，最后是导入表的统计信息部分。

处理导出来的ddl文件

方法一，利用sed命令批量替换 (推荐)

这一步其实如果linux的sed命令熟悉的话可以直接替换掉sql语句中的相关行，我今天也是临时网上搜了下，经过大量实验，然后居然成功了，如下：

\[oracle@rhel6\_lhr dpdump\]$ sed 's/^ STORAGE(INITIAL.\*/STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645/g' lhrsql20150515.sql > lhrsql20150515.sql\_bk2

\[oracle@rhel6\_lhr dpdump\]$ more lhrsql20150515.sql\_bk2 | grep "STORAGE(INITIAL"

STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645

\[oracle@rhel6\_lhr dpdump\]$ more lhrsql20150515.sql\_bk2 | grep "STORAGE(INITIAL 131072"

\[oracle@rhel6\_lhr dpdump\]$ more lhrsql20150515.sql | grep "STORAGE(INITIAL 131072"

STORAGE(INITIAL 131072 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645

。。。。。。。。。。。。。

可以看到替换已经成功，如果不熟悉该命令，那么先熟悉该命令就麻烦了。

方法二：sqlldr导入到数据库，利用update来更新

都是搞数据库的，这样做虽然麻烦点，但是绝对不会出错，而且也是一种技巧，如果有的文本很大又很难处理的话我们就可以导入到数据库中，然后处理。

首先建表：

create table imp\_sql\_lhr (id number ,textvarchar2(4000)) ;

sqlldr的控制文件内容:sqlldr\_table.ctl：

UNRECOVERABLE

load data

LENGTH CHARACTER

infile 'lhrsql20150515.sql'

APPEND imp\_sql\_lhr

trailing nullcols

(

id SEQUENCE(1,1),

text char(4000) "TRIM(:text)"

)

sqlldr命令：

sqlldr lhr/lhr control=sqlldr\_table.ctl log=a.logparallel=y readsize=4194304 streamsize=10485760 date\_cache=5000 direct=true

导入到数据库后，我们就可以非常方便的来处理表中的数据了，如下：

![Image 1][]

SELECT\*

FROMimp\_sql\_lhr a wherea.text like'%STORAGE(INITIAL%'anda.text notlike'%STORAGE(INITIAL 65536%';![Image 1][]

执行更新语句：

UPDATEimp\_sql\_lhr t

SETt.text =

'STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645'

WHEREt.text LIKE'%STORAGE(INITIAL%'

ANDt.text NOTLIKE'%STORAGE(INITIAL 65536 %';

最后利用spool来导出到sql文本中：

set echo on

set trimspool on

set trimout on

set linesize 4000

set pagesize 0

set sqlblanklines on

set feedback off

set serveroutput off

set term off

set echo off

spool lhrsql20150515.sql\_bk2

SELECT t.text from imp\_sql\_lhr t order by id;

spool off

执行处理好的sql语句

该步骤比较简单，就是把处理好的ddl语句提前执行一下，让数据库中包含相应的对象，这样再执行impdp导入的时候就不会再创建这些表了。

需要注意的是：DDL语句中创建存过、函数、包的语句中是不包含对象所属的schema的，这样的话如果那个用户执行sql脚本的话，这些对象就创建在那个用户下了，这个显然是错误的，不是我们期望的，那么如何处理这个问题呢，想了想，很简单的嘛，我们sql脚本执行完毕后，再执行一次impdp的命令就可以把这些对象重建，然后把错误的存过删除就可以了。

SELECTt.\*

fromimp\_sql\_lhr t wheret.text like'CREATE PROCEDURE%'orderbyid;

![Image 1][]

\[oracle@rhel6\_lhr dpdump\]$ sqlplus lhr/lhr

SQL\*Plus: Release 11.2.0.3.0 Production on Fri May 15 16:32:08 2015

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning, Automatic Storage Management, OLAP, Data Mining

and Real Application Testing options

16:32:09 SQL> set echo off;

16:32:21 SQL> set serveroutput off;

16:32:30 SQL> set timing on;

16:32:40 SQL> set time on;

16:32:45 SQL> set timing off;

16:32:50 SQL> set time off;

SQL>

SQL> @lhrsql20150515.sql\_bk2;

Session altered.

。。。。。。。。。。。。。。。。。。。。。。。。。。。 省略

SQL> exit

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning, Automatic Storage Management, OLAP, Data Mining

and Real Application Testing options

impdp继续导入

\[oracle@rhel6\_lhr dpdump\]$ impdp lhr/lhr directory=DATA\_PUMP\_DIR dumpfile=lhrsql20150515.dmp logfile=lhrsql20150515\_imp.log parallel=4;

Import: Release 11.2.0.3.0 - Production on Fri May 15 19:05:29 2015

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning, Automatic Storage Management, OLAP, Data Mining

and Real Application Testing options

Master table "LHR"."SYS\_IMPORT\_FULL\_02" successfully loaded/unloaded

Starting "LHR"."SYS\_IMPORT\_FULL\_02": lhr/\*\*\*\*\*\*\*\* directory=DATA\_PUMP\_DIR dumpfile=lhrsql20150515.dmp logfile=lhrsql20150515\_imp.log parallel=4

Processing object type SCHEMA\_EXPORT/USER

ORA-31684: Object type USER:"CNY\_ETL" already exists

ORA-31684: Object type USER:"LCM2" already exists

ORA-31684: Object type USER:"FXDM\_ETL" already exists

ORA-31684: Object type USER:"NRDM\_ETL" already exists

ORA-31684: Object type USER:"NRDM" already exists

ORA-31684: Object type USER:"DW\_ETL" already exists

ORA-31684: Object type USER:"SOR" already exists

ORA-31684: Object type USER:"DWUSER1" already exists

ORA-31684: Object type USER:"DWII\_ETL" already exists

ORA-31684: Object type USER:"FXDM" already exists

ORA-31684: Object type USER:"TEST1" already exists

ORA-31684: Object type USER:"LHR" already exists

ORA-31684: Object type USER:"ONL1" already exists

ORA-31684: Object type USER:"CNYDM" already exists

ORA-31684: Object type USER:"DPA" already exists

ORA-31684: Object type USER:"DWUSER" already exists

ORA-31684: Object type USER:"SQCHECK" already exists

ORA-31684: Object type USER:"TEST" already exists

Processing object type SCHEMA\_EXPORT/SYSTEM\_GRANT

Processing object type SCHEMA\_EXPORT/ROLE\_GRANT

Processing object type SCHEMA\_EXPORT/DEFAULT\_ROLE

Processing object type SCHEMA\_EXPORT/PRE\_SCHEMA/PROCACT\_SCHEMA

Processing object type SCHEMA\_EXPORT/DB\_LINK

ORA-31684: Object type DB\_LINK:"SOR"."COG\_DB" already exists

ORA-31684: Object type DB\_LINK:"DPA"."COG\_DB" already exists

Processing object type SCHEMA\_EXPORT/SEQUENCE/SEQUENCE

ORA-31684: Object type SEQUENCE:"SOR"."SEQ\_BDS\_CL\_IP\_RL\_ID" already exists

ORA-31684: Object type SEQUENCE:"SOR"."SEQ\_GOLD\_RATE\_INFO" already exists

ORA-31684: Object type SEQUENCE:"SOR"."SEQ\_MBR\_API\_ELGBLTY" already exists

ORA-31684: Object type SEQUENCE:"SOR"."SEQ\_MBR\_MKT\_ELGBLTY" already exists

ORA-31684: Object type SEQUENCE:"SOR"."SEQ\_MBR\_MMKNG\_ROLE" already exists

ORA-31684: Object type SEQUENCE:"SOR"."SEQ\_ORG\_CD\_HSTRY" already exists

ORA-31684: Object type SEQUENCE:"SOR"."SQ\_DW\_IP\_IP\_RL" already exists

ORA-31684: Object type SEQUENCE:"SOR"."SQ\_MKT\_CLNDR\_ID" already exists

ORA-31684: Object type SEQUENCE:"FXDM"."SEQ\_GOLD\_MBR\_MMKNG\_ROLE\_D" already exists

ORA-31684: Object type SEQUENCE:"FXDM"."SEQ\_GOLD\_MINAMNT\_CONFIG" already exists

ORA-31684: Object type SEQUENCE:"DPA"."SEQ\_BDS\_MBR\_D\_ID" already exists

ORA-31684: Object type SEQUENCE:"DPA"."SEQ\_DL\_MKT\_INFO" already exists

ORA-31684: Object type SEQUENCE:"DPA"."SEQ\_GOLD\_RATE\_INFO" already exists

ORA-31684: Object type SEQUENCE:"DPA"."SEQ\_MBR\_AUTH\_BY\_API\_D" already exists

ORA-31684: Object type SEQUENCE:"DPA"."SEQ\_MBR\_MMKNG\_ROLE\_D" already exists

ORA-31684: Object type SEQUENCE:"DPA"."SEQ\_ORG\_D" already exists

ORA-31684: Object type SEQUENCE:"DPA"."SQ\_DW\_BEST\_QUOTE" already exists

ORA-31684: Object type SEQUENCE:"DPA"."SQ\_DW\_BOND\_MID\_QUOTE\_ID" already exists

ORA-31684: Object type SEQUENCE:"DPA"."SQ\_DW\_MEMBER\_D\_ID" already exists

Processing object type SCHEMA\_EXPORT/TABLE/TABLE

ORA-39151: Table "DPA"."FX\_DL\_MKT\_INFO" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."FX\_FWD\_CPI\_QT" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."FX\_FWD\_DL\_BY\_SF\_CP" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."FX\_FWD\_QT\_BY\_DIR" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."FX\_SPOT\_CPI\_QT" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."FX\_SPOT\_DL\_BY\_SF\_CP" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."FX\_SPOT\_QT\_BY\_DIR" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."FX\_SWAP\_CPI\_QT" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."FX\_SWAP\_DL\_BY\_SF\_CP" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."FX\_SWAP\_DL\_LEG\_MKT\_INFO" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."FX\_SWAP\_QT\_BY\_DIR" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."BOND\_TURNOVER\_RATE\_F" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."MONI\_TORT\_CRCLTN\_AMNT\_F" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "DPA"."MONI\_TURNOVER\_RATE\_F" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "SOR"."BST\_QT\_HIST" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

ORA-39151: Table "SOR"."BST\_QT" exists. All dependent metadata and data will be skipped due to table\_exists\_action of skip

。。。。。。。。。。。。。。。。。。。。。。。。。省略

ORA-39112: Dependent object type TABLE\_STATISTICS skipped, base object type TABLE:"SOR"."QUE\_BOND\_DTL" creation failed

ORA-39112: Dependent object type TABLE\_STATISTICS skipped, base object type TABLE:"SOR"."QUE\_FX\_FWD\_SWAP\_DTL" creation failed

ORA-39112: Dependent object type TABLE\_STATISTICS skipped, base object type TABLE:"SOR"."QUE\_CCS\_DTL" creation failed

ORA-39112: Dependent object type TABLE\_STATISTICS skipped, base object type TABLE:"SOR"."QUE\_CREPO\_DTL" creation failed

ORA-39112: Dependent object type TABLE\_STATISTICS skipped, base object type TABLE:"SOR"."QUE\_FCO\_DTL" creation failed

ORA-39112: Dependent object type TABLE\_STATISTICS skipped, base object type TABLE:"SOR"."QUE\_FRA\_DTL" creation failed

ORA-39112: Dependent object type TABLE\_STATISTICS skipped, base object type TABLE:"SOR"."QUE\_IBO\_DTL" creation failed

ORA-39112: Dependent object type TABLE\_STATISTICS skipped, base object type TABLE:"SOR"."QUE\_IRS\_DTL" creation failed

ORA-39112: Dependent object type TABLE\_STATISTICS skipped, base object type TABLE:"SOR"."QUE\_RIBD\_DTL" creation failed

ORA-39112: Dependent object type TABLE\_STATISTICS skipped, base object type TABLE:"SOR"."FX\_BM\_FXO\_DL\_DAY\_HIST" creation failed

Job "LHR"."SYS\_IMPORT\_FULL\_02" completed with 2165 error(s) at 19:16:19

\[oracle@rhel6\_lhr dpdump\]$

删除错误用户下的包、存过和函数

执行如下的脚本来删除相应的错误对象：

BEGIN

FORCUR IN(SELECT'DROP '|| D.OBJECT\_TYPE ||

' '|| D.OBJECT\_NAME SQLT

FROMdba\_objects d

WHEREd.OWNER =

'LHR'

ANDd.CREATED >=

to\_date('2015-05-15 09:25:27',

'YYYY-MM-DD HH24:MI:SS')

ANDD.OBJECT\_TYPE IN('FUNCTION',

'PROCEDURE',

'PACKAGE'))

LOOP

EXECUTEIMMEDIATECUR.SQLT;

ENDLOOP;

END;

数据校验

执行如下脚本和源库作比较，查看数据是否完整。

SELECTd.OWNER,count(1)

FROMdba\_objects d

WHEREd.OWNER in(SELECTa.username

FROMDBA\_USERS A

WHEREA.account\_status = 'OPEN'

ANDA.username NOTIN

('SYS', 'SYSTEM', 'MGMT\_VIEW', 'SYSMAN', 'DBSNMP'))

group byd.OWNER;

SELECTd.OWNER,

d.status,count(1)

FROMdba\_objects d

WHEREd.OWNER in(SELECTa.username

FROMDBA\_USERS A

WHEREA.account\_status = 'OPEN'

ANDA.username NOTIN

('SYS', 'SYSTEM', 'MGMT\_VIEW', 'SYSMAN', 'DBSNMP'))

group byd.OWNER, d.status;

SELECTd.OWNER,

d.OBJECT\_NAME,

d.OBJECT\_TYPE,

d.status

FROMdba\_objects d

WHEREd.status =

'INVALID'

and d.owner in(SELECTa.username

FROMDBA\_USERS A

WHEREA.account\_status = 'OPEN'

ANDA.username NOTIN

('SYS', 'SYSTEM', 'MGMT\_VIEW', 'SYSMAN', 'DBSNMP'));

总结

到此所有的处理算是基本完毕，过程很简单，但是不同的场景处理方式有很多种，我们应该学会灵活变通，核心即expdp和impdp但是需要做很多的处理。

aboout me

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

本文作者：小麦苗，只专注于数据库的技术，更注重技术的运用

QQ：642808185 若加QQ请注明你所正在读的文章标题

创作时间地点：2015-05-15 10:00~ 2015-05-16 19:00 于唐镇金唐公寓宿舍

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

[Image 1]: