Re: Importing tables w/large initial extents into a small database

On Mon, 11 May 1998 15:58:14 +0200,
Eugen Nyffeler <eugen.nyffeler_at_ubs.com> wrote:
>Joel Garry wrote:
>
>< cut, cut, cut>
>
>> If you are brave and careful, you can edit the ffff.dmp to have whatever
>> storage characteristics you want. You have to be careful because there are
>> special characters that imp uses in there. I often just strip out the
>> creation statements to another file and convert them to sql with some
>> judicious global replacing in my favorite editor.
>>
>> An alternative is to get one of the various collections of scripts that
>> makes sql create statements from your dictionary. See the tools links off my
>> homepage, or use dejanews to find stuff that's been posted (search for
>> "jared still" for one recent one).
>>
>>
>> --
>> These opinions are my own and not necessarily those of Information Quest
>> jgarry@eiq.com http://www.informationquest.com
>> http://ourworld.compuserve.com/homepages/joel_garry
>> "See your DBA?" I AM the @#%*& DBA!
>
>Try:
>$ imp user/pwd file=exportfile show=y log=yourfile
>
>This should give you a file (yourfile) with all the create statements.
>Change the values , run it prior the import and used the ignore=y during
>the actual import. In this case you don't have to change the orig
>exportfile.

An excellent suggestion, except for the fact the resulting log file requires a whole lot of manual intervention. The resulting file has line breaks in all sorts of weird places, and no easy way to know when the next line is supposed to begin. In other words, you can't just put a ; at the end of each line, substitute DROP for ^TABLE and have a sql file. The one I just tried, had stuff like the end of line being VARCHA" and the beginning of the next line like "R2(30), (with quotes and comma).

Ideally, I would like something editable, substituteable and runnable programmatically. I'm biased towards unix, but the person I was responding to was NT.

Thank you for pointing out that I wasn't too clear about not editing actual export files that will be used in the future with import. That was what I meant by brave and careful. Work on a copy.

jg
--
These opinions are my own and not necessarily those of Information Quest

or Pebble In The Sky                     http://www.informationquest.com

http://ourworld.compuserve.com/homepages/joel_garry jgarry@nospameiq.com
"See your DBA?"  I AM the @#%*& DBA!     Remove nospam to reply.  Sorry.