Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Identity Management (MOSC)

Getting error in OIM logs -<DU Retry Failed Job - Kernel Error - Orchestration process is not in fa

Jul 28, 2015 10:23AM edited Aug 10, 2015 2:27PM in Identity Management (MOSC) 1 commentAnswered

Hi OIM gurus,

I am seeing this error in logs in OIM 11gR2 PS2 when a user logs into the OIM system.

<Jul 27, 2015 3:56:58 PM EDT> <Error> <oracle.iam.custom.scheduletask> <BEA-000000> <DU Retry Failed Job - Kernel Error - Orchestration process is not in failed status to handle the failures - 16,707>

<Jul 27, 2015 3:57:04 PM EDT> <Error> <oracle.iam.custom.scheduletask> <BEA-000000> <DU Retry Failed Job - Kernel Error - Orchestration process is not in failed status to handle the failures - 16,939>

<Jul 27, 2015 3:57:09 PM EDT> <Error> <oracle.iam.custom.scheduletask> <BEA-000000> <DU Retry Failed Job - Kernel Error - Orchestration process is not in failed status to handle the failures - 16,761>

Tagged:

Identity Manager

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month