Import gives errors

[samdba]

Hi all,

I did the following:

step1 on serverA
exp80 system/manager@prod --(to prod DB) file=expprod.dmp log=expprod.log full=y rows=Y consistent=y

Here. Oracle ver. is 8.0.5

step2
copy expprod.dmp over to new server (serverB)

step3
imp80 system/manager@dev (to serverB)
file=expprod.dmp log=impdev.log full=y ignore=y

Here, Oracle ver. is 8.1.7.1.5

I did get some errors
=============
IMP-00019: row rejected due to ORACLE error 1
IMP-00003: ORACLE error 1 encountered
ORA-00001: unique constraint (constraint_name) violated

and similar errors.


My questions:

1. Is it because, I have not disabled the constraints?

2. If I disable the constraints such as primary key, won't it insert duplicate records?

3. Say for example, in the table exported, there are 5 columns and the table already there in the database in which import to be done, has 4 or 6 columns, will it still do import into that table?

4. If I drop the table before doing import, what happens to the privileges granted on that table to users?

5. Should I drop whole user with cascade option before doing import and then do the userbased import instead of FULL?

Pl. help.

Thanks in Adv.

[Shestakov]

If u need only rows from dump file u can truncate table before import.

[samdba]

If u need only rows from dump file u can truncate table before import.


Actually, I want to do FULL import and not just rows. also indexes, packages and everything.

Thanks,

[Shestakov]

I asked u about rows, because u should deside for yourself :
"Me need old rows in this table or not? If not need, then i can truncate table, if need i'll get a lot of messages about constraints violation.
And that's it.

[samdba]

Can somebody reply to my questions 3,4 and 5 pl?

[marist89]

3. 4-no, 6-yes as long as they are named the same.
4. the privs get dropped
5. if you do, you also drop any privs that might be granted to that user from other schemas.