Q
Problem solve Get help with specific problems with your technologies, process and projects.

Tons of errors with import of replicated database

I am trying to import from an exported dump file. The database which is to be imported has been replicated as well. It gave me tons of errors. I then dropped the newly created DB, re-created it and performed import twice as suggested by an experienced DBA. Please tell me what to do and how to resolve the issue.

I am trying to import from an exported dump file. The database which is to be imported has been replicated as well. The import is being performed in a newly created database which was created using the Oracle Database Configuration Assistant. It is empty (except for the objects created during DB creation by ODCA).

The export environment is Unix, and the environment where it is to be imported is Windows XP. Both boxes are physically located separately. I used the following parameters in parfile when I tried to import it:

USERID = System/
  
   @atlsmo
FILE = E:regisimportatlsmo.dmp
LOG = E:regisimportatlsmo_022706_x.log
BUFFER = 4096000
FULL = Y
IGNORE = Y

  
It gave me tons of errors such as:
IMP-00061: Warning: Object type "SYSTEM"."REPCAT$_OBJECT_NULL_VECTOR" already exists with a different identifier
IMP-00017: following statement failed with ORACLE error 23327:
ORA-00001: unique constraint (SYSTEM.HELP_TOPIC_SEQ) violated
IMP-00017: following statement failed with ORACLE error 2264:
I then dropped the newly created DB, re-created it and then performed import twice as suggested by an experienced DBA. The first time I used the following parameters:
FULL = Y
ROWS = Y
CONSTRAINTS = N
INDEXES = N
(I did not use the IGNORE parameter at all for the first import.)

Then I imported again a second time with the following parameters:

FULL = Y
ROWS = N
CONSTRAINTS = Y
INDEXES = Y
IGNORE = Y
This was in vain; I am still getting tons of errors and the import is successful with warnings.

Please tell me what to do and how to resolve the issue. Please remember that the original database which has to be first exported is also replicated.

When you perform a FULL export, you will also export objects owned by SYSTEM. Many of these object already exist in your new database. So when you perform a FULL import, you will receive an error. This is expected behavior. I ignore errors pertaining to SYSTEM objects on import of a full export dump. The import process will proceed with the other objects and everything will be fine. I would use the following parameters to perform your import into a nearly empty database:
USERID=system 
FILE=.... FULL=Y 
The rest of the parameters can use their default values.

Dig Deeper on Oracle database backup and recovery

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close