impdp errors

[PaulM]

I'm getting the following errors on a data pump import run as system.
I have run expdp and impdp before with no errors. The datafiles I'm
trying to read are between 7 and 17 Mb. How do I resolve these
errors?

ORA-31626: job does not exist
ORA-31676: cannot create job SYS_IMPORT_SCHEMA_O1 for user SYSTEM
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT_INT", line 600
ORA-39080: failed to create queues "" and "" dor Data Pump job
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPC$QUE_INT", line 1580
ORA-01403: no data found

Thanks,
Paul

[ddf]

Your error message text for the reported ORA-31676 error doesn't match
with what Oracle provides in the documentation:

31676, 00000, "illegal value for number of workers, %s"
// *Cause: Called create worker processes with an illegal number of
workers
// specified.
// *Action: Make sure that the number of workers value is greater than
0 and
// less than the maximum value for the platform (normally
32767). If
// this error occurs from a Data Pump client (e.g. expdp or
impdp)
// and you specified the parallel parameter, try the
operation again
// with a smaller value for the parallel parameter. If the
error
// occurs again, contact Oracle Customer Support and report
the error.

It DOES match with an ORA-31637, though:

31637, 00000, "cannot create job %s for user %s"
// *Cause: Unable to create or restart a job. Refer to any following
or
// prior error messages for clarification.
// *Action: Eliminate the problems indicated.

Without an Oracle version it's difficult to assess this situation and
provide an answer. It appears you typed in these messages from memory
-- please post the Oracle version and the exact error messages
reported by impdp using copy and paste. When this information is
available a possible solution can be offered.


David Fitzjarrell

[joel garry]

Probably install and/or configure advanced streams streams_pool_size,
if David's advice doesn't lead elsewhere. My guess is you have it on
the source and not on the target database. There are other patch-
level dependent possibilities, including invalid AQ objects and other
things interfering with AQ.

jg
--
@home.com is bogus.
http://www3.signonsandiego.com/stories/2009/may/05/1b5bizbrfs211519/?uniontrib