| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: constraints during imp/exp
Say constraints=y in your export parameter file.
Before export create only the schema user, not the tables, they will be automatically created at import time.
jcollins_at_sasquatch.com wrote:
> problem is: i do an export from my 8.0.5 db and import into 8.1.5 and i get unique key and primary key constraint violations when either i or the exp utility tries to enable them.
>
> here are the specifics:
> export from nt 8.0.5 enterprise with utf8 charset.
>
> parfile looks like this:
> file=exp_foo.dmp
> log=exp_foo.log
> owner=foo
> compress=y
> rows=y
> constraints=n
> grants=n
> indexes=n
>
> import into sparc/solaris 2.6 8.1.5 with utf8 charset.
>
> imp system/foo_at_bar file=exp_foo.dmp log=imp_of_exp_foo.log fromuser=foo touser=foo
>
> the really weird thing is that the constraint is enambled and on the source db and when you exp a search for uniqueness yields 82 identical rows!
--
 |
 |