Oracle加快数据导入速度测试v1

OracIe加快数据导入速度测试

v1.0

目录

1.报告概述4

2.EXP测试4

2.1.Exp学习及测试4

2.1.1.Exp参数4

2.1.2.Expbuffer5

2.1.3.ExpDIRECT8

2.1.4.Exp导出测试时间对比9

2.2.Exp导出问题11

221.Exp使用直接路径写,导入空的分区会报错11

2.2.2.Exp使用直接路径写，导入存在default值的字段会报错14

2.2.3.exp导出报错EXP-00006,0000016

2.2.4.exp导出报错EXP-0011316

3.Expdp测试17

3.1.Expdp相关的信息17

3.1.1.Expdp预估导出大小17

3.1.2.Expdp的导出文件方式19

3.1.3.Impdp的导入文件方式20

3.2.数据泵使用的其它信息21

3.2.1.数据泵相关的进程信息查询21

3.2.2.如何获取每个类型的详细时间22

3.2.3.如何清理数据泵的作业表23

3.2.4.小结27

3.3.数据泵的案例27

3.3.1.分区太多Bug2995902527

3.3.2.SYS_EXPORT_SCHEMA_01表blockchange变化很高28

3.3.3.数据泵导出缓慢-Sharedpool收缩导致28

3.3.4.Expdp遭遇ORA-07445的背后29

3.3.5.内存太小expdp报错UDE-31623ORA-3162329

3.3.6.Expdp由于存储问题JOB状态为DEFINING31

3.3.7.ImpdpORA-01628undosegmentsmax#extents(32765)32

3.3.8.小结34

3.4.expdp的并彳亍35

3.4.1.Oracle数据泵导出使用并行参数，单个表能否真正的并行？35

3.4.2.阅读并行pdb文档37

3.4.3.阅读并行Mos文档38

3.4.4.OracleLOB可以并行导出吗38

3.4.5.OracleIndex可以并行导入吗38

3.4.6.如何加快泵导入的速度40

3.4.7.数据泵19c导出并行42

3.4.8.数据泵19c导入并行1004644

3.4.9.数据泵19c导入索引增强45

3.4.10.数据泵慢分析47

3.4.11.小结48

4.Exp与Expdp的区别48

4.1.Mos官方说法48

4.2.实验及个人总结49

5.附件51

1.报告概述

本篇文档学习测试Oracle加快数据导入速度进行测试。

数据迁移Oracle内部的逻辑数据迁移一般使用exp,expdp,imp,impdp;那么当数据量比较小的时候都无所

谓，但是当数据量很大的情况下，如何加快导入的速度呢？

Oracle数据泵的并行在11g,19c有什么不同,如何加快数据导入的速度？

本篇文章基于上述问题进行学习测试！

2.EXP测试

2.1.Exp学习及测试

2.1.1.Exp参数

Exp还有比较有意思的参数，可以设置报错结束时间，给你一个机会在一定时间内解决问题，而不是直接

停止！这个功能在数据泵是默认使用的，例如表空间满导入报错，并不会直接终止Job会给一定的时间让用

户进行处理，当然超时还是会报错终止！

WhatistheuseoftheRESUMABLEparameterinEXPORT?(DocID152013.1)

Buffer

ALERT:Export(EXP)WithLargeBUFFERCanSilentlyProduceACorruptDumpFile(DocID223399.1)

TheexportparameterBUFFERspecifiesthesizeinbytesofthebufferusedtofetchrowsfromatable.Adata

corruptioncanoccuriftheBUFFERparameterhasbeensettoavaluesomorethan32,768rowswillbefetched.

ThisimpliesarelationtothelengthoftherowsthatarefetchedintheBUFFER.Inaddition,thestructureofthetable

andtheactualdataintherows,haveanimpactontheoccurrenceofthisbugtoo.Therefore,anexactandsafevalue

fortheBUFFERparametercannotbegiven.

version

Forexample:

->theAVG_ROW_LENGTHis100bytes

->thetablehasmorethan32,768rows

->criticalBUFFERvalue3276800orhigher(32k*100;about3.1Mb)

->datacorruption*can*occurif:BUFFER=3200000(orhigher)

-buffer的参数取决于常规路径导出时，达到这个buffer阈值后写入dump文件中，当buffer设置为

3.2Mbytes,buffer单位bytes可能会崩溃。

