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)

OAM Server fatal error: OpCode = 22 [AuthenticateWAudit]

Nov 19, 2015 10:38PM edited Dec 9, 2015 10:25PM in Identity Management (MOSC) 10 commentsAnswered

Hi community,

I'm having a issue when applying changes from OAM Console:

When trying to make changes on oamconsole (in this particular case the IAMSuiteAgent), the following error messages are shown on logs:

<Nov 19, 2015 10:31:46 PM CLT> <Warning> <oracle.oam.agent-default> <OAMAGENT-00410> <OAM Server can not be accessed, fallback to container policy: OpCode = 22 [AuthenticateWAudit], Returned Status = Major code: 3(FatalError) Minor code: 2(NoCode) , extraInfo = [anonymous Authentication]>

<Nov 19, 2015 10:31:52 PM CLT> <Error> <oracle.oam.agent-default> <BEA-000000> <OAM Server fatal error: OpCode = 22 [AuthenticateWAudit], Returned Status = Major code: 3(FatalError) Minor code: 2(NoCode) , extraInfo = [anonymous Authentication]>

<Nov 19, 2015 10:31:52 PM CLT> <Error> <oracle.oam.agent-default> <OAMAGENT-00411> <Failed to access server: MajorCode: FATAL_ERROR, MinorCode: FATAL_ERROR>

Tagged:

Access Management

1

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