Apress.Expert.Oracle.Database.Architecture.9i.and.10g.Programming.Techniques.and.Solutions.Sep.2005

112
CHAPTER 3 ■ FILES
That is just the head, or top, of the file; binary data is represented by the ....... (don’t be
surprised if your terminal “beeps” at you when you look at this data). Now, using a binary FTP
(same caveat as for a DMP file!), I moved this allobject.dat file to a Windows XP server and
created a directory object to map to it:
tkyte@ORA10G> create or replace directory TMP as 'c:\temp\'
2 /
Directory created.
Then I created a table that points to it:
tkyte@ORA10G> create table t
2 ( OWNER VARCHAR2(30),
3 OBJECT_NAME VARCHAR2(30),
4 SUBOBJECT_NAME VARCHAR2(30),
5 OBJECT_ID NUMBER,
6 DATA_OBJECT_ID NUMBER,
7 OBJECT_TYPE VARCHAR2(19),
8 CREATED DATE,
9 LAST_DDL_TIME DATE,
10 TIMESTAMP VARCHAR2(19),
11 STATUS VARCHAR2(7),
12 TEMPORARY VARCHAR2(1),
13 GENERATED VARCHAR2(1),
14 SECONDARY VARCHAR2(1)
15 )
16 organization external
17 ( type oracle_datapump
18 default directory TMP
19 location( 'allobjects.dat' )
20 )
21 /
Table created.
And now I’m able to query the data unloaded from the other database immediately:
tkyte@ORA10G> select count(*) from t;
COUNT(*)
----------
48018
That is the power of the Data Pump file format: immediate transfer of data from system to
system over “sneaker net” if need be. Think about that the next time you’d like to take a subset
of data home to work with over the weekend while testing.
One thing that wasn’t obvious here was that the character sets were different between
these two databases. If you notice in the preceding head output, the character set of my Linux
database WE8ISO8859P1 was encoded into the file. My Windows server has this: