IMPDP and EXPDP

Is there an option to be specified in EXPDP(Data Pump Export) and IMPDP(Data Pump import) to export/import the packages, procedures from one user/schema to the other with in the same database?

You can use include parameter and the remap schema parameter.
Expdp user/password include=procedure,packages ...
If you have a loopback dblink, then you can do it all pin one command without creating a dump file. There is no expdp required. Do this
Impdp user/password network_link=your_loopback_dblink include=package,procedure remap_schema=old:new schemas=old ...
Hope this helps
Dean

Similar Messages

Confusing impdp and expdp stuff

Hello, I am kinda new to Oracle in general.
Building a test environment.
Want to move a production schema to a test RAC db i have built.
I read up and decided that expdp would be the best method ( correct me if i am wrong please )
I am on oracle linux.
Now I have expdp'ed a schme succesfully but when impdping on the other system i am getting a total of 735 errors.
I have created the same exact user and am using the following command
Please let me know whether I am missing a step here.
$>impdp system/<password> directory=impdp_dir dumpfile=UNIXDATA.DMP logfile=impdpUNIXdata.log fromuser='unixdata' touser='unixdata' commit=Y ignore=Y
would the log file help?
one of them
Processing object type SCHEMA_EXPORT/JOB
ORA-39083: Object type JOB failed to create with error:
ORA-00001: unique constraint (SYS.I_JOB_JOB) violated
also this
ORA-39083: Object type MATERIALIZED_VIEW failed to create with error:
ORA-31625: Schema UNIXDATA is needed to import this object, but is unaccessible
ORA-01435: user does not exist
THANKS ALOT FOR YOUR HELP!
Ali
Edited by: user10270464 on Apr 16, 2010 5:40 AM

Hi,
You don't say what version of Oracle you are using so trying to help without that info is more difficult. It also looks like you are using some old exp parameters and some new expdp parameters. Your mixed command is:
impdp system/<password> directory=impdp_dir dumpfile=UNIXDATA.DMP logfile=impdpUNIXdata.log fromuser='unixdata' touser='unixdata' commit=Y ignore=Y
You said that you did a schema mode export, so I would change the impdp command to be:
impdp system/<password> directory=impdp_dir dumpfile=UNIXDATA.DMP logfile=impdpUNIXdata.log table_exists_action=append
The parameters I changed were:
fromuser='unixdata' -- if the only thing in the dumpfile is what you want, then you don't need fromuser
touser='unixdata' -- since you are importing into the same schema, you don't need touser
commit=y -- no such equivalent in datapump
ignore=y -- the same as table_exists_action=append
Now for your errors.
The first one is not familiar with me, but I have seen the second error, but can't remember the details. Having the version that you are running may help job my memory.
Dean

Impdp and expdp failed due to following error

hi,
to every one
when ever i issue impdp or empdp command it gives the error
i have used intesivly data pump but i am not get the idea that why this going to do on this DBserver only.
even i have just give impdp username and passward but the error is same if any one have information then me is waiting for u'r reply.
error is :
Import: Release 10.2.0.1.0 - Production on Friday, 24 February, 2006 18:53:06
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Password:
Connected to: Oracle Database 10g Release 10.2.0.1.0 - Production
ORA-39006: internal error
ORA-39065: unexpected master process exception in DISPATCH
ORA-01775: looping chain of synonyms
ORA-39097: Data Pump job encountered unexpected error -1775

Hi,
Error: ORA-01775: looping chain of synonyms
Cause: You created a series of synonyms that resulted in a circular reference.
Action: The options to resolve this Oracle error are:
Correct the synonyms so that the circular reference is removed.
A circular reference can occur as follows:
CREATE SYNONYM syn1 for syn2;
CREATE SYNONYM syn2 for syn3;
CREATE SYNONYM syn3 for syn1;
see user_synonyms ...

Datapump expdp impdp and sequences

