Full impdp

Hi Guys,
I took a full expdp from a database and want to perform a full impdp into another database.
Do I have to create the users and tablespaces in advanced? Or the full import will take care of it?
Since i already have system,sys,sysaux, etc tablespaces in the new database, i supposed full import will throw the errors?
thanks

Hi,
If the full was specified on export, the dumpfile contains the users and the tablespaces. If you import this dumpfile the users are created so you don't have to pre-create them. For the tablespaces, impdp will attempt to create them in the same directory structure that they were in. Let's say your original tablespaces were created in:
/scratch/db1/datafiles
If this directory doesn't exist where you are importing, then you can either:
remap_datafile=/scratch/db1/datafiles/datafile1.f:/new_directory_spec/datafile1.f
etc
or you can precreate them. If you want to precreate them, then if you don't know what they are you should do this:
impdp user/password include=tablespace sqlfile=tbs.sql ...
Then look at the tbs.sql to see what the tablespace names are and then you can edit the file and change the new location to create the datafiles.
Once the tablespaces are created you can run your impdp command adding:
exclude=tablespace
since they are already created.
Hope this helps.
Dean

Similar Messages

Impdp network_link full=y

I am trying to learn full db imp through network link , thats what my understanding is , create user, grant necessary privileges, create db link on target server + create all tablespaces, and schema users (which source db has) and run this command, make me right if i am not....
impdp test/test@db10g full=y network_link=REMOTE_FULL directory=TEST_DIR logfile=impdpfull.log
if for some reason full impdp have issue try to go for schema impdb like
impdp test/test@db10g directory=TEST_DIR network_link=REMOTE_FULL remap_schema=scott:scott

Pl post OS details. Your approach looks good. What has your testing revealed ?
http://download.oracle.com/docs/cd/E11882_01/server.112/e16536/dp_import.htm#SUTIL919
Srini

Upgrading using expdp and impdp

I am upgrading from 10.2 to 11.1 by creating a new 11.1 db and then expdp from the 10.2 db and impdp to the 11.1 db. There is Oracle text installed and in use in the 10g db. Should I install the Oracle text in the 11.1 db first before I do a full impdp? Or install Oracle text and only do schema level impdp and ignore importing to ctxsys schema? I would like to know what's the correct way to do this w/o screwing up the text index on the application schema.
Thanks.

Hi,
CTXSYS is never part of an export (think about that, it is the same as with SYS). Only Indexes used by schemas are exported. The best way to work with Oracle Text and an upgrade is to script the indexes before the export by using ctx_report.create_index_script. Make the export and import, and run afterwards the scripts for the text indexes. In the export the preferences for Text indexes are lost (not exported), so you can get in trouble if you need to change such indexes with preferences.
Herald ten Dam
http://htendam.wordpress.com

Impdp errors