FILESIZE

ORA-01403duringexportusingFILESIZEparameter(DocID282079.1)

Inwindows,themaximumfilesizelimitis2GB.

Use2000M,insteadof2GB

EXP-00002:Errorinwritingtoexportfile

EXP-00056:Oracleerror1403encountered

ORA-01403:Nodatafound

EXP-00000:Exportterminatedunsuccessfully

exp<user>/<password>file='dump_l.dmpdump_2.dmp,dump_3.dmp1

log=export.logfilesize=2000Mtables=<table_name>

举例：

expuserid=lhr/lhrfile=/tmp/testl,test2,test3,test4,test5filesize=2Glog=test.log

举例：迁移项目使用的参数列表

SQL>SELECTCURRENT_SCNFROMV$DATABASE；

CURRENT_SCN

26238040

[oracle@t3vi/home/oracle/exp_schema.par

userid="exp_user/exp_user"

OWNER=YZ

FILE=/home/oracle/exp_schema_yz01.dmp

LOG=/home/oracle/exp_schema_yz01.log

FLASHBACK_SCN=26238040

statistics=none

direct=N

feedback=10000

--buffer=1024000

--FLASHBACK导出SCN号

--statistics是否迁移统计信息，否

--buffer导出cache大小，满足cache时写入file

--direct是否直接路径写

--FEEDBACK显示每X行(0)的进度

nohuptimeexpparfile=exp_schema.par&

2.1.2.Expbuffer

.EXP10046TraceBuffer1024000

SQL>createuserexp__useridentifiedby"exp_user";

SQL>grantdbatoexp_user;

[oracle@t3expexp_user/exp__user

Export:Release.0-ProductiononThuMay2602:48:372022

Copyright(c)1982,2011,Oracleand/oritsaffiliates.Allrightsreserved.

Connectedto:OracleDatabase11gEnterpriseEditionRelease.0-64bitProduction

WiththePartitioning,OLAP,DataMiningandRealApplicationTestingoptions

Enterarrayfetchbuffersize:4096>

--此时,对于Oracledb来说有一个新的连接，可以对这个连接开启10046trace

sqlplus/assysdba

colsidfor999999

colserial#for99999

colusernamefora20

colprogramfora20

colsql_idfora30

coleventfora30

setlinesize140

selectsidjserial#username,program,sql_idjeventfromv$sessionwhereusername='EXP_USER';

SIDSERIAL#USERNAMEPROGRAM-SQL_IDEVENT

4323EXP_USERexp@t3(TNSVI-V3)SQL*Netmessagefromclient

SQL>SELECTS.USERNAME,

P.SPIDOS_PROCESS_ID

FROMV$SESSIONS,V$PROCESSP

WHERES.PADDR=P.ADDR

ANDS.SID=43;

USERNAMEOS_PROCESS_ID

EXPJJSER19633

V_0S_PID=19633

V_LEVEL=12

v_exec_oral0046trc=$(echo"oradebugsetospid"${V_OS_PID)";

oradebugunlimit;

oradebugevent10046tracenamecontextforever4level"${V_LEVEL}“；

oradebugtracefile_name;

exit;"|sqlplus-s/assysdba|sed-e'/A*$/d')

一执行导出

[oracle@t3~]$expexp_user/exp_user

Enterarrayfetchbuffersize:4096>1024000

Exportfile:expdat.dmp>/home/oracle/exp_schema_yz_10046_01.dmp

(l)E(ntiredatabase),(2)U(sers),or(3)T(ables):(2)U>U

Exportgrants(yes/no):yes>

Exporttabledata(yes/no):yes>

Compressextents(yes/no):yes>no

ExportdoneinUS7ASCIIcharactersetandAL16UTF16NCHARcharacterset

serverusesAL32UTF8characterset(possiblecharsetconversion)

Abouttoexportspecifiedusers・・・

Usertobeexported:(RETURNtoquit)>YZ

Usertobeexported:(RETURNtoquit)>

Exportterminatedsuccessfullywithwarnings.

■■关闭该session的10046,由于exp导出完成session自动关闭，因此10046sessiontraceoff提示找不到进

程id

$echo"${v__exec_oral0046trc}"

Oraclepid:19,Unixprocesspid:19633,image:oracle@t3(TNSVI-V3)

Statementprocessed.

Statementprocessed.

/u01/app/oracle/diag/rdbms/dgtest001/dgtest001/trace/dgtest001__ora_19633.trc

.查询exp最慢的SQL

tkprof/u01/app/oracle/diag/rdbms/dgtest001/dgtest001/trace/dgtest001_ora_19633.trc

dgtest001_ora_19633.txt

[oracle@t3~]$catdgtest001_ora_19633.txt|grep-iTOTAL|grep-vwaited|grep-vFOR|awk-F',

'(print$4}'|sort-n|tail-10

0.86

0.87

0.93

0.96

1.07

2.55

2.77

3.27

40.70

69.35

********************************************************************************

SQLID:Ifrvh4kv91y7kPlanHash:903426141

SELECT/*+NESTEDTABLE_GETREFS+*/"YZ"."TEST_BIG1".*

FROM

"YZ"."TEST_BIG1"

callcountcpuelapseddiskquerycurrentrows

Parse10.000.000200

Execute10.000.000000

Fetch4813.7440.6916370524175005544384

total4833.7540.7016370524175205544384

Missesinlibrarycacheduringparse:1

Optimizermode:ALL_ROWS

Parsinguserid:94

Numberofplanstatisticscaptured:1

Rows(1st)Rows(avg)Rows(max)RowSourceOperation

554438455443845544384TABLEACCESSFULLTEST_BIG1(cr=241750pr=163705pw=0

time=848380uscost=46664size=1202608521card=5809703)

Elapsedtimesincludewaitingonfollowingevents:

EventwaitedonTimesMax.WaitTotalWaited

SQL*Netmessagetoclient4810.000.00

directpathread12922.0934.11

SQL*Netmoredatatoclient277120.234.97

SQL*Netmessagefromclient4812.0021.56

dbfilesequentialread20.000.00

********************************************************************************

我们可以发现，导出的大表直接路径读totalwaited等待最多，sql解析一次，执行一次，但是fetch达到

481次？？？select可以认为一个大表的数据导出消耗40s.

.EXP10046TraceBuffer20480000

[oracle@t3~]$catdgtest001_ora_25733.txt|grep-iTOTAL|grep-vwaited|gr叩-vFOR|awk-F

'(print$4)1|sort-n|tail-10

0.86

0.87

0.90

3.04

4.03

5.92

7.92

11.58

50.45

99.59

********************************************************************************

SQLID:Ifrvh4kv91y7kPlanHash:903426141

SELECT/*+NESTEDTABLEGETREFS+*/"YZ"."TEST_BIG1".*

FROM

“YZ"."TEST_B：[G1”

callcountcpuelapseddiskquerycurrentrows

Parse10.000.000200

Execute10.000.000000

Fetch683.0150.4516370524134505544384

total703.0150.4516370524134705544384

Missesinlibrarycacheduringparse:1

Optimizermode:ALL_ROWS

Parsinguserid:94

Numberofplanstatisticscaptured:1

Rows(1st)Rows(avg)Rows(max)RowSourceOperation

554438455443845544384TABLEACCESSFULLTEST_BIG1(cr=241345pr=163705pw=0

time=1217368uscost=46664size=1202608521card=5809703)

Elapsedtimesincludewaitingonfollowingevents:

EventwaitedonTimesMax.WaitTotalWaited

SQL*Netmessagetoclient680.000.00

directpathread12920.8441.45

SQL*Netmoredatatoclient279150.205.82

SQL*Netmessagefromclient680.7116.17

dbfilesequentialread20.000.00

我们可以看到fetch获取的次数从481次降低到了68次，但是时间反而延长了！cache加大没有看到时间变少！

从测试结果看,buffer越大并不代表导出时间越少，因为从读取写入cache的时间会更长，常规路径写的

时间消耗分为2部分：1.从table读取数据写入cache;

2.从cache写入磁盘file文件中；

当cache加大时，第一个步骤的时间加大了，由于测试数据不够多，了解即可。

2.1.3.ExpDIRECT

参数DIRECT：常规路径导出与直接路径导出(文档ID155477.1)

OracleDatabase-EnterpriseEdition-Version7.3.0.0to[Release7.3.0to11.2]

1.2.ConventionalpathExport.

ConventionalpathExportusestheSQLSELECTstatementtoextractdatafromtables.Dataisread

fromdiskintothebuffercache,androwsaretransferredtotheevaluatingbuffer.Thedata,

afterpassingexpressionevaluation,istransferredtotheExportclientwhichthenwritesthe

dataintotheexportfile.

1.3.DirectpathExport.

WhenusingaDirectpathExport,thedataisreadfromdiskdirectlyintotheexportsession's

programglobalarea(PGA):therowsaretransferreddirectlytotheExportsession'sprivate

buffer.ThisalsomeansthattheSQLcommand-processinglayer(evaluationbuffer)canbe

bypassed,becausethedataisalreadyintheformatthatExportexpects.Asaresult,unnecessary

dataconversionisavoided.ThedataistransferredtotheExportclient,whichthenwritesthe

dataintotheexportfile.

1.4.TheparameterDIRECTspecifieswhetheryouusethedirectpathExport(DIRECT=Y)orthe

conventionalpathExport(DIRECT=N).

1.5.TousedirectpathExport,specifytheDIRECT=Yparameteronthecommandlineorinthe

parameterfile.ThedefaultisDIRECT=N,whichextractsthetabledatausingtheconventional

path.

1.6.Thisparameterisonlyapplicabletotheoriginalexportclient.ExportDataPump(expdp)

usesaDirectPathunloadbydefaultandswitchestoExternalTablemodeifrequired.

2.Performanceissues.

2.1.DirectpathExportcanbemuchfasterthanConventionalpathExportbecausetheSQLcommand-

processinglayerisbypassed.

2.2.YoumaybeabletoimproveperformancebyincreasingthevalueoftheRECORDLENGTHparameter

whenyouinvokeadirectpathExport.Yourexactperformancegaindependsuponthefollowing

factors:

-DB_BLOCK_SIZE

-thetypesofcolumnsinyourtable

-yourI/Olayout(thedrivereceivingtheexportfileshouldbeseparatefromthediskdrive

wherethedatabasefilesreside)

ThefollowingvaluesaregenerallyrecommendedforRECORDLENGTH:

-multiplesofthefilesystemI/Oblocksize

-multiplesofDB_BLOCK_SIZE

Forexample,invokingaDirectpathExportwithamaximumI/Obufferof64kbcanimprovethe

performanceoftheExportwithalmost50%.Thiscanbeachievedbyspecifyingtheadditional

ExportparametersDIRECTandRECORDLENGTH.E.g.:

>exp<LOGIN>/<PASSWORD>FILE=<DUMP_NAME>.dmpLOG=<LOG_NAME>>.log\

FULL=yDIRECT=yRECORDLENGTH=65535―

>imp<LOGIN>/<PASSWORD>FILE=<DUMP_NAME>.dmpLOG=<LOG_NAME>.log\

FULL=yRECORDLENGTH=65535

2.3.ADirectpathExportdoesnotinfluencethetimeittakestoImportthedata.Thatis,an

exportfilecreatedusingDirectpathExportorConventionalpathExport,willtakethesame

amountoftimetoImport.

3.4.导出参数QUERYo

参数QUERY仅适用于常规路径导出。不能在直接路径导出（DIRECT=Y）中指定。此QUERY参数允许您在执行表模式

导出时从一组表中选择行的子集。

例子：

>exp<LOGIN>/<PASSWORD>TABLES=<TABLE_NAME>QUERY=\"WHERE<COLUMN_NAME1>=\1<VALUE1>\'和

<COLUMN_NAME2>\<VALUE2>\"

3.5.导出参数BUFFERo

BUFFER参数仅适用于常规路径导出。它对直接路径导出没有影响。此BUFFER参数指定用于获取行的缓冲区的大小

（以字节为单位）。它确定由Export获取的数组中的最大行数。对于直接路径导出，使用RECORDLENGTH参数指定

Export用于写入导出文件的缓冲区大小。

3.6.导出参数RECORDLENGTHo

RECORDLENGTH参数指定文件记录的长度（以字节为单位）。您可以使用此参数指定导出I/O缓冲区的大小（最大值

为64kb）。更改RECORDLENGTH参数仅影响写入磁盘之前累积的数据大小。它不影响操作系统文件块的大小。如果

您未定义此参数，则它默认为与平台相关的BUFSIZ值（大多数情况下为1024字节）。

如果有迁移项目必须使用exp时可以考虑仔细阅读上述mos文章，其中我们梳理重点信息：

源端db版本,可以filter大部分的异常！

1.默认情况下exp的导出是先读取到内存中的buffer,buffer的大小由exp参数BUFFER控制,数据写

入足够的buffer之后，写入导出的文件；

2.如果使用直接路径写后,exp直接读取数据写入磁盘中的文件；

3.直接路径写or常规路径导出对导入时间无影响；

4.直接路径写的cache和什么有关系呢？和另一个参数RECORDLENGTH最大64kB,达到这个参数

值开始写入磁盘数据，默认与平台BUFSIZE值相同1024bytes;

2.1.4.Exp导出测试时间对比

SQL>createuserexp_useridentifiedby"exposer";

SQL>grantdbatoexp_user;

--制造一个大表进行测试

SQL>sqlplusyz/yz

createtabletest__biglasselect*fromdba_objects;

insertintotest_biglselect*fromtest_bigl;

r

r

SQL>commit;

SQL>selectownersegment_name^segment_type>bytes/1024/1024fromdba_segmentswhereowner=*YZ

andsegment_name="TEST_BIG1";

OWNER-一SEGMENT_NAMESEGMENT_TYPEBYTES/1024/1024

YZTEST_BIG1TABLE1348

SQL>SELECTCURRENT_SCNFROMV$DATABASE;

CURRENT_SCN

26238040

--排除测试干扰，重启测试库执行导出操作！！！

SQL>shutdownimmediate;

startup

[oracle@t3~]$vi/home/oracle/exp_schema.par

userid="exp__user/exp__user"

OWNER=YZ

FILE=/home/oracle/exp__schema__yz01.dmp

LOG=/home/oracle/exp_schema_yz01.log

FLASHBACK_SCN=26238040

statistics=none

direct=N

feedback=10000

--buffer=1024000

--FLASHBACK导出SCN号

--statistics是否迁移统计信息，否

--buffer导出cache大小，满足cache时写入file

--direct是否直接路径写

--FEEDBACK显示每X行(0)的进度

nohuptimeexpparfile=exp_schema.par&

序列direbufferRECORDLENGTHDump_size(Mb)Time

Ct(bytes)

常规导出1N默认0815real0m40.837s

user0m10.040s

sys0ml.556s

常规导出2N10240000815real0m39.497s

userOmlO.OHs

sys0m0.690s

直接路径导3Y0默认802real0m26.793s

user0m0.360s

sys0m0.830s

直接路径导4Y065536802real0m24.982s

user0m0.133s

sys0m0.476s

2.2.Exp导出问题

2.2.1.Exp使用直接路径写,导入空的分区会报错

参数DIRECT：常规路径导出与直接路径导出(文档ID155477.1)

警告：如果存在空表分区，直接路径导出(EXP)会损坏转储(文档ID1604983.1)

OracleDatabase-EnterpriseEdition-Versionandlater

Youperformedadirectpathexport(table,schemaorfull)usingthetraditionalexportutility

(EXP).Iftheexportedobjectsincludeanemptytablepartition,thentheexportdumpiscorrupt

andcannotbeimported.

Onlyexpversions>=areaffected.Thetraditionalexportutilityisde-supported

beginningwiththeversion11gandisnomoremaintained.

实验测试，创建一个分区表,制造一个空的分区没有数据，没有segments

connectyz/yz

createtablepart001

(

col001number

col002varchar2(100)

)

partitionbyrange(col001)

(

partitionp001valueslessthan(10),

partitionp002valueslessthan(100),

partitionp003valueslessthan(1000)

)；

insertintopart001values(5,'Text5');

insertintopart001values(500,'Text500');

commit;

实验直接路径写，进行导出导入测试

#>expyz/yzfile=part001.dmptables=part001direct=y

Thiswillshow:

AbouttoexportspecifiedtablesviaDirectPath・・•

・,exportingtablePART001

,,exportingpartitionP0011rowsexported

・,exportingpartitionP0020rowsexported

,,exportingpartitionP0031rowsexported

Exportterminatedsuccessfullywithoutwarnings.

SQL>droptablepart001;

[oracle@t3~]$impyz/yzfile=part001.dmpfull=y

Import:Release.0-ProductiononWedMay2511:45:272022

Copyright(c)1982,2011,Oracleand/oritsaffiliates.Allrightsreserved.

Connectedto:OracleDatabase11gEnterpriseEditionRelease.0-64bitProduction

WiththePartitioning,OLAP,DataMiningandRealApplicationTestingoptions

ExportfilecreatedbyEXPORT:Vil.02.00viadirectpath

importdoneinUS7ASCIIcharactersetandAL16UTF16NCHARcharacterset

importserverusesAL32UTF8characterset(possiblecharsetconversion)

,importingYZ'sobjectsintoYZ

・importingYZ'sobjectsintoYZ

,,importingpartition"PART001":"P001"1rowsimported

,,importingpartitionMPART001":"P002"

IMP-00009:abnormalendofexportfile

Importterminatedsuccessfullywithwarnings.

一使用参数show可以查询异常信息

[oracle@t3impyz/yzfile=part001.dmpfull=yshow=y

Import:Release.0-ProductiononWedMay2511:46:112022

Copyright(c)1982,2011,Oracleand/oritsaffiliates.Allrightsreserved.

Connectedto:OracleDatabase11gEnterpriseEditionRelease.0-64bitProduction

WiththePartitioning,OLAP,DataMiningandRealApplicationTestingoptions

ExportfilecreatedbyEXPORT:V11.02.00viadirectpath

importdoneinUS7ASCIIcharactersetandAL16UTF16NCHARcharacterset

importserverusesAL32UTF8characterset(possiblecharsetconversion)

,importingYZ'sobjectsintoYZ

•importingYZ'sobjectsintoYZ

"CREATETABLE“PART001"("COL001"NUMBER,"COL002"VARCHAR2(100))PCTFREE1"

"0PCTUSED40INITRANS1MAXTRANS255TABLESPACE"USERS'*PARTITIONBYRANGE"

"("COL001")(PARTITION"P001"VALUESLESSTHAN(10)PCTFREE10PCTUSED4"

"0INITRANS1MAXTRANS255STORAGE(INITIAL8388608NEXT1048576MINEXTENTS1"

"FREELISTS1FREELISTGROUPS1BUFFER_POOLDEFAULT)TABLESPACE"USERS"LOGG"

"INGNOCOMPRESS,PARTITION"P002"VALUESLESSTHAN(100)PCTFREE10PCTUSED"

"40INITRANS1MAXTRANS255TABLESPACE"USERS"LOGGINGNOCOMPRESS,PARTITIO"

"N"P003nVALUESLESSTHAN(1000)PCTFREE10PCTUSED40INITRANS1MAXTRANS"

"255STORAGE(INITIAL8388608NEXT1048576MINEXTENTS1FREELISTS1FREELIST"

"GROUPS1BUFFER_POOLDEFAULT)TABLESPACE"USERS"LOGGINGNOCOMPRESS)"

,,skippingpartition"PART001":"P001"

..skippingpartition"PART001":"P002"

IMP-00009:abnormalendofexportfile

Importterminatedsuccessfullywithwarnings.

OracleMos的解决方案：

intheexportoutput(orlogfile),thenyouobtainacorruptdump.Youcanverifythedumpwith

thecommands:

#>impuser/passwfull=y

or:

#>impuser/passwfull=yshow=y

whichwillshowyouoneofthebehaviorslistedabove.

Toworkaroundthispleaseuse:

-conventionalpathexport(expdirect=n)

Or:

-materializetheemptypartitionsbeforerunningdirectpathexports:

connect/assysdba

execdbms_space_admin.materialize__deferred_segments(schema_name=>'TEST*,table_name=>

'PART001',partition_name=>'P0021);

Or:

-DataPumpexport(expdp)

尝试一下exec的存储过程的调用？为什么能规避问题？

一导入后是不完整的导入，数据会丢失！

selectPARTITION__NAMEcount(*)fromuser_segmentswheresegment_name='PART001'groupby

PARTITION__NAME;

PARTITION_NAMECOUNT(*)

P0011

可以发现Oraclellg新特性，段延迟创建，如果没有数据则不在分配segments,那么直接路径写的方式会

导入报错！但是我们可以使用存储过程指定对没有数据的空的分区，指定创建一个segments,这样再次使用

exp迁移不报错！

新建测试表进行测试

--user

createtablepart002

(

col001number,

col002varchar2(100)

)

partitionbyrange(col001)

(

partitionp001values