Hi all. I have a 10g XE database on my dev machine witha whole load of test data in it. I want to copy the schema to another machine without the data which I can do with expdp usr/pwd CONTENT=metadata_only and I can import it with impdp and everyhing works tickety boo. Except that all the sequences are populated where the test data left off. Can someone please tell me how to copy the schema with the sequences reset please ? I'm guessing either I can export the schema resetting the sequences (somehow) or export EXCLUDING the sequeces and create them seperately (somehow). Thanks for reading.

I don't think you can reset the sequences directly. You can run the import to an sql file and then use search/replace on it:
$ impdp user/pass dumpfile=test.dmp directory=MY_DIR include=SEQUENCE sqlfile=sequences.sql
You will have several lines like this inside "sequences.sql":
CREATE SEQUENCE "USER"."SEQ_NAME" MINVALUE 1 MAXVALUE 99999999 INCREMENT BY 1 START WITH 1857 CACHE 20 ORDER CYCLE ;
Then just use regular expressions to replace "START WITH NNNN" by "START WITH 1"

I need help with IMPDP and the parameter 'EXCLUDE'...

Hi all... Im new at this forum and Im looking for some help =)
I'm working with DataPump (EXPDP and IMPDP), and I'm importing some tables from HR... I'm able to import those tables without any problem, but I have to exclude the TRIGGER and PROCEDURES. I'm using the parameter EXCLUDE=TRIGGER,PROCEDURE and it shows me an error message , because its unable to find the object call "PROCEDURE"... if I remove the EXCLUDE=PROCEDURE then it shows no error message... can someone help me?
this is the script Im using....
IMPDP system/mypassword directory=DATA_PUMP REMAP_SCHEMA=HR:EXAMEN include=table:\"in('DEPARTAMENTS','EMPLOYEES','JOB_HISTORY','JOBS')\" EXCLUDE=TRIGGER,PROCEDURE DUMPFILE=IMP_HR.DMP LOGFILE=IMP_HR_.LOG

Hi,
Use:
EXCLUDE=TRIGGER
EXCLUDE=PROCEDURE
Always read the docs first:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/dp_import.htm#i1010670

Trigger-Body isnt remaped during IMPDP and REMAP_SCHEMA in Oracle 10g

Hello,
we are facing the following problem:
During an IMPDP we are remaping the schema. The schema includes triggers. The trigger bodys are of normal syntax without a relation to the schema/user.
If we start the import with datapump using the remap_schema option the triggers are remap to the new schema. But the trigger bodys point to the old schema.
For example:
CREATE OR REPLACE TRIGGER "OLD_SCHEMA".NAME_OF_TRIGGER
BEFORE INSERT ON "OLD_SCHEMA"."TABLE_NAME" REFERENCING OLD AS OLD NEW AS NEW FOR EACH ROW BEGIN
END;
After using the REMAP_SCHEMA option:
CREATE OR REPLACE TRIGGER "NEW_SCHEMA".NAME_OF_TRIGGER
BEFORE INSERT ON "OLD_SCHEMA"."TABLE_NAME" REFERENCING OLD AS OLD NEW AS NEW FOR EACH ROW BEGIN
END;
So the Trigger Body in the NEW_SCHEMA uses a link to the OLD_SCHEMA and the trigger doesn't work. We wrote the trigger without referencing to a schema. So the OLD_SCHEMA resp. NEW_SCHEMA syntax must be added by datapump.
The question: Is there a way to remap the triggers correctly in the new schema or is this behavior "normal" to Oracle 10g Datapump?
We are using Oracle 10g Database 10.2.0.4 with the latest Patches on Windows Server 2003 SP2.
Thank you for you attention.

Hello,
I had the same problem and you can't fix it by changing a parameter of impdp. You really need to change the source of those triggers so they don't use hard-code schema references.
Solution would be to change the source code of those triggers. Or to use the "script" parameter of impdp and recreate the triggers yourself after the impdp has finished.
For more info check Metalink note: 750783.1
I hope this helps.
Regards,
Michiel.

Conversions between character sets when using 'exp' and 'expdp' utilities

