Expdp/impdp error

Hi Aman,
Sorry about that. Posting it as new one:
SQL> ALTER USER SCOTT DEFAULT TABLESPACE TEST;
User altered.
SQL> ALTER USER TEST DEFAULT TABLESPACE TEST;
User altered.
SQL> ALTER TABLESPACE TEST
2 STORAGE
3 MAXEXTENTS UNLIMITED;
STORAGE
ERROR at line 2:
ORA-02142: missing or invalid ALTER TABLESPACE option
SQL> EXIT
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Pr
oduction
With the Partitioning, OLAP and Data Mining options
C:\Documents and Settings\Rafialvi>expdp system/manager directory=MYDIR dumpfile
=expdpf.dmp schemas=scott
Export: Release 10.2.0.1.0 - Production on Monday, 15 February, 2010 16:34:57
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining 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 475
ORA-29283: invalid file operation
I tried in linux still the same error persist:
[oracle@dbcl1n1 AUCD1 ~]$ expdp system/system directory=MYDIR dumpfile=expdpf.dmp schemas=adprod
Export: Release 10.2.0.4.0 - 64bit Production on Monday, 15 February, 2010 3:22:33
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, Real Application Clusters, 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 operation
Thanks,
Rafi.
C:\Documents and Settings\Rafialvi>
Thanks,
Rafi

