some thoughts, i apologize if this is redundant to other posts, I didn't
*read* all.
1) No matter how you do this it would be prudent to slice it up into smaller
pieces.
2) Direct Path formats are fussy, and, if i remember, prefer/need fixed
length fields.
Fixed lengths in a non-varchar field could mean LOTS of dead space
3) Exception processing and rollback/commit should be important
considerations (mentioned).
I think you have to specify an exception file for SQL loader ????
4) Tablespace extents can be a bigger problem.
5) Frequently, data of this proportion (size) is partitioned to speed the
overall application performance.
There may be significant performance and logistical benefits to
partitioning.
It might be worth while reviewing some of the Oracle Tuning books or
posting on a list like Orafans.
6) If your only going to do this one time sounds like Perl would do it.
A little slower, ehh, who cares.
You're not the guy that trashed the NY stock exchange are you? ;-0
7) If it dies, your just going to drop the table, right??
8) Did anyone mention disabling indexes ??
9) ditto with constraints
10) IF your going to write Perl code, to prep the file(s), split the files,
validate data, etc. just do Perl.
11) Didn't they just announce a DBD::Oracle Pure-OCI module like last week
???
Check the announce archives.
They did for Python. (sorry)
Sounds like a *fun* project.
clp
P.S. don't try this at home.
-----Original Message-----
From: Marcotullio, Angelo [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 08, 2001 1:11 PM
To: [EMAIL PROTECTED]
Subject: RE: Data Extract
Orlando wrote: "There's a way to bypass rollback- and index
creation during
the import, which speeds things up a lot. I believe this is the same
technique used by the SQL*Loader "direct path" option."
No, this is not correct. SQL*Loader "direct path" writes
database blocks
directly. It does not do inserts. Any form of import will
do inserts.
-----Original Message-----
From: Orlando Andico [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 08, 2001 11:50 AM
To: Marcotullio, Angelo
Cc: [EMAIL PROTECTED]
Subject: RE: Data Extract
On Fri, 8 Jun 2001, Marcotullio, Angelo wrote:
..
> Oracle export (exp) creates a binary file that can only be
loaded using
the
> import (imp) program. The problem with import is that it
uses insert
> statements to load the data.
There's a way to bypass rollback- and index creation during
the import,
which speeds things up a lot. I believe this is the same
technique used by
the SQL*Loader "direct path" option.
--
Orlando Andico <[EMAIL PROTECTED]>
Mosaic Communications, Inc.
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GE d(-) s: a-25 C++++ UBLSI++++$ P+++ L+++>++++ E- W++ N(+)
o K? w O-- M- !V PS(++) PE- Y PGP-- t(+)@ 5(+) X++@ R(+) tv@
b++ DI++ G e++@ h--(*) r% y+
------END GEEK CODE BLOCK------