When I make export with exp utility with NLS_LANG environment
variable not set, export is done with US7ASCII character set,
but when server uses some other character set e.g. EE8ISO8859P2,
there can be some national specific characters lost with such a conversion.
But when I use expdp utility and have not NLS_LANG set,
in log file there is not mentioned that export is done in other character set
than that on the server, does it mean that it uses character set on server?

When I make export with exp utility with NLS_LANG environment
variable not set, export is done with US7ASCII character set,
but when server uses some other character set e.g. EE8ISO8859P2,
there can be some national specific characters lost with such a conversion.
But when I use expdp utility and have not NLS_LANG set,
in log file there is not mentioned that export is done in other character set
than that on the server, does it mean that it uses character set on server?

Impdp and commit=y

Hello,
I'm doing a large scale import using datapump on a table with many partitions.
In the import utility there was commit=y that prevented too much undo in huge loads. is there something similar to use in the datapump?
Thanks

no, "commit" hasn't translate in impdp
a trick will be change "undo_retention" to a lower value before import and set to original value when the import finish.

Impdp and scheduler maintenance window

Environment: Oracle 11.1.0.7.0 running on HP-UX B.11.31 U ia64.
I was performing import using impdp. Before starting the import, I manaully disabled the maintenance window.
But once, import over, when I try to enable the maintenance window, when I checked, it got already enabled.
On investigating found that the timing of enable match with the import finish time.
Before performing the import using impdp, I have disabled maintenance window using;
DBMS_SCHEDULER.DISABLE(name=> mwindow,force=>TRUE);
After Import, when i checked the maintenance window using;
SELECT
w.window_name,
w.repeat_interval,
w.duration,
w.enabled
FROM dba_scheduler_windows w
the value as ENABLED = TRUE.
On querying the select * from DBA_SCHEDULER_WINDOW_LOG, the timing of LOG_DATE matches with the import impdp finish time. However on the column ADDITIONAL_INFO
has value of REASON="manually enabled"

Are you doing a system import here ?
If you are doing a system import then properties of the maintenance window will also be imported and that may include enabling the window.
Since a system export exports system-level properties as well, you might need to disable the maintenance window before doing your system export.
Hope this helps,
Ravi.

IMPDP and GATHER_SCHEMA_STATS

1.Do I have to GATHER_SCHEMA_STATS after every IMPDP of data?
2.How frequently should we gather schema level statistics?

1. If, you do statisticas=no then you should collect statisticas for imported objects/schema. IF you are specifiying statisticas=YES and if your server configuration is different by memmory of file layout is different or by cpu number, still you want to collect statisticas. I think, collecting statisticas after each IMP job would be more appropriate coz that way you have fresh statisticas on which you can rely on.
2. About how frequent you should collect statisticas depend on how much data you are updateing/inserting/deleting.
In 9i, you can run GATHER_SCHEMA_STATS everyday with STALE option. In this case, Oracle will automatically find objects which need new statisticas and collect it.
In 10g, statisticas are collected automatically and that should be work fine for almost every kind of database. Still you can change configuration. Statisticas job is run through new scheduler.
Read this
Thanks
~Keyur

[10g] database job and expdp!!

Hi, all.
I want to run the followings by using database job on a daily basis.
The database is 10.2.0.2.0
"expdp system/oracle schemas=nmsuser dumpfile=test.dmp logfile=expdp_test.log"
Is there anyone who could give me a hint or sample code?
Thanks and Regards.

Dear seenshoo.
Thanks for your reply.
I issued the followings.
BEGIN
DBMS_SCHEDULER.CREATE_JOB(
job_name=>'TEST_EXPORT_JOB',
job_type=>'EXECUTABLE',
job_action=>'C:\oracle\product\10.2.0\admin\RAC\dpdump\expdp_nmsuser_daily.bat',
start_date=>SYSTIMESTAMP,
repeat_interval=>'freq=HOURLY; INTERVAL=1',
end_date=>NULL,
ENABLED=>TRUE,
comments=>'DAILY EXPORTING');
end;
Now, how can i excute it? I am reading manual, but do not know where it is.
Thanks and Regards.

Compress=Y in Exp and Expdp

