First page Back Continue Last page Graphics

Continuation of Notes


Notes:

Notes continued from the previous page:
DBMS_METADATA.GET_DDL('TABLE','WEBHITS_EXTERNAL')
------------------------------------------------------

CREATE TABLE "DAVE"."WEBHITS_EXTERNAL"
( "YEAR" VARCHAR2(4),
"REFERER" VARCHAR2(100),
"INTEREST" VARCHAR2(100),
"TECH_SUBJECT" VARCHAR2(250),
"HITS" NUMBER
)
ORGANIZATION EXTERNAL
( TYPE ORACLE_DATAPUMP
DEFAULT DIRECTORY "MICKEYMANTLE"

LOCATION
( 'WEBHITS_EXTERNAL_P1.DMP',
'WEBHITS_EXTERNAL_P2.DMP'
)
)
PARALLEL 2

Moving on to another point related to ORACLE_DATAPUMP, it would be nice it the dump files could be read by any datapump import operation. However, it seems that the dump files can be used only as the source for other external table datapump operations. Unfortunately, I have not been able to read the dump files – even for SQLFILE operations – with anything by external table / ORACLE_DATAPUMP. Unless Oracle provides (or documents) a way of determining the contents of a dump file created in this way, this create the situation that dump files exist but we’ve lost track of what is in them!
Finally, note that, just like datapump export, an ORACLE_DATAPUMP external table will not overwrite an existing data file; an error is returned:
KUP-11012: file webhits_external.dmp in c:\temp already exists