Re: Import/Export problem

On Tue, 19 May 1998 17:04:19 -0400, Mark Adams <madams_at_jewels.com> wrote:
>John Kanagaraj wrote:
>
>> Steve Miller wrote:
>> >
>> > Yacov,
>> >
>> > I'm not very familiar with what you were initially trying to do,
 but as
>> > far as your question of modifying the .dmp file directly, you won't
 be able
>> > to do that. Assuming you can't export again to get your "create
>> > statements" for modification, I've had fairly good luck using
 strings
>> > against the .dmp file and then re-directing into a another file -
 which I
>> > then modify to re-create the object.
>> >
>> > for example:
>> >
>> > strings my_table.dmp | egrep -i "create table" > my_table.sql
>> >
>> > I then vi my_table.sql, modify the table create statment and/or
 storage,
>> > and then use that to create my table in the database. I'll then
 import
>> > my_table.dmp and ensure I specify ignore=Y. That should do it. I'm
 not
>> > sure if this answers the initial question, but I hope it helps. If
 I
>> > "missed it", let me know and I'll take another shot.
>> >
>> > Steve
>> >
>> > Yacov Wolfowicz <yacovw_at_ecitele.com> wrote in article
>> > <355B2F58.6CA8846C_at_ecitele.com>...
>> > > Hi,
>> > > First, let me thank all those who bothered to try and help me.
>> > > Thanks very much.
>> > >
>> > > But...
>> > > Its not so simple. It seems that the database was create somewhere
 else
>> > > and then imported to our machine. The size of all db objects (
 tables,
>> > > indexes etc. ) conforms with the large db. As a result, when i try
 to
>> > > import it to my personal machine ( after creating tablespaces and
 db
>> > > files ) i get error messages saying something like
>> > >
>> > > "Cannot create initial extent......"
>> > >
>> > > Maybe the db was created at our site using backup and restore, or
 else
>> > > the objects should hold their initial settings, Or maybe the db
 was
>> > > created with gigantic objects to begin with.
>> > >
>> > > The question remains : is there any way i can edit the .dmp file?
>> > > --
>> > > Life is hard...
>> > > and then you die
>>
>> Hi All!
>> One thing to watch out for is "COMPRESS EXTENTS" being set to "yes" on
>>
>> export - this means that large tables in many extents (which could fit
>>
>> into the existing tablespaces) gets compressed into 1 large initial
>> extent. There is no way around this but to pre-create all such tables
>> and ignore errors during import.
>>
>> HTH
>> John Kanagaraj
>
> Of how much use would a program to parse the dump file's sql(YACC),
>calc the table/index size and reconstitue the sql with the proper
>sizings be? I have written such a program (it still needs some work on
>selects and views -ie. not all shift/conflicts are resolved).
>
>-Mark Adams
>

Very useful, IMO. Be sure and test with large numbers of fields in a table and some spaghetti constraints.

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.