Datapump error in 10.2

Hi I have followed metalink Note:266875.1 to create directory but am getting the following error:
expdp system/password@database directory=datapump schemas=rnp dumpfile=rnp.dmp logfile=datapump_log:rnp.log
ORA-39006: internal error
ORA-39065: unexpected master process exception in DISPATCH
ORA-01403: no data found
ORA-39097: Data Pump job encountered unexpected error 100
PRIVILEGE DIRECTORY_NAME
ADMIN_DIR
READ DATAPUMP
WRITE DATAPUMP
READ DATAPUMP_LOG
WRITE DATAPUMP_LOG
READ DATA_PUMP_DIR
READ DATA_PUMP_DIR
WRITE DATA_PUMP_DIR
WRITE DATA_PUMP_DIR
SMM_DPUMP_DIR1
WORK_DIR
READ datapump
WRITE datapump
Any ideas/suggestions. Thanks

Hello,
Though its very hard to troubleshoot without log but using your details you provided here. I think in this case import is not able find schema references embedded within the body of definitions of indexes, views, procedures, functions and packages.
So using remap_schema won't prevent this issue as remapping will be done only on your source schema. And for this reason mapping may not be complete successfully, because there are certain schema references that Import is not capable of finding.
Here what you can do and find the culprit or exact issue
impdp system/password directory=TEST_DIR dumpfile=yourproduction.dmp remap_schema=x:x1 sqlfile=mynewimport.sql Then see you sql file for offending (index) statement and you can fix it and try to run it manaually.
Hope this helps.
Regards

Similar Messages

DATAPUMP ERROR ::::PLZ HELP ME

