Re: Problem with IMPORT

Thanks Colin and Mick:
I figured if you have to use IGNORE=Y all the constraints have to be disabled before import. It is an inconvenience but not all that bad.

Venkat

>I have just had a similar situation. I had to pre-create about six tables to adjust
storage
>paramters, and then import the entire user schema - about 30 tables. When creating the
six
>tables, I created them without the constraints. Imported the database schema which
enabled
>all constraints after the data was loaded.
>
>Regards,
>Mick
>
>Venkat wrote:
>
>> I am trying to import an export file (USER export) using FROMUSER/TOUSER. The export
was
>> done in DIRECT mode (7.3.3). When I run import logged in as the DBA that created the
>> export file and FROMUSER/TOUSER (ignore=Y. I pre-created all the objects with new
storage
>> settings), it is giving me all kinds of Integrity constraint violated - Primary Keys
not
>> found errors. What am I doing wrong ?
>> Is it because I precreated the tables with all the constraints intact? The import is
done
>> in alphabetical order so I can see why the errors are occurring. I thought import
>> disables all constraints and enables them at the end
Received on Mon May 25 1998 - 09:52:36 CDT