Hi Khaja,
You was quite right thanks man.I was not creating directory.But still struggliing with below problem on windows and export is going on linux...
code code
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Feb 15 17:24:09 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter user-name: /as sysdba
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> create directory mydir3 as 'C:\oracle\product\10.2.0\expdptest';
Directory created.
SQL> grant read,write on mydir3 to public;
grant read,write on mydir3 to public
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> grant read,write on directory mydir3 to public;
Grant succeeded.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Pr
oduction
With the Partitioning, OLAP and Data Mining options
C:\Documents and Settings\Rafialvi>expdp system/manager directory=MYDIR3
Export: Release 10.2.0.1.0 - Production on Monday, 15 February, 2010 17:28:47
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
Starting "SYSTEM"."SYS_EXPORT_SCHEMA_01": system/******** directory=MYDIR3
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 320 KB
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SYNONYM/SYNONYM
Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/PRE_TABLE_ACTION
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/GRANT/CROSS_SCHEMA/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_
PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/VIEW/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/VIEW/GRANT/CROSS_SCHEMA/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/VIEW/COMMENT
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/POST_TABLE_ACTION
Processing object type SCHEMA_EXPORT/POST_SCHEMA/PROCACT_SCHEMA
. . exported "SYSTEM"."REPCAT$_AUDIT_ATTRIBUTE" 5.960 KB 2 rows
. . exported "SYSTEM"."REPCAT$_OBJECT_TYPES" 6.515 KB 28 rows
. . exported "SYSTEM"."REPCAT$_RESOLUTION_METHOD" 5.656 KB 19 rows
. . exported "SYSTEM"."REPCAT$_TEMPLATE_STATUS" 5.304 KB 3 rows
. . exported "SYSTEM"."REPCAT$_TEMPLATE_TYPES" 5.921 KB 2 rows
. . exported "SYSTEM"."DEF$_AQCALL" 0 KB 0 rows
. . exported "SYSTEM"."DEF$_AQERROR" 0 KB 0 rows
. . exported "SYSTEM"."DEF$_CALLDEST" 0 KB 0 rows
. . exported "SYSTEM"."DEF$_DEFAULTDEST" 0 KB 0 rows
. . exported "SYSTEM"."DEF$_DESTINATION" 0 KB 0 rows
. . exported "SYSTEM"."DEF$_ERROR" 0 KB 0 rows
. . exported "SYSTEM"."DEF$_LOB" 0 KB 0 rows
. . exported "SYSTEM"."DEF$_ORIGIN" 0 KB 0 rows
. . exported "SYSTEM"."DEF$_PROPAGATOR" 0 KB 0 rows
. . exported "SYSTEM"."DEF$_PUSHED_TRANSACTIONS" 0 KB 0 rows
. . exported "SYSTEM"."DEF$_TEMP$LOB" 0 KB 0 rows
. . exported "SYSTEM"."LOGSTDBY$APPLY_MILESTONE" 0 KB 0 rows
. . exported "SYSTEM"."LOGSTDBY$APPLY_PROGRESS":"P0" 0 KB 0 rows
. . exported "SYSTEM"."LOGSTDBY$EVENTS" 0 KB 0 rows
. . exported "SYSTEM"."LOGSTDBY$HISTORY" 0 KB 0 rows
. . exported "SYSTEM"."LOGSTDBY$PARAMETERS" 0 KB 0 rows
. . exported "SYSTEM"."LOGSTDBY$PLSQL" 0 KB 0 rows
. . exported "SYSTEM"."LOGSTDBY$SCN" 0 KB 0 rows
. . exported "SYSTEM"."LOGSTDBY$SKIP" 0 KB 0 rows
. . exported "SYSTEM"."LOGSTDBY$SKIP_TRANSACTION" 0 KB 0 rows
. . exported "SYSTEM"."MVIEW$_ADV_INDEX" 0 KB 0 rows
. . exported "SYSTEM"."MVIEW$_ADV_PARTITION" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_AUDIT_COLUMN" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_COLUMN_GROUP" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_CONFLICT" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_DDL" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_EXCEPTIONS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_EXTENSION" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_FLAVORS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_FLAVOR_OBJECTS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_GENERATED" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_GROUPED_COLUMN" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_INSTANTIATION_DDL" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_KEY_COLUMNS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_OBJECT_PARMS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_PARAMETER_COLUMN" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_PRIORITY" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_PRIORITY_GROUP" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_REFRESH_TEMPLATES" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_REPCAT" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_REPCATLOG" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_REPCOLUMN" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_REPGROUP_PRIVS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_REPOBJECT" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_REPPROP" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_REPSCHEMA" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_RESOLUTION" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_RESOLUTION_STATISTICS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_RESOL_STATS_CONTROL" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_RUNTIME_PARMS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_SITES_NEW" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_SITE_OBJECTS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_SNAPGROUP" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_TEMPLATE_OBJECTS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_TEMPLATE_PARMS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_TEMPLATE_REFGROUPS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_TEMPLATE_SITES" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_TEMPLATE_TARGETS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_USER_AUTHORIZATIONS" 0 KB 0 rows
. . exported "SYSTEM"."REPCAT$_USER_PARM_VALUES" 0 KB 0 rows
. . exported "SYSTEM"."SQLPLUS_PRODUCT_PROFILE" 0 KB 0 rows
Master table "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
Dump file set for SYSTEM.SYS_EXPORT_SCHEMA_01 is:
C:\ORACLE\PRODUCT\10.2.0\EXPDPTEST\EXPDAT.DMP
Job "SYSTEM"."SYS_EXPORT_SCHEMA_01" successfully completed at 17:29:13
C:\Documents and Settings\Rafialvi>dumpfile=expdpf.dmp schemas=scott
'dumpfile' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Rafialvi>impdp system/manager directory=MYDIR3 dumpfil
e=expdpf.dmp remap_schema=scott:test
Import: Release 10.2.0.1.0 - Production on Monday, 15 February, 2010 17:30:46
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31640: unable to open dump file "C:\oracle\product\10.2.0\expdptest\expdpf.d
mp" for read
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
C:\Documents and Settings\Rafialvi>expdp scott/tiger directory=MYDIR3
Export: Release 10.2.0.1.0 - Production on Monday, 15 February, 2010 17:35:51
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "C:\oracle\product\10.2.0\expdptest\expdat
.dmp"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists
C:\Documents and Settings\Rafialvi>dumpfile=expdpf.dmp schemas=scott
'dumpfile' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Rafialvi>expdp scott/tiger directory=MYDIR3
Export: Release 10.2.0.1.0 - Production on Monday, 15 February, 2010 17:36:19
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "C:\oracle\product\10.2.0\expdptest\expdat
.dmp"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists
C:\Documents and Settings\Rafialvi>dumpfile=expdptest.dmp schemas=scott
'dumpfile' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Rafialvi>expdp scott/tiger directory=MYDIR3
Export: Release 10.2.0.1.0 - Production on Monday, 15 February, 2010 17:36:43
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "C:\oracle\product\10.2.0\expdptest\expdat
.dmp"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists
C:\Documents and Settings\Rafialvi>dumpfile=expdptest3.dmp schemas=scott
'dumpfile' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Rafialvi>expdp scott/tiger directory=MYDIR3
Export: Release 10.2.0.1.0 - Production on Monday, 15 February, 2010 17:47:31
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "C:\oracle\product\10.2.0\expdptest\expdat
.dmp"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists
C:\Documents and Settings\Rafialvi>dumpfile=expdptest13.dmp schemas=scott
'dumpfile' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Rafialvi>expdp scott/tiger directory=MYDIR3
Export: Release 10.2.0.1.0 - Production on Monday, 15 February, 2010 17:48:32
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "C:\oracle\product\10.2.0\expdptest\expdat
.dmp"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists
C:\Documents and Settings\Rafialvi>dumpfile=expdptest131.dmp schemas=scott
'dumpfile' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Rafialvi>expdp scott/tiger directory=MYDIR3
Export: Release 10.2.0.1.0 - Production on Monday, 15 February, 2010 17:50:15
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31641: unable to create dump file "C:\oracle\product\10.2.0\expdptest\expdat
.dmp"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists
How to get rid of below error khaja.
Thanks,
Rafi.

Similar Messages

EXP/IMP..of table having LOB column to export and import using expdp/impdp

we have one table in that having colum LOB now this table LOB size is approx 550GB.
as per our knowldge LOB space can not be resused.so we have alrady rasied SR on that
we are come to clusion that we need to take backup of this table then truncate this table and then start import
we need help on bekow ponts.
1)we are taking backup with expdp using parellal parameter=4 this backup will complete sussessfully? any other parameter need to keep in expdp while takig backup.
2)once truncate done,does import will complete successfully..?
any SGA PGA or undo tablespace size or undo retention we need to increase.. to completer susecfully import? because its production Critical database?
current SGA 2GB
PGA 398MB
undo retention 1800
undo tbs 6GB
please any one give suggestion to perform activity without error...also suggest parameter need to keep during expdp/impdp
thanks an advance.

Hi,
From my experience be prepared for a long outage to do this - expdp is pretty quick at getting lobs out but very slow at getting them back in again - a lot of the speed optimizations that may datapump so excellent for normal objects are not available for lobs. You really need to test this somewhere first - can you not expdp from live and load into some test area - you don't need the whole database just the table/lob in question. You don;t want to find out after you truncate the table that its going to take 3 days to import back in....
You might want to consider DBMS_REDEFINITION instead?
Here you precreate a temporary table (with same definitiion as the existing one), load the data into it from the existing table and then do a dictionary switch to swap them over - giving you minimal downtime. I think this should work fine with LOBS at 10g but you should do some research and see if it works fine. You'll need a lot of extra tablespace (temporarily) for this approach though.
Regards,
Harry

Impdp errors with ORA-01400: cannot insert NULL into

Hi Experts,
I have very intresting situation when I use impdp to import table back to DB.
Environment:
Database Server: 10.2.0.4 Enterprise
OS: RHEL 5.5 64-bit
We have a table and it's size is 350+ GB and so to reclaim space I want to perform expdp/impdp operation. When I following below steps:
1) expdp table
2) drop table
3) impdp full table
It works like a charm and I am able to reclaim 83% space and table size shows about 20GB.
But when I follow below method:
1) expdp table
2) truncate table (To save some time not to import indexes, stats, constraints , etc)
3) impdp table
I get following error:
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
Master table "SYS"."SYS_IMPORT_TABLE_01" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_TABLE_01": sys/******** tables=<schema>.<table_name> directory=test_dir dumpfile=<table_name>_%u.dmp logfile=impdp_<table_name>.log parallel=16 CONTENT=DATA_ONLY
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
ORA-31693: Table data object "<schema"."table_name" failed to load/unload and is being skipped due to error:
ORA-01400: cannot insert NULL into ("schema"."table_name"."ID")
Job "SYS"."SYS_IMPORT_TABLE_01" completed with 1 error(s) at 16:12:28
Please advise how to proceed further, it seems like I am hitting some sort of Bug but metalink does not show any.
Regards,
MS
Edited by: user10651321 on Nov 9, 2012 4:38 PM

expdp and impdp operations should not be executed as SYS - try SYSTEM account instead. See first Note section here - http://docs.oracle.com/cd/B19306_01/server.102/b14215/dp_import.htm#sthref243
Pl post the complete expdp and impdp commands used, along with a description of the table for which you encounter this error.
HTH
Srini

XE11: expdp/impdp

Hello,
i would like to use expdp and impdp.
As i installed XE11 on Linux, i unlocked the HR account:
ALTER USER hr ACCOUNT UNLOCK IDENTIFIED BY hr;
and use the expdp:
expdp hr/hr DUMPFILE=hrdump.dmp DIRECTORY=DATA_PUMP_DIR SCHEMAS=HR
LOGFILE=hrdump.log
This quits with:
ORA-39006: internal error
ORA-39213: Metadata processing is not available
The alert_XE.log reported:
ORA-12012: error on auto execute of job "SYS"."BSLN_MAINTAIN_STATS_JOB"
ORA-06550: line 1, column 807:
PLS-00201: identifier 'DBSNMP.BSLN_INTERNAL' must be declared
I read some entries here and did:
sqlplus sys/******* as sysdba @?/rdbms/admin/catnsnmp.sql
sqlplus sys/******* as sysdba @?/rdbms/admin/catsnmp.sql
sqlplus sys/******* as sysdba @?/rdbms/admin/catdpb.sql
sqlplus sys/******* as sysdba @?/rdbms/admin/utlrp.sql
I restarted the database, but the result of expdp was the same:
ORA-39006: internal error
ORA-39213: Metadata processing is not available
What's wrong with that? What can i do?
Do i need "BSLN_MAINTAIN_STATS_JOB" or can this set ro FALSE?
I created the database today on 24.07. and the next run for "BSLN_MAINTAIN_STATS_JOB"
is on 29.07. ?
In the Windows-Version it is working correct, but not in the Linux-Version.
Best regards

Hello gentlemen,
back to the origin:
'Is expdp/impdp working on XE11'
The answer is simply yes.
After a view days i found out that:
- no stylesheets installed are required for this operation
- a simple installation is enough
And i did:
SHELL:
mkdir /u01/app > /dev/null 2>&1
mkdir /u01/app/oracle > /dev/null 2>&1
groupadd dba
useradd -g dba -d /u01/app/oracle oracle > /dev/null 2>&1
chown -R oracle:dba /u01/app/oracle
rpm -ivh oracle-xe-11.2.0-1.0.x86_64.rpm
/etc/init.d/./oracle-xe configure responseFile=xe.rsp
./sqlplus sys/********* as sysdba @/u01/app/oracle/product/11.2.0/xe/rdbms/admin/utlfile.sql
SQLPLUS:
ALTER USER hr IDENTIFIED BY hr ACCOUNT UNLOCK;
GRANT CONNECT, RESOURCE to hr;
GRANT read, write on DIRECTORY DATA_PUMP_DIR TO hr;
expdp hr/hr dumpfile=hr.dmp directory=DATA_PUMP_DIR schemas=hr logfile=hr_exp.log
impdp hr/hr dumpfile=hr.dmp directory=DATA_PUMP_DIR schemas=hr logfile=hr_imp.log
This was carried out on:
OEL5.8, OEL6.3, openSUSE 11.4
For explanation:
We did the style-sheet-installation for XE10 to have the expdp/impd functionality.
Thanks for your assistance
Best regards
Achim
Edited by: oelk on 16.08.2012 10:20

Log file's format in expdp\impdp

Hi all,
I need to set log file format for expdp\impdp utility. I have this format for my dump file - filename=<name>%U.dmp which generates unique names for dump files. How can i generate unique names for log files? It'd better if dump file name and log file names will be the same.
Regards,
rustam_tj

Hi Srini, thanks for advice.
I read doc which you suggest me. The only thing which i found there is:
Log files and SQL files overwrite previously existing files.
So i cant keep previos log files?
My OS is HP-UX (11.3) and database version is 10.2.0.4
Regards,
rustam

Expdp/impdp :: Constraints in Parent child relationship

Hi ,
I have one table parent1 and tables child1, child2 and chld3 have foreign key created on this parent1.
Now I want to do some deletion on parent1. But since number of records are very high on parent1 , we are going with expdp / impdp with querry option.
I have taken query level expdp on parent1. Now I dropped parent1 with cascade constraints option and all the foreign keys created by child1 ,2 and 3 which references parent1 are automatically dropped.
Now If i fire the impdp for the query level dump file , will these foreign key constraints will get created automatically on child1 ,2 and 3 or I need to manually re-create it ??
Regards,
Anu

Hi,
The FK's will not be in the dumpfile - see the example code below where i generate a sqlfile following pretty much the process you would have done. THis is because the FK is part of the DDL for the child table not the parent.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning option
OPS$ORACLE@EMZA3>create table a (col1 number);
Table created.
OPS$ORACLE@EMZA3>alter table a add primary key (col1);
Table altered.
OPS$ORACLE@EMZA3>create table b (col1 number);
Table created.
OPS$ORACLE@EMZA3>alter table b add constraint x foreign key (col1) references a(col1);
Table altered.
OPS$ORACLE@EMZA3>
EMZA3:[/oracle/11.2.0.1.2.DB/bin]# expdp / include=TABLE:\"=\'A\'\"
Export: Release 11.2.0.3.0 - Production on Fri May 17 15:45:50 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning option
Starting "OPS$ORACLE"."SYS_EXPORT_SCHEMA_04": /******** include=TABLE:"='A'"
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 0 KB
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
. . exported "OPS$ORACLE"."A"                                0 KB       0 rows
Master table "OPS$ORACLE"."SYS_EXPORT_SCHEMA_04" successfully loaded/unloaded
Dump file set for OPS$ORACLE.SYS_EXPORT_SCHEMA_04 is:
/oracle/11.2.0.3.0.DB/rdbms/log/expdat.dmp
Job "OPS$ORACLE"."SYS_EXPORT_SCHEMA_04" successfully completed at 15:45:58
Import: Release 11.2.0.3.0 - Production on Fri May 17 15:46:16 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning option
Master table "OPS$ORACLE"."SYS_SQL_FILE_FULL_01" successfully loaded/unloaded
Starting "OPS$ORACLE"."SYS_SQL_FILE_FULL_01": /******** sqlfile=a.sql
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Job "OPS$ORACLE"."SYS_SQL_FILE_FULL_01" successfully completed at 15:46:17
-- CONNECT OPS$ORACLE
ALTER SESSION SET EVENTS '10150 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10904 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '25475 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10407 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10851 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '22830 TRACE NAME CONTEXT FOREVER, LEVEL 192 ';
-- new object type path: SCHEMA_EXPORT/TABLE/TABLE
CREATE TABLE "OPS$ORACLE"."A"
   (    "COL1" NUMBER
   ) SEGMENT CREATION IMMEDIATE
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
NOCOMPRESS LOGGING
STORAGE(INITIAL 16384 NEXT 16384 MINEXTENTS 1 MAXEXTENTS 505
PCTINCREASE 50 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "SYSTEM" ;
-- new object type path: SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ALTER TABLE "OPS$ORACLE"."A" ADD PRIMARY KEY ("COL1")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 16384 NEXT 16384 MINEXTENTS 1 MAXEXTENTS 505
PCTINCREASE 50 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "SYSTEM" ENABLE;
-- new object type path: SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
DECLARE I_N VARCHAR2(60);
I_O VARCHAR2(60);
NV VARCHAR2(1);
c DBMS_METADATA.T_VAR_COLL;
df varchar2(21) := 'YYYY-MM-DD:HH24:MI:SS';
stmt varchar2(300) := ' INSERT INTO "SYS"."IMPDP_STATS" (type,version,flags,c1,c2,c3,c5,n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,d1,cl1) VALUES (''I'',6,:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11,:12,:13,NULL,:14,:15,NULL,:16,:17)';
BEGIN
DELETE FROM "SYS"."IMPDP_STATS";
c(1) := 'COL1';
DBMS_METADATA.GET_STAT_INDNAME('OPS$ORACLE','A',c,1,i_o,i_n);
EXECUTE IMMEDIATE stmt USING 0,I_N,NV,NV,I_O,0,0,0,0,0,0,0,0,NV,NV,TO_DATE('2013-05-17 15:43:24',df),NV;
DBMS_STATS.IMPORT_INDEX_STATS('"' || i_o || '"','"' || i_n || '"',NULL,'"IMPDP_STATS"',NULL,'"SYS"');
DELETE FROM "SYS"."IMPDP_STATS";
END;
/Regards,
Harry
http://dbaharrison.blogspot.com/

System generated Index names different on target database after expdp/impdp

After performing expdp/impdp to move data from one database (A) to another (B), the system name generated indexes has different names on the target database, which caused a major issue with GoldenGate. Could anyone provide any tricks on how to perform the expdp/impdp and have the same system index name generated to be the same on both source and target?
Thanks in advance.
JL

While I do not agree with Sb choice of wording his solution is correct. I suggest you drop and recreate the objects using explicit naming then you will get the same names on the target database after import for constraints, indexes, and FK's.
A detailed description of the problem this caused with Golden Gate would be interesting. The full Oracle and Golden Gate versions is use might also be important to the solution, if one exists other than explicitl naming.
HTH -- Mark D Powell --
Edited by: Mark D Powell on May 30, 2012 12:26 PM

Expdp+Impdp: Does the user have to have DBA privilege?

Is a "normal" user (=Without DBA privilege) allowed to export and import (with new expdp/impdp) his own schema?
Is a "normal" user (=Without DBA privilege) allowed to export and import (with new expdp/impdp) other (=not his own) schemas ?
If he is not allowed: Which GRANT is necessary to be able to perform such expdp/impdp operations?
Peter
Edited by: user559463 on Feb 28, 2010 7:49 AM

Hello,
Is a "normal" user (=Without DBA privilege) allowed to export and import (with new expdp/impdp) his own schema?Yes, a User can always export its own objects.
Is a "normal" user (=Without DBA privilege) allowed to export and import (with new expdp/impdp) other (=not his own) schemas ?Yes, if this User has EXP_FULL_DATABASE and IMP_FUL_DATABASE Roles.
So, you can create a User and GRANT it EXP_FULL_DATABASE and IMP_FULL_DATABASE Roles and, being connected
to this User, you could export/import any Object from / to any Schemas.
On databases, on which there're a lot of export/import operations, I always create a special User with these Roles.
NB: In DataPump you should GRANT also READ, WRITE Privileges on the DIRECTORY (if you use "dump") to the User.
Else, be accurate on the choice of your words, as previously posted, DBA is a Role not a Privilege which has another meaning.
Hope this help.
Best regards,
Jean-Valentin

[ETL] TTS vs expdp/impdp vs ctas (dblink)

Hi, all.
The database is oracle 10gR2 on a unix machine.
Assuming that the db size is about 1 tera bytes (table : 500 giga, index : 500 giga),
how much faster is TTS (transportable tablespace) over expdp/impdp, and over ctas (dblink) ?
As you know, the speed of etl depends on the hardware capacity. (io capacity, network bandwith, the number of cpu)
I just would like to hear general guide from your experience.
Thanks in advance.
Best Regards.

869578 wrote:
Hi, all.
The database is oracle 10gR2 on a unix machine.
Assuming that the db size is about 1 tera bytes (table : 500 giga, index : 500 giga),
how much faster is TTS (transportable tablespace) over expdp/impdp, and over ctas (dblink) ?
As you know, the speed of etl depends on the hardware capacity. (io capacity, network bandwith, the number of cpu)
I just would like to hear general guide from your experience.
Thanks in advance.
Best Regards.http://docs.oracle.com/cd/B19306_01/server.102/b14231/tspaces.htm#ADMIN01101
Moving data using transportable tablespaces is much faster than performing either an export/import or unload/load of the same data. This is because the datafiles containing all of the actual data are just copied to the destination location, and you use an export/import utility to transfer only the metadata of the tablespace objects to the new database.
If you really want to know "how much faster" you're going to have to benchmark. Lots of variables come in to play so best to determine this in your actual environment.
Cheers,

Error : Temporary Tablespace is Empty when doing expdp/impdp

Hi all,
I was doing expdp on my oracle 10.1.0.2.0 DB on Win XP P, though the user is having a default temporary tablespace with a temp file on autoextend enabled, I got the message as...
ORA-25153: Temporary Tablespace is Empty
Then I created a new temporary tablespace for the user with 500M tempfile and autoextend enabled, then expdp went through.
Now I am doing the impdp for the same .dmp file to generate one sqlfile for the DB,
again I am facing the same error message as...
ORA-25153: Temporary Tablespace is Empty
----- PL/SQL Call Stack -----
object line object
handle number name
17FE07EC 13460 package body SYS.KUPW$WORKER
17FE07EC 5810 package body SYS.KUPW$WORKER
17FE07EC 3080 package body SYS.KUPW$WORKER
17FE07EC 3530 package body SYS.KUPW$WORKER
17FE07EC 6395 package body SYS.KUPW$WORKER
17FE07EC 1208 package body SYS.KUPW$WORKER
17ABE058 2 anonymous block
Job "CHECKUP"."SYS_SQL_FILE_FULL_02" stopped due to fatal error at 10:09
The message indicates that...
ORA-25153: Temporary Tablespace is Empty
Cause: An attempt was made to use space in a temporary tablespace with no files.
Action: Add files to the tablespace using ADD TEMPFILE command.
SO my question is every time I do any imp exp have I to add temp file in my temporary tablespace? will it not be cleared on the completion of the job?
Any advice please.

Hi Sabdar,
The result of the query is as...
SQL> SELECT * FROM DATABASE_PROPERTIES where
2 PROPERTY_NAME='DEFAULT_TEMP_TABLESPACE';
PROPERTY_NAME
PROPERTY_VALUE
DESCRIPTION
DEFAULT_TEMP_TABLESPACE
TEMP
Name of default temporary tablespace
So the default temporary tablespace is TEMP which is not having any tempfile as I cloned this DB from the primary DB, but the user I am using for the impdp is 'checkup' and the temporary tablespace for 'checkup' is 'checkup_temp1' which s having tempfile.
SO then why the impdp job is going to server's temporary tablespace instead of user's temporary tablespace.
Is there any way to get whether 'checkup_temp1' tablespace is the default temporary tablespace for 'checkup' or not?
Can I create create the user mentioning default temporary tablespace anyway because it is giving me error as...
SQL> create user suman identified by suman
2 default tablespace checkup_dflt
3 default TEMPORARY TABLESPACE checkup_temp1;
default TEMPORARY TABLESPACE checkup_temp1
ERROR at line 3:
ORA-00921: unexpected end of SQL command
Then I did ...
SQL> create user suman identified by suman
2 default tablespace checkup_dflt
3 TEMPORARY TABLESPACE checkup_temp1;
User created.
Regards

Synonyms Error while EXPDP/IMPDP

Hi Firends..
I have to refresh my UAT DB with my Prod DB while doing so i always have to recreate the synonyms and also have to grant the priveleges once again on the target DB.
As i am using EXPDP to backup my DB and as this being a logical backup and a logical backup means the objects which includes synonyms as well, are backed up and then during import this should be recreated in the target DB.
Following are the command that i am using:
expdp dumpfile=file_name.dmp logfile=logfile_name.log schemas=abc_liv directory=DATA_PUMP_DIR status=100 exclude=statistics
impdp dumpfile=file_name.dmp logfile=logfile_name.log remap_schema=abc_liv:abc directory=DATA_PUMP_DIRwhere:
abc_liv = prod schema
abc = uat schema
Note:
UAT and Prod DB both has three schemas each and there are lots of dependencies among the three schemas.
UAT schemas names are different and Prod schemas names are different.
Kindly enlighten me...
BR

Thanks Guys,
OS:RHEL 64 bit
DB:11.2.0.2 64 bit SE
I do drop the entire schema and then recreate the same schema. Following is the command that i use:
drop user schema_name cascade;As the cascade keyword is used, all the schema objects are also dropped along with the user and then i have a fresh schema of the same name which is dumped with the data of the Prod DB.
Following are the errors that i am getting during Import:(Too many errors)
ALTER_PACKAGE_SPEC:"schema_name"."PKG_LMS_ALO_PKG_MAIN" created with compilation warnings
ORA-39082: Object type ALTER_PACKAGE_SPEC:"schema_name"."PKG_REROUTE_MASTERS" created with compilation warnings
ORA-39082: Object type ALTER_PACKAGE_SPEC:"schema_name"."PKG_WF_GLOBAL_VARIABLES" created with compilation warnings
Processing object type SCHEMA_EXPORT/FUNCTION/ALTER_FUNCTION
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."CHECKDUPLICAT" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."CHG_FUN_GET_CHARGE_DETAILS" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."CHG_FUN_GET_CHGBASIS_DESC" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."CHG_FUN_GET_PENAL_APPLIC_YN" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."CPF_FUN_EXT_AGENCY_OTHER" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."DOC_FUN_GETSMDESC" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."FUNCTION_SET_EXPECTEDAPPRDATE" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."FUNCTION_SET_EXPECTEDFIDATE" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."FUN_ACTIVITY_COMPLETED_YN" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."FUN_ACTIVITY_DONEYN" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."FUN_ACTUAL_DISB_DONE_YN" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."FUN_ADD_UPD_EXP" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."FUN_ADV_INSTALL_DISPLAY_YN" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."WFS_GET_USER_MODULE_SPECIFIED" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."WF_FUN_GET_AVL_PARAM_DETAILS" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."WF_FUN_GET_NO_OF_CASES" created with compilation warningsProcessing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."ADD_PARAMETER" created with compilation warningsORA-39082: Object type ALTER_PROCEDURE:"schema_name"."CHECK_APPL_IMPACT_PERF_REROUTE" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."CHECK_FAULT" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."FEE_WAIVER_REQ_M_YN" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."FIND_DEDUP_MATCH" created with compilation warningsORA-39082: Object type ALTER_PROCEDURE:"schema_name"."FIND_DEDUP_MATCH_APPL" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."GENERATE_ENVELOPE" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."GENERATE_TRNAUDIT_LOG" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."GET_DOCUMENTS_FORADDITION_XML" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."GET_DOCUMENTS_FORWAIVER_XML" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."LMSRSP_CMPSUM_OUTSTPORTFOLIO" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."LMSRSP_CUST_OS_EXP_SUM" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."LMSRSP_FUTURE_INFLOWS" created with compilation warningsORA-39082: Object type ALTER_PROCEDURE:"schema_name"."LMSRSP_INTEREST_CERTIFICATE" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."LMSRSP_NONSTARTERCASE_DET" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."LMSRSP_NONSTARTERCASE_SUM" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."LMSRSP_ODPREEMI_EMISUMMARY" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."LMSRSP_SHORT_PDC_REPORT" created with compilation warningsORA-39082: Object type ALTER_PROCEDURE:"schema_name"."LOS_BATCH_PROCEDURE" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"schema_name"."PC_CALC_RISK_PARAMETERS" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"schema_name"."FUN_ALLOC_SPFC_USER" created with compilation warnings
ORA-39082: Object type
CHEMA_EXPORT/VIEW/VIEWProcessing object type SCHEMA_EXPORT/VIEW/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39082: Object type VIEW:"schema_name"."AST_VEW_ASSET" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."AST_VEW_ASSETTYPE" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."AST_VEW_ASSET_TYPE" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."AST_VEW_ASTCLASS" created with compilation warningsORA-39082: Object type VIEW:"schema_name"."AST_VEW_ATTR_MAPPING" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."AST_VEW_EXT_AGENCY" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."AST_VEW_VEHICLE_TYPE" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."BASE_SEC_MST_USERPROFILE" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_RPT_VEW_CHGBASISCODE" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_RPT_VEW_TAX_DETAILS" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_VEW_ACC_BOOKS" created with compilation warningsORA-39082: Object type VIEW:"schema_name"."CHG_VEW_ACC_METHOD" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_VEW_AMORT_METHOD" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_VEW_CALC_BASIS" created with compilation warnings
ORA-39082: Object type
VIEW:"schema_name"."CHG_VEW_CALC_FROM" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_VEW_CALC_TYPE" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_VEW_CHG_RECOMODE" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_VEW_EVENT" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_VEW_FEES" created with compilation warningsORA-39082: Object type VIEW:"schema_name"."CHG_VEW_FEES_RANGE" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_VEW_FEE_ACC_DETAILS" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_VEW_FEE_DETAILS" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."CHG_VEW_FEE_MST_DETAILS" created with compilation warnings
ORA-39082: Object type IEW:"schema_name"."V_LMS_CHEQUE_BOUNCE_LETTER" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."V_LMS_ACCRUED_INCOME_REPORT" created with compilation warnings
ORA-39082: Object type VIEW:"schema_name"."V_LMS_REPAY_FREQ" created with compilation warnings
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
ORA-39082: Object type PACKAGE_BODY:"schema_name"."AST_PKG_ASSET" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."CHG_PKG_API" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."DOC_PKG_DOCUMENT" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."EXT_PKG_EXT_AGENCY" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."PKG_ACCOUNT" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."PKG_ACCOUNTING" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."PKG_ADV_ALLOCATION" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."PKG_ALLOCATION" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."PKG_ASSET" created with compilation warningsORA-39082: Object type PACKAGE_BODY:"schema_name"."PKG_BASE_SEC_AUDIT" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."PKG_CHARGES" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."PKG_CRS_XML" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."PKG_DDP_MAIN" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."PKG_EODDETAILS" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"schema_name"."PKG_EOD_PROCESS" created with compilation warnings
ORA-39082: Object type
TRIGGER:"schema_name"."TRNTRG_T_APPLICANT_BUSINESS_IN" created with compilation warnings
ORA-39082: Object type TRIGGER:"schema_name"."TRNTRG_T_APPLICANT_BUSINESS_IN" created with compilation warnings
ORA-39082: Object type TRIGGER:"schema_name"."TRNTRG_ADDRESS_DETAILS" created with compilation warnings
ORA-39082: Object type TRIGGER:"schema_name"."TRNTRG_ADDRESS_DETAILS" created with compilation warnings
ORA-39082: Object type TRIGGER:"schema_name"."TRNTRG_T_APPLICANT_EMPLOYMENT" created with compilation warnings
ORA-39082: Object type TRIGGER:"schema_name"."TRNTRG_T_APPLICANT_EMPLOYMENT" created with compilation warnings
ORA-39082: Object type TRIGGER:"schema_name"."TRNTRG_T_APPLICANT_LIABILITIES" created with compilation warnings
ORA-39082: Object type TRIGGER:"schema_name"."TRNTRG_T_APPLICANT_LIABILITIES" created with compilation warnings
ORA-39082: Object type TRIGGER:"schema_name"."TRNTRG_T_SUBPRODUCT" created with compilation warnings
ORA-39082: Object type TRIGGER:"schema_name"."TRNTRG_T_SUBPRODUCT" created with compilation warnings
ORA-39082: Object type TRIGGER:"schema_name"."TRNTRG_T_ORG_APPLICANT_DETAILS" created with compilation warnings
ORA-39082: Object type TRIGGER:"schema_name"."TRNTRG_T_ORG_APPLICANT_DETAILS" created with compilation warnings
Processing object type SCHEMA_EXPORT/JOB
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 1687 error(s) at 17:32:05Once the import is done, I recreate the synonyms and also give the required grants and then i get around 1750 invalid objects in the DB and when i run the UTLRP to compile the objects the invalid count is reduced to 89..
BR
Edited by: user12045405 on 11 Jul, 2012 5:28 AM
Edited by: user12045405 on 11 Jul, 2012 5:29 AM

Schema Expdp-IMPdp , i have the below errors in my imp log

Hello All,
I am doing some exp/imp of schemas in a OBI environment and size around 300GB of each shema, after quiet a long time.., and not sure of the imp log errors whether to ignore or rerun my import with any changes or drop schemas and reimport ......
My IMP statement is
impdp system/********@OBIDEV schemas=ODS,DWH,STG,GEOGRAPHY directory=dumpdir dumpfile=BI2011_SCHEMAS.dmp logfile=impBI2011_SCHEMAS.log
Errors from the imp log :
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"GEOGRAPHY" already exists
ORA-31684: Object type USER:"DWH" already exists
ORA-31684: Object type USER:"STG" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
ORA-39083: Object type ROLE_GRANT failed to create with error:
ORA-01919: role 'ROLE_SRC' does not exist
Failing sql is:
GRANT "ROLE_SRC" TO "STG" WITH ADMIN OPTION
ORA-39083: Object type ROLE_GRANT failed to create with error:
ORA-01919: role 'ROLE_STG' does not exist
Failing sql is:
GRANT "ROLE_STG" TO "ODS" WITH ADMIN OPTION
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
a
--- and after some lines again the below errors, many failing sql's to created the tables ..
ORA-39083: Object type TABLE:"STG"."STG_ART_STOCK_OIG_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
Failing sql is:
CREATE TABLE "STG"."STG_ART_STOCK_OIG_XT" ("YEARWEEK" NUMBER, "ARTICLE_NUMBER" NUMBER, "BU_CODE" NUMBER, "ART_QTY_STOCK" NUMBER, "PM_CODE" VARCHAR2(10 BYTE)) ORGANIZATION EXTERNAL ( TYPE ORACLE_LOADER DEFAULT DIRECTORY "BI_SRC_FILES" ACCESS PARAMETERS ( RECORDS DELIMITED BY NEWLINE CHARACTERSET WE8MSWIN1252 STRING SIZES ARE IN BYTES BADFILE 'ART_STOCK_OIG.bad'
ORA-39083: Object type TABLE:"STG"."STG_ART_STOCK_INGKA_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
ORA-39083: Object type TABLE:"STG"."STG_ART_PMCODE_INGKA_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
Failing sql is:
CREATE TABLE "STG"."STG_IFPM_XT" ("YEAR" VARCHAR2(255 BYTE), "TERTIAL" VARCHAR2(255 BYTE), "YW" VARCHAR2(255 BYTE), "STORE_NAME" VARCHAR2(255 BYTE), "BUDGET" VARCHAR2(255 BYTE), "ACTUAL_SALES" VARCHAR2(255 BYTE), "CUSTOMERS" VARCHAR2(255 BYTE), "VISITORS" VARCHAR2(255 BYTE), "REST_SALES" VARCHAR2(255 BYTE), "EXIT_CAFE_SALES" VARCHAR2(255 BYTE), "SWE_FOOD_SALES" VARCHAR2
ORA-39083: Object type TABLE:"STG"."HFB_PA_EXT" failed to create with error:
ORA-06564: object TEMP does not exist
Failing sql is:
CREATE TABLE "STG"."HFB_PA_EXT" ("HFB_ID" NUMBER, "HFB_DESC" VARCHAR2(100 BYTE), "RA_ID" NUMBER, "RA_DESCR" VARCHAR2(100 BYTE), "PA_ID" NUMBER, "PA_DESCR" VARCHAR2(100 BYTE)) ORGANIZATION EXTERNAL ( TYPE ORACLE_LOADER DEFAULT DIRECTORY "TEMP" ACCESS PARAMETERS ( records delimited by newline
    skip 1
    fields terminated by ','
    missing field values are null
      ) LOCAT
ORA-39151: Table "GEOGRAPHY"."CAHC" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "ODS"."ZZ_ODS_ART_STOCK_T"                  26.81 GB 321434766 rows
imported "ODS"."ODS_PM_CODE_T":"SYS_P15548"          259.4 MB 3418214 rows (are the sys tables effected here)
Then the rows started importing ....
Share all the possible ways to avoid the above all errors in the imp log as it has to be shared with the client ,    Thanks for the swif response and help in advance.
Regards,
RanG

HI,
RanG wrote:
Hello All,
I am doing some exp/imp of schemas in a OBI environment and size around 300GB of each shema, after quiet a long time.., and not sure of the imp log errors whether to ignore or rerun my import with any changes or drop schemas and reimport ......
My IMP statement is
impdp system/********@OBIDEV schemas=ODS,DWH,STG,GEOGRAPHY directory=dumpdir dumpfile=BI2011_SCHEMAS.dmp logfile=impBI2011_SCHEMAS.log
Errors from the imp log :
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"GEOGRAPHY" already exists
ORA-31684: Object type USER:"DWH" already exists
ORA-31684: Object type USER:"STG" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
ORA-39083: Object type ROLE_GRANT failed to create with error:
ORA-01919: role 'ROLE_SRC' does not exist
Failing sql is:
GRANT "ROLE_SRC" TO "STG" WITH ADMIN OPTION
ORA-39083: Object type ROLE_GRANT failed to create with error:
ORA-01919: role 'ROLE_STG' does not exist
Failing sql is:
GRANT "ROLE_STG" TO "ODS" WITH ADMIN OPTION
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
a
--- and after some lines again the below errors, many failing sql's to created the tables ..
ORA-39083: Object type TABLE:"STG"."STG_ART_STOCK_OIG_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
Failing sql is:
CREATE TABLE "STG"."STG_ART_STOCK_OIG_XT" ("YEARWEEK" NUMBER, "ARTICLE_NUMBER" NUMBER, "BU_CODE" NUMBER, "ART_QTY_STOCK" NUMBER, "PM_CODE" VARCHAR2(10 BYTE)) ORGANIZATION EXTERNAL ( TYPE ORACLE_LOADER DEFAULT DIRECTORY "BI_SRC_FILES" ACCESS PARAMETERS ( RECORDS DELIMITED BY NEWLINE CHARACTERSET WE8MSWIN1252 STRING SIZES ARE IN BYTES BADFILE 'ART_STOCK_OIG.bad'
ORA-39083: Object type TABLE:"STG"."STG_ART_STOCK_INGKA_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
ORA-39083: Object type TABLE:"STG"."STG_ART_PMCODE_INGKA_XT" failed to create with error:
ORA-06564: object BI_SRC_FILES does not exist
Failing sql is:
CREATE TABLE "STG"."STG_IFPM_XT" ("YEAR" VARCHAR2(255 BYTE), "TERTIAL" VARCHAR2(255 BYTE), "YW" VARCHAR2(255 BYTE), "STORE_NAME" VARCHAR2(255 BYTE), "BUDGET" VARCHAR2(255 BYTE), "ACTUAL_SALES" VARCHAR2(255 BYTE), "CUSTOMERS" VARCHAR2(255 BYTE), "VISITORS" VARCHAR2(255 BYTE), "REST_SALES" VARCHAR2(255 BYTE), "EXIT_CAFE_SALES" VARCHAR2(255 BYTE), "SWE_FOOD_SALES" VARCHAR2
ORA-39083: Object type TABLE:"STG"."HFB_PA_EXT" failed to create with error:
ORA-06564: object TEMP does not exist
Failing sql is:
CREATE TABLE "STG"."HFB_PA_EXT" ("HFB_ID" NUMBER, "HFB_DESC" VARCHAR2(100 BYTE), "RA_ID" NUMBER, "RA_DESCR" VARCHAR2(100 BYTE), "PA_ID" NUMBER, "PA_DESCR" VARCHAR2(100 BYTE)) ORGANIZATION EXTERNAL ( TYPE ORACLE_LOADER DEFAULT DIRECTORY "TEMP" ACCESS PARAMETERS ( records delimited by newline
    skip 1
    fields terminated by ','
    missing field values are null
      ) LOCAT
ORA-39151: Table "GEOGRAPHY"."CAHC" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "ODS"."ZZ_ODS_ART_STOCK_T"                  26.81 GB 321434766 rows
imported "ODS"."ODS_PM_CODE_T":"SYS_P15548"          259.4 MB 3418214 rows (are the sys tables effected here)
Then the rows started importing ....
Share all the possible ways to avoid the above all errors in the imp log as it has to be shared with the client ,    Thanks for the swif response and help in advance.
Regards,
RanG
Because the table already exists. You can use the TABLE_EXISTS_ACTION option, so you can tell impdp what to do if the table it is trying to create already exists.
TABLE_EXISTS_ACTION={SKIP | APPEND | TRUNCATE | REPLACE}
impdp system/********@OBIDEV schemas=ODS,DWH,STG,GEOGRAPHY directory=dumpdir dumpfile=BI2011_SCHEMAS.dmp logfile=impBI2011_SCHEMAS.log table_exists_action=replace
Thank you

Expdp impdp fails from 10g to 11g db version

Hello folks,
Export DB Version : 10.2.0.4
Import DB Version : 11.2.0.1
Export Log File
Export: Release 10.2.0.4.0 - Production on Wednesday, 03 November, 2010 2:19:20
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, Data Mining and Real Application Testing options
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 45 GB
. . exported "DYM"."CYCLE_COUNT_MASTER" 39.14 GB 309618922 rows
Master table "DYM"."SYS_EXPORT_SCHEMA_01" successfully loaded/unloaded
Dump file set for DYM.SYS_EXPORT_SCHEMA_01 is:
Job "DYM"."SYS_EXPORT_SCHEMA_01" successfully completed at 02:56:49
Import Log File
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
ORA-31693: Table data object "DYM_PRJ4"."CYCLE_COUNT_MASTER" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEOPEN callout
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 1 error(s) at 10:54:38
from 10g expdp to 11g impdp is not allowed ? any thoughts appreciated ??

Nope , I do not see any error file.
Current log# 2 seq# 908 mem# 0:
Thu Nov 04 11:58:20 2010
DM00 started with pid=530, OS id=1659, job SYSTEM.SYS_IMPORT_FULL_02
Thu Nov 04 11:58:20 2010
DW00 started with pid=531, OS id=1661, wid=1, job SYSTEM.SYS_IMPORT_FULL_02
Thu Nov 04 11:58:55 2010
DM00 started with pid=513, OS id=1700, job SYSTEM.SYS_IMPORT_FULL_02
Thu Nov 04 11:58:55 2010
DW00 started with pid=520, OS id=1713, wid=1, job SYSTEM.SYS_IMPORT_FULL_02
Thu Nov 04 12:00:54 2010
Thread 1 cannot allocate new log, sequence 909
Private strand flush not complete
Current log# 2 seq# 908 mem# 0: ####################redo02.log
Thread 1 advanced to log sequence 909 (LGWR switch)
Current log# 3 seq# 909 mem# 0: ###################redo03.log
Thu Nov 04 12:01:51 2010
Thread 1 cannot allocate new log, sequence 910
Checkpoint not complete
Current log# 3 seq# 909 mem# 0:###################redo03.log

Expdp / impdp - Private synonyms using DB link not imported

Hi
I'd appreciate any help with this.
We are taking an export (expdp) of a database on Oracle EE 10.2.0.3 in Prod and then importing it into an identical DB on 10.2.0.5 in Dev.
I doubt the minor version difference is an issues, but I mention it for completeness.
Our expdp in prod used to look like this:
expdp agdba/x directory=DATA_PUMP_DIR dumpfile=X.DMP logfile=X.LOG schemas=A,B,C,D
We have changed it to:
expdp agdba/x directory=DATA_PUMP_DIR dumpfile=X.DMP logfile=X.LOG full=y EXCLUDE=SCHEMA:"IN ('E', 'F')"
( so basically do a full export, but exclude schemas E & F )
The impdp in dev has not changed (we import one schema at a time):
impdp agdba/x DUMPFILE=X.DMP LOGFILE=imp_X.LOG SCHEMAS=A DIRECTORY=DATA_PUMP_DIR TABLE_EXISTS_ACTION=SKIP
DB user AGDBA has been granted the DBA role...
The Issue:_
Private synonyms that use a DB link are NOT imported, but private synonyms that do NOT use a DB link ARE imported.
I can fix the issue by simply recreating the private synonyms using the DB link - e.g.:
CREATE SYNONYM EVENTLOGTBL FOR EVENTLOGTBL@FCISTOSMS;
Things were working fine until we change the expdp to use FULL. I see a few posts about synonyms and FULL=Y issues, but nothing quite like our problem.
Any ideas?
Thanks,
Andreas

Andreas Hess wrote:
So the problem is expdp FULL=Y for some reason does not export synonyms that refer to objects via DB links. I doubt that ... More than few times a week I refresh non-prod databases from a prod db, (it is schema level export not FULL=Y), and two of the schema own db links, and others have synonyms pointing to them. I have never encountered synonym problem (except that if db_links are invalid then impdp takes extremely long time to timeout while compiling pl/sql code.). We normally change db_links after the impdp is done, or (while it is importing table via another session).
I just re-ran sqlfile option with include=db_link,synonym option and i can see statements that create synonyms and create db links.
However i think the order in which impdp runs might be the source of your problem ... see this
Starting "ME"."SYS_SQL_FILE_SCHEMA_01": ME/******** dumpfile=xxxx.%u.dmp directory=xxxx_exp schemas=schema1,schema2,schema3 sqlfile=schema.sql include=db_link,synonym
Processing object type SCHEMA_EXPORT/SYNONYM/SYNONYM <<<< Synonyms are created first
Processing object type SCHEMA_EXPORT/DB_LINK <<<< db_links come later
Job "ME"."SYS_SQL_FILE_SCHEMA_01" successfully completed at 08:32:02So, it is conceivable that if you drop synonyms/db_links from your schemas before impdp, some synonyms will fail to create properly. This could be a version specific issue, mine is 11.2 and I don't see failures for synonym creation, i.e. no error messages while impdp. Next time you could try to drop objects except db_links and see if you still have the same issue.
Raj

EXPDP/IMPDP TIMESTAMP0

Hi All,
I encountered a strange problem when I was doing an export from a 10.2.0.3 on solaris to a 10.2.0.3 databsae on another solaris box.
expdp system dumpfile=db_20100617.dmp logfile=db_20100617.log directory=expdp full=y compression=metadata_only parallel=2 status=30
and this is my import statement
impdp system dumpfile=db_20100617.dmp logfile=db_20100617_imp.log directory=expdp full=y parallel=4
I've followed this process twice, and everytime on my destination database, all my columns with (source) data_type=TIMESTAMP(6) woudl be converted to data_type=TIMESTAMP(0) which causes a select that defines the column name (select column1 from tablea) to crash with a End-of-communication error.
Fortunately, the work around was to alter table modify column and set it to timestamp(6), but I was wondering if anyone else had seen this before. My log shows no errors with table creation, only issues package compilation and dblinks.
Has anyone seen this problem before or know how to bypass it?

Hi All,
Just to finish off this thread. I've put it through metalink and they havne't confirmed it as a bug. Their only resolution according to oracle support was to recreate the table manually. Because any table created using
create table ... as select *
also causes the issue during an export stage. Using the get_ddl function also produces the same error with timestamp(0).
Anyway all, thanks for your time.
Cheers.

Expdp/impdp error

Similar Messages

Maybe you are looking for