HI all,
every day, I generate an export DATAPUMP of my Oracle base; (Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 on Redhat Linux Server)
Suddenly, this morning I have a problem; my procedure of export does not works any more I have this oracle error:
Error codes -29283: ORA-29283: invalid file operation
ORA-06512: At “SYS.UTL_FILE”, line 475
ORA-29283: invalid file operation
ORA-31626: job does not exist
ORA-31626: job does not exist
Someone can help me please;
Thank you ;
Regards,
CREATE OR REPLACE PROCEDURE SP_DPUMP_EXPORT (
P_DIRECTORY_NAME IN VARCHAR2
AS
|| Procedure: here
||
|| Creates a nightly DataPump Export of all User schema
||
idx NUMBER; -- Loop index
JobHandle NUMBER; -- Data Pump job handle
PctComplete NUMBER; -- Percentage of job complete
JobState VARCHAR2(30); -- To keep track of job state
LogEntry ku$_LogEntry; -- For WIP and error messages
JobStatus ku$_JobStatus; -- The job status from get_status
Status ku$_Status; -- The status object returned by get_status
BEGIN
-- Build a handle for the export job
JobHandle :=
DBMS_DATAPUMP.OPEN(
operation => 'EXPORT'
,job_mode => 'FULL'
,remote_link => NULL
,job_name => 'DEVXEN03_'||'OBJECTS'
,version => 'LATEST'
-- Using the job handle value obtained, specify multiple dump files for the job
-- and the directory to which the dump files should be written. Note that the
-- directory object must already exist and the user account running the job must
-- have WRITE access permissions to the directory
DBMS_DATAPUMP.ADD_FILE(
handle => JobHandle
,filename => 'DEVXEN03_'||TO_CHAR(SYSDATE-1,'YYYYMMDD')||'.dmp'
,directory => P_DIRECTORY_NAME
,filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE
/* ,filesize => '100M'*/
DBMS_DATAPUMP.ADD_FILE(
handle => JobHandle
,filename => 'DEVXEN03_'||TO_CHAR(SYSDATE-1,'YYYYMMDD')||'.log'
,directory => P_DIRECTORY_NAME
,filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE
-- Apply a metadata filter to restrict the DataPump Export job to only return
-- selected tables and their dependent objects from the Miva schema
/*DBMS_DATAPUMP.METADATA_FILTER(
handle => JobHandle
,NAME => 'SCHEMA_EXPR'
,VALUE => '= ''ALL'''
\* ,object_type => 'TABLE'*\
-- Initiate the DataPump Export job
DBMS_DATAPUMP.START_JOB(JobHandle);
-- If no exception has been returned when the job was initiated, this loop will
-- keep track of the job and return progress information until the job is done
PctComplete := 0;
JobState := 'UNDEFINED';
WHILE(JobState != 'COMPLETED') and (JobState != 'STOPPED')
LOOP
DBMS_DATAPUMP.GET_STATUS(
handle => JobHandle
,mask => 15 -- DBMS_DATAPUMP.ku$_status_job_error + DBMS_DATAPUMP.ku$_status_job_status + DBMS_DATAPUMP.ku$_status_wip
,timeout => NULL
,job_state => JobState
,status => Status
JobStatus := Status.job_status;
-- Whenever the PctComplete value has changed, display it
IF JobStatus.percent_done != PctComplete THEN
DBMS_OUTPUT.PUT_LINE('*** Job percent done = ' || TO_CHAR(JobStatus.percent_done));
PctComplete := JobStatus.percent_done;
END IF;
-- Whenever a work-in progress message or error message arises, display it
IF (BITAND(Status.mask,DBMS_DATAPUMP.ku$_status_wip) != 0) THEN
LogEntry := Status.wip;
ELSE
IF (BITAND(Status.mask,DBMS_DATAPUMP.ku$_status_job_error) != 0) THEN
LogEntry := Status.error;
ELSE
LogEntry := NULL;
END IF;
END IF;
IF LogEntry IS NOT NULL THEN
idx := LogEntry.FIRST;
WHILE idx IS NOT NULL
LOOP
DBMS_OUTPUT.PUT_LINE(LogEntry(idx).LogText);
idx := LogEntry.NEXT(idx);
END LOOP;
END IF;
END LOOP;
-- Successful DataPump Export job completion, so detach from the job
DBMS_OUTPUT.PUT_LINE('Job has succesfully completed');
DBMS_OUTPUT.PUT_LINE('Final job state = ' || JobState);
DBMS_DATAPUMP.DETACH(JobHandle);
EXCEPTION
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE('ERROR DATA PUMP EXPORT : '||SQLERRM);
END SP_DPUMP_EXPORT;
Message was edited by:
HAGGAR

in your sql prompt logged as a sysdba
--define variable
var JobHandle
execute each step as in your procedure and check at what location you get an error.
1)
JobHandle :=
DBMS_DATAPUMP.OPEN(
operation => 'EXPORT'
,job_mode => 'FULL'
,remote_link => NULL
,job_name => 'DEVXEN03_'||'OBJECTS'
,version => 'LATEST'
-- Using the job handle value obtained, specify multiple dump files for the job
-- and the directory to which the dump files should be written. Note that the
-- directory object must already exist and the user account running the job must
-- have WRITE access permissions to the directory
2)
DBMS_DATAPUMP.ADD_FILE(
handle => JobHandle
,filename => 'DEVXEN03_'||TO_CHAR(SYSDATE-1,'YYYYMMDD')||'.dmp'
,directory => P_DIRECTORY_NAME
,filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE
/* ,filesize => '100M'*/
3)
DBMS_DATAPUMP.ADD_FILE(
handle => JobHandle
,filename => 'DEVXEN03_'||TO_CHAR(SYSDATE-1,'YYYYMMDD')||'.log'
,directory => P_DIRECTORY_NAME
,filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE
-- Initiate the DataPump Export job
4)
DBMS_DATAPUMP.START_JOB(JobHandle);
execute it manually or try to include exception handling for each statements in the procedure. to know exactly where the error occurs.
SS

Datapump error

We are running Oracle 10.2.0.4 on RHEL 5.2 64bit (kernel is 2.6.18-92). We have a Windows share mounted on the machine using the cifs filesystem type. Data punp reports the following error:
Export: Release 10.2.0.4.0 - 64bit Production on Wednesday, 04 February, 2009 9:26:07
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-39097: Data Pump job encountered unexpected error -31643
ORA-39065: unexpected master process exception in FILE
ORA-31643: unable to close dump file "/mount/windows/BI_DP_QA421/amir_t1.dmp"
ORA-19510: failed to set size of 1 blocks for file "/mount/windows/BI_DP_QA421/amir_t1.dmp" (blocksize=4096)
ORA-27045: unable to close the file
Linux-x86_64 Error: 5: Input/output error
Additional information: 4
The same process runs successfully in RHEL 4 U7.
Any ideas how to fix this?
Thanks

The answer is yes to all the questions. The folder exists, it is writable, mounted. I also created files, deleted files and copied files between the Linux and the share.
The problem started when we tried the data pump on RHEL 5.2. All was fine when it runs on a RHEL 4U7. From my research, smbfs was dropped from the 2.6 kernel and cifs was the replacment. On RHEL4 the share is mounted as smbfs and data pump have no problems. On RHEL 5 u 2 it is mounted as cifs - and the erros occure.

Recreating database where repository is located

Do to the way a database was migrated from one server to another i need to recreate a database to remove internal references to the old server. this database contains the owb repository. i am planning to take a full export, drop the database, recreate the database and do an import.
is anyone aware of any issues with this? ...i.e. dbid stored somewhere in the repository?

well...things didn't go as planned.
datapump errored out when i did a full export with the following:
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [PROCOBJ:"STRAIN"."STRAIN_OPT_INDEX_JOB"]
ORA-22813: operand value exceeds system limits
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 6241
----- PL/SQL Call Stack -----
object line object
handle number name
0x17adf6b50 14916 package body SYS.KUPW$WORKER
0x17adf6b50 6300 package body SYS.KUPW$WORKER
0x17adf6b50 2340 package body SYS.KUPW$WORKER
0x17adf6b50 6861 package body SYS.KUPW$WORKER
0x17adf6b50 1262 package body SYS.KUPW$WORKER
0x17adab5f0 2 anonymous block
Job "SYSTEM"."WATCH" stopped due to fatal error at 16:46:50
...i've got a tar open on this but can't proceed without a full export!
let me know how your attempt goes.
thanks.

Error while taking dump using datapump

getting following error -
Export: Release 10.2.0.1.0 - Production on Friday, 15 September, 2006 10:31:41
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Starting "XX"."SYS_EXPORT_SCHEMA_02": XX/********@XXX directory=dpdump dumpfile=XXX150906.dmp logfile=XXX150906.log
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_METADATA.FETCH_XML_CLOB []
ORA-31642: the following SQL statement fails:
BEGIN "DMSYS"."DBMS_DM_MODEL_EXP".SCHEMA_CALLOUT(:1,0,0,'10.02.00.01.00'); END;
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA", line 907
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DMSYS.DBMS_DM_MODEL_EXP' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6235
----- PL/SQL Call Stack -----
object line object
handle number name
2A68E610 14916 package body SYS.KUPW$WORKER
2A68E610 6300 package body SYS.KUPW$WORKER
2A68E610 9120 package body SYS.KUPW$WORKER
2A68E610 1880 package body SYS.KUPW$WORKER
2A68E610 6861 package body SYS.KUPW$WORKER
2A68E610 1262 package body SYS.KUPW$WORKER
255541A8 2 anonymous block
Job "XX"."SYS_EXPORT_SCHEMA_02" stopped due to fatal error at 10:33:12
Action required is contact customer support. And on metalink found a link that states it a bug in 10g release 1 that was suppose to be fixed in 10g release 1 version 4.
some of the default schemas were purposely dropped from the database. The only default schema available now are -
DBSNMP, DIP, OUTLN, PUBLIC, SCOTT, SYS, SYSMAN, SYSTEM, TSMSYS.
DIP, OUTLN, TSMSYS were created again.
Could this be a cause of problem??
Thanks in adv.

Hi,
Below is the DDL taken from different database. Will this be enough ? One more thing please, what shall be the password should it be DMSYS.....since this will not be used by me but system.
CREATE USER "DMSYS" PROFILE "DEFAULT" IDENTIFIED BY "*******" PASSWORD EXPIRE DEFAULT TABLESPACE "SYSAUX" TEMPORARY TABLESPACE "TEMP" QUOTA 204800 K ON "SYSAUX" ACCOUNT LOCK
GRANT ALTER SESSION TO "DMSYS"
GRANT ALTER SYSTEM TO "DMSYS"
GRANT CREATE JOB TO "DMSYS"
GRANT CREATE LIBRARY TO "DMSYS"
GRANT CREATE PROCEDURE TO "DMSYS"
GRANT CREATE PUBLIC SYNONYM TO "DMSYS"
GRANT CREATE SEQUENCE TO "DMSYS"
GRANT CREATE SESSION TO "DMSYS"
GRANT CREATE SYNONYM TO "DMSYS"
GRANT CREATE TABLE TO "DMSYS"
GRANT CREATE TRIGGER TO "DMSYS"
GRANT CREATE TYPE TO "DMSYS"
GRANT CREATE VIEW TO "DMSYS"
GRANT DROP PUBLIC SYNONYM TO "DMSYS"
GRANT QUERY REWRITE TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_JOBS_RUNNING" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_REGISTRY" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_SYS_PRIVS" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_TAB_PRIVS" TO "DMSYS"
GRANT SELECT ON "SYS"."DBA_TEMP_FILES" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_LOCK" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_REGISTRY" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_SYSTEM" TO "DMSYS"
GRANT EXECUTE ON "SYS"."DBMS_SYS_ERROR" TO "DMSYS"
GRANT DELETE ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT INSERT ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT SELECT ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT UPDATE ON "SYS"."EXPDEPACT$" TO "DMSYS"
GRANT SELECT ON "SYS"."V_$PARAMETER" TO "DMSYS"
GRANT SELECT ON "SYS"."V_$SESSION" TO "DMSYS"
The other database has the DMSYS and the status is EXPIRED & LOCKED but I'm still able to take the dump using datapump??

Getting error while importing datapump through attach keyword.

Hi All,
I am giving job_name for export :
expdp scott/tiger dumpfile=scott.dmp logfile=scott.log job_name=ashwin directory=datapump
Export: Release 10.2.0.1.0 - Production on Wednesday, 23 February, 2011 14:41:58
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Starting "SCOTT"."ASHWIN": scott/******** dumpfile=scott.dmp logfile=scott.log job_name=ashwin directory
=datapump
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 384 KB
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TABLE/TABLE
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/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
. . exported "SCOTT"."PLAN_TABLE" 17.03 KB 3 rows
. . exported "SCOTT"."DEPT" 5.656 KB 4 rows
. . exported "SCOTT"."DEPT1" 5.656 KB 4 rows
. . exported "SCOTT"."EMP" 7.820 KB 14 rows
. . exported "SCOTT"."SALGRADE" 5.585 KB 5 rows
. . exported "SCOTT"."BONUS" 0 KB 0 rows
Master table "SCOTT"."ASHWIN" successfully loaded/unloaded
Dump file set for SCOTT.ASHWIN is:
D:\ORACLE\DATAPUMP\SCOTT.DMP
Job "SCOTT"."ASHWIN" successfully completed at 14:42:10
So my job name here is ashwin
but when I am trying to import through this job I am getting following error
impdp scott/tiger attach=ashwin
Import: Release 10.2.0.1.0 - Production on Wednesday, 23 February, 2011 14:51:16
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORA-31626: job does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.KUPV$FT", line 430
ORA-31638: cannot attach to job ASHWIN for user SCOTT
ORA-31632: master table "SCOTT.ASHWIN" not found, invalid, or inaccessible
ORA-00942: table or view does not exist
I am not able to find out my fault... please help me in this regard.. Thanks...

user7280060 wrote:
Hi All,
I am giving job_name for export :
expdp scott/tiger dumpfile=scott.dmp logfile=scott.log job_name=ashwin directory=datapump
Export: Release 10.2.0.1.0 - Production on Wednesday, 23 February, 2011 14:41:58
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Starting "SCOTT"."ASHWIN": scott/******** dumpfile=scott.dmp logfile=scott.log job_name=ashwin directory
=datapump
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 384 KB
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/TABLE/TABLE
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/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
. . exported "SCOTT"."PLAN_TABLE" 17.03 KB 3 rows
. . exported "SCOTT"."DEPT" 5.656 KB 4 rows
. . exported "SCOTT"."DEPT1" 5.656 KB 4 rows
. . exported "SCOTT"."EMP" 7.820 KB 14 rows
. . exported "SCOTT"."SALGRADE" 5.585 KB 5 rows
. . exported "SCOTT"."BONUS" 0 KB 0 rows
Master table "SCOTT"."ASHWIN" successfully loaded/unloaded
Dump file set for SCOTT.ASHWIN is:
D:\ORACLE\DATAPUMP\SCOTT.DMP
Job "SCOTT"."ASHWIN" successfully completed at 14:42:10
So my job name here is ashwin
but when I am trying to import through this job I am getting following error
impdp scott/tiger attach=ashwin
Import: Release 10.2.0.1.0 - Production on Wednesday, 23 February, 2011 14:51:16
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORA-31626: job does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.KUPV$FT", line 430
ORA-31638: cannot attach to job ASHWIN for user SCOTT
ORA-31632: master table "SCOTT.ASHWIN" not found, invalid, or inaccessible
ORA-00942: table or view does not exist
I am not able to find out my fault... please help me in this regard.. Thanks...When you run the data pump, in the session of yours, Oracle creates a master table. This table is available only the time till the job is not over and after that , it's also dumped into the dump file. What you have done is, you have got the job completed and this has caused the job table to be dropped. Later on when you are trying to attach to it, it's not happening since the table is not there. So what you should do, if you want to test it out, create a job that would tak esome time to finish. Kill the job or suspend the job and then later, try to reattach to it. See in your schema, what's the job table name that is created and use it.
HTH
Aman....

Error while export using DATAPUMP

hi ,
When i try to export the database using DataPump I am getting the following error.
Details :
DB version : 10.2.0.2
OS : (HP-Unix)
error :
dbsrv:/u02/oradata2> 6 dumpfile=uatdb_preEOD28_jul.dmp logfile=uatdb_preEOD28jul.log directory=expdp_new <
Export: Release 10.2.0.1.0 - 64bit Production on Sunday, 27 July, 2008 10:00:38
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
Starting "OCEANFNC"."JOB6": userid=oceanfnc/********@uatdb content=ALL full=Y job_name=job6 dumpfile=uatdb_preEOD28_jul.dmp logfile=uatdb_preEOD28jul.log directory=expdp_new
Estimate in progress using BLOCKS method...
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_METADATA.FETCH_XML_CLOB []
ORA-31642: the following SQL statement fails:
BEGIN "DMSYS"."DBMS_DM_MODEL_EXP".SCHEMA_CALLOUT(:1,0,1,'10.02.00.01.00'); END;
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA", line 907
ORA-04067: not executed, package body "DMSYS.DBMS_DM_MODEL_EXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "DMSYS.DBMS_DM_MODEL_EXP"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6235
----- PL/SQL Call Stack -----
object line object
handle number name
c0000002ae4f0a60 14916 package body SYS.KUPW$WORKER
c0000002ae4f0a60 6300 package body SYS.KUPW$WORKER
c0000002ae4f0a60 9120 package body SYS.KUPW$WORKER
c0000002ae4f0a60 1880 package body SYS.KUPW$WORKER
c0000002ae4f0a60 6861 package body SYS.KUPW$WORKER
c0000002ae4f0a60 1262 package body SYS.KUPW$WORKER
c000000264e48dc0 2 anonymous block
Job "OCEANFNC"."JOB6" stopped due to fatal error at 10:00:41
Kindly advice me reg this!
Thanks

hi,
we got a metalink note for this problem and the metalink id is "Note Id: 433022.1 " . Even after running the Mentioned catalog.sql and catproc.sql, in our DB, we are facing some problems. The error description :
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.system_info_exp(0,dynconnect,10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5327
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.system_info_exp(1,dynconnect,10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5327
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/POST_SYSTEM_ACTIONS/PROCACT_SYSTEM
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('SYS',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('SYSTEM',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('OUTLN',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('TSMSYS',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('ANONYMOUS',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('OLAPSYS',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('SYSMAN',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('MDDATA',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('UATFNC',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('MGMT_VIEW',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('SCOTT',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('BRNSMS',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('FLEXML',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('FLEXBO',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('BRN000',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('FLEXRPT',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('BRN800',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('BRN900',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
ORA-39127: unexpected error from call to export_string :=EXFSYS.DBMS_EXPFIL_DEPASEXP.schema_info_exp('OCEANFNC',0,1,'10.02.00.01.00',newblock)
ORA-04067: not executed, package body "EXFSYS.DBMS_EXPFIL_DEPASEXP" does not exist
ORA-06508: PL/SQL: could not find program unit being called: "EXFSYS.DBMS_EXPFIL_DEPASEXP"
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_METADATA", line 5412
Kindly advice me regarding this !!
Thanks a lot for ur reply !!

Error in import table data using oracle datapump

i am trying to import table data using oracle datapump
CREATE TABLE emp_xt (
ID NUMBER,
NAME VARCHAR2(30)
ORGANIZATION EXTERNAL (
TYPE ORACLE_DATAPUMP
DEFAULT DIRECTORY backup
LOCATION ('a.dmp')
it return the following error
ORA-29913: error in executing ODCIEXTTABLEOPEN callout
ORA-29400: data cartridge error
KUP-04084: The ORACLE_DATAPUMP access driver does not support the ROWID column.
ORA-06512: at "SYS.ORACLE_DATAPUMP", line 19
please help me

.dmp file generated from exp command file not from oracle_datapump

ORACLE 10g : Datapump-Import : Error: unknown parameter name 'REMAP_TABLE'

Hi,
I am working on Oracle 10g. When executed import datapump script in the UNIX box with option “RMAP_TABLE” I received the error “unknown parameter name 'REMAP_TABLE' “Can you please give me solution for it?
Scripts :-
impdp eimsexp/xyz TABLES=EIMDBO.DIVISION DIRECTORY=DATAMART_DATA_PUMP_DIR DUMPFILE=expdp_DATAMART_tables_%u_$BATCH_ID.dmp LOGFILE=impdp_DATAMART_tables.log REMAP_TABLE=EIMDBO.DIVISION:EIM2DBO:YR2009_DIM_DIVISION
Note :- The YR2009_DIM_DIVISION table is available in the target database. It is without partition table. The EIMDBO.DIVISION is partition table.
Thanks,

See your post here
ORACLE 10g : Datapump-Import : Error: unknown parameter name 'REMAP_TABLE'
Srini

Error while importing schemas using datapump

Hi,
I am trying to import schema from qc to development. after importing i got the following error attached below:
Processing object type SCHEMA_EXPORT/TABLE/GRANT/WITH_GRANT_OPTION/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/GRANT/CROSS_SCHEMA/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
ORA-39065: unexpected master process exception in RECEIVE
ORA-39078: unable to dequeue message for agent MCP from queue "KUPC$C_2_20090421161917"
Job "SYS"."uat.210409" stopped due to fatal error at 20:15:13
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 2 with process name "DW02" prematurely terminated
ORA-31671: Worker process DW02 had an unhandled exception.
ORA-39078: unable to dequeue message for agent KUPC$A_2_20090421161934 from queue "KUPC$C_2_20090421161917"
ORA-06512: at "SYS.KUPW$WORKER", line 1397
ORA-06512: at line 2
ORA-39029: worker 3 with process name "DW03" prematurely terminated
ORA-31671: Worker process DW03 had an unhandled exception.
ORA-39078: unable to dequeue message for agent KUPC$A_2_20090421162030 from queue "KUPC$C_2_20090421161917"
ORA-06512: at "SYS.KUPW$WORKER", line 1397
ORA-06512: at line 2
ORA-39029: worker 4 with process name "DW04" prematurely terminated
ORA-31671: Worker process DW04 had an unhandled exception.
ORA-39078: unable to dequeue message for agent KUPC$A_2_20090421162031 from queue "KUPC$C_2_20090421161917"
ORA-06512: at "SYS.KUPW$WORKER", line 1397
ORA-06512: at line 2
Is my import completed successfully or not??. please help...

When a datapump job runs, it creates a table called the master table. It has the same name as the job name. This is used to keep track of where all of the information in the dumpfile is located. It is also used when restarting a job. For some reason, this table got dropped. I'm not sure why, but in most cases, datapump jobs are restartable. I don't know why the original message was reported, but I was hoping the job woudl be restartable. You could always just rerun the job. Since the job that failed already created tables and indexes, if you restart the job, all of the objects that are dependent on those objects will not be created by default.
Let's say you have table tab1 with an index ind1 and both table and index are anaylized. Since tab1 is already created, the datapump job will mark all of the objects dependent on tab1 to skip. This includes the index, table_statistics, and index_statistics. To get around this, you could say
table_exists_action=replace
but this will replace all tables that are in the dumpfile. Your other options are:
table_exists_action=
truncate -- to truncate the data in the table and then just reload the data, but not the dependent objects
append -- to append the data from the dumpfile to the existing table, but do not import the dependent objects
skip -- skip the data and dependent objects from the dumpfile.
Hope this helps.
Dean

Reg : Datapump export failing with ORA-31633 error

Hi,
I am trying to export one of the production databases (10.2.0.4.0) using datapump - backup is failing with the following error.
[UBASE2]:/backup/exports/scripts>more /backup/exports/cron/cron_UBASE_log
Export Start
Sat Oct 10 10:32:00 GMT 2009
Export: Release 10.2.0.4.0 - 64bit Production on Saturday, 10 October, 2009 10:32:00
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-31626: job does not exist
ORA-31633: unable to create master table "SYSTEM.FULL_UBASE"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 871
ORA-00955: name is already used by an existing object
Export End
Sat Oct 10 10:32:01 GMT 2009
I tried to attach to the existing job to kill that, but i am getting the below error -
[UBASE2]:/backup/exports/scripts>expdp attach=FULL_UBASE
Export: Release 10.2.0.4.0 - 64bit Production on Saturday, 10 October, 2009 14:31:46
Copyright (c) 2003, 2007, Oracle. All rights reserved.
Username: / as sysdba
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-31626: job does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.KUPV$FT", line 438
ORA-31638: cannot attach to job FULL_UBASE for user SYS
ORA-31632: master table "SYS.FULL_UBASE" not found, invalid, or inaccessible
ORA-00942: table or view does not exist
As this is critical production database please help me how to resolve this.
Thanks in Advance.
Raju A
Oracle DBA.

Hi,
Have you verified if your DBMS_AQ environment has been corrupted? If so, then you'll have to drop and recreate a number of queue related objects all over again. Furthermore, ORA-00942 appears to be the main problem as it is a case sensitivity error. You should change the table names to UPPERCASE and then try again.
Hope this helps.
Regards,
Naveed.

Datapump import error on 2 partioned tables

I am trying to run impdp to import two tables that are partioned and use the LOB types...for some reason it always errors out. Anyone seen this issue in 11g?
Here is the info:
$ impdp parfile=elm_rt.par
Master table "ELM"."SYS_IMPORT_TABLE_05" successfully loaded/unloaded
Starting "ELM"."SYS_IMPORT_TABLE_05": elm/******** parfile=elm_rt.par
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/INDEX
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/AUDIT_OBJ
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31671: Worker process DW01 had an unhandled exception.
ORA-04030: out of process memory when trying to allocate 120048 bytes (session heap,kuxLpxAlloc)
ORA-06512: at "SYS.KUPW$WORKER", line 1602
ORA-06512: at line 2
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 2 with process name "DW01" prematurely terminated
ORA-31671: Worker process DW01 had an unhandled exception.
ORA-04030: out of process memory when trying to allocate 120048 bytes (session heap,kuxLpxAlloc)
ORA-06512: at "SYS.KUPW$WORKER", line 1602
ORA-06512: at line 2
Job "ELM"."SYS_IMPORT_TABLE_05" stopped due to fatal error at 13:11:04
elm_rt.par_
$ vi elm_rt.par
"elm_rt.par" 25 lines, 1340 characters
DIRECTORY=DP_REGRESSION_DATA_01
DUMPFILE=ELM_MD1.dmp,ELM_MD2.dmp,ELM_MD3.dmp,ELM_MD4.dmp
LOGFILE=DP_REGRESSION_LOG_01:ELM_RT.log
DATA_OPTIONS=SKIP_CONSTRAINT_ERRORS
CONTENT=METADATA_ONLY
TABLES=RT_AUDIT_IN_HIST,RT_AUDIT_OUT_HIST
REMAP_TABLESPACE=RT_AUDIT_IN_HIST_DAT01:RB_AUDIT_IN_HIST_DAT01
REMAP_TABLESPACE=RT_AUDIT_IN_HIST_IDX04:RB_AUDIT_IN_HIST_IDX01
REMAP_TABLESPACE=RT_AUDIT_OUT_HIST_DAT01:RB_AUDIT_OUT_HIST_DAT01
PARALLEL=4

Read this metalink note 286496.1. (Export/Import DataPump Parameter TRACE - How to Diagnose Oracle Data Pump)
This will help you generate trace for the datapump job.

Trigger Compilation Errors after Full Import with Datapump

Hello All,
We did a full import with Oracle Datapump, and encountered some errors related to triggers:
ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT_RESET" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT_RESET" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CUBCNVT_AUDIT" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT_RESET" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT_RESET" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT" created with compilation warnings
ORA-39082: Object type TRIGGER:"CONVERT3"."CURCNVT_AUDIT" created with compilation warningsWe are wondering if there is some bug with the datapump on oracle 10.2.0.2. What caused such errors and how to resolve this trigger issue?
Thanks!

Hello,
Show errors / at the end of the trigger and see if any of the dependent objects is missing resulting in error at compilation.
Also you can try manually fixing the issue
CREATE OR REPLACE TRIGGER table1_trg
   AFTER INSERT
   ON TABLE1    REFERENCING NEW AS new OLD AS old
   FOR EACH ROW
DECLARE
   tmpvar   NUMBER;
BEGIN
Trigger code
EXCEPTION
   WHEN OTHERS
   THEN
      -- Consider logging the error and then re-raise
      RAISE;
END table1_trg;
SHOW ERRORS;Regards

ORA-39070 Error when using datapump and writing to ASM storage

I am able to export data using datapump when i write to a file system. However, when i try to write to an ASM storage, i get the following errors.
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation
below are the steps i tooks.
create or replace directory jp_dir2 as '+DATA/DEV01/exp_dir';
grant read,write on directory jp_dir2 to jpark;
expdp username/password schemas=testdirectory=jp_dir2 dumpfile=test.dmp log=test.log
Edited by: user564785 on Aug 25, 2011 6:49 AM

google: expdp ASM
first hit:
http://asanga-pradeep.blogspot.com/2010/08/expdp-and-impdp-with-asm.html
"Log files created during expdp cannot be stored inside ASM, for log files a directory object that uses OS file system location must be given. If not following error will be thrown
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation
"

Check for import errors programmatically using datapump api

Hi,
I have pl/sql that imports some tables over DBLink using dbms_datapump. Is there a way to programmatically check that the import job had no errors at all, before proceeding to the next step after the import is completed?
I saw several samples for showing the progress of the import job using while loops and whether it completed or not.
But none explaining how to check whether any of the import steps failed, or if all steps completed successfully.
Thanks,
JGP

check this
[Datapump Demos|http://www.morganslibrary.org/reference/dbms_datapump.html]

Datapump error in 10.2

Similar Messages

Maybe you are looking for