Re: Import/Export problem

Hi,

I would recommend using the import statement with the inctype=system and showonly=y (or whatever the option). Then take the logfile of the output and edit it to re-size the tablespace parameters to suit your target system. Use the resulting ddl to create your tablespaces. You can then use the "indexfile" option of import to generate table and index definitions to a file. Alter the table/index creation statements before running them against the database. Once you've created the appropriately size objects then import the data into the tables with "ignore errors = y" (again-> or whatever the option sytax is). I might have missed a specific or two, but this might work for you.

Coburn Watson  

In article <355B2F58.6CA8846C_at_ecitele.com>, "yaki_at_math.tau.ac.il;yacovw"@ecitele.com wrote:

> This is a multi-part message in MIME format.
> --------------70CFDBE2589A8E6AD199B6FE
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
>
> 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?
  Received on Thu May 14 1998 - 00:00:00 CDT