Hello all,
I want to do a full impdp but im getting many errors.
im using
impdp user/password@database directory=DATA_PUMP_DIR
FULL=Y
dumpfile=EXPORT.DMP
im trying to do this in my laptop for test purpose. I am using 11.2.0.1.0 version.
1. cn i do this with sys user? IF im doing from sys user its giving me errors like
ORA-31625: Schema Example is needed to import this object, but is unaccessible
ORA-39083: Object type PACKAGE_BODY failed to create with error:
ORA-39083: Object type SYNONYM failed to create with error:
ORA-01917: user or role '' does not exist
2. Whn im trying to do this with user with full imp privileges im gettin error.
ORA-31655: no data or metadata objects selected for job
ORA-39154: Objects from foreign schemas have been removed from import
Master table "ABC"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "ABC"."SYS_IMPORT_FULL_01": abc/******** directory=DATA_PUMP_DIR FULL=
Y DUMPFILE=ORCL.DMP
Job "ABC"."SYS_IMPORT_FULL_01" successfully completed at 11:42:49
please suggest how to over come this
In the laptop where im trying to do impdp I haven't created any directory structure,, no tablespaces, no users I jst installed oracle

im still not gettin nywher.......
as i mentioned this is a test machine so
no users, no tablespaces, no schemas are created in this test machine jst oracle has been installled.
Please suggest me what to be done next.
From the production DB i have taken the full=y expdp

EXPDP Error on 10.2.0.4

Hello,
Oracle DB 10.2.0.4
Windows 2003R2
I am getting below error:
C:\WINDOWS>expdp system/******* full=y estimate_only=y
Export: Release 10.2.0.4.0 - 64bit Production on Thursday, 21 February, 2013 0:2
4:27
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 488
ORA-29283: invalid file operationEven with the SYS user, I am getting same error.
I have even re-installed data-pump on this database, but with no luck!
Kindly advice.
Thanks,
Suddhasatwa

Hi,
LOGFILE
Default: import.log
Purpose
Specifies the name, and optionally, a directory object, for the log file of the import job.
Syntax and Description
LOGFILE=[directory_object:]file_name
If you specify a directory_object, it must be one that was previously established by the DBA and that you have access to. This overrides the directory object specified with the DIRECTORY parameter. The default behavior is to create import.log in the directory referenced by the directory object specified in the DIRECTORY parameter.
If the file_name you specify already exists, it will be overwritten.
All messages regarding work in progress, work completed, and errors encountered are written to the log file. (For a real-time status of the job, use the STATUS command in interactive mode.)
+_A log file is always created unless the NOLOGFILE parameter is specified. As with the dump file set, the log file is relative to the server and not the client._+Note:
Data Pump Import writes the log file using the database character set. If your client NLS_LANG environment sets up a different client character set from the database character set, then it is possible that table names may be different in the log file than they are when displayed on the client output screen.
Example
The following is an example of using the LOGFILE parameter. You can create the expfull.dmp dump file used in this example by running the example provided for the Export FULL parameter. See FULL.
impdp hr/hr SCHEMAS=HR DIRECTORY=dpump_dir2 LOGFILE=imp.log DUMPFILE=dpump_dir1:expfull.dmp
Because no directory object is specified on the LOGFILE parameter, the log file is written to the directory object specified on the DIRECTORY parameter.Edited by: Chanchal Wankhade on Feb 20, 2013 10:22 PM

Import from another system

Hi,
our Peoplesoft system is :oracle 10g R2, tools 8.49. We are creating another one , also with oracle 10g R2. We have done a full export of Oracle database :
expdp system/password@MYDB DIRECTORY=dpump_dir1 DUMPFILE=exp_ful_MYDB_PROD_230109 FULL=Y Logfile=expMYDB_230109.logNow to import to new database, should I import FULL :
impdp system/password@newdb DUMPFILE=EXP_FUL_MYDB.DMP LOGFILE=ALAIN.log FULL=Yor to a schema :
impdp sysadm/***@NEWDB DUMPFILE=EXP_FUL_MYDB.DMP SCHEMAS=sysadm LOGFILE=import.logMany thanks

Since a Peoplesoft database is not only one schema, but at least three (PS, PEOPLE and the objects owner - SYSADM), a full import should do the trick.
It could be some different path depending how you built the target database where you are doing the import into.
Nicolas.

CROSS PLATFORM MIGRATION

Guys,
I'm in place of migrating 10g production database (currently running on windows server) to 11g ( on RHEL 5). The following is the plan.
1.install oracle software on new server
2.create empty 11g database
3.expdp from 10g (full).
4.impdp into 11g database.
I've a doubt need exact steps in importing a full database.
1.create tablespace & users.
2.IMPDP username/password directory=datapump dumpfile=upgrade.dmp full=y ignore=y.
correct me if i'm wrong.
how to create an empty database?.
if i done full impdp, how the enterprise manager will be???
Regards,
Sakthi.

Hello,
how to create an empty database?.You can use DBCA or CREATE DATABASE Statement. The link below details the steps to use DBCA:
http://download.oracle.com/docs/cd/E11882_01/server.112/e10897/install.htm#ADMQS0231
if i done full impdp, how the enterprise manager will be??? Enterprise Manager is likely to be down.
When you change the HOST or SID, it's better to reconfigure Enterprise Manager. To do that you may execute the following statements:
export ORACLE_SID=<SID>
emca -deconfig dbcontrol db -repos drop
emca -config dbcontrol db -repos createYou'll need the ORACLE_SID, the Listener Port, the ORACLE_HOME, the password of SYS, DBSNMP and SYSMAN.
Hope this help.
Best regards,
Jean-Valentin

How-to list the contents of a Data Pump Export file?

How can I list the contents of a 10gR2 Data Pump Export file? I'm looking at the Syntax Diagram for Data Pump Import and can't see a list-only option.
Regards,
Al Malin

use the parameter SQLFILE in the impdp which writes all the sql ddl's to the specified file.
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14215/dp_import.htm
SQLFILE
Default: none
Purpose
Specifies a file into which all of the SQL DDL that Import would have executed, based on other parameters, is written.
Syntax and Description
SQLFILE=[directory_object:]file_name
The file_name specifies where the import job will write the DDL that would be executed during the job. The SQL is not actually executed, and the target system remains unchanged. The file is written to the directory object specified in the DIRECTORY parameter, unless another directory_object is explicitly specified here. Any existing file that has a name matching the one specified with this parameter is overwritten.
Note that passwords are not included in the SQL file. For example, if a CONNECT statement is part of the DDL that was executed, it will be replaced by a comment with only the schema name shown. In the following example, the dashes indicate that a comment follows, and the hr schema name is shown, but not the password.
-- CONNECT hr
Therefore, before you can execute the SQL file, you must edit it by removing the dashes indicating a comment and adding the password for the hr schema (in this case, the password is also hr), as follows:
CONNECT hr/hr
For Streams and other Oracle database options, anonymous PL/SQL blocks may appear within the SQLFILE output. They should not be executed directly.
Example
The following is an example of using the SQLFILE parameter. You can create the expfull.dmp dump file used in this example by running the example provided for the Export FULL parameter. See FULL.
impdp hr/hr DIRECTORY=dpump_dir1 DUMPFILE=expfull.dmpSQLFILE=dpump_dir2:expfull.sql
A SQL file named expfull.sql is written to dpump_dir2.
Message was edited by:
Ranga
Message was edited by:
Ranga

Impdp fails with ORA-01427 during full import of 10.2 db into 11.2

Hello all,
I'm running a full import from a dump file taken from our production db (10.2.0.4.0) on RHEL4 into a test db (11.2.0.3.0) on RHEL6. I've done something very similar before with no errors but this time it returns the following in the output at the end of the partially successful import:
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TABLE_STATISTICS]
ORA-06502: PL/SQL: numeric or value error
LPX-00225: end-element tag "COL_STATS_ITEM" does not match start-element tag "HIVAL"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9001
----- PL/SQL Call Stack -----
object      line object
handle    number name
0x1ea3a92c8     20462 package body SYS.KUPW$WORKER
0x1ea3a92c8      9028 package body SYS.KUPW$WORKER
0x1ea3a92c8     16665 package body SYS.KUPW$WORKER
0x1ea3a92c8      3956 package body SYS.KUPW$WORKER
0x1ea3a92c8      9725 package body SYS.KUPW$WORKER
0x1ea3a92c8      1775 package body SYS.KUPW$WORKER
0x1e9ec90f8         2 anonymous block
ORA-39097: Data Pump job encountered unexpected error -1427
ORA-39065: unexpected master process exception in DISPATCH
ORA-01427: single-row subquery returns more than one row
Job "SYSTEM"."SYS_IMPORT_FULL_02" stopped due to fatal error at 13:32:00
The import is into a database that has had all the application users dropped (only Oracle-defined users still existing) but with table_exists_action set to skip (the default). Several user objects from the source db are missing from the target.
I've run this twice with the same results. I can imagine that there is a problem with the master table and/or the data dictionary but it gives no indication of the deeper cause.
Any ideas, anyone?
Regards, Keith.

Pl post the complete expdp and impdp commands used.
Retry expdp or impdp with the EXCLUDE=STATISTICS option.
MOS Doc 878626.1
HTH
Srini

Expdp full and impdp full fails with error....pls help..!(Oracle 11g)

Hi
I wanted to refresh my dev environment quickly..
As we also wanted to migrate from exp/imp to datapump, I tried these..
Only thing worked for me is impdp on network mode using remap schema.
1)First i wanted to implement expdp and impdp standard procedures(Full database export/import)
My expdp failed with the following error on a full export..
Pls see below:
C:\Documents and Settings\oracle2>expdp system/<p.w> full=Y directory=DATA_PUMP_DIR dumpfile=OAPFULL.dmp logfile=OAPFULL.log
Export: Release 11.1.0.7.0 - Production on Thursday, 26 April, 2012 16:12:49
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_FULL_02": system/******** full=Y directory=DATA_PUMP_DIR dumpfile=OAPFULL.dmp logfile=OAPFULL.log
Estimate in progress using BLOCKS method...
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 4.351 GB
Processing object type DATABASE_EXPORT/TABLESPACE
Processing object type DATABASE_EXPORT/PASSWORD_VERIFY_FUNCTION
Processing object type DATABASE_EXPORT/PROFILE
Processing object type DATABASE_EXPORT/SYS_USER/USER
Processing object type DATABASE_EXPORT/SCHEMA/USER
Processing object type DATABASE_EXPORT/ROLE
Processing object type DATABASE_EXPORT/GRANT/SYSTEM_GRANT/PROC_SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/GRANT/SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/ROLE_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/DEFAULT_ROLE
Processing object type DATABASE_EXPORT/SCHEMA/TABLESPACE_QUOTA
Processing object type DATABASE_EXPORT/RESOURCE_COST
Processing object type DATABASE_EXPORT/SCHEMA/DB_LINK
Processing object type DATABASE_EXPORT/TRUSTED_DB_LINK
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/SEQUENCE
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/DIRECTORY/DIRECTORY
Processing object type DATABASE_EXPORT/DIRECTORY/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/CONTEXT
Processing object type DATABASE_EXPORT/SCHEMA/PUBLIC_SYNONYM/SYNONYM
Processing object type DATABASE_EXPORT/SCHEMA/SYNONYM
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31672: Worker process DW01 died unexpectedly.
Job "SYSTEM"."SYS_EXPORT_FULL_02" stopped due to fatal error at 16:14:562)As the above failed, I tried impdp with network_link import and full=y and its a different issue!
impdp system/<p.w> NETWORK_LINK=OAPLIVE.WORLD full=y logfile=OAPDRfull2.log table_exists_
action=REPLACE
Import: Release 11.1.0.7.0 - Production on Thursday, 26 April, 2012 13:36:01
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/******** NETWORK_LINK=OAPLIVE.WORLD full=y logfile=OAPDRfull2.log table_exists_action=REPLACE
Estimate in progress using BLOCKS method...
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 4.670 GB
Processing object type DATABASE_EXPORT/TABLESPACE
ORA-31684: Object type TABLESPACE:"SYSAUX" already exists
*************lots more of object already exists errors here............(space limit so cant paste)***************
ORA-31684: Object type SYNONYM:"GEOPROD"."EXT_POSTAIM_PRESORT_61" already exists
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.DISPATCH_WORK_ITEMS [SYNONYM:"GEOPROD"."EXT_POSTAIM_PRESORT_61"]
ORA-31600: invalid input value 200001 for parameter HANDLE in function CLOSE
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.DBMS_METADATA", line 569
ORA-06512: at "SYS.DBMS_METADATA", line 4731
ORA-06512: at "SYS.DBMS_METADATA", line 792
ORA-06512: at "SYS.DBMS_METADATA", line 4732
ORA-06512: at "SYS.KUPW$WORKER", line 2718
ORA-03113: end-of-file on communication channel
ORA-02055: distributed update operation failed; rollback required
ORA-02063: preceding lines from OAPLIVE.WORLD
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 7858
----- PL/SQL Call Stack -----
object      line object
handle    number name
242F2F2C     18256 package body SYS.KUPW$WORKER
242F2F2C      7885 package body SYS.KUPW$WORKER
242F2F2C      8657 package body SYS.KUPW$WORKER
242F2F2C      1545 package body SYS.KUPW$WORKER
241DDF3C         2 anonymous block
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA []
ORA-31642: the following SQL statement fails:
SELECT unique ku$.seq# from sys.metanametrans$ ku$ WHERE ku$.htype='DATABASE_EXPORT' AND ku$.model='ORACLE' AND NOT ( ku$.seq#>=(select a.seq# from sys.metanametrans$ a where
   a.model='ORACLE' and a.htype='DATABASE_EXPORT' and a.name ='DATABASE_EXPORT/SCHEMA/SYNONYM')) order by ku$.seq#
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA_INT", line 5002
ORA-01427: single-row subquery returns more than one row
ORA-06512: at "SYS.DBMS_
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 7853
----- PL/SQL Call Stack -----
object      line object
handle    number name
242F2F2C     18256 package body SYS.KUPW$WORKER
242F2F2C      7885 package body SYS.KUPW$WORKER
242F2F2C      2744 package body SYS.KUPW$WORKER
242F2F2C      8523 package body SYS.KUPW$WORKER
242F2F2C      1545 package body SYS.KUPW$WORKER
241DDF3C         2 anonymous block
Job "SYSTEM"."SYS_IMPORT_FULL_01" stopped due to fatal error at 13:39:48So its basically these 2 issues I want to know how to fix.
1-expdp error cause and fix
2-impdp error cause and fix -Also how to avoid object alreay exists error?
Also for example the package etc. is the same name..but i want new package from LIVE so it means if the same name package, view, etc is there, it wouldnt get updated?
Any way to overcome this?
I need it exactly same as LIVE...(with a few exceptions which is small enough i can do after impdp finishes fine)
Pleaseeeeeeee help!!
Thanks&Regards.......

Hi..
Thanks for the links..I applied the tips on each of them but it didnt work.
Also my database is 11g so it is not true that this happens on 10g only.
Things tried:
1)I tried with different values on parallel parameter but same error
2)I applied the following:
alter system set open_cursors=1024 scope=spfile;
alter system set "_optimizer_cost_based_transformation"=off;
commit;
The 3rd link was bit better
I tried to find out where exactly the error was causesusing
expdp attach =SYS_EXPORT_FULL_03
But I cant figure out what the object : PUBLIC
oracle/context/isearch/GetPage
is..?
Does this needs to be excluded from the export?if so, how?
Can someone help how to fix the error now?
Processing object type DATABASE_EXPORT/SCHEMA/SYNONYM
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31672: Worker process DW01 died unexpectedly.
Job "SYSTEM"."SYS_EXPORT_FULL_03" stopped due to fatal error at 11:29:32
C:\Documents and Settings\ora2>expdp attach=SYS_EXPORT_FULL_03
Export: Release 11.1.0.7.0 - Production on Tuesday, 01 May, 2012 11:35:38
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Username: system
Password:
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Job: SYS_EXPORT_FULL_03
Owner: SYSTEM
Operation: EXPORT
Creator Privs: TRUE
GUID: 8499C802F52A414A8BCACE552DDF6F11
Start Time: Tuesday, 01 May, 2012 11:37:56
Mode: FULL
Instance: geooap
Max Parallelism: 1
EXPORT Job Parameters:
Parameter Name      Parameter Value:
     CLIENT_COMMAND        system/******** parfile=h:\datapump\oapfull.par
State: IDLING
Bytes Processed: 0
Current Parallelism: 1
Job Error Count: 0
Dump File: H:\datapump\oapfull.dmp
    bytes written: 4,096
Worker 1 Status:
Process Name: DW01
State: UNDEFINED
Object Schema: PUBLIC
Object Name: oracle/context/isearch/GetPage
Object Type: DATABASE_EXPORT/SCHEMA/PUBLIC_SYNONYM/SYNONYM
Completed Objects: 766
Total Objects: 766
Worker Parallelism: 1

Full expdp and impdp: one db to another

Hi! Good Day!
I Would like to ask for any help regarding my problem.
I would like to create a full export of one database to and import it on another database. This 2 database are on a separate machines.
I am trying to use the expdp and impdp tool to do this task. However, i have been experiencing some problems during the import task.
here is the detail of my problems:
When i try to impdp the dump file, it seems that i was not able to iimport the user's data and metadata.
Here is the exact command that i've used during the import and export task:
export (server #1)
expdp user01/******** directory=ora3_dir full=y dumpfile=db_full%U.dmp filesize=2G parallel=4 logfile=db_full.log
import (server #2)
impdp user01/******** directory=ora3_dir dumpfile=db_full%U.dmp full=y log=db_full.log sqlfile=db_full.sql estimate=blocks parallel=4
here is the log that was generated during the impdp running:
Import: Release 10.2.0.1.0 - 64bit Production on Friday, 27 November, 2009 17:41:07
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Master table "SSMP"."SYS_SQL_FILE_FULL_01" successfully loaded/unloaded
Starting "SSMP"."SYS_SQL_FILE_FULL_01": ssmp/******** directory=ora3_dir dumpfile=ssmpdb_full%U.dmp full=y logfile=ssmpdb_full.log sqlfile=ssmpdb_full.sql
Processing object type DATABASE_EXPORT/TABLESPACE
Processing object type DATABASE_EXPORT/PROFILE
Processing object type DATABASE_EXPORT/SYS_USER/USER
Processing object type DATABASE_EXPORT/SCHEMA/USER
Processing object type DATABASE_EXPORT/ROLE
Processing object type DATABASE_EXPORT/GRANT/SYSTEM_GRANT/PROC_SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/GRANT/SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/ROLE_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/DEFAULT_ROLE
Processing object type DATABASE_EXPORT/SCHEMA/TABLESPACE_QUOTA
Processing object type DATABASE_EXPORT/RESOURCE_COST
Processing object type DATABASE_EXPORT/SCHEMA/DB_LINK
Processing object type DATABASE_EXPORT/TRUSTED_DB_LINK
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/SEQUENCE
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/DIRECTORY/DIRECTORY
Processing object type DATABASE_EXPORT/DIRECTORY/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/DIRECTORY/GRANT/CROSS_SCHEMA/OBJECT_GRANT
Processing object type DATABASE_EXPORT/CONTEXT
Processing object type DATABASE_EXPORT/SCHEMA/PUBLIC_SYNONYM/SYNONYM
Processing object type DATABASE_EXPORT/SCHEMA/SYNONYM
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/TYPE_SPEC
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/POST_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/PRE_TABLE_ACTION
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/GRANT/CROSS_SCHEMA/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/INDEX
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/CONSTRAINT/CONSTRAINT
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/COMMENT
Processing object type DATABASE_EXPORT/SCHEMA/PACKAGE/PACKAGE_SPEC
Processing object type DATABASE_EXPORT/SCHEMA/PACKAGE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/FUNCTION/FUNCTION
Processing object type DATABASE_EXPORT/SCHEMA/FUNCTION/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/PROCEDURE/PROCEDURE
Processing object type DATABASE_EXPORT/SCHEMA/PROCEDURE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/FUNCTION/ALTER_FUNCTION
Processing object type DATABASE_EXPORT/SCHEMA/PROCEDURE/ALTER_PROCEDURE
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/VIEW
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/GRANT/CROSS_SCHEMA/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/COMMENT
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type DATABASE_EXPORT/SCHEMA/PACKAGE_BODIES/PACKAGE/PACKAGE_BODY
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/TYPE_BODY
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/POST_TABLE_ACTION
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TRIGGER
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/TRIGGER
Processing object type DATABASE_EXPORT/SCHEMA/JOB
Processing object type DATABASE_EXPORT/SCHEMA/DIMENSION
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCACT_INSTANCE
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCDEPOBJ
Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCOBJ
Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
Job "SSMP"."SYS_SQL_FILE_FULL_01" successfully completed at 17:43:09
Thank you in advance.

I believe there are lines like that in the export log.
here's an extract from the log file:
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/TRIGGER
Processing object type DATABASE_EXPORT/SCHEMA/JOB
Processing object type DATABASE_EXPORT/SCHEMA/DIMENSION
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCACT_INSTANCE
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCDEPOBJ
Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCOBJ
Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
. . exported "SSMP"."SMALLBOX" 450.2 MB 2489790 rows
. . exported "SSMP"."LTCONFSB" 397.9 MB 3122899 rows
. . exported "SSMP"."INFRJCT" 317.3 MB 3615810 rows
. . exported "SSMP"."ICTEST1" 202.5 MB 789618 rows
. . exported "SSMP"."EQUIPERF" 315.3 MB 3008636 rows
. . exported "SSMP"."INFOPE2" 190.7 MB 569039 rows
. . exported "SSMP"."SMALLBSB" 189.8 MB 2659468 rows
. . exported "PRS1"."STKDTLOLD" 193.4 MB 983322 rows
. . exported "SSMP"."ICTEST11" 185.2 MB 553916 rows
. . exported "PRS1"."PURCHASE" 166.5 MB 122787 rows
. . exported "SSMP"."JIGREC" 183.5 MB 2664488 rows
. . exported "SSMP"."SALES" 112.4 MB 294134 rows
. . exported "SSMP"."P_INFOPE" 160.4 MB 485773 rows
. . exported "SSMP"."CIOP" 128.1 MB 385160 rows
. . exported "SSMP"."SMALLBOX2" 126.0 MB 589964 rows
. . exported "SSMP"."SHIPOUT" 123.4 MB 281778 rows
. . exported "SSMP"."INFHISTORY" 129.9 MB 786844 rows
. . exported "SYSMAN"."MGMT_TARGETS" 14.90 KB 11 rows
. . exported "SSMP"."LOGCNT" 4.937 KB 1 rows
. . exported "SSMP"."WEEKINF" 45.07 KB 700 rows
. . exported "SSMP"."DEPTNM" 12.33 KB 81 rows
. . exported "SSMP"."WFRID" 5.953 KB 2 rows
. . exported "SSMP"."MATDTLS" 85.53 KB 199 rows
. . exported "SSMP"."ICRATTACH" 9.257 KB 11 rows
. . exported "SSMP"."WIP2" 20.34 KB 67 rows
. . exported "SSMP"."MATINFO" 17.83 KB 43 rows
. . exported "SSMP"."ICRFAPP" 11.48 KB 11 rows
. . exported "SSMP"."WMXINF" 43.60 KB 500 rows
. . exported "SSMP"."MLDMACHINE" 32.30 KB 228 rows
. . exported "SSMP"."ICRNAME" 10.48 KB 23 rows
. . exported "SSMP"."XLODCNT" 4.937 KB 1 rows
. . exported "SSMP"."IJPLODCNT" 5.234 KB 1 rows
. . exported "SSMP"."MONTHINF" 14.67 KB 152 rows
. . exported "SSMP"."YYSTMP" 15.57 KB 59 rows
. . exported "SSMP"."MPRICE" 39.95 KB 365 rows
. . exported "SYSMAN"."ESM_COLLECTION" 8.585 KB 91 rows
. . exported "SSMP"."INFCHKSHT" 6.406 KB 4 rows
. . exported "SSMP"."MRKLNO" 4.929 KB 1 rows
. . exported "SSMP"."JPNMARK" 5.890 KB 2 rows
. . exported "SSMP"."LODCNT" 4.921 KB 1 rows
. . exported "SSMP"."MRPNAME" 29.73 KB 310 rows
. . exported "SYSMAN"."EXPORT000381" 49.68 KB 244 row

Impdp FULL=Y

Hi,
Oracle 10.2.0.3
> Expdp system/abc@xyz dumpfile=dmp_dir:dmp1.dmp full=y
Without changing any thing i executed:-
> impdp ssystem/alok@xyz dumpfile=dmp_dir:dmp1.dmp full=y
This import command is not giving any error for existing objects.It should give error for those objects/tablespaces/schemas which are already available in database.
Kindly share the reason behind this.
Thanks

There is not enough information in this post to know what is going on. Can you post the export.log file and the import.log file.
Thanks
Dean

Impdp specific schema from dump which has been created using full=y

Hi,
I have received a dump (expdp) which has been created using the parameter FULL=Y. I just want to import (impdp) only one schema into my database. I have used remap_schema and exclude=grants. The schema i want to import is carried out successfully, but in my import log i keep getting the messages such as :
ORA-31684: Object type TABLESPACE:"TS_BCST1" already exists
ORA-31684: Object type USER:"OUTLN" already exists
ORA-31684: Object type SEQUENCE:"SYSTEM"."MVIEW$_ADVSEQ_GENERIC" already exists
How can i use impdp only to import objects under my specific schema and not have impdp attempt to create system/sys users and its objects, create tablespaces, etc etc.
Kindly assist.
Regards,
Karan

Use SCHEMAS parameter in the impdp command to import the scpecific schema.
Eg.
impdp system/password schemas=user1 remap_schema=user1:user2 directory=dir dumpfile=user1.dmp...........
You can specify list of schemas you want to import with , (comma) saperated in the SCHEMAS parameter.

Question on expdp and impdp for full batabase

I have 10.2.0.4.0 db1 on solaris10.
I have to convert the database character set from WE8ISO8859P1 to AL32UTF8 by the export and import method per note [ID 260192.1]
I will not move the database for the converstion.
Waht I have done:
ran csscan for the db1 ( from WE8ISO8859P1 to AL32UTF8 ). The results are perfect -- no "lossy" "truncation".
ran expdp with full=y sucessfully
removed the db1 by DBCA.
created the db1 with AL32UTF8 by DBCA unselect all the option of schemas. And the tablespaces/datafiles are in exact the same locations as the db1 before it was removed.
I will run impdp with full=y
Questions:
There are some users exist in the origina dbl say source, but not exist in new created target, so are some of the tablespaces.
Do I have to manually create these users and tablespaces in the target database?
I thought impdp full=y would make a full load of the database which should create the new users and the new tablespaces on the target, correct?
Thanks for the help.
TIA

Actually the answer for what you need to do depends in part on if you are importiing back into the origional souce after it was clearned out or importing into a new database.
When the target is not the source then on a full import if the file paths exist and the import can allocate the data sets then the import should create the tablespaces however if the same pathing cannot be used or if the souce database in on the same server and you obviously do not want to overwrite the existing database data files then you would need to pre-create the target tablespaces in order to use different files.
The users should create. I do not have the time to run a test if the user default tablespace does not exist but I would expect the database to create the user defaulting the user default tablespace to whatever tablespace you have set for the database as a whole.
I would pre-create owners and grant the usernames the necessary system privileges in advance including quotas since it is possilbe that existing owners may not have all necessary privileges to re-creaate what alreadys exists.
HTH -- Mark D Powell --

Database full compile while doing schema import using impdp

hi,
oracle 10g
Database full compile while doing schema import using impdp..
what is happening here..
regards,
Deepak

My scenario
I need to import the particular schema from the full export dump. which has taken by using expdp. while importing i am using remap_schema for a single schema.
But it try to import the full dump and compile all the schema objects.
regards,
Deepak

Full impdp

Similar Messages

Maybe you are looking for