Solved

Not  able to  import using Data pump

Posted on 2006-06-13
3
3,120 Views
Last Modified: 2008-01-09
Hi
I exported  entire scott  database  using  expdp now but unable to  import one table from this  dmp   to my HR  schema..  my impdp command is as follows ..

C:\> impdp hr/hr  tables=scott.emp directory=dpump_dir dumpfile=dpump_dir:scott.dmp  logfile=dpump_dir:scott.log

I tried all alternates like changing username  and pwd from hr/hr  to scott tiger ,, i tried with  even schema option ,, but nothing   worked .. it  imports in own  schema  but not in other schema .. I just want to  import this  object from scott  schema to hr  schema..
Here output from my log file

;;;
Import: Release 10.1.0.2.0 - Production on Tuesday, 13 June, 2006 10:18

Copyright (c) 2003, Oracle.  All rights reserved.
;;;
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Master table "HR"."SYS_IMPORT_TABLE_01" successfully loaded/unloaded
Starting "HR"."SYS_IMPORT_TABLE_01":  hr/******** directory=dpump_dir dumpfile=dpump_dir:scott.dmp logfile=dpump_dir:scott.log tables=scott.emp
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-31684: Object type TABLE:"SCOTT"."EMP" already exists
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OBJECT_GRANT
ORA-39111: Dependent object type OBJECT_GRANT:"RHM_ROLE" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"PUBLIC" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"SCOTT"."EMP" already exists
ORA-39111: Dependent object type OBJECT_GRANT:"HR" skipped, base object type TABLE:"SCOTT"."EMP" already exists
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
ORA-39111: Dependent object type INDEX:"SCOTT"."PK_EMP" skipped, base object type TABLE:"SCOTT"."EMP" already exists
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ORA-39111: Dependent object type CONSTRAINT:"SCOTT"."PK_EMP" skipped, base object type TABLE:"SCOTT"."EMP" already exists
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39111: Dependent object type INDEX_STATISTICS skipped, base object type INDEX:"SCOTT"."PK_EMP" already exists
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39111: Dependent object type TABLE_STATISTICS skipped, base object type TABLE:"SCOTT"."EMP" already exists
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39111: Dependent object type REF_CONSTRAINT:"SCOTT"."FK_DEPT" skipped, base object type TABLE:"SCOTT"."EMP" already exists
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
ORA-39111: Dependent object type TRIGGER:"SCOTT"."DEL_EMP_TRIG" skipped, base object type TABLE:"SCOTT"."EMP" already exists
Job "HR"."SYS_IMPORT_TABLE_01" completed with 20 error(s) at 10:18
0
Comment
Question by:rehman123
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 12

Accepted Solution

by:
jwahl earned 500 total points
ID: 16892514
to import in another schema add  FROMUSER=<username> TOUSER=<username> to the parameters.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Using SQL Scripts we can save all the SQL queries as files that we use very frequently on our database later point of time. This is one of the feature present under SQL Workshop in Oracle Application Express.
Shell script to create broker configuration file using current broker Configuration, solely for purpose of backup on Linux. Script may need to be modified depending on OS-installation. Please deploy and verify the script in a test environment.
Via a live example show how to connect to RMAN, make basic configuration settings changes and then take a backup of a demo database
Via a live example, show how to restore a database from backup after a simulated disk failure using RMAN.
Suggested Courses

622 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question