| Impdp - Packge Body Import taking Huge Time [message #566396] |
Thu, 13 September 2012 23:46  |
sap_arul
Messages: 27
Registered: November 2005
Location: BANGALORE
|
Junior Member |
|
|
Hi,
I am try to import 4G dump in Oracle 11R2 version, in that we have around 9000+ Package Body which is taking huge time than other objects (about 8 to 12 hrs) and also it is expecting lots of system space (roughly about 10GB).
I have tried both parallel and non-parallel.
Please advice, how to improve speed of the package body import.
Details about the Schema & Import
No. of objects in Schema
SQL> select object_type,count(1) from user_objects GROUP BY ROLLUP( object_type);
OBJECT_TYPE COUNT(1)
------------------- ----------
FUNCTION 248
INDEX 5161
JAVA CLASS 471
JAVA RESOURCE 1
JAVA SOURCE 16
LIBRARY 1
LOB 131
MATERIALIZED VIEW 1
PACKAGE 9605
PACKAGE BODY 9526
PROCEDURE 491
OBJECT_TYPE COUNT(1)
------------------- ----------
SEQUENCE 17684
SYNONYM 15699
TABLE 5795
TABLE PARTITION 18
TRIGGER 377
TYPE 105
VIEW 2707
68037
Impdp Parameter
userid=USERID/PASSWORD
logfile=IMPORT.LOG
dumpfile = DATA_FINAL.DMP
directory=IMPORT_DUMP_DIR
job_name = IMPORT_JOB_imp
REMAP_TABLESPACE = SOURCE:DEST
remap_schema = SOURCE:DEST
EXCLUDE=GRANT,STATISTICS
Regards,
Arul.
|
|
|
|
|
|
| Re: Impdp - Packge Body Import taking Huge Time [message #566981 is a reply to message #566396] |
Fri, 21 September 2012 14:34  |
 |
LKBrwn_DBA
Messages: 487
Registered: July 2003
Location: WPB, FL
|
Senior Member |
|
|
What Mahesh is looking for is: if you used the "CONTENT=METADATA_ONLY" for your export.
Othewise (if you did full/schema export) then impdp has to read the full dump file even if it will not import the data or anything else.
Now, if you want to speed the import of procedures/packages, use the said export parameter and take another export.
[Updated on: Fri, 21 September 2012 14:47] by Moderator Report message to a moderator |
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
