Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Import question

Import question

From: blah <blah_at_blah.com>
Date: Mon, 08 Jul 2002 06:23:13 GMT
Message-ID: <ldaW8.4$5r4.109@news0.optus.net.au>


Hi All,

Can someone please help me out with this?

To refresh a test database with production data I use import. I drop indexes, disable constraints and truncate the tables before doing a user level import.

The problem with this method is that I get alot of constraint already exists errors when doing the import because the constraint in the test database is only disabled.

If I drop all the constraints the not null constraints are not imported because they are part of the create table statement in the import file.

Question 1
How do I stop the above error happening and still have my not null constraints?

Question 2
If I have a not null constraint in my test database called sys_co100 and I am importing from a production database that has an unname index what is stopping the database during import from naming the unnamed index sys_co100 which would cause the index not to be created in the test database and give a constraint already exists error?

Thanks,
Chris Received on Mon Jul 08 2002 - 01:23:13 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US