Re: Integrity Constraints

ORACLE does the export in alphabetical table order, so if your child comes before your parent you'll get an error when it tries to enable the foreign key constraint. However, there is a fairly simple workaround. Once you've done the initial import, run it again with ROWS=N. This won't import any data, but will add the constraints missed off by the first import, assuming the first import successfully built your tables. You'll get error messages when it tries to enable constraints that it could successfully enable during the first import, but as long as you're using IGNORE=Y then so what ? Received on Sat Feb 22 1997 - 00:00:00 CET