I have been using oracle export/import as well as datapump export/import on a regular basis in building our database environments. I noticed the difference between the normal export and the datapump export.
Export(exp) has the compress=Y/N option whereas i didnt see the option in Datapump.
I was looking at the Documentation and found that
http://download.oracle.com/docs/cd/B14117_01/server.101/b10825/dp_export.htm#i1005864
"A parameter comparable to COMPRESS is not needed. " --This is what described in the documentation.
Does Datapump export does automatic compresssion?
I have tried exporting a table(size-14G) from our Database with "norows" option using normal export and tried Datapump export using Metadata_only option and generated the Sql for the metadata definitions.
The script from the normal export shows the initial extent size of 2g whereas SQLfile from the datapump import shows 260M.
Now,which is the best approach for creating objects while Data movement across Databases.
Please clarify.

using compress=y in export means:
exp determines the total size of the segment, uses that as the size of the new initial extent, and sets the next extent to 10 percent of the initial extent.
It is a remnant from the V6 days when there were only dictionary managed tablespaces, and many DBAs (including yours truly) where micromanaging table size and free space size.
That said, even Oracle admits it was not their brightest moment, and you shouldn't use it, ever.
Obviously introducing expdp, in a LMT world, was the moment to get rid of it.
Sybrand Bakker
Senior Oracle DBA

TDE (Encryption) and expdp (Datapump)

Hi,
I'm testing TDE's features on an Oracle 10g R2 database. I edit the sqlnet.ora then I created a wallet on database 1 (DEV1), a table, did inserts, pumped (expdp) data and tried re-import it in another database (DEV2) which I use with DataGuard for failover, but something went wrong. So I try re-create my wallet on the first database (DEV1) by alter system set wallet close and delete it from my hard drive and drop table purge. I went trought the whole process of creating the wallet and table but when I tried expdp I got the ORA-28362 master key not found.
How could I not be able to export my data ? What can I do to do a clean deletion of the wallet and recreate it ?
Thanks for you help
Francis

Thank you,
but I already read those pages and understand them. But as I said, even though I delete and recreate the wallet, I can't get datapump to extract data with the ENCRYPTION_PASSWORD parameter. If I don't put this parameter everything is ok! but the data is not encrypted.

Database Vault and expdp

Hi, i want export the database schema which is protected by database vault.
Metalink Note:433887.1 describes this, but i receive errors.
expdp bernst/password schemas=HR file=/tmp/test
ORA-31626 job does not exist
ORA-31633 unable to create master table bernst.sys_export_schema_05
ORA-06512 at sys.dbms_sys_error
ORA-06512 at sys.KUPV$FT
ORA-01950 no privileges on tablespace USERS
any ideas?
regards Frank

This is late but, somebody will see it.
Be sure to do this.
First of all, create a user called pepe in this way.
create user pepe identified by PASSWORD default tablespace users temporary tablespace temp;
Then...
SQL> CREATE DIRECTORY datapump AS 'full_path';
SQL> GRANT EXP_FULL_DATABASE to pepe;
SQL> GRANT READ, WRITE ON DIRECTORY datapump to pepe;
You should be able then to run the expdp utility.
Alex.

Impdp and available memory

Just a quick one on how available memory can affect datapump imp.
Will increasing the SGA from 2GB to 8GB of a database on which data is being imported affect the total import time?
Just a bit curious!
Thanks

Hi,
What is the method of the Import Method. Whether it is External Path or Direct Path. If it is Direct Path it will not use buffer cache, it will directly insert after the HWM. If it is External Path it will use the SGA. I dont find a point to increase the size of SGA for the import process alone. If you have a luxury of having 8GB instance for import process you can have it for the normal databse operations too. Rather you can do the import process on the less peak time or you need to address the below questions to increase the size of SGA for this process
1) how much data are you going to insert?
2) how many users are going to be connected to the Oracle database when import is going to happen?
3) how big is your improting data and how it wll affect the performance
You can go for direct path insert which will be faster than the external path
Thanks,
Vijay

IMPDP and EXPDP

Similar Messages

Maybe you are looking for