Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> imp.exe full=y imports SYSTEM's objects, violates constraints...
I am attempting full export from DB1 Orcl 9.2.0.1 on Win -> full
import into the empty, pre-created DB2 9.2.0.7 on different Win
system using this (DOS batch) command:
%IMPUTIL% %IMPORTER%/%IMPORTERPWD%@%NETALIAS% file="%DUMPPATH%\%DUMPFILE%"
log="%IMPLOG%" full=y ignore=y commit=y buffer=65536
Import log records reveals many, many errors due to full import's attempt to import objects belonging to SYSTEM, OUTLN, WMSYS, DBSNMP. Of course these schemas already existed in target db as they were created at the database creation time therefore the errors and violations like:
---
. importing SYSTEM's objects into SYSTEM
IMP-00061: Warning: Object type "SYSTEM"."REPCAT$_OBJECT_NULL_VECTOR"
already exists with a different identifier
---
. . importing table "REPCAT$_AUDIT_ATTRIBUTE"
IMP-00019: row rejected due to ORACLE error 1 IMP-00003: ORACLE error 1 encountered ORA-00001: unique constraint (SYSTEM.REPCAT$_AUDIT_ATTRIBUTE_PK) violatedIMP-00003: ORACLE error 1 encountered
---
. importing WMSYS's objects into WMSYS . . importing table "WM$ADT_FUNC_TABLE" 0 rows imported . . importing table "WM$ENV_VARS" IMP-00019: row rejected due to ORACLE error 1
Column 2 9.2.0.1.0 0 rows imported
---
Now the question is - should the above errors worry me, and if so - can anything be done to fix the above mess (especially since patch level wise import database is not necessarily at the same level as the "donor" database)?
Purpose of the exercise is to come up with the least troublesome way (find simplest, most straightforward procedure with min amount of steps) to move one development database from one Win "box" to another Win "box" (may be with higher patch level and quite likely with tablespaces/files sitting in different locations)...
Branimir
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Oct 14 2005 - 14:25:56 CDT
![]() |
![]() |