Grants worked for me
A reader, February 23, 2017 - 3:14 pm UTC
I was recently having a similar issue for an export that previously worked. Running the grant similar to this is what fixed my issue. Thanks!
grant create session, create table, create procedure, exp_full_database, imp_full_database to TESTE;
February 25, 2017 - 12:58 am UTC
Glad we could help
One more possible cause
Ralf Kölling, October 18, 2020 - 10:18 am UTC
Another cause for this error I found out today:
The behavior also comes up if the master table of your datapump export exists already (in my case because I shut down the virtual box with the database when the hourly export was just running ...). After I located the table with
SELECT o.status, o.object_id, o.object_type, o.owner||'.'||object_name
FROM dba_objects o, dba_datapump_jobs j
WHERE o.owner=j.owner_name
AND o.object_name=j.job_name;
and dropped it everything worked fine again (Thanks Job Oprel for the hint!!!)
October 19, 2020 - 2:32 am UTC
Thanks for stopping by and adding the information
additional advice
Nicole Pasikowski, April 30, 2021 - 5:36 pm UTC
This was helpful but did not entirely solve my issue. Here are two other items:
alter user teste quota unlimited on users; (or whatever tablespace is their default)
grant execute on dbms_metadata to teste; (necessary if it has been revoked from public)
Also from sqlplus with test account try:
1. creating a table
2. inserting into the table
3. try running expdp on the command line
This helped me flush out the problems I was having.
May 03, 2021 - 4:42 am UTC
Good input
Another potential issue..
SJW, February 03, 2022 - 9:44 pm UTC
..the user doesn't have privilege/quota on the default tablespace
February 04, 2022 - 5:22 am UTC
Ah yes - good point that I'd forgotten to mention.
dbms_datapump.set_debug
Patrick Jolliffe, July 18, 2022 - 11:48 am UTC
For anyone else that comes here via Google (as I did) and would like some idea of how to troubleshoot this error in a more logical way, I just discovered this function (not in official documentation, but exposed in package body).
Output information is exposed in sql trace file.
Below shows redacted trace for the issue I am working on...
DECLARE
L_HANDLE NUMBER;
BEGIN
DBMS_DATAPUMP.SET_DEBUG(on_off=>1);
L_HANDLE := DBMS_DATAPUMP.ATTACH('<redacted>','<redacted>') ;
END;
SHDW: *** ATTACH call ***
SHDW: job_name = <redacted>
SHDW: job_owner = <redacted>
SHDW: ena_sec_roles = NULL
SHDW: Trapped to shadow error handling routine
SHDW: Top-level error number reported = -31626
SHDW: Shadow context error supplied = 0
SHDW: Error stack at time of error report:
SHDW: ORA-31626: job does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.KUPV$FT", line 421
ORA-31638: cannot attach to job <redacted> for user <redacted>
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 414
ORA-31632: master table "<redacted>.,<redacted>" not found, invalid, or inaccessible
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 406
ORA-00942: table or view does not exist
ORA-06512: at "SYS.KUPV$FT_INT", line 2847
ORA-06512: at "SYS.KUPV$FT", line 210
SHDW: Backtrace stack:
SHDW: ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
ORA-06512: at "SYS.KUPV$FT", line 421
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 414
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 406
ORA-06512: at "SYS.KUPV$FT_INT", line 2847
ORA-06512: at "SYS.KUPV$FT", line 210
ORA-06512: at "SYS.DBMS_DATAPUMP", line 5315
SHDW: Call stack:
SHDW: ----- PL/SQL Call Stack -----
object line object
handle number name
0xec271c590 1840 package body SYS.DBMS_DATAPUMP.SHADOW_ERROR
0xec271c590 5327 package body SYS.DBMS_DATAPUMP.ATTACH
0xf419a1220 6 anonymous block
July 21, 2022 - 2:57 am UTC
thanks for dropping by Patrick
ORA-31626: job does not exist
vadim, March 12, 2024 - 9:00 pm UTC
ORA-31626: job does not exist
ORA-31633: unable to create master table "BLAH_BLAH.FOXTEST0226"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 1163
ORA-01950: no privileges on tablespace 'FOX_APP_DATA'
ORA-06512: at "SYS.KUPV$FT", line 1056
ORA-06512: at "SYS.KUPV$FT", line 1044
March 18, 2024 - 3:54 am UTC
um.... your question?