Oracle Fusion Middleware Error Messages Reference, 11g Release 2 (11.1.2.0.0)

11g Release 2 (11.1.2.0.0)

E35988-01

Contents

Title and Copyright Information

Preface

- Audience

- Documentation Accessibility

- Conventions

1 FED-10104 to FED-18084

2 FEDSTS-10102 to FEDSTS-20100

3 IDAAS-00001 to IDAAS-63011

4 OAAM-00000 to OAAM-94100

5 OAM-00001 to OAM-36105

6 OAMSSA-00001 to OAMSSA-22030

7 STS-10506 to STS-15541

Oracle® Fusion Middleware

Error Messages Reference

11g Release 2 (11.1.2.0.0)

E35988-01

July 2012

Oracle Fusion Middleware Error Messages Reference, 11g Release 2 (11.1.2.0.0)

E35988-01

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Preface

This manual provides information about the error messages you may encounter when installing and using Oracle Fusion Middleware components. It augments the message texts by providing additional cause and action information. For more information on error messages in Oracle Application Server, browse the documentation on the Oracle Technology Network (OTN) at http://www.oracle.com/technology/products/ias/index.html.

Audience

This manual is intended for anyone who uses Oracle Fusion Middleware and requires more information about an error message encountered in the product.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 FED-10104 to FED-18084

FED-10104: A name identifier update using protocol version {0} cannot be performed on a federation created with protocol version {1}

Cause: Unable to perform a name identifier update with the current version.

Action: Try using a different protocol version.
Level: 1

Type: ERROR

Impact: Configuration

FED-10105: Attribute Service location not found in provider metadata for {0}

Cause: Attribute service location was not in the provider metadata.

Action: Verify that the provider metadata contains the attribute service location.
Level: 1

Type: ERROR

Impact: Configuration

FED-10106: AssertionID service location not found in provider metadata for {0}

Cause: AssertionID service location was not in the provider metadata.

Action: Verify that the provider metadata contains the AssertionID service location.
Level: 1

Type: ERROR

Impact: Configuration

FED-10108: Cannot create federation with opaque name identifier: invalid data store

Cause: An opaque name identifier was used without a federation data store.

Action: Use a federation data store when an opaque identifier is used or configure Oracle Identity Federation to use a non-opaque Name ID.
Level: 1

Type: ERROR

Impact: Configuration

FED-10109: The nameid user store attribute has not been set for partner {0}.

Cause: Assertion to user record via NameId is enabled but no user attribute was specified.

Action: Specify a userstore attribute to which the name identifier value should be mapped.
Level: 1

Type: ERROR

Impact: Configuration

FED-10110: Cannot find service provider metadata for Affiliation={0};affiliationID type={1}

Cause: The federation did not contain a service provider that is part of the affiliation.

Action: Import the metadata of a service provider that is a member of the affiliation.
Level: 1

Type: ERROR

Impact: Configuration

FED-10111: Cannot find provider metadata for providerID={0}; providerID type={1}

Cause: There was no metadata available for the provider with the given ID.

Action: Verify that the provider ID is correct or that the provider is included in the federation.
Level: 1

Type: ERROR

Impact: Configuration

FED-10112: No default identity provider was set for the single sign-on operation.

Cause: The default single sign-on identity provider configuration property was not set.

Action: Set the default single sign-on identity provider in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Configuration

FED-10113: Federation termination protocol not enabled

Cause: The federation termination protocol was not enabled.

Action: Verify that the federation termination protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10114: NameIDPolicy not supported: {0}

Cause: The NameIDPolicy requested is not supported or not enabled.

Action: Check that the requested name identifier format is supported and enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10115: Cannot find the AssertionConsumerServiceURL in the requester metadata.

Cause: Could not find the AssertionConsumerServiceURL in the requester's provider metadata.

Action: Verify that the AssertionConsumerServiceURL is present in the provider metadata.
Level: 1

Type: ERROR

Impact: Configuration

FED-10117: Provider is not enabled: {0}

Cause: The peer provider is not enabled in the federation.

Action: Verify that the provider is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10118: Single sign-on binding unknown: {0}

Cause: The single sign-on binding is not one of the known bindings.

Action: Verify that the single sign-on binding is one of the bindings known by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Configuration

FED-10119: The specified binding ({0}) for single sign-on with {1} is not supported by the peer provider.

Cause: The binding specified is not one of the bindings supported by the peer provider.

Action: Verify that the binding specified is supported by the peer provider.
Level: 1

Type: ERROR

Impact: Configuration

FED-10120: Unable to find a suitable binding to send the request.

Cause: Oracle Identity Federation could not find a binding to send the request.

Action: Verify that Oracle Identity Federation and the remote providers have a common binding for the profile.
Level: 1

Type: ERROR

Impact: Configuration

FED-10121: Unable to start identity provider-initiated single sign-on: Unknown metadata version.

Cause: The service provider metadata version was not recognized.

Action: Verify that the metadata version is one of the versions supported by the identity provider.
Level: 1

Type: ERROR

Impact: Configuration

FED-10122: Unable to start identity provider-initiated single sign-on: SP {0} does not belong to affiliation {1}.

Cause: The target service provider was not part of the affiliation.

Action: Check the provider federation to verify that the target service provider is in the affiliation.
Level: 1

Type: ERROR

Impact: Configuration

FED-10123: Unknown NameIDPolicy {0}

Cause: The NameIDPolicy is not one of the known policies.

Action: Verify that the NameIDPolicy is one of the policies that is accepted by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Configuration

FED-10124: User cannot be located for federation with provider ID {0} name identifier {1} and message: {2}

Cause: Federation does not exist between the user, Oracle Identity Federation and the given peer provider.

Action: Verify that the federation exists, or configure the server to create one.
Level: 1

Type: ERROR

Impact: Configuration

FED-10125: AssertionID responder functionality is not enabled.

Cause: The AssertionID responder functionality has been disabled in the Oracle Identity Federation configuration.

Action: Enable the AssertionID responder functionality.
Level: 1

Type: ERROR

Impact: Configuration

FED-10126: Attribute Query requester functionality is not enabled.

Cause: The Attribute Query requester functionality has been disabled in the Oracle Identity Federation configuration.

Action: Enable the AttributeQuery requester functionality.
Level: 1

Type: ERROR

Impact: Configuration

FED-10127: AssertionID requester functionality is not enabled.

Cause: The AssertionID requester functionality has been disabled in the Oracle Identity Federation configuration.

Action: Enable the AssertionID requester functionality.
Level: 1

Type: ERROR

Impact: Configuration

FED-10128: Attribute Query responder functionalities are not enabled.

Cause: The Attribute Query responder functionality has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the Attribute Query responder functionality is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10129: Authentication Query responder functionalities are not enabled.

Cause: The Authentication Query responder functionality has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the Authentication Query requester functionality is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10130: No metadata exists for protocol {0} used by provider {1}

Cause: Metadata for this provider was not found.

Action: Load metadata for the provider.
Level: 1

Type: ERROR

Impact: Configuration

FED-10131: Unknown service provider: {0}

Cause: The service provider is not in the federation.

Action: Verify the trusted provider federation configuration.
Level: 1

Type: ERROR

Impact: Configuration

FED-10132: Single sign-on functionality is not enabled

Cause: The single sign-on functionality has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the single sign-on functionality is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10133: Identity provider functionality is not enabled.

Cause: The identity provider functionality has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the identity provider functionality is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10134: Incoming authentication request uses a protocol profile which is not enabled: {0}

Cause: Protocol profile has not been enabled in the Oracle Identity Federation configuration.

Action: Verify that the profile used for the authentication request is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10135: Incoming request uses a protocol profile which is not enabled: {0}

Cause: Protocol profile has not been enabled in the Oracle Identity Federation configuration.

Action: Verify that profile used for the incoming request is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10136: Incoming assertion uses a protocol profile which is not enabled: {0}

Cause: Protocol profile has not been enabled in the Oracle Identity Federation configuration.

Action: Verify that the profile used in the assertion is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10139: Register Name Identifier protocol is disabled.

Cause: The Register Name Identifier protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the Register Name IdentifierProtocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10140: SAML 1.0 protocol functionality is not enabled.

Cause: The SAML version 1.0 protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the SAML version 1.0 protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10141: SAML 1.1 protocol functionality is not enabled.

Cause: The SAML version 1.1 protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the SAML version 1.1 protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10142: SAML 2.0 protocol functionality is not enabled.

Cause: The SAML version 2.0 protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the SAML version 2.0 protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10143: Service provider functionality is not enabled

Cause: Service provider functionality has been disabled in the Oracle Identity Federation configuration

Action: Verify that service provider functionality is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10169: EventFactory was not found for {0}.

Cause: EventFactory for this class was not registered.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FED-10178: Metadata version parameter unknown: {0}

Cause: The metadata version parameter is unknown.

Action: Check that the metadata version parameter is correct.
Level: 1

Type: ERROR

Impact: Configuration

FED-10187: Logout configuration error: webContext (={0}) and/or relativePath (={1}) for logout are incorrect.

Cause: The webContext and/or relativePath for logout were incorrectly configured.

Action: Verify that the webContext and relativePath for logout are correctly configured.
Level: 1

Type: ERROR

Impact: Configuration

FED-10188: Invalid name identifier format

Cause: The name identifier format is invalid, or custom name ID format is disabled.

Action: Verify that the name identifier format is valid, or that customizable name ID format is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10189: Attribute authority does not support any appropriate name identifier formats.

Cause: The attribute authority does not support the requested subject name identifier format.

Action: Either use a subject format other than "userid", or use a different attribute authority.
Level: 1

Type: ERROR

Impact: Configuration

FED-10191: The service provider integration module is not enabled: {0}.

Cause: The service provider integraton module is disabled in the Oracle Identity Federation configuration.

Action: Enable the appropriate service provider integration module.
Level: 1

Type: ERROR

Impact: Configuration

FED-10195: Authentication engine configuration error: WebContext={0} ; RelativePath={1}

Cause: The Web Context and/or the Relative Path properties of the authentication engine configuration were not set.

Action: Check that the authentication engine configuration defines the required web context and relative path.
Level: 1

Type: ERROR

Impact: Configuration

FED-10196: Service provider integration module configuration error: WebContext={0} ; RelativePath={1}

Cause: The Web Context and/or the Relative Path properties of the service provider integration module configuration were not set.

Action: Check that the service provider integration module configuration defines the required web context and relative path.
Level: 1

Type: ERROR

Impact: Configuration

FED-10197: The service provider anonymous user ID was not set.

Cause: The Oracle Identity Federation server needed to create a session of type anonymous but the Anonymous User ID is not set in the configuration.

Action: Set the Anonymous User ID in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Configuration

FED-10205: OpenID 2.0 protocol functionality is not enabled.

Cause: The OpenID version 2.0 protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the OpenID version 2.0 protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-10206: OAuth 2.0 protocol functionality is not enabled.

Cause: The OAuth version 2.0 protocol has been disabled in the Oracle Identity Federation configuration.

Action: Verify that the OAuth version 2.0 protocol is enabled.
Level: 1

Type: ERROR

Impact: Configuration

FED-11002: Cannot retrieve the unique user federation ID from the federation record.

Cause: Could not retrieve the unique user federation ID from the federation record.

Action: Verify that the federation record is correctly formatted.
Level: 1

Type: ERROR

Impact: Data

FED-12006: Unsupported attribute value type Object {0}

Cause: Attribute value object received from the peer provider was not of a supported type.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: WARNING

Impact: Other

FED-12016: Message Creation Exception: unable to create the message: {0}

Cause: Could not create the protocol message.

Action: Check the Oracle Identity Federation logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FED-12020: Translation Exception: unable to translate message: {0}.

Cause: There was a problem marshalling or unmarshalling the message.

Action: Check the Oracle Identity Federation logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FED-12037: SAML Artifact Exception: {0}

Cause: An error occurred while creating or parsing a SAML Artifact.

Action: Check the Oracle Identity Federation logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FED-12038: SAML Protocol Exception: {0}

Cause: An error occurred while creating or parsing a SAML Protocol message.

Action: Check the Oracle Identity Federation logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FED-12042: Error while generating Oracle Identity Federation provider metadata.

Cause: An error occurred while creating the Oracle Identity Federation provider metadata.

Action: Check logs and configuration, or contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Other

FED-12081: Error while generating Oracle Identity Federation XRDS metadata.

Cause: An error occurred while creating the Oracle Identity Federation XRDS metadata.

Action: Check logs and configuration, or contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Other

FED-12085: Identity Provider Discovery service page disabled

Cause: The IdP Discovery service page is disabled

Action: Update the configuration to enable that service if needed
Level: 1

Type: ERROR

Impact: Other

FED-12086: The credentials provided during the registration data retrieval operation could not be validated

Cause: The credentials provided by the requesting client could not be valited

Action: Ensure that the client is sending the correct credentials
Level: 1

Type: ERROR

Impact: Other

FED-13000: Cannot complete the logout process.

Cause: Oracle Identity Federation could not complete the logout process, due to a lack of profile support from the service providers.

Action: Perform the logout process using another binding or check that the various peer providers support approriate logout profiles.
Level: 1

Type: ERROR

Impact: Programmatic

FED-13008: Cannot create temporary federations.

Cause: Temporary federation store is unavailable.

Action: Check configuration of data store. Make sure the data store is up and has space available.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FED-13018: Cannot create a permanent federation record with a transient data store.

Cause: Could not create a permanent federation due to the store being unavailable.

Action: Check configuration of data store. Make sure the data store is up and has space available.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FED-13019: The Authentication Engine ID and Service Provider Engine ID are null.

Cause: The engine did not return an authentication engine ID or a service provider engine ID.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Programmatic

FED-13020: Both the Authentication Engine ID and Service Provider Engine ID are set.

Cause: The engine returned both an authentication engine ID and an service provider engine ID, where only one should be set.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Programmatic

FED-13021: Cannot retrieve session during logout flow.

Cause: The session could not be retrieved.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: WARNING

Impact: Programmatic

FED-15005: Name identifier registration is already in progress.

Cause: A name identifier registration was in progress when a new registration was initiated.

Action: Wait until the name identifier registration finishes.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15006: The single sign-on Assertion has been marked as logged out: {0}.

Cause: A non-expired logout request containing the Assertion SessionIndex invalidated the single sign-on assertion.

Action: Perform single sign-on again.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15007: The single sign-on Assertion has been marked as logged out: {0}.

Cause: A non-expired logout request with no SessionIndex invalidated the single sign-on Assertion.

Action: Perform single sign-on again.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15008: A SAML 2.0 name identifier update cannot be performed on a non-SAML 2.0 federation record.

Cause: Tried to perform a SAML 2.0 name identifier update.

Action: Try a different protocol version.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15009: An error occurred while dereferencing the SAML 2.0 Artifact: {0} - {1}

Cause: A problem occurred with the SAML 2.0 Artifact.

Action: Verify the contents of the SAML 2.0 Artifact.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15010: Artifact not present

Cause: The artifact was not present in the request.

Action: Verify that the artifact is set in the request
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15011: Cannot find the authentication request associated with the assertion: {0}.

Cause: The assertion was replayed.

Action: Verify that the assertion has not been replayed.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15012: Cannot select the binding to use to send the request.

Cause: Either the profile was not supported by the remote server, or could not agree with the Oracle Identity Federation server on a common binding.

Action: Verify that the remote server and the Oracle Identity Federation server have a common binding.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15013: Cannot select the binding to use to send the response.

Cause: Either the profile was not supported by the remote server, or could not agree with the Oracle Identity Federation server on a common binding.

Action: Verify that the remote server and the Oracle Identity Federation server have a common binding.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15015: Error encountered while parsing XML element {0}, child of {1} in incoming XML message.

Cause: Could not parse an XML element from the incoming XML message.

Action: Verify that the incoming XML message is valid and correctly formatted.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15018: Error while decoding the authentication result: user ID missing.

Cause: The user ID was missing in the result returned by the authentication process.

Action: Verify that the user ID is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15020: Name identifier format not supported or missing for attribute responder: {0}

Cause: The name identifier format for the attribute responder was unknown or not accepted.

Action: Verify that the name identifier format is one of the formats that is accepted by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15021: Name identifier format not supported or missing for authentication responder: {0}

Cause: The name identifier format for the authentication responder was unknown or not accepted.

Action: Verify that the name identifier format is one of the formats that is accepted by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15022: Error processing response message.

Cause: Was unable to process the response message.

Action: Check the Oracle Identity Federation logs for more specific information.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15024: Query received is not an Attribute Query.

Cause: Internal server error; expected an AttributeQuery message, but received a different message.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15025: Query received is not an Authentication Query.

Cause: Internal server error; expected an AuthenticationQuery message, but received a different message.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15026: Issuer is not set in the incoming assertion request message: the provider is unknown

Cause: The issuer attribute was not set in the assertion request message.

Action: Verify that the issuer attribute is set in the assertion request message.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15027: Issuer is not set in the incoming attribute query message: the provider is unknown

Cause: The issuer attribute was not set in the attribute query message.

Action: Verify that the issuer attribute is set in the attribute query message.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15028: Issuer is not set in the incoming authentication query message: the provider is unknown

Cause: The issuer attribute was not set in the authentication query message.

Action: Verify that the issuer attribute is set in the authentication query message.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15032: No service provider federation found for provider {0} and name identifier format {1} and name identifier value {2}

Cause: Unable to find the service provider federation corresponding to this provider and name identifier in the federation data store.

Action: Check the federation data store to verify that a user identity federation exists with the provider ID and name identifier submitted in the query.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15033: Outgoing assertion protocol profile is not supported or not enabled: {0}

Cause: The outgoing assertion protocol profile was not supported, or enabled.

Action: Verify that the assertion protocol profile is supported by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15034: Profile is unknown: {0}

Cause: The profile was unknown.

Action: Verify that the profile version is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15035: Provider ID is missing from the authentication request

Cause: The provider ID was missing from the authentication request.

Action: Verify that the provider ID is present in the authentication request.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15037: Request destination is invalid

Cause: The request destination was not a valid URL.

Action: Verify that the request destination is a valid URL and correspond to the URL where the request was posted.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15038: Response destination is invalid

Cause: The response destination was not a valid URL.

Action: Verify that the response destination is a valid URL and correspond to the URL where the response was posted.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15039: Response does not correspond to any requests

Cause: The response was replayed

Action: verify that the response is not replayed
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15041: Cannot process the incoming request

Cause: Single sign-on is required with peer provider in order to fulfill the current request.

Action: Perform single sign-on before attempting to execute the protocol operation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15042: The InResponseTo header does not correspond to a ManageNameID request.

Cause: The InResponseTo pointed to a message other than ManageNameID.

Action: Check with the peer provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15043: The received assertion does not contain an AuthenticationStatement: {0}

Cause: The assertion did not contain an authentication statement.

Action: Contact the peer provider for more details on why the assertion does not contain an authentication statement, and examine the assertion for possible information.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15044: The response does not contain any assertions: {0}

Cause: The identity provider did not include any assertions in the response.

Action: Check that the identity provider includes an assertion with the response.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15055: Invalid version format in the active identity provider federation entry: {0}

Cause: The version format was incorrect.

Action: Verify that the version parameter is in a valid format.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15061: Unknown message: {0}

Cause: A protocol message was sent on the incorrect service URL.

Action: Verify that the message sent to the service URL is of correct type.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15062: Authentication request destination is invalid

Cause: The authentication request destination was not a valid URL.

Action: Verify that the authentication responder functionalities are enabled.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15063: Authentication request is expired.

Cause: The authentication request has expired or is not yet valid.

Action: Verify the time settings between this server and the peer provider are synchronized. Alternatively the server clock drift can be increased in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15064: Destination URL cannot be validated: {0}

Cause: Destination URL could not be validated.

Action: Verify that the URL is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15065: The destination field ({0}) from the SAML 2.0 message does not match the actual request URL {1}

Cause: The message was submitted on a URL that is different from the URL that was specified by the remote provider in the destination field.

Action: Contact remote provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15067: Invalid response.

Cause: Protocol response was corrupt.

Action: Verify that an XML message is well-formed and correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15070: The response cannot be validated.

Cause: Message does not follow the configuration requirements.

Action: Check previous error messages for more information.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15071: The server is not included in the AudienceRestrictionCondition.

Cause: The value of the provider ID entry in the federations for the identity provider was incorrect.

Action: Verify that the federations entry corresponding to the assertion consumer is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15072: Unknown version in factory request.

Cause: The protocol version sent back from the peer provider is not valid.

Action: Verify that the peer provider is configured to the correct protocol version.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15073: The profile is not supported.

Cause: The profile is not supported or is not enabled.

Action: Verify that the profile is supported by Oracle Identity Federation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15074: The user authenticated at identity provider is different from the user specified in the request message.

Cause: For security reasons, the user authenticated at the identity provider must be the same user that was specified in the request.

Action: Verify that the user authenticated at the identity provider is the same user as indicated in the request.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15075: User from existing session ({0}) is different from user received in single sign-on assertion ({1}) for message: {2}.

Cause: The user from the existing session was different than the user in the assertion.

Action: Action is not allowed.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15076: Cannot validate the SubjectConfirmation's InResponseTo field with the authentication request for message {0}

Cause: The value of the InResponseTo field did not correspond to an authentication request.

Action: Contact administrator, remote server, or Oracle Support Services.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15078: Unsupported protocol.

Cause: Protocols supported are Liberty 1.x, SAML1.x/2.0 and WS-Federation.

Action: Ensure the protocol used is either Liberty 1.x or SAML1.x/2.0 or WS-Federation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15080: The user previously performed a single sign-on operation with a protocol version ({0}) different from SAML2.0.

Cause: The federation was created with a single sign-on of different protocol version.

Action: Single sign-on can only be performed with same protocol version for the particular service provider
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15081: User tried to initiate protocol with a federation belonging to another user.

Cause: User tried to initiate protocol with a federation belonging to another user.

Action: Cannot initiate protocol as another user.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15086: Multiple users are found during attribute responder operation for name identifier: {0} and name identifier format = {1}.

Cause: Multiple users were present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15088: Multiple users are found during automatic account linking for name identifier: {0} name identifier format: {1} and message: {2}.

Cause: Multiple users were present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15089: User was not found during attribute responder operation for name identifier: {0} and name identifier format = {1}.

Cause: User was not present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15091: User was not found during automatic account linking for name identifier: {0} name identifier format: {1} and message: {2}.

Cause: User was not present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15092: RegisterNameIdentifier was not successful.

Cause: Status of RegisterNameIdentifier response was in error.

Action: Check global name identifier format of this Oracle Identity Federation server or with the uploaded peer provider metadata.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15093: A federation for this user does not exist locally: {0}.

Cause: The identity provider sent a federation name identifier, but the federation was not found locally.

Action: Enable auto account linking property for SAML20 protocol to create the federation for this user. Enable allow federation creation property to create the federation for this user.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15097: The identity provider sent an assertion with version 2.0 different from the existing single sign-on version: {0} with message: {1}.

Cause: Existing session was not of the single sign-on version 2.0.

Action: Logout the user to delete the existing session.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15099: The wtrealm parameter is empty.

Cause: A WS-Federation signin request was received with an empty wtrealm parameter.

Action: Verify that the wtrealm parameter is not empty.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15100: There is no assertion consumer URL in the requester's configuration.

Cause: There was no assertion consumer URL in the requester configuration.

Action: Enter the assertion consumer URL of the requester in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15101: WS-Federation protocol is not enabled.

Cause: The WS-Federation protocol was not enabled in the Oracle Identity Federation configuration.

Action: Enable the WS-Federation protocol in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15102: Default name identifier format for SAML 1.x assertion cannot be processed: {0}

Cause: The default name identifier format cannot be processed.

Action: Verify that the default name identifier format is correct in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15103: Default name identifier format for SAML 1.1 assertion cannot be processed: {0}

Cause: The default name identifier format cannot be processed.

Action: Verify that the default name identifier format is correct in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15104: The user previously performed a single sign-on operation with a protocol version ({0}) different from WS-Fed 1.1.

Cause: The user previously performed a single sign-on operation with a protocol version other than WS-Federation 1.1

Action: No action.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15105: The identity provider sent an assertion with WS-Fed version 1.1 different from the existing single sign-on version: {0}.

Cause: The single sign-on version in the assertion was different than the existing single sign-on version.

Action: Verify that the peer provider is configured to the correct protocol version.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15106: Multiple users were found during attribute based authentication using NameID mapping for name identifier: {0} name identifier format: {1} and message: {2}.

Cause: Multiple users were present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15107: Multiple users were found during attribute based authentication using Attribute mapping for name identifier: {0} name identifier format: {1} and message: {2}.

Cause: Multiple users were present in the user data store which satisfies the search criteria of attribute values.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15108: User was not found during attribute based authentication using NameID mapping for name identifier: {0} name identifier format : {1} and message : {2}.

Cause: User was not present in the user data store which satisfies the search criteria of name identifier value.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15109: User was not found during attribute based authentication using Attribute Mapping for name identifier: {0} and name identifier format : {1} and message : {2}.

Cause: User was not present in the user data store which satisfies the search criteria of attribute values.

Action: Check the data store and correct any errors.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15110: User mapping based on name identifier and attribute features are not enabled for attribute based authentication for name identifier: {0} name identifier format: {1} and message: {2}.

Cause: User mapping based on name identifier and attribute features were not enabled for attribute based authentication.

Action: Verify that user mapping based on NameID and attribute features are enabled for attribute based authentication.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15111: The message is not a request security token response: {0}.

Cause: The message received from the identity provider was not a Request Security Token Response.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15112: The message contains an assertion with an empty issuer attribute: {0}.

Cause: The message contained an assertion with an empty issuer attribute.

Action: Verify that the peer provider is configured to use the correct provider ID for the issuer.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15113: The action parameter (wa={0}) is not one of the actions currently recognized by the identity provider.

Cause: The value of the action parameter was not one of the values recognized by Oracle Identity Federation.

Action: Verify that the peer provider is using the correct version of the WS-Federation protocol.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15114: Unknown WS-Federation request message: {0}

Cause: The WS-Federation Request message contained in the wreq parameter is unknown or incorrect.

Action: Contact remote provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15115: Error while interacting with remote providers via SOAP protocol.

Cause: An error occurred while sending or receiving a SOAP message to a remote provider.

Action: Check with the peer provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15116: The identity provider discovery service returned an empty string as the identity provider.

Cause: The discovery service returned the empty string as the identity provider's provider ID.

Action: The identity provider's providerID parameter should either be missing or contain a value. Check with the discovery service
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15117: The identity provider discovery service returned an empty or null refid.

Cause: The discovery service did not include the required refID parameter.

Action: Check with the discovery service
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15118: Could not find provider ID for issuer of request.

Cause: Oracle Identity Federation cannot identify the SOAP requester as it did not authenticate via HTTP Basic/SSL Client.

Action: Configure OHS so that it protects the SAML 1.x SOAP URL to require HTTP basic authentication or SSL client authentication
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15119: Incoming message does not contain a SAML 1.x Request.

Cause: The incoming SOAP Request does not contain a SAML 1.x request and Oracle Identity Federation was expecting one.

Action: Verify that the SOAP Requestor is sending a SAML 1.x Request; verify that the SOAP Requestor is not sending a non SAML 1.x message to the SAML 1.x SOAP URL
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15120: UserID was not sent from user provisioning system.

Cause: Request from user provisioning system does not contain UserID attribute.

Action: Verify that request from user provisioning system contains UserID attribute
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15121: Attribute response is malformed.

Cause: The attribute response was malformed.

Action: Verify that the attribute response is not malformed.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15122: Unknown identity provider: {0}

Cause: The identity provider is unknown.

Action: Verify that the identity provider is in the federations configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15123: Invalid subject format for protocol version SAML 1.x

Cause: The subject format was invalid.

Action: Verify that the peer provider is using the correct subject format.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15124: Provider federation does not exist for userID: {0}.

Cause: Provider federation has been deleted or the userID is not valid.

Action: Check the request or retry.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15125: Single sign-on response was not signed.

Cause: The single sign-on response signature requirements were not met.

Action: Verify that a signature was present in the single sign-on response and that Oracle Identity Federation is using the correct certificate for signature validation.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15128: An internal error occurred while processing the credentials

Cause: The authentication engine did not return the required refID parameter.

Action: Check that the authentication flow correctly sent the refID parameter to the Oracle Identity Federation server
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15130: AssertionID parameter not present

Cause: The AssertionID was not present in the request.

Action: Verify that the AssertionID is set in the request
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15132: Unknown refID

Cause: User previously accessed the Oracle Identity Federation server with a different host name than the one in the current request and cookies were not transmitted.

Action: Use the same hostname and fully qualified domain URL to access the Oracle Identity Federation server.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15133: Unknown FedID: {0}

Cause: No federation record exists with specified fedID in the configured federation data store.

Action: Check federation data store configuration and verify that federation record with specified fedID exists in data store.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15134: The service provider could not map the identity provider response to a user

Cause: The Oracle Identity Federation service provider was not able to map the response from the identity provider to a user record.

Action: Check the message sent from the identity provider and error logs in the service provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15135: "Unknown Identity Provider; SuccinctID:{0}"

Cause: The identity provider is unknown.

Action: Verify that the identity provider is in the federations configuration.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15136: Unsolicited OpenID Response: {0}

Cause: The OpenID Response received is unsolicited and the OP is not trusted

Action: Contact the OP as the Oracle Identity Federation Server does not support unsolicited responses
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15137: Nonce missing from Response

Cause: The Response did not contain a Nonce element

Action: Contact the OP
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15138: The OP sent an authentication response with version OpenID 2.0 different from the existing SSO version: {0} for message: {1}

Cause: Existing session was not of the single sign-on version OpenID 2.0

Action: Logout the user to delete the existing session.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15139: OpenID Association Failed with ProviderID: {0}

Cause: The OpenID Association operation failed.

Action: Check the logs for more detailed error messages, and correct the problem related to the error.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15140: OpenID Signature Verification Failed with ProviderID: {0}

Cause: The Signature Verification of the OpenID Message failed

Action: Check the logs for more detailed error messages, and contact the OP
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15141: OpenID Direct Message Verification Failed with ProviderID: {0}

Cause: The OpenID Direct Verification operation failed while validating a response

Action: Check the logs for more detailed error messages, and contact the OP
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15142: OpenID XRDS processing failed with ProviderID: {0}

Cause: The XRDS document could not be retrieved

Action: Check the logs for more detailed error messages, and contact the OP
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15143: OpenID ClaimedID verification failed against the OP XRDS document for message: {0}

Cause: The XRDS document downloaded from the ClaimedID location does not match the OP's information

Action: Check the logs for more detailed error messages, and contact the OP
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15144: The OpenID RP is unknown

Cause: The OpenID RP is not a known partner: either the RP was not provisioned or Oracle Identity Federation IdP is not configured to interact with Generic OpenID RPs

Action: Add the OpenID RP or the configure Oracle Identity Federation IdP to interact with Generic OpenID RPs if needed
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15145: The Federation SSO operation with the Identity Provider partner {0} failed with the following status: top status={1} secondary status={2} and message={3}

Cause: The Federation SSO operation failed to complete.

Action: Check the message sent from the identity provider and error logs in the service provider.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15146: OAuth Access Token Request operation failed with partner {0} for the Access Token URL {1}

Cause: The Access Token message exchange failed

Action: Check the logs for more detailed error messages and contact the partner
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15147: OAuth Access Token Request operation failed with partner {0} for the resource {1}

Cause: An error occurred while retrieving user data from the partner resource

Action: Check the logs for more detailed error messages and contact the partner
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15148: The OAuth Partner sent an authentication response with version OAuth 2.0 different from the existing SSO version: {0} for message: {1}

Cause: Existing session was not of the single sign-on version OAuth 2.0

Action: Logout the user to delete the existing session.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15149: The partner did not return a success response: {0}

Cause: The federation partner returned an error.

Action: Check the message and contact if necessary the partner.
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-15150: The identity provider sent an assertion with version 1.1 different from the existing single sign-on version: {0} with message: {1}.

Cause: Existing session was not of the single sign-on version 1.1.

Action: Logout the user to delete the existing session.
Level: 1

Type: WARNING

Impact: Requests/Responses

FED-15151: Unsolicited OAuth Response: {0}

Cause: The OAuth Response received is unsolicited and the IdP is not trusted

Action: Contact the IdP as the Oracle Identity Federation Server does not support unsolicited responses
Level: 1

Type: ERROR

Impact: Requests/Responses

FED-18002: The assertion has already been processed: {0}

Cause: The assertion has been replayed.

Action: Verify that the assertion is not replayed.
Level: 1

Type: ERROR

Impact: Security

FED-18004: Attribute authority is not trusted.

Cause: The attribute authority is not marked as trusted in the federations.

Action: Configure the peer provider as a trusted provider to enable protocol exchanges.
Level: 1

Type: ERROR

Impact: Security

FED-18005: Identity provider is not trusted: {0}

Cause: The identity provider is not marked as trusted in the federations.

Action: Verify configuration of the provider in the federations settings of the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Security

FED-18006: Message cannot be validated : {0}.

Cause: Incoming message is invalid.

Action: Please check previous log entries for more specific information.
Level: 1

Type: ERROR

Impact: Security

FED-18007: Message has expired or is not yet valid.

Cause: The message validity period has expired.

Action: Verify the time settings between this server and the peer provider are synchronized. Alternatively, the server clock drift can be increased in the Oracle Identity Federation configuration.
Level: 1

Type: ERROR

Impact: Security

FED-18008: Message is not signed.

Cause: The message was not signed.

Action: Verify that the message is signed.
Level: 1

Type: ERROR

Impact: Security

FED-18010: The service provider is not part of the affiliation.

Cause: The provider is not part of the affiliation.

Action: Verify that the provider is part of the affiliation in the federations
Level: 1

Type: ERROR

Impact: Security

FED-18011: Service provider is not trusted.

Cause: Service provider is not in the federations configuration.

Action: Verify configuration of the federations
Level: 1

Type: ERROR

Impact: Security

FED-18012: Assertion cannot be validated: {0}.

Cause: Assertion could not be validated.

Action: Check the message to verify that the assertion is valid, and after check with the peer provider that sent the assertion.
Level: 1

Type: ERROR

Impact: Security

FED-18013: Assertion cannot be validated; confirmation method is missing for message: {0}.

Cause: The confirmation method was missing from the assertion.

Action: Check the message to verify that the assertion is valid, and after check with the peer provider that sent the assertion.
Level: 1

Type: ERROR

Impact: Security

FED-18014: Assertion cannot be validated; InResponseTo is missing for message: {0}.

Cause: The InResponseTo attribute was missing from the assertion.

Action: Check the message to verify that the assertion is valid, and after check with the peer provider that sent the assertion.
Level: 1

Type: ERROR

Impact: Security

FED-18015: Assertion cannot be validated; recipient is missing for message: {0}.

Cause: The recipient was missing from the assertion.

Action: Check the message to verify that the assertion is valid, and after check with the peer provider that sent the assertion.
Level: 1

Type: ERROR

Impact: Security

FED-18016: Assertion cannot be validated; validity time is missing for message {0}.

Cause: The validity time was missing from the assertion.

Action: Check the message to verify that the assertion is valid, and after check with the peer provider that sent the assertion.
Level: 1

Type: ERROR

Impact: Security

FED-18017: The AssertionConsumerServiceURL found in the authentication request message cannot be validated.

Cause: URL was not one of the assertion consumer support URL found in the metadata.

Action: Verify that the URL is correct.
Level: 1

Type: ERROR

Impact: Security

FED-18018: Assertion has expired or is not yet valid: {0} for message: {1}

Cause: The assertion validity period has expired.

Action: Verify the time settings between this server and the peer provider are synchronized. Alternatively, the server clock drift can be increased in the admin console.
Level: 1

Type: ERROR

Impact: Security

FED-18020: Authentication request is not signed.

Cause: Authentication request was not signed.

Action: Authentication request needs to be signed.
Level: 1

Type: ERROR

Impact: Security

FED-18027: Evaluation of the assertion's conditions failed.

Cause: Assertion conditions were not valid.

Action: Check logs for more detailed error messages.
Level: 1

Type: ERROR

Impact: Security

FED-18035: URL query signature verification failed.

Cause: The message or signature may have been tampered with.

Action: Contact administrator to investigate transport error or possible security incident.
Level: 1

Type: ERROR

Impact: Security

FED-18038: Signature verification failed.

Cause: The message or signature may have been tampered with.

Action: Contact administrator to investigate transport error or possible security incident.
Level: 1

Type: ERROR

Impact: Security

FED-18040: Cannot locate temporary federations.

Cause: The temporary federation did not exist, possibly expired.

Action: No Action.
Level: 1

Type: ERROR

Impact: Security

FED-18043: Unexpected recipient: {0} for message: {1}

Cause: The recipient in the assertion did not match the configured provider.

Action: Contact remote provider to verify the provider information.
Level: 1

Type: ERROR

Impact: Security

FED-18045: Unsupported liberty version: {0}

Cause: The version of liberty was not supported.

Action: The supported versions of liberty are 1.1 and 1.2.
Level: 1

Type: ERROR

Impact: Security

FED-18046: Unknown descriptor type: {0}

Cause: Unknown descriptor type .

Action: Contact remote provider for verifying the metadata.
Level: 1

Type: ERROR

Impact: Security

FED-18051: Authentication instant was not sent from the authentication engine.

Cause: The authentication engine did not send an authentication instant.

Action: Check the authentication engine implementation.
Level: 1

Type: WARNING

Impact: Security

FED-18052: Authentication mechanism was not sent from the authentication engine.

Cause: The authentication engine did not send an authentication mechanism.

Action: Check the authentication engine implementation.
Level: 1

Type: WARNING

Impact: Security

FED-18056: Authentication error, the authentication mechanism is not enabled: {0}

Cause: The Authentication Mechanism used to authenticate the user is disabled.

Action: A user tried to use a disabled authentication mechanism/engine to login.
Level: 1

Type: ERROR

Impact: Security

FED-18057: Authentication error, the authentication engine is not enabled: {0}

Cause: The Authentication Engine used to authenticate the user is disabled.

Action: A user tried to use a disabled authentication mechanism/engine to login.
Level: 1

Type: ERROR

Impact: Security

FED-18058: Service provider engine error, the service provider engine is not enabled: {0}

Cause: The service provider engine used to integrate with the AAA server is disabled.

Action: Enable the service provider engine.
Level: 1

Type: ERROR

Impact: Security

FED-18059: User from existing session ({0}) is different from user locally authenticated ({1})

Cause: A user already authenticated in Oracle Identity Federation re-authenticated but with a different user ID.

Action: Check the user's activity and session status, and report a possible security incident to the administrator.
Level: 1

Type: ERROR

Impact: Security

FED-18060: User has already existing session with SessionID={0} and the authentication engine specified a different SessionID={1}

Cause: A user already authenticated in Oracle Identity Federation with a SessionID that is different from the one specified by the authentication engine

Action: Check the authentication engine implementation to be sure that it returns the correct SessionID.
Level: 1

Type: ERROR

Impact: Security

FED-18082: Authentication failed: requested authentication method could not be fulfilled by Identity Provider

Cause: The authentication mechanism needs to be set to fulfill the requested authentication method by Service Provider.

Action: Contact the Service provider and set the authentication mechanisms in the Oracle Identity Federation configuration for IdP.
Level: 1

Type: ERROR

Impact: Security

FED-18083: Authentication failed: unknown user attribute for Oracle Access Manager 11g authentication engine: {0}

Cause: The Oracle Identity Federation configuration specifies an unknown HTTP Header containing the UserID.

Action: Check the Oracle Identity Federation configuration for which HTTP Header used by Oracle Access Manager 11g to hold the UserID is specified.
Level: 1

Type: ERROR

Impact: Security

FED-18084: The Partner is not configured to use the Test SP Engine: {0}

Cause: The partner has not been configured to be used with the Test SP Engine.

Action: Configure the Partner.
Level: 1

Type: ERROR

Impact: Security

2 FEDSTS-10102 to FEDSTS-20100

FEDSTS-10102: The LDAP connection settings have not been configured.

Cause: The configuration properties for LDAP connection have not been set.

Action: Enter the LDAP connection settings in the Oracle Identity Federation / Oracle Secure Token Service Data Stores configuration..
Level: 1

Type: ERROR

Impact: Configuration

FEDSTS-10107: Federation does not exist: cannot complete the requested operation

Cause: Federation does not exist for the user with the peer provider.

Action: Verify that the federation exists, or configure the server to create one.
Level: 1

Type: ERROR

Impact: Configuration

FEDSTS-10146: Could not locate the X.509 certificate for {0}, for use {1}

Cause: The X.509 certificate for the given provider and for the specified use was not found.

Action: Check the metadata and the configuration for the given provider.
Level: 1

Type: ERROR

Impact: Configuration

FEDSTS-10152: LDAP BindDN or password is incorrect.

Cause: The LDAP BindDN or password was configured incorrectly.

Action: Check the LDAP configuration entry for BindDN and bind password.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10158: Unable to find the exception handler mapping for the exception {0}.

Cause: ExceptionHandler mapping for this exception was missing in the configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10159: Unable to find the request handler mapping for this URL {0}.

Cause: RequestHandler mapping for this URL was missing in the configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10160: Unable to find the response handler mapping for this event response {0}.

Cause: ResponseHandler mapping for this EventResponse cannot be found in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10161: Unable to locate a mapping for {0}.

Cause: Mapping for this class could not be located.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10164: Invalid peer provider configuration for: {0}

Cause: Metadata for this peer provider is invalid.

Action: Load metadata for this peer provider.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10168: DiscoveryProvider was not found for {0}.

Cause: A DiscoveryProvider for this type of provider is not configured.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10170: Handler was not found for URL: {0}.

Cause: Handler for this response is missing from configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10174: Property was not found: {0}.

Cause: Property is not set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10175: First package-search-order is used as default package search order.

Cause: Group of package-search-order was found in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: WARNING

Impact: Configuration

FEDSTS-10179: Mapping was not defined for action {0}

Cause: Mapping for the specified action was not defined in the configuration.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Configuration

FEDSTS-10180: Business Processing Plugin error: {0} does not implement OperationListener

Cause: Business Processing Plugin configuration is incorrect.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10181: Property is not type of Boolean: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10182: Property is not of type Long: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10183: Property is not of type Set: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10184: Property is not of type List: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10185: Property is not of type Map: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10186: Property is not of type String: {0}

Cause: Property was not correctly set in configuration file.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10203: Property could not be retrieved from the Credential Store Framework: {0}

Cause: The Credential Store Framework did not refresh.

Action: Set the credentials again using Enterprise Manager or restart the WLS Managed Server where Oracle Identity Federation / Oracle Secure Token Service is running.
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-10208: Namespace missing in Attribute: {0}

Cause: Namespace missing in Attribute configuration.

Action: Enter the namespace for the attribute in Attribute mapping
Level: 1

Type: WARNING

Impact: Configuration

FEDSTS-10503: The load of configuration for instance{0} failed for element {1} :{2}

Cause: The configuration file may be invalid or the instance and element may not be present

Action: Check the configuration file for validity and make sure the instance and the element exist
Level: 1

Type: ERROR

Impact: Configuration

FEDSTS-10508: Oracle Identity Federation / Oracle Secure Token Service is disabled

Cause: The Oracle Identity Federation / Oracle Secure Token Service is disabled

Action: Check the configuration and enable Oracle Identity Federation / Oracle Secure Token Service if required
Level: 1

Type: INCIDENT_ERROR

Impact: Configuration

FEDSTS-11005: Error while deserializing data, mismatched classes while reading database records: expected {0}, got {1}

Cause: The data could not be deserialized.

Action: Check that the entry contains valid data.
Level: 1

Type: ERROR

Impact: Data

FEDSTS-11008: RequestHandlerMapping {0} already exists.

Cause: RequestHandlerMapping was already present.

Action: No Action.
Level: 1

Type: WARNING

Impact: Data

FEDSTS-11009: ResponseHandlerMapping {0} already exists.

Cause: ResponseHandlerMapping was already present.

Action: No Action.
Level: 1

Type: WARNING

Impact: Data

FEDSTS-11010: Replacement RequestHandlerMapping is: {0}.

Cause: RequestHandlerMapping was replaced with the new RequestHandlerMapping.

Action: No Action.
Level: 1

Type: WARNING

Impact: Data

FEDSTS-11011: Replacement ResponseHandlerMapping is: {0}.

Cause: ResponseHandlerMapping was replaced with the new ResponseHandlerMapping.

Action: No Action.
Level: 1

Type: WARNING

Impact: Data

FEDSTS-11013: SQL error while interacting with the database.

Cause: SQL query may not have been properly formed.

Action: Check log entries and database connection configuration.
Level: 1

Type: ERROR

Impact: Data

FEDSTS-11014: Could not add an SQL operation to the Batch Queue

Cause: The SQL operation could not be added because the batch queue might be full

Action: Tune the RBDMS, the JDBC Datasource and the queue settings
Level: 1

Type: ERROR

Impact: Data

FEDSTS-11700: Cannot connect to the LDAP server.

Cause: The LDAP credentials were incorrect.

Action: Verify the LDAP credentials in the Oracle Identity Federation / Oracle Secure Token Service configuration.
Level: 1

Type: ERROR

Impact: Network

FEDSTS-11703: Exception while trying to connect to LDAP server.

Cause: Oracle Identity Federation / Oracle Secure Token Service could not open a connection to the LDAP server.

Action: Verify the connection settings in the Oracle Identity Federation / Oracle Secure Token Service configuration and that LDAP server is up.
Level: 1

Type: ERROR

Impact: Network

FEDSTS-11704: Cannot close LDAP connection.

Cause: Problem while closing the LDAP connection.

Action: Check the LDAP server logs.
Level: 1

Type: WARNING

Impact: Network

FEDSTS-12000: XML time value is empty.

Cause: An empty string was passed in as an XML time value attribute.

Action: Verify that none of the time value attributes are empty.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12003: Unsupported handler parameter type: {0}

Cause: Parameter type was not supported.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

FEDSTS-12007: Data Object {0} is no longer valid.

Cause: Object was destroyed.

Action: No Action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12009: Multiple certificates are found for the public key, attempting to select a valid one.

Cause: Multiple certificates were present in the certificate store.

Action: No Action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12010: Previous RequestHandlerMapping is replaced with the new RequestHandlerMapping for URL {0}.

Cause: New RequestHandlerMapping was found for this URL.

Action: No Action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12011: Previous ResponseHandlerMapping is replaced with the new ResponseHandlerMapping for URL {0}.

Cause: New ResponseHandlerMapping was found for this URL.

Action: No Action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12012: Unsupported type for attribute value {0}, type={1}

Cause: One of the retrieved values for the attribute was of an unsupported type.

Action: No Action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12013: Discovery Create Exception: unable to create object in the repository: {0}

Cause: Unable to create a data object in the repository.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12014: Discovery Finder Exception: unable to locate object in the repository: {0}

Cause: Unable to locate a data object in the repository.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12015: Federation Exception: error while accessing or creating the federation record of a user: {0}

Cause: An error occured while accessing or creating the federation record of a user.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12017: Communication Exception: unable to communicate with directory or naming service: {0}

Cause: Could not communicate with directory or naming service.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12018: Duplicate Entry Exception: duplicate entry in the data store: {0}

Cause: There was a duplicate entry in the data store.

Action: Check the data store for duplicate entries.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12026: No Such Algorithm Exception: cryptographic algorithm was not recognized: {0}

Cause: JCE provider was incorrectly configured.

Action: Check that the JCE provider is configured correctly.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12028: Notification Processing Exception: could not call the notifier: {0}.

Cause: Could not process the notification.

Action: Please check any plugins or listeners, or contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12029: Attribute Processing Exception: error when processing attributes for mapping and filtering: {0}

Cause: Could not process attributes for mapping and filtering.

Action: Check the configuration for assertion attribute mapping and filtering.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12030: IOException: {0}

Cause: There was an error during Input/Output an operation.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12031: NamingException: error while interacting with an LDAP server or JNDI module

Cause: There was an error during interaction with an LDAP or JNDI module

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12032: InterruptedException: thread interrupt occurred during sleep() {0}

Cause: Thread interrupt occurred during sleep() method.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12033: Invocation Target Exception: error while invoking method {0}

Cause: There was an error while invoking a method.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12034: No Such Method Exception: a particular method could not be found {0}

Cause: There was an error while finding a method.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12036: Persistence Exception: error while creating or modifying data in the backend store {0}

Cause: Could not create or modify data in the backend store.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12040: Unsupported Encoding Exception: {0}

Cause: The specified character encoding was not supported.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12041: Unknown Provider Exception: {0}

Cause: The specified peer provider was not known.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12043: Discovery Registration Exception: {0}

Cause: An error occurred while registering a Discovery Provider.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12044: No Such Discovery Provider Exception: {0}

Cause: Could not find the specified Discovery Provider.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12045: Parser Configuration Exception: {0}

Cause: An error occurred while parsing an XML document.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12046: Parser Configuration Exception: {0}

Cause: An error occurred while parsing.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12047: SAX Exception: {0}

Cause: An error occurred while handling XML documents.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12048: SOAP Exception: {0}

Cause: An error occurred while handling SOAP messages.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12049: Event Exception: {0}

Cause: An error occurred while processing an Event.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12050: Action Listener Init Exception: {0}

Cause: An error occurred during Action Listener initialization.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12051: Mapping Exception: {0}

Cause: An error occurred while accessing handler mappings.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12052: No Such Target Exception: {0}

Cause: An error occurred while setting up handler mappings.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12053: SAX Parse Exception: {0}

Cause: An error occurred while parsing an XML document.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12054: Malformed URL Exception: {0}

Cause: Either no legal protocol could be found in a specification string or the string could not be parsed.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12055: No Such Mapping Exception: {0}

Cause: Could not find the handler mapping.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12056: Class Not Found Exception: {0}

Cause: Tried to load class with specified name but could not find definition for such class.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12057: Instantiation Exception: {0}

Cause: Tried to load an interface or an abstract class.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12058: Illegal Access Exception: {0}

Cause: Tried to use a field, method, or constructor using reflection, whose definition is not accessible.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12059: Action Registry Exception: {0}

Cause: An error occurred while registering Action Listener.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12060: Service Locator Exception: {0}

Cause: Could not allocate Service Locator.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12061: Algorithm Identifier Exception: {0}

Cause: Inappropriate or unsupported parameters were provided to an algorithm, or an unknown algorithm was requested.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12062: Audit Exception: {0}

Cause: An error occurred while auditing an event.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12063: OPSS Exception: {0}

Cause: An error occurred while using Oracle Platform Security Services libraries.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12064: Exception: {0}

Cause: An error occurred.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12065: Target Exception: {0}

Cause: An error occurred while handling the Target of a Servlet handler.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12066: Servlet Exception: {0}

Cause: An error occurred while initializing or using Servlet.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12067: An HTTP error occurred during SOAP Exchange.

Cause: An HTTP error occurred in SOAP Exchange.

Action: Check Oracle Identity Federation / Oracle Secure Token Service logs for HTTP error code.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12069: Length of input exceeds maximum.

Cause: Length of input exceeds maximum allowed length.

Action: Check that the incoming request is correctly formatted.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12070: No HTTP Message Sender Created

Cause: Could not create the http message sender.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information. Check that http client jar is in the classpath.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12071: A Directory error occurred

Cause: An error occurred while interacting with the Identity Provider module

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12074: PrivilegedActionException: {0}

Cause: PrivilegedExceptionAction while validating Kerberos Token

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12075: LoginException: {0}

Cause: A LoginException occurred while validating kerberos token

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12076: SmeSessionTimeOutException: {0}

Cause: SME session timed out

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12077: Illegal Argument Exception: {0}

Cause: The specified object argument is illegal

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12078: Library Exception: {0}

Cause: An exception occurred while creating library instance

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12079: ResponseHandlerException: {0}

Cause: An exception occurred for the response handler in the library instance

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12080: RequestHandlerException: {0}

Cause: An exception occurred for the request handler in the library instance

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12082: Error while initializing session and user attribute value providers.

Cause: Unknown error while initializing attribute value providers

Action: Check logs and take appropriate action.
Level: 1

Type: WARNING

Impact: Other

FEDSTS-12083: Error while tokenizing attribute value expression.

Cause: Invalid attribute value expression.

Action: Fix the attribute value expression to contain valid tokens.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12084: Error while translating attribute value expression.

Cause: Invalid attribute value expression.

Action: Fix the attribute value expression to contain valid tokens.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12503: Certificate Exception: {0}.

Cause: A certificate exception occurred, indicating a problem with one of the certificates.

Action: Check logs and exception message for more information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-12523: Crypto Exception: {0}.

Cause: A crypto exception has occurred during token issuance.

Action: Check logs and exception message for more information.
Level: 1

Type: ERROR

Impact: Other

FEDSTS-13003: Remove operation not supported.

Cause: The Iterator method remove() was invoked, but is not supported by the implementation.

Action: Replace the remove operation with alternate remove option.
Level: 1

Type: ERROR

Impact: Programmatic

FEDSTS-13004: EntrySet operation not supported.

Cause: The SoftHashMap method entrySet() was invoked, but is not supported by the implementation.

Action: Replace the call to entrySet() with alternate option.
Level: 1

Type: ERROR

Impact: Programmatic

FEDSTS-13006: Internal Error: Unable to register {0} as a provider for {1}

Cause: Unable to register Discovery Provider.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: ERROR

Impact: Programmatic

FEDSTS-13009: Cannot have an empty response name.

Cause: Response name was empty.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13010: Cannot locate class with root name of {0}

Cause: Could not locate class.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13011: Deregistering object failed.

Cause: Deregistered object does not match expected object.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13013: Internal Server Error

Cause: Internal Server Error

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13014: Servlet cannot be configured.

Cause: Servlet configuration failed.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13017: Initializing {0}

Cause: An internal error has occurred.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Programmatic

FEDSTS-13022: Metric End event occured for event {0} before respective event start

Cause: End/Abort event occurred before respective start event

Action: Check the Oracle Identity Federation / Oracle Secure Token Service logs for more specific information.
Level: 1

Type: NOTIFICATION

Impact: Programmatic

FEDSTS-15002: Cannot find User for UserID {0} in User Data Store.

Cause: The user ID was incorrect or the user record does not exist.

Action: Verify that the user ID is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15003: No value in user record for NameIDPolicy requested: {0}

Cause: There was no value for the requested name identifier type.

Action: Verify that name identifier is correct and that the attribute for the requested name identifier exists.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15040: SSL client certificate required to access SOAP service URL

Cause: No SSL Certificate was presented when accessing the SOAP service.

Action: Contact the client to notify that an SSL Certificate is required when accessing the SOAP service.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15046: Unexpected confirmation method: {0} for message: {1}

Cause: Oracle Identity Federation / Oracle Secure Token Service did not recognize the specified confirmation.

Action: Check that the confirmation method included in the Assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15048: Unknown condition in assertion: {0}.

Cause: Oracle Identity Federation / Oracle Secure Token Service did not recognize the specified condition.

Action: Check that the condition included in the assertion is valid.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15049: The contents of the SOAP request body are null. Closing the connection.

Cause: The Oracle Identity Federation / Oracle Secure Token Service server encountered an error while trying to deserialize the incoming message.

Action: Check that the message is correctly formatted.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15052: A time value is invalid

Cause: A string was passed in as a time value that was in an invalid format.

Action: Verify that all of the time value attributes are in the correct format.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15056: Invalid version number: {0}

Cause: The version format was incorrect.

Action: Verify that the version format is correct. Version should consist of a major part and a minor part separated by a period.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15057: Invalid version: {0}, majorVersion={1}, minorVersion={2}

Cause: Either the major or the minor version was negative.

Action: Verify that both the major and minor versions are non-negative.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15058: Error while processing the SOAP envelope.

Cause: Oracle Identity Federation / Oracle Secure Token Service could not process the incoming SOAP envelope.

Action: Check that the SOAP envelope format is correct.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15060: Unknown message parameter: {0}

Cause: One of the message parameters was not recognized.

Action: Verify that all of the message parameter names are recognized by Oracle Identity Federation / Oracle Secure Token Service.
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15083: There is no value for a parameter.

Cause: Parameter was sent without a value.

Action: Ensure that the parameters are passed with valid value.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

FEDSTS-15084: The response handler expects an event response that implements Target.

Cause: EventResponse object was not of the type Target.

Action: Pass EventResponse object of the type Target to the response handler.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

FEDSTS-15085: Throwing a runtime exception.

Cause: An internal error has occurred.

Action: Contact Oracle Support Services to rectify the issue.
Level: 1

Type: INCIDENT_ERROR

Impact: Requests/Responses

FEDSTS-15098: Unknown condition ignored: {0}.

Cause: Peer provider sent a message which contains unknown conditions in the message.

Action: Check with the peer provider.
Level: 1

Type: WARNING

Impact: Requests/Responses

FEDSTS-15131: Certificate was missing when trying to verify digital signature.

Cause: Certificate missing when trying to verify incoming signature.

Action: Verify that the requester specified its identity when making the request, either in the message or by authenticating to the Oracle Identity Federation / Oracle Secure Token Service server via SSL or HTTP Basic Authentication
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15536: Certificate Validation failed for certificate {0}

Cause: The certificate could not be validated

Action: Check the certificate and/or add the necessary Trust Anchor
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15539: The partner identified by {0} is unknown

Cause: The referenced entity is not a partner

Action: Create a partner entry if necessary
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15540: The partner is not trusted: {0}

Cause: The partner is not marked as trusted

Action: Verify the configuration of the partner
Level: 1

Type: ERROR

Impact: Requests/Responses

FEDSTS-15542: The mapping of the AppliesTo element from the WS-Trust Request to a Relying Party Partner failed: could not map {0}

Cause: The location referenced in the AppliesTo element could not be mapped to Resource URL of one of the Relying Party Partners defined in Oracle Identity Federation / Oracle Secure Token Service

Action: If the location referenced in the AppliesTo element should have been mapped to a Relying Party Partner then verify that the Resource URLs defined for this Partner in Oracle Identity Federation / Oracle Secure Token Service are correct.
Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

FEDSTS-18003: Assertion is not signed.

Cause: The assertion was not signed.

Action: Verify that the assertion was signed.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18009: Provider is unknown: {0}

Cause: The provider is not known.

Action: Verify that the provider exists in the list of federations
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18026: Error while reading the client SSL certificate

Cause: Client SSL certificate is corrupt.

Action: Obtain a new client SSL certificate.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18034: Untrusted server certificate chain.

Cause: Certificate Authority certification keystore in JRE did not contain the Certificate Authority certificate.

Action: Add the Certificate Authority certificate of the LDAP server to the Certificate Authority certs keystore of the JRE.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18041: Illegal UTF encoding

Cause: The UTF encoding was not supported.

Action: Verify the UTF encoding to be a valid one.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18047: Certificate {0} is replaced with the certificate {1}.

Cause: Old certificate was replaced with the newer one.

Action: Ensure correct certificate is uploaded for normal functioning of the Oracle federation server.
Level: 1

Type: WARNING

Impact: Security

FEDSTS-18048: The certificate corresponding to the private key is expired: {0}

Cause: The certificate was expired.

Action: Use the certificate with the correct validity period.
Level: 1

Type: WARNING

Impact: Security

FEDSTS-18049: Public key algorithm is not known:{0}.

Cause: Public key algorithm was unknown.

Action: Use the correct certificate with the correct public key algorithm.
Level: 1

Type: WARNING

Impact: Security

FEDSTS-18050: User is not authenticated.

Cause: User was not authenticated.

Action: Login to the server using the correct user.
Level: 1

Type: WARNING

Impact: Security

FEDSTS-18055: Unknown pseudo-random number generator configured. Using Java default.

Cause: Default pseudo-random number generator configured is unknown.

Action: No Action.
Level: 1

Type: NOTIFICATION

Impact: Security

FEDSTS-18066: Authentication failed

Cause: The authentication process failed, the credentials could not be validated.

Action: Check the connection settings.
Level: 1

Type: WARNING

Impact: Security

FEDSTS-18073: An error occurred during a cryptographic operation: {0}

Cause: The Oracle Identity Federation / Oracle Secure Token Service encountered an error while invoking the crypto engine for signature creation/verification, encryption/decryption operations.

Action: Check the logs for more detailed error messages, and correct the problem related to the error.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18074: Signature verification failed for provider ID {0}

Cause: The signature might be have been spoofed.

Action: Contact Administrator to verify
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18075: Decryption operation failed for message sent by provider ID {0}

Cause: The message is not intended for Oracle Identity Federation / Oracle Secure Token Service.

Action: Contact Administrator to verify
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18076: Security services exception: {0}

Cause: An error occurred while verifying/signing/encrypting/decrypting a message.

Action: Please check previous log entries for more specific information.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18077: XML decryption error: EncryptedData element not found

Cause: The XML EncryptedData element was not found when trying to decrypt the incoming data.

Action: Check the message and contact the remote server administrator if necessary.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18078: XML decryption error: could not get the decryption secret key

Cause: The key to decrypt the EncryptedData element could not be retrieved.

Action: Check the message and contact the remote server administrator if necessary.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18079: The return URL could not be validated: {0}

Cause: The specified return URL could not be validated against the list of approved hostnames/domains.

Action: Check if the return URL points to a valid host name/domain, and update if necessary the list of approved host names/domains. If the return URL is not recognized or invalid, do not update the list of approved host names/domains.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18080: Could not retrieve key from the key store. Please verify that the key password is equal to the key store password.

Cause: Invalid key or key password is not equal to the key store password.

Action: Verify that the key is valid and the key password is equal to the key store password.
Level: 1

Type: ERROR

Impact: Security

FEDSTS-18081: Authentication Failed - HTTP Header not set in order to authenticate the user

Cause: The HTTP Header was not set in order to authenticate the user.

Action: Check the User's browser, Agent used in the deployment, the Oracle Identity Federation / Oracle Secure Token Service configuration and whether or not the user was authenticated by the Web Access Management
Level: 1

Type: ERROR

Impact: Security

FEDSTS-20000: Cannot open the key store.

Cause: Invalid or unsupported key store, or incorrect password. During installation, this error is expected.

Action: Verify that password is correct and the store is a valid PKCS #12 PFX wallet or Java KeyStore file. During installation, this error can be ignored.
Level: 1

Type: ERROR

Impact: Session

FEDSTS-20100: The Oracle Identity Federation / Oracle Secure Token Service transient data store cleanup process was unexpectedly terminated.

Cause: The cleanup process could not connect the Oracle Identity Federation / Oracle Secure Token Service transient data store, or an error occurred while destroying expired entries.

Action: Check the Oracle Identity Federation / Oracle Secure Token Service transient data store.
Level: 1

Type: ERROR

Impact: Threads

3 IDAAS-00001 to IDAAS-63011

IDAAS-00001: Cannot load the configuration file.

Cause: The configuration file location was invalid.

Action: Verify the location of the configuration file.
Level: 15

Type: ERROR

Impact: Other

IDAAS-00002: Configured security mechanism for endpoint :: "{0}" is "{1}".

Cause: None

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-00003: Trusted HTTP Header name :: "{0}" and value :: "{1}".

Cause: None

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-00004: Invalid security validator

Cause: No security validator.

Action: Check the configuration.
Level: 15

Type: ERROR

Impact: Other

IDAAS-00005: Security mechanism is null.

Cause: invalid configuration.

Action: Check configuration.
Level: 15

Type: ERROR

Impact: Other

IDAAS-00006: Service instance configuration not found

Cause: Service configuration not found for the given endpoint.

Action: Check the endpoint
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-00007: Error during configuration retrieval

Cause: Unable to retrieve configuration.

Action: Check configuration.
Level: 15

Type: ERROR

Impact: Other

IDAAS-00008: No shared secret in client configuration

Cause: Unable to find shared secret in client configuration

Action: Check the configuration
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-00009: Invalid JSON Syntax when using Jettison Utility to parse a payload

Cause: When JettisonUtil is used to parse a String containing invalid JSON syntax

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-00010: Encountered CSF Store operation error

Cause: Encountered CSF Store operation error

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-11001: Cannot load audit configuration.

Cause: The audit configuration was invalid.

Action: Verify the audit configuration.
Level: 15

Type: ERROR

Impact: Other

IDAAS-11002: Audit Event logging failed.

Cause: Exception occured while Audit Event Logging.

Action: Check the Exception message for the root cause.
Level: 15

Type: WARNING

Impact: Other

IDAAS-12001: Monitoring is disabled.

Cause: Either DMS is not available or Monitoring is disabled in config.

Action: Check if Monitoring is enabled in the config and verify DMS is available.
Level: 15

Type: WARNING

Impact: Other

IDAAS-12002: DMS is not available, monitoring will be disabled.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

IDAAS-12003: Monitoring has initialized successfully

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20001: Cache Info :: operation="{0}" paramName="{1}", paramDetail="{2}".

Cause: Displayed when the cache is operating.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20002: REST Services

Cause: Displayed when the cache is operating.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20003: REST Services deployed successfully

Cause: Displayed when the cache is operating.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20004: Client App Id is required.

Cause: Client App Id is null for the request

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-20005: OS Type is required.

Cause: OS Type is null for the request

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-20006: OS Version is required.

Cause: OS Version is null for the request

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-20007: Client SDK Version is required.

Cause: SDK Version is null for the request

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-20008: Service Domain not found.

Cause: Service Domain not found in the configuration

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-20009: OS Version or Client SDK Version not supported.

Cause: OS Version or Client SDK Version not supported

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-20010: No valid service found for the request.

Cause: No valid service found for the request

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-20011: SMTP Server Configuration is invalid

Cause: SMTP Server Configuration is invalid

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-20012: Wrongly formatted address is encountered

Cause: a wrongly formatted address is encountered during sending an email

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-20013: Invalid security credentials

Cause: invalid credentials.

Action: Check credentials.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20014: Failed in validating security credentials

Cause: security exception.

Action: Check configuration.
Level: 15

Type: ERROR

Impact: Other

IDAAS-20015: Failed in provider initialization

Cause: Incorrect configuration.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-20016: Provider initialization success

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20017: Invalid credential type is provided :: Credential Type "{0}"

Cause: Invalid credential Type.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20018: Invalid credential is provided

Cause: Invalid credential is provided.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20019: User is not found :: User "{0}"

Cause: User is not found.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20020: Invalid parameter is provided

Cause: Invalid parameter is provided

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20021: Operation is not supported

Cause: Operation is not supported

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20022: property is not set

Cause: property is not set

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20023: Resource Name is not found :: Resource Name "{0}"

Cause: Resource Name is not found

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-20024: Error during configuration retrieval

Cause: Unable to retrieve configuration.

Action: Check configuration.
Level: 15

Type: ERROR

Impact: Other

IDAAS-20025: Unsupported REST API Version

Cause: Client Request unsupported REST API Version.

Action: Check configuration.
Level: 15

Type: ERROR

Impact: Other

IDAAS-20026: No message is available from the underlying exception

Cause: No message is available from the underlying exception

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-20027: No error code is available from the underlying exception

Cause: No error code is available from the underlying exception

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-20028: No error code is available from the underlying exception, because the exception is not an "OICException"

Cause: No error code is available from the underlying exception, because the exception is not an "OICException"

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-20029: REST Server Internal Error

Cause: REST Server Internal Error

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-21001: More than 1 token service is configured in the same Service Domain.

Cause: More than 1 token service in the configuration for mobile Service Domain

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-21002: No token service found in the Service Domain.

Cause: No token service found in the Service Domain

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-21003: More than 1 user profile service is configured in the same Service Domain.

Cause: More than 1 user profile service in the configuration for mobile Service Domain

Action: None
Level: 15

Type: TRACE

Impact: Other

IDAAS-21009: Missing credential in the idaas authz header.

Cause: None

Action: None.
Level: 15

Type: WARNING

Impact: Other

IDAAS-21010: Failed in token validation :: Token "{0}"

Cause: Invalid or expired token.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21011: Token validation success

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21012: Failed in token creation :: User "{0}"

Cause: Invalid credential.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21013: Token creation success :: User "{0}"

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21014: Failed in token termination :: Token Value "{0}"

Cause: Invalid or expired token.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21015: Token termination success

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21016: Failed in token retrieval

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21017: Token retrieval success

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21018: Token invalid :: Token Value "{0}"

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21019: Token is expired :: Token Value "{0}"

Cause: Token is expired.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21020: Invalid token type is provided :: Token Type "{0}"

Cause: Invalid token type is provided.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21021: Failed in Access Token creation :: Token "{0}"

Cause: Invalid credential.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-21022: Missing request parameter :: Parameter "{0}"

Cause: None

Action: None.
Level: 15

Type: WARNING

Impact: Other

IDAAS-22001: Invalid format for basic credential

Cause: Invalid basic credential format.

Action: check credentials
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-22002: Authorization failed on resource "{0}" for "{1}"

Cause: Not enough permission on the resource.

Action: Check permission
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-22003: Authorization success

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-22004: Resource is not protected :: Resource "{0}"

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-23001: Invalid endpoint :: endpoint="{0}".

Cause: The rest service endpoint is invalid.

Action: Verify the endpoint.
Level: 15

Type: WARNING

Impact: Other

IDAAS-23002: Unable to find client configuration

Cause: Unable to find client configuration

Action: Check the request
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-23003: Client basic credentias validated

Cause: None

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-23004: Client trusted http header validated

Cause: None

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24001: Resource is not found :: Resource Name "{0}"

Cause: Resource is not found

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24002: Resource is already Used

Cause: Resource is already Used

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24003: Resource method is not allowed

Cause: Resource method is not allowed

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24004: Resource has invalid attributes

Cause: Resource has invalid attrs

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24005: IDS is throwing exception

Cause: IDS is throwing exception

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24006: Bad Search Filter

Cause: Bad Search Filter

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24007: Invalid scope :: Scope Name "{0}"

Cause: Invalid Scope

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24008: Relationship is not found

Cause: Relationship is not found

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24009: search Filter is not found

Cause: searchFilter is not found

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24010: Authorization is failed because adminGroup is not found

Cause: adminGroup is not found

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24011: Authorization is failed because the adminGroup is invalid :: adminGroup "{0}"

Cause: adminGroup is invalid

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24012: Authorization is failed because the user is not authenticated :: user "{0}"

Cause: user is invalid

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24013: Authorization is failed because the authenticate user is not a part of adminGroup :: user "{0}"

Cause: An authenticate user does not have a permission to perform a particular User Profile operation

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24014: Access Control is failed

Cause: Access Control is failed

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-24015: User doesn't have sufficient access rights to perform the operation

Cause: This IDS AuthorizationException is thrown when user doesn't have sufficient access rights to perform the operation

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-25001: JAXRS endpoint is called, no args in call.

Cause: Displayed when the Jax-RS endpoint is called.

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-25002: JAXRS endpoint is called, parameters="{0}".

Cause: Displayed when the Jax-RS endpoint is called containing parameters

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-30001: Proxy host is defined: {0}, but unable to get the proxy protocol.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30002: Proxy protocol and host are defined: {0}, {1}. But unable to get the proxy port.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30003: Unable to setup proxy.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30004: Security Mechanism not supported yet: SAE, TAP

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30005: Unable to get a response, error code: {0}

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30006: Unable to decrypt JSON response.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30007: An error may occurred during this class creation, the IDP list has not been created

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30008: The provided crypto type [{0}] is not supported. Shall be {1} or {2}.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30009: Unable to initiate the SAE encryption using the given configuration.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30010: Password cannot be empty for user: {0}.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30011: Connection with RPfC server fails with HTTP error: {0}.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30012: Unable to decode using the SAE library.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30013: Invalid URL: {0}.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30014: Unable to encode using the SAE library.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30015: The configuration properties shall not be null or empty.

Cause: Invalid argument for properties in constructor.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30016: Unable to get System Configuration for attribute named {0} or {1}.

Cause: Invalid argument for properties in constructor.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30017: Application ID shall not be null or empty.

Cause: Invalid argument for properties in constructor.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30018: The server has not found anything matching the Request-URI: {0}.

Cause: Invalid argument for properties in constructor.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-30019: Unable to retrieve the IDP lists using the given applicationID : {0}.

Cause: Invalid argument for properties in constructor.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-40001: Cannot load the configuration file.

Cause: The configuration file location was invalid.

Action: Verify the location of the configuration file.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40002: Application is : "{0}"

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40003: Tap token in RequestContextTap : "{0}"

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40004: Parsed TAP token toString() : "{0}"

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40005: TAP Keystore initialized

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40006: Exception in processRequest method

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40007: Found tokenValue : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40008: Redirecting to : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40009: tokenservice returned null, local authentication failed

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40010: Request Parameters : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40011: Username and/or password is empty. Please enter a value and try again.

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40012: User created : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40013: User not created : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40014: {0} is added to provider map

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40015: {0} does not have contract implementation for {1}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40016: The user not found having attribute : {0} with value : {1}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40017: Exception in user registration

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40018: Exception in user lookup

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40019: Exception in protocol handler of invokeAuthnRequest

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40020: RP Cache Store initialized

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40021: Deserialized Request Context : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40022: Deserialized object string representation : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40023: Deserialized string set : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40024: Successfully wrote all elements of Request Context : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40025: Serialized string set : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40026: Returning false for nonce : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40027: Returning true for nonce : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40028: Request Unauthorized. Credentials did not match.

Cause: Security Mechanism validation failed.

Action: Check security credentials.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40029: Request Unauthorized. Credentials not found.

Cause: Security Mechanism validation failed.

Action: Check security credentials.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40030: Request Unauthorized. Credentials invalid

Cause: Security Mechanism validation failed.

Action: Check security credentials.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40031: Failed to create session

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-40032: Could not find shared secret.

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-40033: SAE library error while verifying SAE Token

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-40034: SAE library error while generating SAE Token

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-40035: saeToken parameter is null

Cause: Exception occurred.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

IDAAS-40036: Personal Information

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40037: User Name *

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40038: First Name *

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40039: Last Name *

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40040: Email *

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40041: Location Information

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40042: Location

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40043: Timezone

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40044: Password Information

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40045: Choose a Password *

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40046: Re-enter Password *

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40047: HTTP request details : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-40048: HTTP response error details : {0}

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40049: OIC component disabled

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40050: Request context is null

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40051: There is an error while executing default session contract

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40052: Request ID parameter is null.

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40053: Error while redirecting as there is no url and request params present

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40054: Error while checking integrity of user registration data

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40055: No user registration data received from registration page

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40056: No read-only user registration data token received from registration page

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-40057: Error while validating read-only user registration data token

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-41001: Association is expired

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-41002: OpenID Provider Response : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-41003: Returning OpenID Context : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-41004: Cached openid context for Request Id : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-41005: There is an error with OpenID Yadis protocol discovery

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-41006: OpenID Yadis endpoint is null

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-41007: There is an error with OpenID provider response's signature verification

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-41008: There is an error with local signature generation while validating OpenID provider's response

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42001: Invalid OAuth provider : {0}

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42002: Redirection to following URL : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-42003: Authorization code is null

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42004: Access token not found : {0}

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42005: Error while getting profile from : {0}

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42006: Failed to parse the user profile json : {0}

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42007: OAuth provider user profile response : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-42008: OAuth access token json : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-42009: OAuth access token sent to return URL: {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-42010: Unexpected value in accesstoken response

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42011: OAuth accesstoken : {0} with expiry value : {1}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-42012: OAuth token cached in AccessTokenCache with context (AppID, selectedIdp, scope, userID): {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-42013: OAuth accesstoken cached with : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-42014: Returning OAuth Context : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-42015: Cached oauth context for Request Id : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-42016: OAuth AccessToken Sample JSON

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-42017: OAuth access token json response

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-42018: Error while getting OAuth version 1.0 access token

Cause: Exception occurred.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42019: Error while getting OAuth version 1.0 request token

Cause: Exception occurred.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42020: Unable to get the server time sync parameter: {0}

Cause: Bad configuration, this paramter shall be an integer.

Action: review the configuration.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42021: OAuth request token is null

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42022: OAuth consumer key and/or secret null

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42023: There is an error while creating JSON representation of OAuth access token.

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-42024: Invalid OAuth access token value.

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-43001: There is an error while executing OAM session contract

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-43002: TAPToken of OAM submit url is null

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-44001: IDP provider response did not have the state of the RP

Cause: Request ID missing.

Action: Check parameters to createSession ().
Level: 15

Type: ERROR

Impact: Other

IDAAS-44002: Post IDP Selector parameters : {0}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-44003: The Post IDP selector parameters are null.

Cause: none

Action: none
Level: 15

Type: ERROR

Impact: Other

IDAAS-44004: There is an error while fetching user attributes from the identity provider

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-44005: There is an error while authenticating user with the identity provider

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-44006: There is an error while getting access token for the user from the identity provider

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-44007: Invalid identity provider implementation : {0}

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-44008: Unable to instantiate identity provider implementation

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-45001: applicationID query parameter is null

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-45002: application: {0} : protocol : {1}

Cause: None.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

IDAAS-45003: No identity providers found for application : {0}

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-45004: applicationID query param is null

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-45005: Exception occurred while retrieving identity providers

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-45006: Could not find application : {0}

Cause: Invalid application name specified.

Action: Check application parameter.
Level: 15

Type: ERROR

Impact: Other

IDAAS-45007: Could not authenticate for application : {0} with username : {1}

Cause: Invalid combination of application, username and password (HTTP BASIC).

Action: Check application, username and password.
Level: 15

Type: ERROR

Impact: Other

IDAAS-45008: Mobile application request id parameter is null.

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-45009: Mobile application return payload encryption data error.

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-45010: Mobile application return url is null.

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-45011: Error while redirecting to mobile application return url.

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-45012: There is an error while creating JSON response for mobile applications.

Cause: None.

Action: None.
Level: 15

Type: ERROR

Impact: Other

IDAAS-61001: Required Attribute "{0}" is not found in "{1}".

Cause: Displayed when a required attribute in DeviceProfile for Plug-in is missing

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-61002: Attribute "{0}" in "{1}" should be of type "{2}", instead of "{3}".

Cause: Displayed when an attribute in DeviceProfile for Plug-in is associated with a mismatched type

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-61003: Hardware Id "{0}" should be of string type.

Cause: Displayed when an attribute in DeviceProfile for Plug-in is associated with a mismatched type

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-61004: Handle "{0}" should be of string type.

Cause: Displayed when an attribute in DeviceProfile for Plug-in is associated with a mismatched type

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-61005: "{0}" should be of map / JSON-Object type.

Cause: Displayed when an attribute in DeviceProfile for Plug-in is associated with a mismatched type

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-61006: Invalid JSON in Multi-Step Authentication Handle.

Cause: Displayed when data stored in OIC Multi-Step Authentication handle contains invalid JSON syntax

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-61007: Error during sending an email when OTPByEmail Challenge

Cause: Error during sending an email when OTPByEmail Challenge

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-61008: Invalid geolocation string: {0}

Cause: Invalid geolocation string

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-61009: The Denied Action is triggered

Cause: The Denied Action is triggered

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-61010: The Challenge Action is triggered

Cause: The Challenge Action is triggered

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-61011: The Wipe Out Action is triggered

Cause: The Wipe Out Action is triggered

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-61012: SMTP Security Type "{0}" is not supported

Cause: SMTP Security Type is not supported

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-62001: Challenge mechanism has not been set up for user "{0}".

Cause: Displayed by OAAM-OIC Security Plugin when Challenge question is not set up properly for a user

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-62002: Challenge mechanism has not been set up for user "{0}". Please visit: {1}

Cause: Displayed by OAAM-OIC Security Plugin when Challenge question is not set up properly for a user

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-62003: What is your OTP Code?

Cause: Displayed question by OAAM-OIC Security Plugin when OTP Challenge

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-62004: This {0} user id is not known to OAAM server.

Cause: This user id is not known to OAAM Server

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-62005: Black Listed Mobile Device Rule is triggered

Cause: Black Listed Mobile Device Rule is triggered by OAAM Server

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-62006: Lost or Stolen Device Rule is triggered

Cause: Lost or Stolen Device Rule is triggered by OAAM Server

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-62007: This {0} user id is not known to OAAM server. Please visit: {1}

Cause: This user id is not known to OAAM Server

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-62008: OIC-OTP Code

Cause: OTP Subject when OAAM-OIC Security Plugin is sending an email/SMS for OTP challenge

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-62009: OIC OTP Code :

Cause: OTP Body Text when OAAM-OIC Security Plugin is sending a SMS/ an Email for OTP challenge

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-62010: UMS Client Configuration is missing

Cause: UMS Client Configuration is missing

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-62011: Error During Sending SMS Using UMSClient

Cause: Error During Sending SMS using UMSClient

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-63001: Mobile SSO Agent credential is missing

Cause: Mobile SSO Agent crediential is missing

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-63002: Client application identity header refers to a non-agent app: {0}

Cause: Client application identity header refers to a non-agent app

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-63003: Client application being registered "{0}" participates in SSO, but not an agent app. Hence, it cannot register directly to OIC Server.

Cause: Client application being registered participates in SSO, but not an agent app. Hence, it cannot register directly to OIC Server.

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-63004: Invalid Credential during Mobile operation

Cause: Generic Invalid Credential

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-63005: User token is not enough; uid+password is needed for authentication to add a new business app or register a mobile agent app

Cause: user token is not enough; uid+password is needed for authentication to add a new business app or register a mobile agent app

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-63006: Internet Identity (Relying party for cloud) based User Token is expected.

Cause: Internet Identity (Relying party for cloud) based User Token is expected.

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-63007: Application {0} cannot be used to register Application {1}, due to SSO Priorities setting

Cause: When Application-X cannot be used to register Application-Y, due to SSO Priorities setting

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-63008: Client application "{0}" referred in identity header participates in SSO, but it is not an agent app. Hence, it cannot acquire token of {1} type from OIC Server directly.

Cause: Client application referred in identity header participates in SSO, but it is not an agent app. Hence, it cannot acquire (user) token from OIC Server directly.

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-63009: Missing "clientId" field in Create Client Registration Request

Cause: Missing "clientId" field in Create Client Registration Request

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-63010: Client application "{0}" does not participate Single-Sign-On. It can register itself directly to OIC Server. It does not need the Client Registration Handle of another app in the HTTP header.

Cause: Client application does not participate Single-Sign-On. It can register itself directly to OIC Server. It does not need the Client Registration Handle of another app in the HTTP header.

Action: None.
Level: 15

Type: TRACE

Impact: Other

IDAAS-63011: Missing device profile attribute(s): {0}

Cause: Missing device profile attribute(s)

Action: None.
Level: 15

Type: TRACE

Impact: Other

4 OAAM-00000 to OAAM-94100

OAAM-00000: Invalid message.

Cause: Unable to find message definition.

Action: Report to administrator.
Level: 1

Type: ERROR

Impact: Process

OAAM-00001: A system internal error occurred. The system cannot complete the operation at this time.

Cause: A system internal error occurred. The error may be the result of a constraint or the unavailability of resources.

Action: Try again. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-00002: The operation is not allowed.

Cause: The user may not have sufficient privileges.

Action: Report to the administrator about insufficient privileges.
Level: 1

Type: ERROR

Impact: Process

OAAM-00003: Database error.

Cause: The database may not be available.

Action: Try again. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-00004: Insufficient context data. Required: {0}.

Cause: The expected context information is not provided.

Action: Report to the administrator about the insufficient context data.
Level: 1

Type: ERROR

Impact: Process

OAAM-00005: Database error. Exception message is {0}.

Cause: The error may have resulted from the unavailability of the database or a database querying exception.

Action: Report the database error message to the administrator.
Level: 1

Type: ERROR

Impact: Process

OAAM-01001: Property name is required.

Cause: The property name is missing from the data.

Action: Make sure that the property name is provided for the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-01002: Property value is required.

Cause: The property value is missing from the data.

Action: Make sure the property value is provided for the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-01003: Property with name {0} already exists.

Cause: The property with the name already exists.

Action: Use a different property name and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-01004: Property with name {0} does not exist.

Cause: The property with the name was not found in the system.

Action: Make sure the property name provided is correct and then retry the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-01005: Property search query is required to search properties.

Cause: The property search query was not provided for the search.

Action: Make sure that the valid property search query is provided.
Level: 1

Type: ERROR

Impact: Process

OAAM-01006: Cannot delete property {0} because it is a {1} type of property.

Cause: Property cannot be deleted. System- and file-based properties cannot be deleted. Only properties saved in the database can be deleted.

Action: System-based properties cannot be deleted. Only properties saved in the database and files can be deleted.
Level: 1

Type: ERROR

Impact: Process

OAAM-01007: Cannot modify property {0} because it is a {1} type of property.

Cause: Property cannot be changed. System-based properties cannot be changed. Only properties saved in the database and files can be changed.

Action: System-based properties cannot be changed. Only properties saved in the database and files can be changed.
Level: 1

Type: ERROR

Impact: Process

OAAM-01101: Object type was not specified for finding usage.

Cause: The required object type was not specified for finding usage.

Action: The object type must be specified to find the usage information. Specify non-null integer value and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-01102: Object unique key was not specified for finding usage.

Cause: The required object unique key (primary key) was not specified for finding usage.

Action: The object unique (primary) key must be specified to find the usage. Specify a non-null long value and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-01103: Usage cannot be computed for object type {0}.

Cause: Usage API supports certain types of objects. The specified object is not specified by the Usage API.

Action: Specify the object type, which can be referenced by other objects in the system.
Level: 1

Type: ERROR

Impact: Process

OAAM-01104: Usage information for the primary object of type {0} with a unique ID of {1} cannot be determined.

Cause: Usage API is trying to find the usage of an object that does not exist.

Action: A unique ID of the object was provided, which was not found in the system. Make sure that the unique ID and the object are correct and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-10000: Valid Case ID is required.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-10001: Case {0} not found

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-10002: No user {0}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-10004: User is blocked

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-10005: No questions registered {0} {1}

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-10006: Invalid application {0} and login {1} combination.

Cause: Combination may be incorrect or user name is used in place of the login name.

Action: Report to administrator.
Level: 1

Type: ERROR

Impact: Process

OAAM-10007: Challenge questions are already reset.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-10008: Challenge Question Set is already reset.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-10009: End Date is required.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-10010: End Date should be in future.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-10011: Valid Application name or user group name is required.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-10301: Note cannot be null or empty.

Cause: Note cannot be null or empty string.

Action: Provide a valid note.
Level: 1

Type: ERROR

Impact: Process

OAAM-10302: Closed case {0} cannot be escalated.

Cause: Closed case {0} cannot be escalated.

Action: Reopen the closed case before trying to escalate it.
Level: 1

Type: ERROR

Impact: Process

OAAM-10303: The Case {0} is not a CSR case; therefore, it cannot be escalated.

Cause: The Case {0} is not a CSR case; therefore, it cannot be escalated.

Action: The case type for case {0} should be changed to CSR for escalation.
Level: 1

Type: ERROR

Impact: Process

OAAM-10304: Query cannot be null.

Cause: Query cannot be null.

Action: Provide a valid query object.
Level: 1

Type: ERROR

Impact: Process

OAAM-10305: No query expression found.

Cause: No query expression found.

Action: Provide the required parameters for the query expression.
Level: 1

Type: ERROR

Impact: Process

OAAM-10306: No records found.

Cause: No records found.

Action: Change the criteria before performing the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-10307: No linked sessions found.

Cause: No linked sessions found.

Action: For the given case, no linked sessions were found.
Level: 1

Type: ERROR

Impact: Process

OAAM-10308: No sessions to link.

Cause: No sessions to link.

Action: Provide sessions to link.
Level: 1

Type: ERROR

Impact: Process

OAAM-10309: No sessions to unlink.

Cause: No sessions to unlink.

Action: Provide sessions to unlink.
Level: 1

Type: ERROR

Impact: Process

OAAM-11111: User not authorized to access the method {0}.

Cause: User is not authorized to access the method {0}.

Action: Retry accessing the method {0} with valid authorization.
Level: 1

Type: ERROR

Impact: Process

OAAM-11112: Session ID of Admin users is required for case action.

Cause: Session ID was not provided for performing the case action.

Action: Retry the same case action and provide the valid Admin user Session ID for that API call.
Level: 1

Type: ERROR

Impact: Process

OAAM-11113: Choose the action template for creating action instance.

Cause: Action template was not provided for performing the action instance creation.

Action: Retry the same action instance creation by choosing valid action template.
Level: 1

Type: ERROR

Impact: Process

OAAM-11114: Subaction ID is required for case action.

Cause: Subaction was not provided for performing the case action.

Action: Retry the same case action and provide the valid Subaction ID for that API call. The Subaction ID is the case action enumeration.
Level: 1

Type: ERROR

Impact: Process

OAAM-11115: New status required for case change status action.

Cause: New status was not provided for performing the change status case action.

Action: Retry the same case action and provide the valid new status (Integer object) for that API call. New status is the case status enumeration.
Level: 1

Type: ERROR

Impact: Process

OAAM-11116: Reopen the closed case before trying to edit: Case ID {0}

Cause: The case is in the Closed state. In this state, the case disposition or expiration cannot change.

Action: The case is closed. In the Closed state, the disposition, severity, or expiration cannot be changed. To change these attributes, change the status of the case along with new severity, expiration time, or disposition
Level: 1

Type: ERROR

Impact: Process

OAAM-11117: Case with ID {0} is expired. It cannot be edited.

Cause: The case is in the Expired state. In this state, the case disposition or expiration date cannot be changed.

Action: The case is expired, and in the Expired state, its disposition, severity, or expiration cannot be changed. Reopen the case first and then try this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-11120: Case reset action cannot be completed because: {0}.

Cause: Case reset action cannot be performed because of the reason provided by the error message.

Action: Retry the same case action after fixing the issue.
Level: 1

Type: ERROR

Impact: Process

OAAM-11121: Challenge question-related case action cannot be performed because: {0}.

Cause: Challenge question-related case action cannot be performed because of the reason provided by the error message.

Action: Retry the same case action after fixing the issue.
Level: 1

Type: ERROR

Impact: Process

OAAM-11122: The customer's registration profile is not active and hence cannot be reset.

Cause: The customer's registration profile have already been reset.

Action: Cannot reset customer's registration profile since they are not active.
Level: 1

Type: ERROR

Impact: Process

OAAM-11123: Cannot reset user's image, as it is not set.

Cause: User does not have the image set.

Action: Cannot reset the user's image because the user is not registered or the image is not active for the user.
Level: 1

Type: ERROR

Impact: Process

OAAM-11124: Cannot reset the user's phrase, as it is not set.

Cause: The user does not have a phrase set.

Action: Cannot reset the user's phrase because either the user is not registered or the phrase is not active for the user.
Level: 1

Type: ERROR

Impact: Process

OAAM-11125: OTP reset action cannot be performed with cases that are not CSR cases.

Cause: For OTP reset actions that are performed with cases, the case has to be a CSR case. OTP reset cannot be performed with a case of any other type.

Action: Create a CSR case for the user and then try to do the OTP-related resets.
Level: 1

Type: ERROR

Impact: Process

OAAM-11126: OTP reset action cannot be performed with case in an incorrect state.

Cause: For OTP reset actions that are performed with cases, the case has to be in the correct state. An OTP reset cannot be performed with a case in the Closed, Escalated, or Expired state.

Action: Change the state of the case to Open, New, or Pending and then retry the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-11127: OTP reset profile attempted for user who does not have OTP profile enabled.

Cause: The user's OTP profile is not enabled. For such users, the OTP profile reset cannot be performed.

Action: Make changes to the user's preferences to register the OTP profile and then try this operation again.
Level: 1

Type: ERROR

Impact: Process

OAAM-11129: OTP reset keypad attempted for user who does not have OTP keypad enabled.

Cause: The user's OTP keypad is not enabled. For such users, the OTP keypad reset cannot be performed.

Action: Make the changes to the users preferences to register the OTP keypad and then try this operation again.
Level: 1

Type: ERROR

Impact: Process

OAAM-11130: Authentication pad is already reset.

Cause: Authentication pad is already reset.

Action: No action required to reset.
Level: 1

Type: ERROR

Impact: Process

OAAM-11131: OTP failure counter for user is already in reset state. It may be possible that the user does not OTP enabled.

Cause: The user's OTP failure counter is already at zero. It is already in reset state. For such users, an OTP failure counter reset cannot be performed.

Action: Make sure that the user is registered for OTP and that the OTP failure counter is not at zero.
Level: 1

Type: ERROR

Impact: Process

OAAM-11132: OTP reset cannot be performed at this time because of an error. Try the reset again.

Cause: The OTP reset operation experienced a system error. Try the operation again.

Action: The OTP reset encountered an error. Make sure the user is registered for OTP and try the operation again.
Level: 1

Type: ERROR

Impact: Process

OAAM-11133: Access to link specified sessions to case is denied.

Cause: Attempt was made to link the sessions of some users for which the agent does not have access.

Action: Add the administrative user to the user group in the security set up for the OAAM administrative application.
Level: 1

Type: ERROR

Impact: Process

OAAM-11134: User does not access to create a case for user belonging to user group {0}.

Cause: Attempt was made to create a case for user belonging to the user group for which the administrative user does not have access.

Action: Add the administrative user to the user group in the security set up for the OAAM administrative application.
Level: 1

Type: ERROR

Impact: Process

OAAM-15001: Enter Organization ID and User name, or only User ID.

Cause: A combination of Organization ID and User name or User ID are allowed.

Action: Enter Organization ID and User name, or User ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-15002: Organization ID is required.

Cause: Organization ID is not entered.

Action: Enter Organization ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-15100: An attempt was made to change the status of expired cases. Select an extension duration to continue.

Cause: The status of expired cases cannot be changed.

Action: Select an extension duration so that the cases are no longer expired. Then, change the status.
Level: 1

Type: ERROR

Impact: Process

OAAM-15101: An attempt was made to extend the expiration of a closed case. Select a status other than close to continue.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-20000: Policy name cannot be null or empty.

Cause: Policy name cannot be null or empty.

Action: Provide a valid policy name.
Level: 1

Type: ERROR

Impact: Process

OAAM-20001: Policy weight must be between {0} and {1}.

Cause: Policy weight must be between {0} and {1}.

Action: Ensure that the policy weight is between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20002: Policy description cannot be null or empty.

Cause: Policy description cannot be null or empty.

Action: Provide a valid policy description.
Level: 1

Type: ERROR

Impact: Process

OAAM-20003: A policy with name {0} already exists.

Cause: A policy with name {0} already exists.

Action: A policy with name {0} exists. Use a different name.
Level: 1

Type: ERROR

Impact: Process

OAAM-20004: Policy ID cannot be null.

Cause: Policy ID cannot be null.

Action: Provide a non-null Policy ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20005: Policy with Policy ID {0} does not exist.

Cause: Policy with Policy ID {0} does not exist.

Action: Provide a valid Policy ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20009: Rule ID cannot be null.

Cause: Rule ID cannot be null.

Action: Provide a non-null Rule ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20010: Rule with the given ID not found.

Cause: Rule with the given ID not found.

Action: Provide a valid Rule ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20011: Profile rule map for the given Map ID not found.

Cause: Profile rule map for the given Map ID not found.

Action: Provide a valid profile rule Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20012: Profile for the given Map ID not found.

Cause: Profile for the given Map ID not found.

Action: Provide a valid Map ID with profile.
Level: 1

Type: ERROR

Impact: Process

OAAM-20013: Profile Rule Map ID cannot be null.

Cause: Profile Rule Map ID cannot be null.

Action: Provide a non-null Profile Rule Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20014: Rule Condition Map ID cannot be null.

Cause: Rule Condition Map ID cannot be null.

Action: Provide a non-null Rule Condition Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20015: Rule parameter value not found.

Cause: Rule parameter value not found.

Action: Provide a valid Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20016: Rule parameter not found.

Cause: Rule parameter not found.

Action: Provide a valid Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20017: The following policies depend on some of the policies being deleted: {0}.

Cause: The following policies depend on some of the policies being deleted: {0}.

Action: Remove the dependency. The policies cannot be deleted until the dependency is removed.
Level: 1

Type: ERROR

Impact: Process

OAAM-20018: Rule parameter value was not found for the given rule parameter. The rule may not work as expected unless the error is fixed.

Cause: Rule parameter value was not found for the given rule parameter.

Action: When a rule is added to a policy, the value of each rule parameters is kept. The system was not able to find a corresponding value for the rule parameter in the policy data. Verify the rule and its details. Make sure the migration had no errors if this rule had been migrated from the previous release.
Level: 1

Type: ERROR

Impact: Process

OAAM-20019: Rule name cannot be null.

Cause: Rule name cannot be null.

Action: Provide a valid rule name.
Level: 1

Type: ERROR

Impact: Process

OAAM-20020: Rule description cannot be null.

Cause: Rule description cannot be null.

Action: Provide a valid rule description.
Level: 1

Type: ERROR

Impact: Process

OAAM-20021: Rule score must be between {0} and {1}.

Cause: Rule score must be between {0} and {1}.

Action: Provide a rule score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20022: Rule weight must be between {0} and {1}.

Cause: Rule weight must be between {0} and {1}.

Action: Provide a rule weight between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20023: Minimum device score must be between {0} and {1}.

Cause: The minimum device score must be between {0} and {1}.

Action: Provide a minimum device score between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20024: Maximum device score must be between {0} and {1}.

Cause: The maximum device score must be between {0} and {1}.

Action: Provide a maximum device score between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20025: Maximum device score must not be less than the minimum device score.

Cause: The maximum device score must not be less than the minimum device score.

Action: Provide a maximum device score that is more than or equal to the minimum device score.
Level: 1

Type: ERROR

Impact: Process

OAAM-20026: Minimum country score must be between {0} and {1}.

Cause: Minimum country score must be between {0} and {1}.

Action: Provide a minimum country score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20027: Maximum country score must be between {0} and {1}.

Cause: Maximum country score must be between {0} and {1}.

Action: Provide a maximum country score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20028: Maximum country score must not be less than minimum country score.

Cause: Maximum country score must not be less than minimum country score.

Action: Provide a maximum country score that is more than or equal to the minimum country score.
Level: 1

Type: ERROR

Impact: Process

OAAM-20029: Minimum state score must be between {0} and {1}.

Cause: Minimum state score must be between {0} and {1}.

Action: Provide a minimum state score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20030: Maximum state score must be between {0} and {1}.

Cause: Maximum state score must be between {0} and {1}.

Action: Provide a maximum state score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20031: Maximum state score must not be less than the minimum state score.

Cause: Maximum state score must not be less than the minimum state score.

Action: Provide a maximum state score that is more than or equal to the minimum state score.
Level: 1

Type: ERROR

Impact: Process

OAAM-20032: Minimum city score must be between {0} and {1}.

Cause: Minimum city score must be between {0} and {1}.

Action: Provide a minimum city score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20033: Maximum city score must be between {0} and {1}.

Cause: Maximum city score must be between {0} and {1}.

Action: Provide a maximum city score value between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20034: Maximum city score must not be less than the minimum city score.

Cause: Maximum city score must not be less than the minimum city score.

Action: Provide a maximum city score that is more than or equal to the minimum city score.
Level: 1

Type: ERROR

Impact: Process

OAAM-20035: A rule with name {0} already exists in this policy.

Cause: A rule with name {0} already exists in this policy.

Action: Provide a different rule name.
Level: 1

Type: ERROR

Impact: Process

OAAM-20036: Policy rule map with ID {0} does not exist.

Cause: Policy rule map with ID {0} does not exist.

Action: Create the appropriate policy-rule mapping.
Level: 1

Type: ERROR

Impact: Process

OAAM-20037: Condition ID cannot be null.

Cause: Condition ID cannot be null.

Action: Provide a valid Condition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20038: Condition with Condition ID {0} does not exist.

Cause: Condition with Condition ID {0} does not exist.

Action: Provide a valid Condition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20039: {0} is not a valid run mode.

Cause: {0} is not a valid run mode.

Action: Provide a valid run mode.
Level: 1

Type: ERROR

Impact: Process

OAAM-20040: {0} is not a valid policy type.

Cause: {0} is not a valid policy type.

Action: Provide a valid policy type.
Level: 1

Type: ERROR

Impact: Process

OAAM-20041: Select checkpoint.

Cause: Select checkpoint.

Action: Provide a valid checkpoint.
Level: 1

Type: ERROR

Impact: Process

OAAM-20042: Destination policy cannot be the same as the source policy.

Cause: The destination policy cannot be the same as the source policy.

Action: Provide a destination policy that is different from the source policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20043: Override with Override ID {0} does not exist.

Cause: Override with Override ID {0} does not exist.

Action: Provide a valid Override ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20044: Override with Override ID {0} does not belong to Policy ID {1}.

Cause: Override with Override ID {0} does not belong to Policy ID {1}.

Action: Provide an Override ID that belongs to the specified policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20045: Override ID cannot be null or empty.

Cause: Override ID cannot be null or empty.

Action: Provide a valid Override ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20046: Column ID cannot be null or empty.

Cause: Column ID cannot be null or empty.

Action: Provide a valid Column ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20047: Rule set result with Column ID {0} does not belong to Policy ID {1}.

Cause: Rule set result with the Column ID {0} does not belong to the Policy ID {1}.

Action: Provide a Column ID that belongs to the specified policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20048: The provided overrides set is not complete for this policy.

Cause: The provided ordered Override IDs array does not contain all the Override IDs for the policy.

Action: Provide an array that has all the Override IDs for the policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20049: Override cannot be added for policy with Policy ID = {0} since no rules have been added to the policy.

Cause: Override cannot be added for policy with Policy ID = {0} since no rules have been added to the policy.

Action: For adding override the policy should have a rule.
Level: 1

Type: ERROR

Impact: Process

OAAM-20050: Condition ID list provided is null or empty.

Cause: Condition ID list provided is null or empty.

Action: Provide a non-null and non-empty list.
Level: 1

Type: ERROR

Impact: Process

OAAM-20051: Rule ID is null or rule for the given ID not found.

Cause: Rule ID is null or rule for the given ID not found.

Action: Provide a valid non-null rule.
Level: 1

Type: ERROR

Impact: Process

OAAM-20052: Rule condition for the given Rule Condition ID not found.

Cause: Rule condition for the given Rule Condition ID not found.

Action: Provide a valid and existing Rule Condition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20053: Policy Rule Map cannot be null.

Cause: Policy Rule Map cannot be null.

Action: Provide a non-null Policy Rule Map.
Level: 1

Type: ERROR

Impact: Process

OAAM-20054: Number of conditions does not match the number of conditions that exists.

Cause: Number of conditions does not match the number of conditions that exists.

Action: Provide the same number as the conditions available.
Level: 1

Type: ERROR

Impact: Process

OAAM-20055: Condition Map provided does not exist.

Cause: Condition Map provided does not exist.

Action: Provide a valid and existent Condition Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20056: Group is already linked and cannot be linked again.

Cause: Group is already linked and cannot be linked again.

Action: Provide a valid and unlinked group for linking.
Level: 1

Type: ERROR

Impact: Process

OAAM-20057: Group ID cannot be null.

Cause: Group ID cannot be null.

Action: Provide a valid and non-null Group ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-20058: Some groups are not linked; therefore, they cannot be unlinked.

Cause: Some of the groups are not linked; therefore, they cannot be unlinked.

Action: Provide only linked groups for unlinking.
Level: 1

Type: ERROR

Impact: Process

OAAM-20059: The condition type for condition {0} is not compatible with the checkpoint for policy {1}.

Cause: The condition type for condition {0} is not compatible with the checkpoint for policy {1}.

Action: Provide a condition where the condition type is compatible with the checkpoint of the policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20060: The condition, {0}, being deleted is associated with one or more policies; therefore, it cannot be deleted.

Cause: The condition, {0}, being deleted is associated with one or more policies; therefore, it cannot be deleted.

Action: Remove the condition from the policies before deleting the condition.
Level: 1

Type: ERROR

Impact: Process

OAAM-20061: The policy type and checkpoint for the policy {0} do not match that of the parent policy {1}.

Cause: The policy type and checkpoint for the policy {0} do not match with that of the parent policy {1}.

Action: Ensure that the policy type and checkpoint for the child policy is the same as that of the parent policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20062: Score must be between {0} and {1}.

Cause: The score must be between {0} and {1}.

Action: Provide a score between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-20063: {0} is not a valid result type.

Cause: {0} is not a valid result type.

Action: Provide a valid result type.
Level: 1

Type: ERROR

Impact: Process

OAAM-20064: {0} is not a valid rule result.

Cause: {0} is not a valid rule result.

Action: Provide a valid value for rule result.
Level: 1

Type: ERROR

Impact: Process

OAAM-20065: Rule results for columns {0} and {1} are the same.

Cause: Rule results for columns {0} and {1} are the same.

Action: Provide different rule results for each column.
Level: 1

Type: ERROR

Impact: Process

OAAM-20066: Filter key type was not provided for retrieving the filter key.

Cause: The filter key type must be provided as an Integer value. The error occurred because the value was not provided to get the correct filter based on the key type.

Action: Provide a non-null value for the filter key type and retry the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-20067: Transaction Definition ID was not provided for retrieving the filter key.

Cause: The Transaction Definition ID provided must be a Long value. The error occurred because the value was not provided to get the correct filter based on the filter key type and transaction definition.

Action: Provide a non-null value for the Transaction Definition ID and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-20068: Transaction not found for the given Transaction Definition ID.

Cause: The Transaction Definition ID provided did not match with any of the transaction definitions in the system.

Action: Provide a valid Transaction Definition ID and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-20069: Filter condition key was not provided.

Cause: The filter condition lookup key provided was either null or empty.

Action: Provide a valid filter condition lookup key string and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-20070: Condition filter was not found based on filter condition key {0}.

Cause: The filter key provided does not match any condition filter.

Action: Provide a correct condition filter descriptor key and then retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-20071: The provided filter key is invalid.

Cause: The filter key provided was either null or empty.

Action: Provide a valid lookup string. Also note that any spaces at the beginning and end of the lookup string will be ignored.
Level: 1

Type: ERROR

Impact: Process

OAAM-20072: No filter descriptor was found for key {0}.

Cause: There is no filter key descriptor that match the key provided.

Action: Provide a lookup string that matches one of the filter keys in the system. Make sure the format is right and there are no typographical errors.
Level: 1

Type: ERROR

Impact: Process

OAAM-20073: Number of rule set results is not equal to the number of rules in the policy.

Cause: Number of RuleSetResults is not equal to the number of rules in the policy.

Action: Number of RuleSetResults should be equal to the number of rules in the policy.
Level: 1

Type: ERROR

Impact: Process

OAAM-20074: Filter key descriptor is invalid.

Cause: The filter key provided was either null or empty.

Action: Provide a lookup string that is not null or empty. Also note that any spaces at the beginning and end of the lookup string will be ignored.
Level: 1

Type: ERROR

Impact: Process

OAAM-20075: A rule must have at least one condition. The current action tries to delete all conditions in this rule. Make sure at least one condition is not selected for deletion.

Cause: A rule must have at least one condition. The current action tries to delete all the conditions in this rule.

Action: Make sure at least one condition is not selected for deletion.
Level: 1

Type: ERROR

Impact: Process

OAAM-20076: Encryption is not supported for numeric data fields.

Cause: Attempt was made to set the numeric data field as encrypted. Encryption is not supported for numeric data fields.

Action: Make sure the data fields selected for encryption do not include numeric data fields. Unselect the numeric data fields and then try the encryption operation again.
Level: 1

Type: ERROR

Impact: Process

OAAM-30001: Group data is required to complete this operation.

Cause: The operation needs group data and that data was not provided.

Action: Provide valid group data and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-30002: A group with name {0} already exists.

Cause: Group by the name and value type already exists.

Action: Try a different group name for the given type of group.
Level: 1

Type: ERROR

Impact: Process

OAAM-30003: Group type {0} not found.

Cause: The group type provided for the operation was not correct.

Action: Try a different group type. Group types can be found in value.type.enum through the system enumerations user interface.
Level: 1

Type: ERROR

Impact: Process

OAAM-30004: Group name is incorrect.

Cause: The group name is incorrect. It is not a valid group name.

Action: Provide an alphanumeric string as the group name.
Level: 1

Type: ERROR

Impact: Process

OAAM-30005: Group description is incorrect.

Cause: The group description is incorrect. It is not a valid group description.

Action: Provide an alphanumeric string for the group description.
Level: 1

Type: ERROR

Impact: Process

OAAM-30006: Group cache type is incorrect.

Cause: The group cache type is incorrect. It is not a valid group cache type.

Action: Provide a correct cache type. Refer to cache type enumeration for possible values.
Level: 1

Type: ERROR

Impact: Process

OAAM-30007: Group with given information not found: {0}.

Cause: Group with given information not found.

Action: Provide the correct information so the group can be retrieved. You can search for the groups in the system.
Level: 1

Type: ERROR

Impact: Process

OAAM-30008: Group type cannot be changed.

Cause: The group type is part of the basic function in the way that the group is used in the system. The group type cannot be changed at this time.

Action: Create another group with the required value type and then use it.
Level: 1

Type: ERROR

Impact: Process

OAAM-30009: Group type {0} not found.

Cause: The group type provided for the operation was not correct.

Action: Try a different group type. Group types can be found in value.list.type.enum through the system enumerations user interface.
Level: 1

Type: ERROR

Impact: Process

OAAM-30010: Group type cannot be changed.

Cause: The group type is part of the basic function in the way that the group is used in the system. The group type cannot be changed at this time.

Action: Create another group with the required type and then use it.
Level: 1

Type: ERROR

Impact: Process

OAAM-30011: Group element {0} is invalid for this group.

Cause: The group element is null or the group element type is not compatible with the group type.

Action: Provide an element that is compatible with the group type.
Level: 1

Type: ERROR

Impact: Process

OAAM-30012: List of groups is required for this operation.

Cause: A list of groups required for this operation was found to be null.

Action: Provide a valid list of groups and then retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-30013: List of groups has invalid group information.

Cause: A list of groups required for this operation contains some group-related information that is incorrect.

Action: Provide a valid list of groups with non-null Group IDs. Any duplicates in the list will be ignored.
Level: 1

Type: ERROR

Impact: Process

OAAM-30014: Query returned multiple groups from different group types.

Cause: The query returned multiple groups of mixed type.

Action: Use more specific search criteria to limit the number of groups returned.
Level: 1

Type: ERROR

Impact: Process

OAAM-30015: Group element with given information not found {0}.

Cause: Group element with given information not found.

Action: Provide correct information so the group element can be retrieved. You can use the searchGroupElements feature to find group elements in the system.
Level: 1

Type: ERROR

Impact: Process

OAAM-30016: Element {0} is not a member of group {1}.

Cause: Element is not a member of the group.

Action: Provide a correct combination of element and group.
Level: 1

Type: ERROR

Impact: Process

OAAM-30017: The group {0} cannot be deleted, because it is linked to the following policies {1}.

Cause: Policies are linked to this group; therefore, the group cannot be deleted.

Action: The group is linked to policies and might contain session and transaction data associated with this group. Hence this group cannot be deleted.
Level: 1

Type: ERROR

Impact: Process

OAAM-30018: The group {0} cannot be deleted, because it is used by rules.

Cause: Policies use this group as a parameter value in their rules; therefore, the group cannot be deleted.

Action: Remove the group name or ID as a value of the rule parameter(s) and then retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-30019: The group {0} cannot be deleted, because it is used by user groups.

Cause: Some user groups use this group; therefore, the group cannot be deleted.

Action: Remove the group name or ID from those user groups and then retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-30020: The IP Cluster object cannot be null.

Cause: The OARMIPCluster object cannot be null.

Action: Pass a non-null OARMIPCluster object.
Level: 1

Type: ERROR

Impact: Process

OAAM-30021: The label for IP cluster cannot be null.

Cause: The label for IP cluster cannot be null.

Action: Pass a non-null label for IP cluster.
Level: 1

Type: ERROR

Impact: Process

OAAM-30022: IP cluster with label {0} already exists.

Cause: IP cluster with label {0} already exists.

Action: Provide a different label for IP cluster.
Level: 1

Type: ERROR

Impact: Process

OAAM-30023: Invalid IP address range. From IP Address cannot be greater than To IP Address.

Cause: Invalid IP address range. From IP Address cannot be greater than To IP Address.

Action: Provide a From IP Address that is less than To IP Address.
Level: 1

Type: ERROR

Impact: Process

OAAM-30024: The IP address {0} is invalid.

Cause: The IP address {0} is invalid.

Action: Provide a valid IP address.
Level: 1

Type: ERROR

Impact: Process

OAAM-30025: The list of Cluster IDs cannot be null.

Cause: The list of Cluster IDs cannot be null.

Action: Provide a non-null list of Cluster IDs.
Level: 1

Type: ERROR

Impact: Process

OAAM-30026: The IP cluster with Cluster ID {0} does not exist.

Cause: The IP cluster with Cluster ID {0} does not exist.

Action: Provide a valid Cluster ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-30027: The IP cluster with Cluster ID {0} is being used by one or more groups and cannot be deleted.

Cause: The IP cluster with Cluster ID {0} is being used by one or more groups and cannot be deleted.

Action: Remove the IP cluster from the groups and then try to delete it.
Level: 1

Type: ERROR

Impact: Process

OAAM-30028: Duplicate element {0} cannot be added to group {1}.

Cause: The element is already present in the group. Duplicate elements cannot be added to the group.

Action: Add a different element to the group.
Level: 1

Type: ERROR

Impact: Process

OAAM-30029: The {0} group cannot be deleted because it is being used by one or more policies.

Cause: The group cannot be deleted because it is being used by one or more policies.

Action: The group cannot be deleted because it is neing used by one or more policies.
Level: 1

Type: ERROR

Impact: Process

OAAM-30030: The IP Range {0} cannot be created because a similar IP Range already exists.

Cause: IP Ranges being created have duplicate entries.

Action: Ensure to enter a unique IP Range.
Level: 1

Type: ERROR

Impact: Process

OAAM-30031: The user cannot be removed from the group(s) {0} because they are primary user groups.

Cause: The user cannot be removed from the groups because they are primary user groups.

Action: Select other groups and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-30032: The group {0} cannot be deleted, because it is used by policies.

Cause: Policies use this group as a parameter value in trigger combinations; therefore, the group cannot be deleted.

Action: Remove the group name or ID as a value from policy trigger combinations and then retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-35001: {0} is a duplicate of enumeration {1}. Enter another {2}.

Cause: Enumeration already exists in the database. Duplicate enumerations cannot be added.

Action: Enter a unique enumeration and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-35002: Default Property cannot be deleted.

Cause: Default Property cannot be deleted.

Action: Select another property and retry this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-40001: Import failed error: {0}.

Cause: Import failed error: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40002: Invalid profile type: {0}.

Cause: Invalid profile type: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40003: Invalid policy type: {0}.

Cause: Invalid policy type: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40004: No policy data for policy: {0}.

Cause: No policy data for policy: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40005: Policy already exists in the database with name {0}.

Cause: The policy already exists in the database with the name {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40006: Import failed, no group: {0}, rule instance: {1}.

Cause: Import failed, no group: {0}, rule instance: {1}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40007: Import failed. Unable to set Override action: {0}.

Cause: Import failed. Unable to set Override action: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40008: Import failed. Unable to set Override alert: {0}.

Cause: Import failed. Unable to set Override alert: {0}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40009: Bad rule data, policy: {0}, Rule Global ID: {1}.

Cause: Bad rule data, policy: {0}, Rule Global ID: {1}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40010: Policy: {0} Rule Global ID: {1} not present.

Cause: Policy: {0} Rule Global ID: {1} not present.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40011: Import failed. Unable to set Alert group: {0}, rule instance: {1}.

Cause: Import failed. Unable to set Alert group: {0}, rule instance: {1}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40012: Import failed. Unable to set Action group: {0}, rule instance: {1}.

Cause: Import failed. Unable to set Action group: {0}, rule instance: {1}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40013: Import failed. Unable to set Exclude group: {0}, rule instance: {1}.

Cause: Import failed. Unable to set Exclude group: {0}, rule instance: {1}.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40014: Question category not found.

Cause: The question category was not found.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40015: Validation not found.

Cause: The validation was not found.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40016: Question locale not found.

Cause: The question locale was not found.

Action: Check the error logs. If the problem remains unresolved, you may contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

OAAM-40017: Question with Question ID {0} not found.

Cause: The question with the Question ID was not found.

Action: Provide a valid Question ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40018: Configurable action with Action ID {0} not found.

Cause: The configurable action with the Action ID was not found.

Action: Provide a valid Action ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40019: Transaction with Transaction ID {0} not found.

Cause: The transaction with the Transaction ID was not found.

Action: Provide a valid Transaction ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40020: Pattern with Pattern ID {0} not found.

Cause: The pattern with the Pattern ID was not found.

Action: Provide a valid Pattern ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40021: Entity with Entity ID {0} not found.

Cause: The entity with the Entity ID was not found.

Action: Provide a valid Entity ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40022: Group with List ID {0} not found.

Cause: The group with the List ID was not found.

Action: Provide a valid List ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40023: Policy set with Policy Set ID {0} not found.

Cause: The policy set with Policy Set ID was not found.

Action: Provide a valid Policy Set ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40024: Answer hint with Answer Hint ID {0} not found.

Cause: The answer hint with the Answer Hint ID was not found.

Action: Provide a valid Answer Hint ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40025: Validation with Validation ID {0} not found.

Cause: Validation with Validation ID not found.

Action: Provide a valid Validation ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40026: Task group with Group ID {0} not found.

Cause: Task group with Group ID not found.

Action: Provide a valid Group ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-40027: A configurable action with the name {0} already exists.

Cause: A configurable action with the name already exists.

Action: Change the name of the existing configurable action.
Level: 1

Type: ERROR

Impact: Process

OAAM-40028: One or more files in the ZIP file are invalid XML files.

Cause: One or more files in the ZIP file are invalid XML files.

Action: One or more files in the ZIP file are invalid XML files.
Level: 1

Type: ERROR

Impact: Process

OAAM-40029: Import content has system properties. System properties are not imported as part of this Import action.

Cause: System properties are not imported as part of Import Properties. System type properties may exist in the import data; they are not imported as part of this Import action.

Action: This is not an error. It is only an informative message about the system properties. System properties are considered to be specific to the system or environment where the OAAM product runs. Such properties are not imported by other OAAM servers even when they are part of the data being imported. No user action is required.
Level: 1

Type: ERROR

Impact: Process

OAAM-40030: Import ignored the following system properties: {0}

Cause: System properties, which were not imported as part of import properties, are listed here.

Action: This is not an error. It is only an informative message about the system properties that were not imported. No user action is required.
Level: 1

Type: ERROR

Impact: Process

OAAM-40031: Export list has some properties that are system properties. System properties are not exported in this Export action.

Cause: System properties are not exported as part of Export Properties. There may be some system type properties in the export list. They are not exported as part of this export.

Action: This is not an error. It is only an informative message about the system properties. System properties are considered to be specific to the system or environment where OAAM product runs. Such properties are not exported by OAAM servers even when they are part of the list of properties being imported. No user action is required.
Level: 1

Type: ERROR

Impact: Process

OAAM-40032: Export has ignored the following system properties: {0}

Cause: System properties, which are not exported as part of Export Properties, are listed here.

Action: This is not an error. It is only an informative message about the system properties which are not exported. No user action is required.
Level: 1

Type: ERROR

Impact: Process

OAAM-40033: File provided does not appear to be correct for Import action.

Cause: The file provided for import may not be correct. The file may not be the one that was exported from OAAM, or it may contain data that cannot be imported into OAAM.

Action: Check that the file was obtained from another OAAM export. See if the file is not empty, and is readable and a valid ZIP file.
Level: 1

Type: ERROR

Impact: Process

OAAM-40034: File import error. Check the log for details.

Cause: A file import error occurred. Invalid import files were found in the ZIP file.

Action: Check whether the ZIP file contains valid import files.
Level: 1

Type: ERROR

Impact: Process

OAAM-40035: Unknown error during import operation. Check the log for details.

Cause: Invalid import files may exist in the ZIP file.

Action: Check if the ZIP file contains invalid import files.
Level: 1

Type: ERROR

Impact: Process

OAAM-40501: Snapshot name cannot be null or empty.

Cause: Snapshot name cannot be null or empty.

Action: Provide a snapshot name.
Level: 1

Type: ERROR

Impact: Process

OAAM-40502: Snapshot description cannot be null or empty.

Cause: Snapshot description cannot be null or empty.

Action: Provide a valid Snapshot description.
Level: 1

Type: ERROR

Impact: Process

OAAM-40503: Snapshot identifier cannot be null.

Cause: Snapshot identifier cannot be null. This API requires a valid snapshot identifier.

Action: Provide a valid snapshot identifier.
Level: 1

Type: ERROR

Impact: Process

OAAM-40504: Snapshot with snapshot identifier {0} does not exist.

Cause: Snapshot with given snapshot identifier does not exist.

Action: Ensure that you provide the correct snapshot identifier for this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-40505: List of snapshots was not found.

Cause: List of snapshot identifiers was not found. The list is a mandatory parameter when performing this operation in the interface.

Action: Provide the correct list of snapshot identifiers and retry the operation. The list is a mandatory parameter and cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-40506: Snapshot data provided does not appear correct.

Cause: Snapshot data bytes do not appear correct.

Action: Ensure that the snapshot bytes array is not null and and that the array represents the correct snapshot data. Make sure the byte data from the saved snapshot ZIP file is represented, and then retry the operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-50001: The fully-qualified transaction key must be a valid string.

Cause: The transaction key supplied to look up the transaction definition is not correct. It should be a non-empty string.

Action: Verify that the transaction key provided is correct and a non-empty string.
Level: 1

Type: ERROR

Impact: Process

OAAM-50002: Transaction definition was not found for the key {0}.

Cause: The key provided does not match any transaction definition.

Action: Verify that the transaction key provided is correct and a non-empty string.
Level: 1

Type: ERROR

Impact: Process

OAAM-50003: Transaction Definition ID is null.

Cause: Transaction Definition ID is null.

Action: Provide a valid Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50004: Transaction Definition ID is invalid or non-existent.

Cause: Transaction Definition ID is invalid or non-existent.

Action: Provide a valid and existent Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50005: Transaction name is null or invalid.

Cause: Transaction name is null or invalid.

Action: Provide a valid transaction name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50006: Transaction definition cannot be null.

Cause: Transaction definition cannot be null.

Action: Provide a valid transaction definition object.
Level: 1

Type: ERROR

Impact: Process

OAAM-50007: Transaction Definition ID is null.

Cause: Transaction Definition ID is null.

Action: Provide a non-null Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50008: Transaction Definition ID is either invalid or does not exist.

Cause: Transaction Definition ID is either invalid or does not exist.

Action: Provide valid Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50009: Transaction definition could not be updated.

Cause: Transaction definition could not be updated.

Action: Check error log for details.
Level: 1

Type: ERROR

Impact: Process

OAAM-50010: Transaction Definition ID list is null or empty.

Cause: Transaction Definition ID list is null or empty.

Action: Provide a valid Transaction Definition ID list.
Level: 1

Type: ERROR

Impact: Process

OAAM-50011: Transaction definition for the given transaction definition {0} not found.

Cause: Transaction definition for the given transaction definition {0} not found.

Action: Provide a valid Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50012: Transaction input data mapping is missing for transaction {0}.

Cause: Transaction input data mapping is missing for transaction {0}.

Action: Provide transaction input data mapping to activate the transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50013: Transaction definition for the given transaction definition {0} not found.

Cause: Transaction definition for the given transaction definition {0} not found.

Action: Provide a valid transaction definition.
Level: 1

Type: ERROR

Impact: Process

OAAM-50014: Transaction input data mapping is missing for transaction {0}.

Cause: Transaction input data mapping is missing for transaction {0}.

Action: Provide transaction input data to activate the transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50015: Source data is missing for transaction {0}.

Cause: Source data is missing for transaction {0}.

Action: Provide the required source data to activate transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50016: Transaction data mapping is missing for transaction {0}.

Cause: Transaction data mapping is missing for transaction {0}.

Action: Provide transaction data mapping to activate transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50017: Transaction data mapping is missing for transaction {0}.

Cause: Transaction data mapping is missing for transaction {0}.

Action: Provide transaction data mapping to activate transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50018: Entity mapping could not be found for transaction {0}.

Cause: Entity mapping could not be found for transaction {0}.

Action: Make sure all entities are mapped before activating transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50019: Transaction and entity mapping is missing for transaction {0}.

Cause: Transaction and entity mapping is missing for transaction {0}.

Action: Provide transaction and entity mapping to activate transaction {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50020: Transaction Entity Definition Map ID cannot be null.

Cause: Transaction Entity Definition Map ID cannot be null.

Action: Provide a valid Transaction Entity Definition Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50021: Transaction Definition ID missing while creating transaction entity map.

Cause: Transaction Definition ID missing while creating transaction entity map.

Action: Provide a valid Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50022: Entity Definition ID missing while creating transaction entity map.

Cause: Entity Definition ID missing while creating transaction entity map.

Action: Provide a valid Entity Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50023: Entity definition validation failed. Operation cannot be performed.

Cause: Entity definition validation failed. Operation cannot be performed.

Action: Provide a valid entity definition.
Level: 1

Type: ERROR

Impact: Process

OAAM-50024: Entity name validation failed.

Cause: Entity name validation failed.

Action: Provide a valid and unique entity name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50025: Invalid entity relation.

Cause: Invalid entity relation.

Action: Provide a valid entity relation.
Level: 1

Type: ERROR

Impact: Process

OAAM-50026: Invalid display order.

Cause: Invalid display order.

Action: Provide a valid display order.
Level: 1

Type: ERROR

Impact: Process

OAAM-50027: Duplicate entity name.

Cause: Duplicate entity name.

Action: Provide a valid and unique entity name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50028: Invalid and non-unique entity relation.

Cause: Invalid and non-unique entity relation.

Action: Provide a valid and unique entity relation.
Level: 1

Type: ERROR

Impact: Process

OAAM-50029: Invalid and non-unique display order.

Cause: Invalid and non-unique display order.

Action: Provide a valid and unique display order.
Level: 1

Type: ERROR

Impact: Process

OAAM-50030: Transaction Definition ID missing while updating transaction entity map.

Cause: Transaction Definition ID missing while updating transaction entity map.

Action: Provide a valid and non-null Transaction Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50031: Entity Definition ID missing while updating transaction entity map.

Cause: Entity Definition ID missing while updating transaction entity map.

Action: Provide a valid and non-null Entity Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50032: Transaction delete is not allowed.

Cause: Transaction delete is not allowed.

Action: Select a valid transaction for delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-50033: Data element definition cannot be null.

Cause: Data element definition cannot be null.

Action: Provide a valid data element definition.
Level: 1

Type: ERROR

Impact: Process

OAAM-50034: Data element definition array cannot be null or empty.

Cause: Data element definition array cannot be null or empty.

Action: Provide a non-null and valid data element definition array.
Level: 1

Type: ERROR

Impact: Process

OAAM-50035: Attribute validation failed.

Cause: Attribute validation failed.

Action: Provide a valid attribute.
Level: 1

Type: ERROR

Impact: Process

OAAM-50036: Creating the attribute failed.

Cause: Creating the attribute failed.

Action: Provide the valid entry for creating the attribute.
Level: 1

Type: ERROR

Impact: Process

OAAM-50037: Attribute not found.

Cause: Attribute not found.

Action: Provide a valid and non-null attribute.
Level: 1

Type: ERROR

Impact: Process

OAAM-50038: Cannot find a matching data element definition.

Cause: Cannot find a matching data element definition.

Action: Provide a valid entry with a matching data element definition.
Level: 1

Type: ERROR

Impact: Process

OAAM-50039: No attribute found to delete.

Cause: No attribute found to delete.

Action: Provide a valid attribute to delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-50040: Source validation failed.

Cause: Source validation failed.

Action: Provide valid source data.
Level: 1

Type: ERROR

Impact: Process

OAAM-50041: Cannot find a matching transaction data mapping.

Cause: Cannot find a matching Transaction Data Mapping ID.

Action: Provide a valid and matching Transaction Data Mapping ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50042: Transaction data mapping is null or empty.

Cause: Transaction data mapping IDs are null or empty.

Action: Provide a non-null or valid Transaction Data Mapping ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50043: No transaction mapping found to delete.

Cause: No transaction mapping found to delete.

Action: Transaction should have one or more mappings to delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-50044: No entity mapping found to delete.

Cause: No entity mapping found to delete.

Action: Entity should have one or more mappings to delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-50045: Transaction name is null or empty.

Cause: Transaction name is null or empty.

Action: Provide a valid and non-null transaction name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50046: Transaction key is null or empty.

Cause: Transaction key is null or empty.

Action: Provide a valid and non-null transaction key.
Level: 1

Type: ERROR

Impact: Process

OAAM-50047: Transaction description is null or empty.

Cause: Transaction description is null or empty.

Action: Provide a valid and non-null transaction description.
Level: 1

Type: ERROR

Impact: Process

OAAM-50048: Duplicate transaction name or transaction key; validation failed.

Cause: Validation failed because of a duplicate transaction name or transaction key.

Action: Provide a valid and unique transaction name or transaction key.
Level: 1

Type: ERROR

Impact: Process

OAAM-50049: Transaction entity map for the ID {0} does not exist.

Cause: Transaction entity map for the ID does not exist.

Action: Provide a valid Transaction Entity Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50050: Transaction Entity Map ID cannot be null.

Cause: Transaction Entity Map ID cannot be null.

Action: Provide a valid and non-null Transaction Entity Map ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50102: Display/name scheme is not set for entity {0}.

Cause: Display/name scheme is not set for entity.

Action: Set the display/name scheme before activation.
Level: 1

Type: ERROR

Impact: Process

OAAM-50103: ID scheme is not set for entity {0}.

Cause: ID scheme is not set for entity.

Action: Set the ID scheme before activation.
Level: 1

Type: ERROR

Impact: Process

OAAM-50104: No data element definitions exist for entity {0}.

Cause: No data element definitions exist for entity.

Action: Add data element definitions before activating.
Level: 1

Type: ERROR

Impact: Process

OAAM-50105: Row and Column values are not unique/valid for data element {0} for entity {1}.

Cause: Row and Column values are not unique/valid for data element for entity.

Action: Provide unique Row and Column values for data elements within an entity.
Level: 1

Type: ERROR

Impact: Process

OAAM-50106: There is more than one data element with the same internal identifier, {0}, for entity {1}.

Cause: There is more than one data element with the same internal identifier for the same entity.

Action: Provide a unique internal identifiers for data element definitions within an entity.
Level: 1

Type: ERROR

Impact: Process

OAAM-50107: Index for numeric data elements is not between {0} and {1} for entity {2}.

Cause: Index for numeric data elements is not between {0} and {1} for entity {2}.

Action: Ensure that index for numeric data elements is between {0} and {1} for entity {2}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50108: Index for non-numeric data elements is not between {0} and {1} for entity {2}.

Cause: Index for non-numeric data elements is not between {0} and {1} for entity {2}.

Action: Ensure that index for non-numeric data elements is between {0} and {1} for entity {2}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50109: No display scheme elements are available for entity {0}.

Cause: No display scheme elements have been added for entity {0}.

Action: Add display scheme elements before activating.
Level: 1

Type: ERROR

Impact: Process

OAAM-50110: There is more than one display data element with the same internal ID, {0}, for entity {1}.

Cause: There is more than one display data element with the same internal ID, {0}, for entity {1}.

Action: Entity should not have more than one display data element with the same internal ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50111: There is more than one display data element with the same order, {0}, for entity {1}.

Cause: There is more than one display data element with the same order, {0}, for entity {1}.

Action: Correct the ordering for the display data elements for entity {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50112: No ID scheme elements are available for entity {0}.

Cause: No ID scheme elements have been added for entity {0}.

Action: Add ID scheme elements before activating.
Level: 1

Type: ERROR

Impact: Process

OAAM-50113: There is more than one ID scheme data element with the same internal ID, {0}, for entity {1}.

Cause: There is more than one ID scheme data element with the same internal ID, {0}, for entity {1}.

Action: The entity should not have more than one ID scheme data element with the same internal ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50114: There is more than one ID scheme data element with the same order, {0}, for entity {1}.

Cause: There is more than one ID scheme data element with the same order, {0}, for entity {1}.

Action: The entity should not have more than one ID scheme data element with the same order.
Level: 1

Type: ERROR

Impact: Process

OAAM-50115: Database error.

Cause: Database error.

Action: Database error.
Level: 1

Type: ERROR

Impact: Process

OAAM-50116: Entity Name field cannot be blank.

Cause: Entity Name field cannot be blank.

Action: Provide an entity name for the Entity Name field.
Level: 1

Type: ERROR

Impact: Process

OAAM-50117: Entity Key field cannot be blank.

Cause: Entity Key field cannot be blank.

Action: Provide an entity key in the Key field.
Level: 1

Type: ERROR

Impact: Process

OAAM-50118: Entity Description field cannot be blank.

Cause: Entity Description field cannot be blank.

Action: Provide an entity description in the Description field.
Level: 1

Type: ERROR

Impact: Process

OAAM-50119: Another entity definition with the same name already exists.

Cause: Another entity definition with the same name already exists.

Action: Provide a unique name for the entity definition.
Level: 1

Type: ERROR

Impact: Process

OAAM-50120: Internal ID field of data elements cannot be blank.

Cause: Internal ID field of data elements cannot be blank.

Action: Provide an internal ID for data elements.
Level: 1

Type: ERROR

Impact: Process

OAAM-50121: Data Type field of the data elements of the entity cannot be blank.

Cause: Data Type field of the data elements of the entity cannot be blank.

Action: Provide a data type for data elements of the entity.
Level: 1

Type: ERROR

Impact: Process

OAAM-50122: Row number of the data elements of the entity cannot be less than zero.

Cause: Row number of the data elements of the entity cannot be less than zero.

Action: Provide positive integers as row numbers for the data elements of the entity.
Level: 1

Type: ERROR

Impact: Process

OAAM-50123: Column number of data elements of the entity cannot be less than zero.

Cause: Column number of data elements of the entity cannot be less than zero.

Action: Provide a positive integer as the column number for data elements of the entity.
Level: 1

Type: ERROR

Impact: Process

OAAM-50124: Internal ID of the data element of the entity should be unique.

Cause: Internal ID of data element of the entity should be unique.

Action: Ensure that the internal ID of the data element of the entity is unique.
Level: 1

Type: ERROR

Impact: Process

OAAM-50125: Name of data element of the entity should be unique.

Cause: Name of data element of the entity should be unique.

Action: Ensure that the name of the data element of the entity is unique.
Level: 1

Type: ERROR

Impact: Process

OAAM-50126: More than one data element definition exists with the same row and column.

Cause: More than one data element definition exists with the same row and column.

Action: Ensure that row and column values are unique for the data element definitions.
Level: 1

Type: ERROR

Impact: Process

OAAM-50127: Validation error: Data element definition identifier should not be set for creating a new data element definition.

Cause: Validation error: Data element definition identifier should not be set for creating a new data element definition. The identifier is generated by the system for the new data element.

Action: Validation error: Data element definition identifier should not be set for creating a new data element definition. The identifier is generated by the system for the new data element.
Level: 1

Type: ERROR

Impact: Process

OAAM-50128: Column value for numeric data elements should be between {0} and {1}.

Cause: Column value for numeric data elements should be between {0} and {1}.

Action: Column value for numeric data elements should be between {0} and {1}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50129: Column value for non-numeric data elements should be between 1 and {0}.

Cause: Column value for non-numeric data elements should be between 1 and {0}.

Action: Column value for non-numeric data elements should be between 1 and {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50130: The entity {0} cannot be disabled because it is used by one or more active transactions.

Cause: The entity {0} cannot be disabled because it is used by one or more active transactions.

Action: The entity {0} cannot be disabled because it is used by one or more active transactions.
Level: 1

Type: ERROR

Impact: Process

OAAM-50131: The entity {0} cannot be deleted because it is used by one or more active transactions.

Cause: The entity {0} cannot be deleted because it is used by one or more active transactions.

Action: The entity {0} cannot be deleted because it is used by one or more active transactions.
Level: 1

Type: ERROR

Impact: Process

OAAM-50132: Entity Definition ID cannot be null.

Cause: Entity Definition ID cannot be null.

Action: Entity Definition ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-50133: Data profile definition not found for the Entity Definition ID.

Cause: Data profile definition not found for the Entity Definition ID.

Action: Data profile definition not found for the Entity Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50134: Data Definition ID does not match with Data Definition ID of the data profile.

Cause: Data Definition ID does not match with Data Definition ID of the data profile.

Action: Data Definition ID does not match with Data Definition ID of the data profile.
Level: 1

Type: ERROR

Impact: Process

OAAM-50135: Unable to create external ID data definition for the Entity Definition ID.

Cause: Unable to create external ID data definition for the Entity Definition ID.

Action: Unable to create external ID data definition for the Entity Definition ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50136: The element with Element ID {0} cannot be deleted because it is used by one or more active transactions.

Cause: The element with Element ID {0} cannot be deleted because it is used by one or more active transactions.

Action: The element with Element ID {0} cannot be deleted because it is used by one or more active transactions.
Level: 1

Type: ERROR

Impact: Process

OAAM-50137: Data element having Data Definition Element ID {0} does not exist.

Cause: Data element having Data Definition Element ID {0} does not exist.

Action: Data element having Data Definition Element ID {0} does not exist.
Level: 1

Type: ERROR

Impact: Process

OAAM-50138: Identification scheme cannot be null.

Cause: Identification scheme cannot be null.

Action: Identification scheme cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-50139: Data Definition Element ID cannot be null.

Cause: Data Definition Element ID cannot be null.

Action: Data Definition Element ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-50140: System error occurred while loading entities.

Cause: System error occurred while loading entities.

Action: System error occurred while loading entities.
Level: 1

Type: ERROR

Impact: Process

OAAM-50141: Error loading object {0} with primary key {1} from database. {2}.

Cause: Error loading object {0} with primary key {1} from database. {2}.

Action: Error loading object {0} with primary key {1} from database. {2}s.
Level: 1

Type: ERROR

Impact: Process

OAAM-50142: Error inserting object {0} to database.

Cause: Error inserting object to database. Database may not be available.

Action: Error inserting object to database. Try the operation again.
Level: 1

Type: ERROR

Impact: Process

OAAM-50200: Configurable Action ID provided is invalid or does not exist.

Cause: Configurable Action ID provided is invalid or does not exist.

Action: Provide a valid and existent Configurable Action ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50201: Configurable Action ID cannot be null.

Cause: Configurable Action ID cannot be null.

Action: Provide a non-null Configurable Action ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50202: Action parameters mismatch.

Cause: Action parameters mismatch.

Action: Provide a valid action parameter.
Level: 1

Type: ERROR

Impact: Process

OAAM-50203: Action name provided cannot be null.

Cause: Action name provided cannot be null.

Action: Provide a non-null action name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50204: Java Class Name provided cannot be null.

Cause: Java Class Name provided cannot be null.

Action: Provide a non-null Java class name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50205: Duplicate action.

Cause: Duplicate action.

Action: Provide a unique value to create a valid action.
Level: 1

Type: ERROR

Impact: Process

OAAM-50206: Configurable action cannot be deleted as it is currently used by one or more Action Instances.

Cause: Configurable action cannot be deleted as it is currently used by one or more Action Instances.

Action: Select a valid configurable action that is not in use.
Level: 1

Type: ERROR

Impact: Process

OAAM-50207: Invalid or non-existent Action ID.

Cause: Invalid or non-existent Action ID.

Action: Provide a valid and existent Action ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50208: Action ID list provided cannot be null or empty.

Cause: Action ID list provided cannot be null or empty.

Action: Provide a non-null and valid Action ID list.
Level: 1

Type: ERROR

Impact: Process

OAAM-50209: Action ID provided cannot be null.

Cause: Action ID provided cannot be null.

Action: Provide a non-null Action ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50210: Action Instance ID provided is invalid or non-existent.

Cause: Action Instance ID provided is invalid or non-existent.

Action: Provide a valid and existent Action Instance ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50211: Action Instance ID cannot be null.

Cause: Action Instance ID cannot be null.

Action: Provide a non-null Action Instance ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50212: Execution Order should be unique for synchronous actions.

Cause: Execution Order should be unique for synchronous actions.

Action: Provide unique execution order for each synchronous action.
Level: 1

Type: ERROR

Impact: Process

OAAM-50213: Action Instance name is a duplicate.

Cause: Action Instance name is a duplicate.

Action: Provide a unique action instance name.
Level: 1

Type: ERROR

Impact: Process

OAAM-50214: Action instance association is not allowed.

Cause: Action instance association is not allowed.

Action: Select the valid instance and parameters for the association.
Level: 1

Type: ERROR

Impact: Process

OAAM-50215: Invalid or non-existent Action Instance ID {0}.

Cause: Invalid or non-existent Action Instance ID {0}.

Action: Provide a valid and existing Action Instance ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-50216: Value {1} provided for the parameter name {0} is not a valid Boolean value.

Cause: Value {1} provided for the parameter name {0} is not a valid Boolean value.

Action: Provide a valid Boolean value for the parameter name {0}. It can be true or false only.
Level: 1

Type: ERROR

Impact: Process

OAAM-50217: Value {1} provided for the parameter name {0} is not a valid Integer value.

Cause: Value {1} provided for the parameter name {0} is not a valid Integer value.

Action: Provide a valid Integer value for the parameter name {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50218: Value {1} provided for the parameter name {0} is not a valid Long value.

Cause: Value {1} provided for the parameter name {0} is not a valid Long value.

Action: Provide a valid Long value for the parameter name {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50219: Value {1} provided for the parameter name {0} is not a valid Date value.

Cause: Value {1} provided for the parameter name {0} is not a valid Date value.

Action: Provide a valid Date value for the parameter name {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-50220: Action parameter value validation failed.

Cause: The action parameter value validation failed.

Action: Verify all the parameter values for its data type are valid.
Level: 1

Type: ERROR

Impact: Process

OAAM-50221: Nonexistent or invalid Parameter ID {0} with the parameter name {1}.

Cause: Nonexistent or invalid Parameter ID {0} with the parameter name {1}.

Action: Provide a valid existing parameter and value.
Level: 1

Type: ERROR

Impact: Process

OAAM-50222: Unable to load configurable action class {0}. Ensure the class is made available in the class path.

Cause: Unable to load configurable action class {0}. Ensure the class is made available in the class path.

Action: Provide a valid class name with the class already in the class path.
Level: 1

Type: ERROR

Impact: Process

OAAM-60001: Pattern ID cannot be null.

Cause: Pattern ID cannot be null.

Action: Pattern ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-60002: Pattern with the name {0} already exists.

Cause: Pattern with the name {0} already exists.

Action: Pattern with the name {0} already exists.
Level: 1

Type: ERROR

Impact: Process

OAAM-60003: Comparison value is required.

Cause: Comparison value is required.

Action: Comparison value is required.
Level: 1

Type: ERROR

Impact: Process

OAAM-60004: The value {0} is invalid.

Cause: The value {0} is invalid.

Action: The value {0} is invalid.
Level: 1

Type: ERROR

Impact: Process

OAAM-60005: The value {0} is not a valid Integer value.

Cause: The value {0} is not a valid Integer value.

Action: The value {0} is not a valid Integer value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60006: The value {0} is not a valid Long value.

Cause: The value {0} is not a valid Long value.

Action: The value {0} is not a valid Long value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60007: The value {0} is not a valid Boolean value.

Cause: The value {0} is not a valid Boolean value.

Action: The value {0} is not a valid Boolean value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60008: The value {0} is not a valid Float value.

Cause: The value {0} is not a valid Float value.

Action: The value {0} is not a valid Float value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60009: The value {0} is not a valid Date value.

Cause: The value {0} is not a valid Date value.

Action: The value {0} is not a valid Date value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60010: The value {0} is not a valid Double value.

Cause: The value {0} is not a valid Double value.

Action: The value {0} is not a valid Double value.
Level: 1

Type: ERROR

Impact: Process

OAAM-60011: Entered values overlaps with {0}-{1} range.

Cause: Entered values overlaps with {0}-{1} range.

Action: Entered values overlaps with {0}-{1} range.
Level: 1

Type: ERROR

Impact: Process

OAAM-60012: The attribute already exists.

Cause: The attribute already exists.

Action: The attribute already exists.
Level: 1

Type: ERROR

Impact: Process

OAAM-60013: Pattern parameter with Parameter ID {0} does not exist.

Cause: Pattern parameter with the Parameter ID {0} does not exist.

Action: Pattern parameter with the Parameter ID {0} does not exist.
Level: 1

Type: ERROR

Impact: Process

OAAM-60014: Parameter ID cannot be null.

Cause: Parameter ID cannot be null.

Action: Parameter ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-60015: Data has already been collected for this pattern. Changing this pattern will potentially render that data inaccurate.

Cause: Data has already been collected for this pattern. Changing this pattern will potentially render that data inaccurate.

Action: Data has already been collected for this pattern. Changing this pattern will potentially render that data inaccurate.
Level: 1

Type: ERROR

Impact: Process

OAAM-60016: Pattern is associated with active policies - {0}.

Cause: Pattern is associated to the active policies - {0}.

Action: Pattern is associated to the active policies - {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-65001: No policy set found.

Cause: No policy set found.

Action: No policy set found.
Level: 1

Type: ERROR

Impact: Process

OAAM-65002: The scoring type value {0} is invalid.

Cause: The scoring type value {0} is invalid.

Action: The scoring type value {0} is invalid.
Level: 1

Type: ERROR

Impact: Process

OAAM-65003: Action override with Block ID {0} does not exist.

Cause: Action override with Block ID {0} does not exist.

Action: Action override with Block ID {0} does not exist.
Level: 1

Type: ERROR

Impact: Process

OAAM-65004: Score action with Score Action ID {0} does not exist.

Cause: Score action with Score Action ID {0} does not exist.

Action: Score action with Score Action ID {0} does not exist.
Level: 1

Type: ERROR

Impact: Process

OAAM-65005: Score Action ID cannot be null.

Cause: Score Action ID cannot be null.

Action: Score Action ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-65006: Action Override ID cannot be null.

Cause: Action Override ID cannot be null.

Action: Action Override ID cannot be null.
Level: 1

Type: ERROR

Impact: Process

OAAM-65007: There is more than one action override with the Checkpoint-From Action values {0}.

Cause: There is more than one action override with the Checkpoint-From Action values {0}.

Action: There is more than one action override with the Checkpoint-From Action values {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-65008: For checkpoint {0}, the score override range {1} overlaps with the score override range {2}.

Cause: For checkpoint {0}, the score override range {1} overlaps with the score override range {2}.

Action: For checkpoint {0}, the score override range {1} overlaps with the score override range {2}.
Level: 1

Type: ERROR

Impact: Process

OAAM-65009: From Action and To Action are the same for checkpoint {0}.

Cause: From Action and To Action are the same for checkpoint {0}.

Action: From Action and To Action are the same for checkpoint {0}.
Level: 1

Type: ERROR

Impact: Process

OAAM-65010: Action Group required.

Cause: Action Group required.

Action: Action Group required.
Level: 1

Type: ERROR

Impact: Process

OAAM-65011: To Action required.

Cause: To Action required.

Action: To Action required.
Level: 1

Type: ERROR

Impact: Process

OAAM-70001: Question {0} cannot be deleted because it is linked to the user.

Cause: Question {0} cannot be deleted because it is linked to the user.

Action: Either unlink the user from this question or delete some other question.
Level: 1

Type: ERROR

Impact: Process

OAAM-70002: Selected Question ID cannot be updated to the given status.

Cause: Selected Question ID cannot be updated to the given status.

Action: Selected Question ID cannot be updated to the given status. Select a different question.
Level: 1

Type: ERROR

Impact: Process

OAAM-70003: IDs in the list cannot be null or empty.

Cause: IDs in the list cannot be null or empty.

Action: Provide a Valid ID list.
Level: 1

Type: ERROR

Impact: Process

OAAM-70004: Invalid status.

Cause: Invalid status.

Action: Provide a valid status: Active or Disabled.
Level: 1

Type: ERROR

Impact: Process

OAAM-70005: Invalid and non-existent Question ID.

Cause: Invalid and non-existent Question ID.

Action: Provide a valid and existent Question ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-70006: Question ID should not be null.

Cause: Question ID should not be null.

Action: Provide a valid Question ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-70007: Question name {0} already exist. Provide a unique question name.

Cause: Question name {0} already exist. Provide a unique question name.

Action: Provide a valid and unique question name.
Level: 1

Type: ERROR

Impact: Process

OAAM-70008: Category cannot be deleted because users have registered questions from this category.

Cause: Category cannot be deleted because users have registered questions from this category.

Action: Category cannot be deleted because users have registered questions from this category.
Level: 1

Type: ERROR

Impact: Process

OAAM-70009: Invalid category.

Cause: Invalid Category ID.

Action: Provide a valid Category ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-70010: Category cannot be null.

Cause: Category cannot be null.

Action: Provide a valid and non-null category.
Level: 1

Type: ERROR

Impact: Process

OAAM-70011: Name cannot be empty or null.

Cause: Name cannot be empty or null.

Action: Provide a valid and non-null name.
Level: 1

Type: ERROR

Impact: Process

OAAM-70012: Invalid or empty category name.

Cause: Invalid or empty category name.

Action: Provide a valid and non-null category name.
Level: 1

Type: ERROR

Impact: Process

OAAM-70013: Validation name {0} already exist. Provide a unique validation name.

Cause: Validation name {0} already exist. Provide a unique validation name.

Action: Provide a valid and unique validation name.
Level: 1

Type: ERROR

Impact: Process

OAAM-70014: Validation cannot be null.

Cause: Validation cannot be null.

Action: Provide a valid and non-null validation.
Level: 1

Type: ERROR

Impact: Process

OAAM-70015: Invalid Validation ID.

Cause: Invalid Validation ID.

Action: Provide a valid Validation ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-70016: Validations {0} are used in the KBA configuration and cannot be deleted.

Cause: Validations are linked and cannot be deleted.

Action: Select only the unlinked validations for deleting.
Level: 1

Type: ERROR

Impact: Process

OAAM-70017: Validation ID {0} is invalid and cannot be deleted.

Cause: Validation ID is invalid and cannot be deleted.

Action: Provide a valid and existent Validation ID.
Level: 1

Type: ERROR

Impact: Process

OAAM-70018: Validation {0} has already been added as global validation.

Cause: Validation will not be added again as a global validation.

Action: Select a new Validation that is not part of the Global Validation list.
Level: 1

Type: ERROR

Impact: Process

OAAM-70019: Validation ID is not in the Global Validation list.

Cause: Validation ID is not found in the Global Validation list.

Action: Select a Validation ID which is part of the Global Validation list.
Level: 1

Type: ERROR

Impact: Process

OAAM-70020: No validation available in Global Validation list for delete.

Cause: No validation available in Global Validation list for delete.

Action: No validation available in Global Validation list for delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-70021: Configuration value {0} is not a positive number.

Cause: Configuration value should be a positive number.

Action: Provide a positive number for the configuration value.
Level: 1

Type: ERROR

Impact: Process

OAAM-70022: Configuration value {0} cannot exceed the category count.

Cause: Configuration value cannot exceed the category count.

Action: Provide the configuration value within the allowed category count.
Level: 1

Type: ERROR

Impact: Process

OAAM-70023: No validation available in Global Validation list for delete.

Cause: No validation available in Global Validation list for delete.

Action: No validation available in Global Validation list for delete.
Level: 1

Type: ERROR

Impact: Process

OAAM-70024: Insufficient questions in the system for configuring {0} questions for each user with {1} questions per menu.

Cause: There are not enough questions in the system for each user to register for the number of questions per menu.

Action: Import/create more questions so that the number of questions that user needs to register multiplied by the questions per menu is less than the total number of questions available.
Level: 1

Type: ERROR

Impact: Process

OAAM-70025: Too few questions are being configured for users. Try to register at least {0} questions for the user.

Cause: You have tried to set the number of questions too low. This can lead to security vulnerability.

Action: For the best mix of security and usability, register at least three and at most five or so questions. These settings are dependent on your particular system implementation.
Level: 1

Type: ERROR

Impact: Process

OAAM-70026: Too many questions are being configured for users. Try to register at most {0} questions for user.

Cause: You have tried to set the number of questions too high. This can lead to usability issues.

Action: For the best mix of security and usability, register at least three and at most five questions. These settings are dependent on your particular system implementation.
Level: 1

Type: ERROR

Impact: Process

OAAM-70027: Selected category {0} cannot be updated to the given status.

Cause: Selected category {0} cannot be updated to the given status.

Action: Selected category {0} cannot be updated to the given status. Select a different category.
Level: 1

Type: ERROR

Impact: Process

OAAM-70028: Categories' status cannot be updated. This will lead to too few active categories.

Cause: Categories cannot be updated. This will result in very few categories being available for the registration logic.

Action: Make sure registration logic and available active categories are consistent with this change. One way to do this will be update the registration logic first and then try this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-70029: Categories cannot be deleted. This will lead to too few active categories.

Cause: Categories cannot be deleted. This will result in very few categories being available for the registration logic.

Action: Make sure registration logic and available active categories are consistent with this change. One way to do this will be update the registration logic first and then try this operation.
Level: 1

Type: ERROR

Impact: Process

OAAM-70030: Category name {0} already exist. Provide a unique category name.

Cause: Category name {0} already exist. Provide a unique category name.

Action: Provide a valid and unique category name.
Level: 1

Type: ERROR

Impact: Process

OAAM-70031: Failed to deactivate selected Categories.

Cause: Failed to deactivate selected Categories. When category is deactivated the questions belonging to that category are also impacted. Some questions cannot be updated to the given status.

Action: Make sure that the questions in selected categories can be updated to the given status.
Level: 1

Type: ERROR

Impact: Process

OAAM-70032: Failed to delete the selected groups. One or more of the groups are in use.

Cause: Failed to delete the selected groups. One or more of the groups are in use.

Action: Remove the usages of the group and delete it.
Level: 1

Type: ERROR

Impact: Process

OAAM-70033: Validation search query cannot be null.

Cause: Validation search query object passed is null.

Action: Make sure to pass non-null search query object.
Level: 1

Type: ERROR

Impact: Process

OAAM-70034: Validations marked for deletion {0} are also used being as global validations.

Cause: Validations marked for deletion are also used being as global validation.

Action: Manage global validations from Registration Logic page.
Level: 1

Type: ERROR

Impact: Process

OAAM-70035: Validation list for delete operation contains null value(s).

Cause: One or more of the validation IDs sent for deletion contain null values.

Action: Make sure no null values are sent in validation ID lists.
Level: 1

Type: ERROR

Impact: Process

OAAM-70036: Question {0} does not exist. It may have been deleted.

Cause: Question {0} does not exist. It may have been deleted.

Action: Question {0} does not exist.
Level: 1

Type: ERROR

Impact: Process

OAAM-70501: User ID cannot be null

Cause: User ID cannot be null

Action: User ID cannot be null
Level: 1

Type: ERROR

Impact: Process

OAAM-70502: User with User ID, {0}, does not exist

Cause: User with User ID, {0}, does not exist

Action: User with User ID, {0}, does not exist
Level: 1

Type: ERROR

Impact: Process

OAAM-70601: IP Address cannot be null

Cause: IP Address cannot be null

Action: IP Address cannot be null
Level: 1

Type: ERROR

Impact: Process

OAAM-70701: Device ID cannot be null

Cause: Device ID cannot be null

Action: Device ID cannot be null
Level: 1

Type: ERROR

Impact: Process

OAAM-70702: Device with Device ID, {0}, does not exist

Cause: Device with Device ID, {0}, does not exist

Action: Device with Device ID, {0}, does not exist
Level: 1

Type: ERROR

Impact: Process

OAAM-70801: Finger Print ID cannot be null

Cause: Finger Print ID cannot be null

Action: Finger Print ID cannot be null
Level: 1

Type: ERROR

Impact: Process

OAAM-70802: Finger Print with Finger Print ID, {0}, does not exist

Cause: Finger Print with Finger Print ID, {0}, does not exist

Action: Finger Print with Finger Print ID, {0}, does not exist
Level: 1

Type: ERROR

Impact: Process

OAAM-70901: Alert ID cannot be null

Cause: Alert ID cannot be null

Action: Alert ID cannot be null
Level: 1

Type: ERROR

Impact: Process

OAAM-70902: Alert with Alert ID, {0}, does not exist

Cause: Alert with Alert ID, {0}, does not exist

Action: Alert with Alert ID, {0}, does not exist
Level: 1

Type: ERROR

Impact: Process

OAAM-80001: Invalid IP address value {0}

Cause: Invalid IP address {0}. Validation failed.

Action: Enter a valid IP address; the value {0} is invalid
Level: 1

Type: ERROR

Impact: Process

OAAM-90001: Task name {0} already exist. Provide a unique task name.

Cause: Task name {0} already exist. Provide a unique task name.

Action: Provide a valid and unique task name.
Level: 1

Type: ERROR

Impact: Process

OAAM-90002: Task type {0} not found. Provide an existing task type.

Cause: Task type {0} not found. Provide an existing task type.

Action: Provide a valid and existing task type.
Level: 1

Type: ERROR

Impact: Process

OAAM-90003: Task status {0} not found. Provide an existing task status.

Cause: Task status {0} not found. Provide an existing task status.

Action: Provide a valid and existing task status.
Level: 1

Type: ERROR

Impact: Process

OAAM-90004: Task name {0} is not apha numeric. Provide an apha numeric task name.

Cause: Task name {0} is not apha numeric. Provide an apha numerictask name.

Action: Provide a valid and alpha numeric task name.
Level: 1

Type: ERROR

Impact: Process

OAAM-90005: Task priority {0} not found. Provide an existing task priority.

Cause: Task priority {0} not found. Provide an existing task priority.

Action: Provide a valid and existing task priority.
Level: 1

Type: ERROR

Impact: Process

OAAM-90006: Schedule type {0} is invalid. Type has to be either onetime or recurring.

Cause: Schedule type {0} is invalid. Type has to be either onetime or recurring.

Action: Provide a valid Schedule type and should be either onetime or recurring.
Level: 1

Type: ERROR

Impact: Process

OAAM-90007: Cancel duration type {0} not found. Provide an existing duration type.

Cause: Cancel duration type {0} not found. Provide an existing duration type.

Action: Provide a valid and existing duration type.
Level: 1

Type: ERROR

Impact: Process

OAAM-90008: Cancel duration unit {0} not found. Provide an existing duration unit.

Cause: Cancel duration unit {0} not found. Provide an existing duration unit.

Action: Provide a valid and existing duration unit.
Level: 1

Type: ERROR

Impact: Process

OAAM-90009: Start date is required for schedule.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-90010: Start time is required for schedule.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-90011: Recurrence type {0} not found. Provide an existing Recurrence type.

Cause: Recurrence type {0} not found. Provide an existing Recurrence type.

Action: Provide a valid and existing Recurrence type.
Level: 1

Type: ERROR

Impact: Process

OAAM-90012: Cutoff time {0} is invalid. Provide a value in the existing range.

Cause: Cutoff time {0} is invalid. Provide a value in the existing range.

Action: Provide a valid value in the cutoff time range.
Level: 1

Type: ERROR

Impact: Process

OAAM-90013: Custom loader {0} is invalid. Provide a valid custom loader.

Cause: Custom loader {0} is invalid. Provide a valid custom loader.

Action: Provide a valid custom loader.
Level: 1

Type: ERROR

Impact: Process

OAAM-90014: Custom run {0} is invalid. Provide a valid custom run.

Cause: Custom run {0} is invalid. Provide a valid custom run.

Action: Provide a valid custom run.
Level: 1

Type: ERROR

Impact: Process

OAAM-90015: From date is required for data filters.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-90016: To time is required for data filters.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-90017: From date should be before To date for data filters.

Cause: null

Action: null
Level: 1

Type: ERROR

Impact: Process

OAAM-90018: Schedule cannot be null.

Cause: Schedule was not selected.

Action: Select a Schedule, and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-90019: Rollup unit {0} not found. Provide an existing rollup unit.

Cause: User specified an invalid rollup unit.

Action: Provide a valid and existing rollup unit.
Level: 1

Type: ERROR

Impact: Process

OAAM-90020: Job name cannot be null.

Cause: User did not specify a job name.

Action: Provide a job name.
Level: 1

Type: ERROR

Impact: Process

OAAM-92000: Job Instance ID's are required.

Cause: No Job Instances were selected.

Action: Select one or more Job Instances, and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-92001: Job Instance ID's cannot be null.

Cause: Job Instance was not selected.

Action: Select one or more Job Instances, and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-92002: Job Instance with Job instance ID {0}, does not exist.

Cause: Invalid Job Instance ID {0} was selected. It may have been deleted.

Action: Refresh the list of Job Instances, then select one or more valid Job Instances and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-92100: Job Instance named "{0}" cannot be paused. Current status is "{1}".

Cause: Job Instances in "{1}" status cannot be paused.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-92101: Job Instance named "{0}" cannot be resumed. Current status is "{1}".

Cause: Job Instances in "{1}" status cannot be resumed.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-92102: Job Instance named "{0}" cannot be canceled. Current status is "{1}".

Cause: Job Instances in "{1}" status cannot be canceled.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-93000: Job ID's are required.

Cause: No Job were selected.

Action: Select one or more Jobs, and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-93001: Job ID cannot be null.

Cause: Job was not selected.

Action: Select one or more Job, and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-93002: Job with Job ID {0}, does not exist.

Cause: Invalid Job ID {0} was selected. It may have been deleted.

Action: Refresh the list of Jobs, then select one or more valid Jobs and try again.
Level: 1

Type: ERROR

Impact: Process

OAAM-93003: Job named "{0}" cannot be processed now.

Cause: There exists Job of same type in Running status.

Action: Try after some time.
Level: 1

Type: ERROR

Impact: Process

OAAM-93100: Job named "{0}" cannot be enabled. Current status is "{1}".

Cause: Job in "{1}" status cannot be enabled.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-93101: Job named "{0}" cannot be disabled. Current status is "{1}".

Cause: Job in "{1}" status cannot be disabled.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-93102: Job named "{0}" cannot be deleted. Current status is "{1}".

Cause: Job in "{1}" status cannot be deleted.

Action: Select another action.
Level: 1

Type: ERROR

Impact: Process

OAAM-93103: Job with Job Name {0} cannot be deleted. The job has already Run.

Cause: Job {0} cannot be deleted.

Action: Try disabling the job instead of deleting.
Level: 1

Type: ERROR

Impact: Process

OAAM-94100: Job cannot be null.

Cause: Job was not selected.

Action: Select a Job, and try again.
Level: 1

Type: ERROR

Impact: Process

5 OAM-00001 to OAM-36105

OAM-00001: Cannot parse the session token.

Cause: The session token appears to be invalid.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-00002: Error occurred while handling the request.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-00003: Request-Response handler configuration is incomplete.

Cause: A request handler mapping was missing.

Action: Add the missing handler mapping to the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-00004: Cannot initialize the Diagnostic Engine.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-00005: Cannot locate the custom login page.

Cause: The custom login page was not found.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-00006: Cannot locate the configuration of the custom login page.

Cause: The custom custom login page was not specified in the configuration.

Action: Add the custom login page location to the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-00007: Cannot edit the custom login page

Cause: The file permissions of the custom login page do not allow write access.

Action: Change the file permissions to allow write access.
Level: 15

Type: ERROR

Impact: Other

OAM-00008: Cannot close the custom login page

Cause: The source code of the custom login page does not support closing of the login page.

Action: Check the custom login page source code.
Level: 15

Type: ERROR

Impact: Other

OAM-00009: Unable to parse the redirection URL

Cause: An error occurred while parsing the redirect URL due to bad encoding or invalid format.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-000010: Cannot add query params to map for logout redirection

Cause: URLDecoder throwing UnsupportedEncodingException

Action: Check the AMLogoutResponseHandler - getQueryMap method code.
Level: 15

Type: ERROR

Impact: Other

OAM-000011: Cannot parse the request token sent from client with User Agent {0} and IP Address {1}.

Cause: The request token appears to be invalid.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-000012: Cannot construct the request token.

Cause: Could not create OAM request token.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-000013: Cannot construct OAM session token.

Cause: Could not create SSO Session token.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-000014: {0} set in {1} must be an integer greater-than or equal to zero.

Cause: SwitchGetToPostLimit was set incorrectly for the authentications scheme.

Action: Correct the SwitchGetToPostLimit challenge parameter within the authentication scheme.
Level: 15

Type: WARNING

Impact: Other

OAM-02001: Retrieve SSO session operation failed.

Cause: Cannot retrieve the SSO session from the request context. Session might have expired.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-02002: Error while processing the submitted credentials.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-02003: Error while processing credential collection.

Cause: An internal error occurred.

Action: Check the authentication scheme configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02004: Error while processing authorization request.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-02005: Error while parsing the SSO session token.

Cause: Error while parsing the SSO session token. Wrong session token format.

Action: Retry. If the error persists verify the key roll-over configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02006: Insufficient authentication level to access the resource.

Cause: An insufficient authentication level was used to access the resource.

Action: Step up the authentication level by re-authenticating to the required level.
Level: 15

Type: ERROR

Impact: Other

OAM-02007: Insufficient privileges. Authorization Denied.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02008: Password expired. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02009: Password reset required. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02010: User account is locked. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02011: No user account found. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02012: No user name password combination found. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02013: Password Policy action not supported by the client. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02052: SME Adapter initialization Failed.

Cause: SME adapter initialization failed.

Action: Verify the SME configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02053: Component {1} initialization Failed.

Cause: Component initialization failed.

Action: Verify the server configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02054: SSO session creation failed.

Cause: Session Management Engine error.

Action: Check Session Management Engine error logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02055: Retrieve SSO session operation failed.

Cause: Session might be expired.

Action: If the problem persists contact the administrator.
Level: 15

Type: ERROR

Impact: Other

OAM-02056: An error occurred while parsing the server token.

Cause: TPE token parsing failed.

Action: check Token Processing Engine logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02057: Wrong Flow Controller configuration for {1}

Cause: Wrong Flow controller configuration

Action: Check flow controller class name and configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02058: Event Flow goes in infinite loop.

Cause: Wrong configuration or too many allowed login attempts.

Action: Check event flow configuration and login attempt configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02059: Flow Controller Cannot handle Event

Cause: Wrong Flow controller configuration

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02060: Flow Controller :{0} Cannot handle Event :{1}

Cause: Wrong Flow controller configuration

Action: Check event to flow controller mapping.
Level: 15

Type: ERROR

Impact: Other

OAM-02061: Event Handler error.

Cause: Wrong event handler configuration

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02062: Event Handler cannot handle the event.

Cause: Wrong event handler configuration

Action: Check event to event handler controller mapping.
Level: 15

Type: ERROR

Impact: Other

OAM-02063: Event Handler :{0} Cannot handle Event :{1}

Cause: Wrong event handler configuration

Action: Check event to event handler controller mapping.
Level: 15

Type: ERROR

Impact: Other

OAM-02064: Authentication Error during policy matching.

Cause: Authentication Error

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02065: Configuration Service Adapter initialization Failed.

Cause: SConfiguration Service failed.

Action: Verify the system configuration file
Level: 15

Type: ERROR

Impact: Other

OAM-02066: Event Factory is not configured create the requested event.

Cause: Wrong event factory configuration

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02067: Wrong event configuration. No event handler specified for event {0}.

Cause: Wrong event factory configuration

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02068: Error occurred while configuring the request cache.

Cause: Wrong request cache handler class configuration.

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02069: Error occurred while loading cache handler for class Name {0}

Cause: Wrong request cache handler class configuration.

Action: Check error log more details.
Level: 15

Type: ERROR

Impact: Other

OAM-02070: An error occurred while loading server aliases.

Cause: TPE token parsing failed.

Action: check system configuration if the aliases are set up properly logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02071: No host configuration found for the alias {0}.

Cause: TPE token parsing failed.

Action: check system configuration if the aliases are set up properly logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02072: Ignoring failure during Identity Store operation.

Cause: Operation to read or update user attribute in Identity Store resulted in exception.

Action: Check the availability of configured Identity Store.
Level: 15

Type: WARNING

Impact: Other

OAM-02073: Error while checking if the resource is protected or not.

Cause: TPE token parsing failed.

Action: check system configuration if the aliases are set up properly logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02074: Error while checking if the resource {0} is protected or not.

Cause: TPE token parsing failed.

Action: check system configuration if the aliases are set up properly logs.
Level: 15

Type: ERROR

Impact: Other

OAM-02075: Component {0} initialized successfully.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02076: {0} Engine initialized successfully.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02077: SSO Engine initialized Successfully.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02078: Processing Event {0}

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02079: SSO session created with session ID {0} for request ({1})

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02080: Cache data sync:{0} for request {1};

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02081: Created {0} : {1}

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02082: Diagnostic Engine Registration failed for Controller Collector.

Cause: Diagnostic Engine Registration failed.

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02083: Diagnostic Engine Registration failed for Credential Collector Controller.

Cause: Diagnostic Engine Registration failed.

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02084: Credential collection process success.

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02085: Successfully validated the submitted credentials.

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02086: {0}: processing Event:{1}.

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02087: Policy ID : {0}

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02088: Scheme result : {0}

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02089: Is Resource Protected status : {0}

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02090: Status : {0}

Cause:

Action: None
Level: 15

Type: ERROR

Impact: Other

OAM-02091: Challenge URL : {0}

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02092: Session Updation Failed

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02093: Session response name {0} is reserved for OAM Server. Value for this response will not be updated in session.

Cause: A session response is configured with name that is internally reserved for OAM Server

Action: Please change the name of the session response not to conflict with OAM Server reserved names
Level: 15

Type: WARNING

Impact: Other

OAM-02094: Assert credential process success.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02095: Assert credential process failed.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02096: An error occurred while building the DAP token {0}.

Cause: Constructing the outgoing DAP token failed.

Action: Check the key and parameters in token.
Level: 15

Type: ERROR

Impact: Other

OAM-02097: An error occurred while decrypting the DAP token {0}.

Cause: Decrypting the incoming DAP token failed.

Action: Check the key configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02098: Cannot parse the DAP token.

Cause: Error occured while parsing the token.

Action: Check the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-02099: {0}: Event processing finished :{1} with status {2}.

Cause:

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-02100: User account is disabled. Authentication failed.

Cause: Insufficient privileges.

Action: Check the authorization permissions.
Level: 15

Type: ERROR

Impact: Other

OAM-02101: An error occurred while creating impersonation session

Cause: Impersonation session creation failed

Action: Check the create impersonation session event
Level: 15

Type: ERROR

Impact: Other

OAM-02102: An error occurred in retrieving the grant

Cause: Unable to retrieve the grants

Action: Check the grant permissions
Level: 15

Type: ERROR

Impact: Other

OAM-02103: An error occurred in end impersonate session

Cause: Unable to do end impersonate session

Action: Check the end impersonate session event
Level: 15

Type: ERROR

Impact: Other

OAM-02104: An error occurred while creating subject for impersonatee

Cause: Authentication Exception thrown while creating subject for impersonatee

Action: Check the createSubject method in SSOEngineController
Level: 15

Type: ERROR

Impact: Other

OAM-02105: An error occurred in end impersonate session

Cause: Policy Manager Exception thrown while creating subject for impersonatee

Action: Check the createSubject method in SSOEngineController
Level: 15

Type: ERROR

Impact: Other

OAM-02106: An error occurred while terminating session

Cause: Unable to terminate session

Action: Check the terminate session event
Level: 15

Type: ERROR

Impact: Other

OAM-02107: An error occurred while enumerating session

Cause: Unable to enumerate session

Action: Check the enumerate sessions event
Level: 15

Type: ERROR

Impact: Other

OAM-02108: An error occurred while updating session attributes

Cause: Unable to update session

Action: Check the update session attributes event
Level: 15

Type: ERROR

Impact: Other

OAM-02109: An excluded resource is configured for OSSO agent.

Cause: Excluded resource configured for OSSO agents.

Action: Update the MOD OSSO configuration to include the excluded resource in the public list.
Level: 15

Type: WARNING

Impact: Other

OAM-02110: Event flow controller is executed in infinite loops.

Cause: Wrong configuration.

Action: Check event flow controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-04001: Configuration parameter type mismatch. Param {0}. Expected type {1}. Actual type {2}

Cause: The configuration parameter type was invalid.

Action: Validate the configuration parameter.
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04002: Unsupported value for config parameter. Parameter {0} . Value {1}. {2}

Cause: The specified configuration parameter was not valid.

Action: Validate the configuration parameter.
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04003: OAM proxy started. Listening on port {0}.

Cause: The OAM proxy has started listening on the specified port.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04004: Read configuration parameter {0} = {1}.

Cause: The OAM proxy has loaded its configuration.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04005: Client connection accepted.

Cause: A client TCP/IP connection was accepted.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04006: Client connection closed. Connection id {0}.

Cause: A client TCP/IP connection was closed.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04007: Message received from client. Message {0}, Host : {1} Port : {2}.

Cause: A message was received from a client on the NAP channel.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04008: Message sent to client. Message {0}, Host : {1} Port : {2}.

Cause: A message was sent to a client on the NAP channel.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04009: New Outbound connection created with OAM Access Server.

Cause: An outbound connection was created with an OAM 10g server.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04010: Message received on outbound channel from OAM Access server. Message {0}, Host : {1} Port : {2}.

Cause: A message was received from an OAM 10g server.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04011: Message sent on outbound channel to OAM 10g Access server. Message {0}, Host : {1} Port : {2}.

Cause: A message was sent to an OAM 10g server.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04012: Outbound connection closed.

Cause: A connection with an OAM 10g server was closed.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04013: Unexpected message received from client. Message {0}

Cause: An unexpected message was received when a simple mode handshake message from the client was expected.

Action: Check the NAP mode configuration of the WebGate and the Server.
Level: 1

Type: WARNING

Impact: Other

OAM-04014: Malformed message received from client. Details {0}

Cause: The length of message received from client was less than 0.

Action: Restart the WebGate if the message is being received repeatedly.
Level: 1

Type: WARNING

Impact: Other

OAM-04015: Outbound connection to Access Server not found.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: WARNING

Impact: Other

OAM-04016: Session ID is missing in AmResponse

Cause: The session ID was not present in the OAM token.

Action: Retry the request.
Level: 1

Type: WARNING

Impact: Other

OAM-04017: OAM proxy end point activation failed. Exception:

Cause: The specified listening port is not available, or is aldready being used.

Action: Restart the server or contact the system administrator.
Level: 1

Type: SEVERE

Impact: Other

OAM-04018: Required configuration parameter missing. Required {0}

Cause: The required configuration parameters were missing.

Action: Verify the configuration.
Level: 1

Type: SEVERE

Impact: Other

OAM-04019: Work manager JNDI lookup failed. Exception:

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04020: Exception encountered while processing the request message:

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04021: NMP initialization failed.

Cause: The NAP handshake with the client failed or an unsupported application was trying to connect to the OAM proxy.

Action: Verify the client version.
Level: 1

Type: SEVERE

Impact: Other

OAM-04022: SSL configuration is not specified for SIMPLE or CERT mode

Cause: The SSL configuration was required but not supplied for the SIMPLE or CERT mode.

Action: Verify the SSL Configuration and rerun the operation.
Level: 1

Type: SEVERE

Impact: Other

OAM-04023: SSL handshake failed. Exception:

Cause: The NAP handshake with a client was not successful.

Action: Check the client configuration.
Level: 1

Type: SEVERE

Impact: Other

OAM-04024: Exception in outbound message processing. Cause {0} . Message details {1}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04025: Error in connecting to Access server. {0}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04026: Error in NAP handshake with AAA server {0}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04027: Cannot create Executor instance

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04028: Outbound Resource Adapter initialization error. {0}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04029: Error in generating AMEvent. Details {0}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04030: Partner lookup failed. Partner id {0}

Cause: The retrieval of partner metadata during client authentication was not successful.

Action: Check if the partner is registered with the Access Server.
Level: 1

Type: SEVERE

Impact: Other

OAM-04031: NAP version mismatch during the NAP handshake. Client Message {0}

Cause: An unsupported NAP version was sent by the client.

Action: Check the client configuration and version. Older clients may need to be upgraded.
Level: 1

Type: SEVERE

Impact: Other

OAM-04032: PAT API error. Details {0}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04033: Error in retrieving secret information. {0} {1}

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04034: Token Cache Enabled.

Cause: Information message indicating that the token cache is enabled.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-04035: Error while reading token cache size from configuration.

Cause: The cache configuration was invalid.

Action: Fix cache configuration and rerun the operation.
Level: 15

Type: ERROR

Impact: Other

OAM-04036: Channel security mode is different as specified in configuration {0}

Cause: The agent tried to communicate in a mode different from its configuration.

Action: Check the agent mode. This may be a security issue if the configuration mode of agent is correct.
Level: 1

Type: SEVERE

Impact: Other

OAM-04037: Exception encountered while processing the HTTP message in OAM proxy:

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAM-04038: OAM proxy configuration parameter SSOOnlyMode is set to true. OAM proxy will skip authorization.

Cause: OAM proxy configuration parameter SSOOnlyMode is set to true.

Action:
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-04039: Agent {0} not privileged to invoke OPCODE {1}

Cause: Agent is not privileged to invoke the operation.

Action: Check the agent configuration.
Level: 1

Type: WARNING

Impact: Other

OAM-04040: Target Resource is not as expected. Target Resource {0} WebGate resource {1}

Cause: Target resource is not as expected. This issue may occur in session scope operations.

Action: Runtime check failure. Check server logs.
Level: 1

Type: WARNING

Impact: Other

OAM-04041: Failed to retrieve valid session from OAM Identity Assertion. Assertion {0}

Cause: Either invalid assertion was specified or session corresponding to assertion is invalid.

Action: Please see logs for more details.
Level: 1

Type: WARNING

Impact: Other

OAM-04042: Failed to check token issuance policy. Resource: {0}. Requestor: {1}

Cause: Evaluation of Token Issuance Policy failed.

Action: Check Token Issuance Policy.
Level: 1

Type: WARNING

Impact: Other

OAM-04043: Request is not processed. Access management service is disabled.

Cause: Access management service is not enabled on server.

Action: Enable the access management service. Set oam proxy global parameter "10gCompatibleGetHostIdentifiersSupport" to true.
Level: 1

Type: WARNING

Impact: Other

OAM-06001: Cannot parse the session token.

Cause: The session token is invalid or the wrong decryption key is present in the configuration.

Action: Verify the key roll-over configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10001: Cannot load the configuration file.

Cause: The configuration file location was invalid.

Action: Verify the location of the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAM-10002: Cannot initialize the PAT Adapter.

Cause: The PAT configuration was invalid.

Action: Verify the PAT configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10003: Cannot initialize the Cache Handlers.

Cause: The request cache handler configuration was invalid.

Action: Verify the request cache handler configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10004: Cannot initialize the Controller.

Cause: The configuration for Controller events was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10005: Cannot initialize the Controller.

Cause: The configuration for the Flow controllerd was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10006: Cannot initialize the Controller.

Cause: The configuration for the Flow Mapping was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10007: Cannot initialize the Controller.

Cause: The configuration for the Event Handlers was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10008: Cannot initialize the Controller.

Cause: The configuration for the Event UI was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10009: Cannot initialize the Controller.

Cause: The Event Handler configuration was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10010: Cannot initialize the Controller.

Cause: The Event Factory configuration was invalid.

Action: Verify the Controller configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10011: An invalid Cookie Domain

Cause: The cookie domain was invalid.

Action: Verify the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAM-10012: Cannot load audit configuration.

Cause: The audit configuration was invalid.

Action: Verify the audit configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10013: Cannot load audit configuration.

Cause: Mismatch between logger and resource configuration.

Action: Verify the audit configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10014: Invalid done URL specified during logout - {0}.

Cause: Done URL specified during logout is not in proper URL format.

Action: Verify the done URL.
Level: 15

Type: ERROR

Impact: Other

OAM-10015: Cache Info :: operation="{0}" paramName="{1}", paramDetail="{2}".

Cause: Displayed when the cache is operating.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-10016: Cache entry expired.

Cause: Displayed on expiry of the cached element.

Action: None.
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-10017: Cannot intialize the server key.

Cause: Unable to retrieve server key from configuration.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-10018: No credcollect req resp handler specified

Cause: No credcollect req resp handler specified

Action: Verify configuration cred collect req resp handler
Level: 15

Type: ERROR

Impact: Other

OAM-12001: Cannot load audit configuration.

Cause: The specified configuration file does not exist, or the audit configuration is invalid.

Action: Check the server error logs.
Level: 15

Type: ERROR

Impact: Other

OAM-12002: User name value specified for special user is invalid.

Cause: The input value format is invalid, or exceeds 30 characters.

Action: Correct the input value.
Level: 15

Type: ERROR

Impact: Other

OAM-12003: Maximum directory size specified is invalid.

Cause: The input value format is invalid, is less than 1 or exceeds 1024.

Action: Correct the input value.
Level: 15

Type: ERROR

Impact: Other

OAM-12004: Maximum file size specified is invalid.

Cause: The input value format is invalid, is less than 1 or exceeds 1024.

Action: Correct the input value.
Level: 15

Type: ERROR

Impact: Other

OAM-12005: Map of audit events is invalid.

Cause: The audit event configuration is missing, or invalid.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-12006: Invalid path for audit event definitions file.

Cause: The audit event definitions file location is incorrect.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-12007: Invalid path for audit bustop directory.

Cause: The audit bustop location is missing, or invalid.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-12501: Getting ServerTokenMapper for: {0}.

Cause: Getting ServerTokenMapper for {0}

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12502: Server Token Not available in the Response.

Cause: Server Token Not available in the Response.

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12503: 10g SSO_ID Token set {0} .

Cause: 10g SSO_ID Token set.

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12504: 10g SSO_ID Decrypted successfully : {0}

Cause: 10g SSO_ID Decrypted successfully.

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12505: Removing the SSO_ID Cookie at Logout.

Cause: Removing the SSO_ID Cookie at Logout.

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12506: "Creating session token with values - " + "Domain: {0}, Version: {1}, Age: {2}, Secure: {3}, " + "Value: {4}";

Cause: Created Session Token with values

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12507: Token Version not found.

Cause: Token Version not found.

Action: Validate the config to include the Token Version.
Level: 15

Type: ERROR

Impact: Other

OAM-12508: 10g SSO_ID Decryption failed.

Cause: 10g SSO_ID Decryption failed.

Action: Verify if the 10gSSO Server Key is present in the config
Level: 15

Type: ERROR

Impact: Other

OAM-12509: Could not get token mapper for token for {0}.

Cause: Could not get token mapper for token.

Action: Validate the config to include the Token Version.[v1.2, v1.4]
Level: 15

Type: ERROR

Impact: Other

OAM-12510: 10g SSO_ID Token NOT created.

Cause: 10g SSO_ID Token NOT created.

Action: Verify if the 10gSSO Server Key/Token Version is present in the config
Level: 15

Type: ERROR

Impact: Other

OAM-12511: Error while creating SSO Transport token.

Cause: Error while creating Transport Token

Action: Validate the config to check for the 10g SSO Server Key
Level: 15

Type: ERROR

Impact: Other

OAM-12512: Cannot retrieve the 10g SSO Key

Cause: Cannot retrieve the 10g SSO Key

Action: Validate the config to check for the 10g SSO Server Key
Level: 1

Type: SEVERE

Impact: Other

OAM-12513: Diagnostic Engine Failed to Start

Cause: Diagnostic Engine Failed

Action: None
Level: 16

Type: NOTIFICATION

Impact: Other

OAM-12514: Request Handling Error

Cause: Request Handling Error

Action: None
Level: 15

Type: ERROR

Impact: Other

OAM-12515: Session Token Not Found

Cause: Session Token Not Found

Action: None
Level: 15

Type: ERROR

Impact: Other

OAM-12516: 10g SSO Server Config Details Missing

Cause: 10g SSO Server Config Details Missing

Action: Add the Config details to oam-config.xml
Level: 15

Type: ERROR

Impact: Other

OAM-12517: OSSO 10g Server coexist token version configured does not match runtime token version

Cause: 10g SSO Server coexist token version and runtime token versions does not match.

Action: Update the OSSO 10g coexist token version to match the runtime version
Level: 15

Type: ERROR

Impact: Other

OAM-14001: Unregistration of OAM Management MBean failed.

Cause: An internal error occurred.

Action: Check the OAM Server logs.
Level: 15

Type: ERROR

Impact: Other

OAM-14002: OAM Server configuration update failed.

Cause: Failed to update OAM Policy or System Configuration.

Action: Check the OAM Server MBean logs.
Level: 15

Type: ERROR

Impact: Other

OAM-14003: Invalid HostIdentifier configuration for AppDomain {0} in OAM Policy.

Cause: Definition of HostIdentifier for application domain was invalid.

Action: Re-check Application Domain configuration in OAM Policy.
Level: 15

Type: ERROR

Impact: Other

OAM-14005: Validation of a input parameter failed.

Cause: One of the input parameter value was illegal.

Action: Check the OAM Server MBean logs.
Level: 15

Type: ERROR

Impact: Other

OAM-14007: Cannot retrieve OAM Server configuration for {0}.

Cause: Cannot retrieve data from OAM System configuration.

Action: Check the OAM Server MBean logs.
Level: 15

Type: ERROR

Impact: Other

OAM-14008: Partner configuration for {0} already exist in system config.

Cause: A partner is already configured.

Action: Delete existing partner or create partner with a different id.
Level: 15

Type: ERROR

Impact: Other

OAM-14009: Application Domain not found in OAM Policy {0}.

Cause: None

Action: None
Level: 15

Type: ERROR

Impact: Other

OAM-14100: Host Information is already registered in OAM HostIdentifier with host {0} and port {1}.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14101: Starting Enable OIM Configuration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14102: Starting Disable OIM Configuration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14103: Completed OAM Server Policy Configuration update.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14104: Completed OAM Server System Configuration update.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14105: Completed OIM Configuration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14106: Completed validation of Input values.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14107: Successfully updated OAM Partner data.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14108: Successfully updated OAM Configuration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14109: Enables OIM Integration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14110: Disables OIM Integration.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14111: Registration of OAM Management MBean failed.

Cause: An internal error occurred.

Action: Check the OAM Server logs.
Level: 15

Type: ERROR

Impact: Other

OAM-14112: Gets the manage server host, NAP port.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14113: Updates OIM host and port.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14114: Error in getting the OAM server info.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-14115: Create and configure OAM partner.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-16001: Cannot parse the session token.

Cause:

Action:
Level: 15

Type: ERROR

Impact: Other

OAM-18001: User Identity Store Configuration is not valid.

Cause: The user identity store configuration was missing, or was invalid.

Action: Verify the user identity store configuration.
Level: 1

Type: ERROR

Impact: Other

OAM-18002: Error while reading User Identity Store Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18003: Error while reading User Identity Store Configuration attribute "{0}".

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18004: User Identity Store name passsed as NULL during user identity store read operation.

Cause: User Identity Store name passsed to read operation was null.

Action: Rerun with actual object.
Level: 1

Type: ERROR

Impact: Other

OAM-18005: User Identity Store ID passsed as blank during user identity store read operation.

Cause: User Identity Store ID passsed to read operation was blank.

Action: Rerun with a valid ID.
Level: 1

Type: ERROR

Impact: Other

OAM-18006: Map of Properties passed as NULL during user identity store create operation.

Cause: Map of Properties passed to create operation was null.

Action: Rerun by passing Map of properties.
Level: 1

Type: ERROR

Impact: Other

OAM-18007: Empty Map of Properties passed during user identity store create operation.

Cause: Map of Properties passed to create operation was empty.

Action: Rerun by passing Map of properties.
Level: 1

Type: ERROR

Impact: Other

OAM-18008: NULL passed during user identity store modify operation.

Cause: Object passed to modify operation was null.

Action: Rerun with actual object.
Level: 1

Type: ERROR

Impact: Other

OAM-18009: Validation Failure - an User Identity Store named "{0}" already exists.

Cause: User Identity Store names must be unique.

Action: Choose a different name for this User Identity Store.
Level: 1

Type: ERROR

Impact: Other

OAM-18010: Exception while encrypting the credetial for User Identity Store.

Cause: Exception while encrypting the crendential for User Idenity Store.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18011: Validation Failure - User Identity Store "{0}" is referred in following authentication schemes : "{1}".

Cause: User Identity Store is referred in authentication schemes.

Action: Delete or change the reference of this User Identity Store from the authentication schemes that refer to it.
Level: 1

Type: ERROR

Impact: Other

OAM-18012: Exception while processing the User Identity Store properties.

Cause: An internal error occurred, Unknown type found while processing.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18013: Exception while processing the User Identity Store properties.

Cause: An internal error occurred, type found as NULL while processing.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18014: Validation Failure - NULL Value passed for property "{0}".

Cause: Value found as NULL for a property.

Action: Rerun with the value of property set.
Level: 1

Type: ERROR

Impact: Other

OAM-18015: Server Configuration is not valid.

Cause: The server configuration was missing, or was invalid.

Action: Verify the server configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-18016: Cannot initialize the Data Sources Manager.

Cause: Configuration store instance found null.

Action: For more details, start logging at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18017: Cannot initialize the Authentication Modules Manager.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18018: Cannot initialize the Server Manager.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18019: Create : {0} : paramList=[{1}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18020: Created : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18021: Modify : {0} : Existing=[{1}] : New=[{2}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18022: Modified to : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18023: Delete : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18024: Deleted : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18025: Read : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18026: After Read : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18027: Read All : {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18028: After Read All : {0} : list is : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-18029: Validation Failure : "{0}" attributes missing in User Identity Store.

Cause: The required attributes were not present in the user identity store.

Action: Add the attributes to the user identity store and rerun the operation.
Level: 1

Type: ERROR

Impact: Other

OAM-18030: Validation Failure : "{0}" attributes missing in OAM Server Instance.

Cause: The required attributes were not specified for the server instance.

Action: Add the attributes to the server instance and rerun the operation.
Level: 1

Type: ERROR

Impact: Other

OAM-18031: Validation Failure : "{0}" attributes missing in {1} Authentication Module.

Cause: The required attributes were not specified for the authentication module.

Action: Add the attributes to the authentication module and rerun the operation.
Level: 1

Type: ERROR

Impact: Other

OAM-18032: Validation Failure - Object not found for deletion.

Cause: The object supplied for deletion has been deleted, or does not exist.

Action: Use the correct data and rerun the operation.
Level: 1

Type: ERROR

Impact: Other

OAM-18033: Validation Failure : {0} Module cannot be deleted. (Referred in Scheme).

Cause: The module was being referred to in a scheme.

Action: Remove the reference from the scheme and then delete the module.
Level: 1

Type: ERROR

Impact: Other

OAM-18034: Authentication module configuration is not valid.

Cause: The authentication module configuration was missing, or was invalid.

Action: Verify the authentication module configuration.
Level: 15

Type: ERROR

Impact: Other

OAM-18035: Validation Failure - a server Instance named "{0}" already exists.

Cause: Same name used for creating a new server instance.

Action:
Level: 15

Type: ERROR

Impact: Other

OAM-18036: OAM Server name passed as NULL during oam server update operation.

Cause: An internal error occurred.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-18037: OAM Server id passed as NULL during oam server update operation.

Cause: User Identity Store name passed to read operation was null.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-18038: The response cookie configuration for update is invalid.

Cause: Invalid OSSO Proxy configuration found during configuration update.

Action: Check the parameter passed during OSSO-Proxy configuration update.
Level: 1

Type: ERROR

Impact: Other

OAM-18039: The global response cookie configuration cannot be deleted.

Cause: The global OSSO response cookie configuration delete is not allowed.

Action: Check the parameter passed during OSSO-Proxy configuration update.
Level: 1

Type: ERROR

Impact: Other

OAM-18040: Error while reading {0} Authentication Module Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18041: Error while reading OAM Server Instance Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18042: The Unique ID for server is null.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18043: The OAM server is null.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18044: Error while reading {0} OAM Server Instance Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18045: OAM Server name passsed as NULL during server read operation.

Cause: User Identity Store name passsed to read operation was null.

Action: Rerun with actual object.
Level: 1

Type: ERROR

Impact: Other

OAM-18046: OAM Server ID passsed as blank during server read operation.

Cause: User Identity Store ID passsed to read operation was blank.

Action: Rerun with a valid ID.
Level: 1

Type: ERROR

Impact: Other

OAM-18047: Error while reading Kerberos Authentication Module Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18048: The Unique Authn module ID is null.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18049: The authn module is null.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18050: Error while reading LDAP Authentication Module Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18051: Error while reading X509 Authentication Module Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18052: Error while reading DAP Authentication Module Configuration.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18053: Internal error occurred while reading {0} Authentication module.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18054: An Authentication Module with name {0} already exists, please specify another name.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18055: Internal error occurred while reading OAM Server {0}.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18056: Internal error occurred while reading Load Balancing Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18057: Internal error occurred while updating Load Balancing Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18058: Internal error occurred while reading SSO Engine Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18059: Internal error occurred while updating SSO Engine Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18060: Internal error occurred while reading Coherence Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18061: Internal error occurred while updating Coherence Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18062: Internal error occurred while reading Session Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18063: Internal error occurred while updating Session Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18064: Internal error occurred while reading Access Protocol Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18065: Internal error occurred while updating Access Protocol Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18066: Internal error occurred while reading Policy Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18067: Internal error occurred while updating Policy Settings.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18068: Invalid Orchestration Strategy.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18069: Error saving Custom Authentication Module.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18070: Custom Authentication module is unavailable.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18071: Error deleting Custom Authentication Module.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18072: Custom Authentication module already exists.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18073: The specified ID Store is not a System Store.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-18074: Delete operation on System Identity Store is not allowed.

Cause: An internal error occurred.

Action: For more details, start foundation config logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-20001: Deleted application domain {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20002: Duplicated application domain {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20003: Saved authentication scheme {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20004: Deleted authentication scheme {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20005: Duplicated authentication scheme {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20006: Button with id {0} is disabled {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20007: Set authentication scheme {0} as the default scheme.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20008: Set {0} as the default authentication scheme.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20009: Saved host identifier {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20010: Deleted host identifier {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20011: Duplicated host identifier{0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20012: Deleted host identifier entry with key {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20013: Saved resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20014: Deleted resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20015: Duplicated resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20016: Saved authentication policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20017: Deleted authentication policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20018: Duplicated authentication policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20019: Saved authorization policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20020: Deleted authorization policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20021: Duplicated authorization policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20022: Saving authentication policy response {0}, {1}, {2}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20023: Saved authentication policy response {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20024: Deleted authentication policy response row with key {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20025: Deleted authentication policy response {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20026: Saved authentication policy resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20027: Deleted authentication policy resource with key {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20028: Deleted authentication policy resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20029: Saving authorization policy response {0}, {1}, {2}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20030: Saved authorization policy response {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20031: Deleted authorization policy response with key {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20032: Deleted authorization policy response {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20033: Saved authorization policy resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20034: Deleted authorization policy resource with key {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20035: Deleted authorization policy resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20036: Added {0}:{1}:{2} constraint.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20037: Added constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20038: Saved constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20039: Deleted constraint with key {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20040: Deleted constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20041: Fetching details for master constraint {0}:{1}:{2}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20042: Saved details for temporal constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20043: Cancelled detail changes for temporal constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20044: Saved details for ip4 constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20045: Cancelled detail changes for ip4 constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20046: Saved details for identity constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20047: Cancelled detail changes for identity constraint {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20048: Added {0}:{1} under identity constraint.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20049: Deleted key {0}:{1} under identity constraint.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20050: Deleted {0}:{1} under identity constraint.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20051: Searching for {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20052: Saved component {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20053: Created component {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20054: Duplicated component {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20055: Deleted component {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20056: Recording action:{0}, child node:{1}, appdomain name:{2}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20057: Cancelled application domain {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20058: Cancelled authentication scheme {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20059: Cancelled host identifier {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20060: Cancelled resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20061: Cancelled authentication policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20062: Cancelled authorization policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20063: Successfully saved application domain {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20100: Cannot save application domain {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20101: Cannot delete application domain {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20102: Cannot duplicate application domain{0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20103: Cannot save authentication scheme {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20104: Cannot delete authentication scheme {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20105: Cannot duplicate authentication scheme {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20106: Cannot set {0} as the default authentication scheme.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20107: Cannot save host identifier {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20108: Cannot delete host identifier {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20109: Cannot duplicate host identifier {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20110: Cannot save resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20111: Cannot delete resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20112: Cannot duplicate resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20113: Cannot save authentication policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20114: Cannot duplicate authentication policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20115: Cannot delete authentication policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20116: Cannot save authorization policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20117: Cannot duplicate authorization policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20118: Cannot delete authorization policy {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20119: Cannot initialize authentication policy response.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20120: Cannot save authentication policy response {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20121: Cannot delete authentication policy response {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20122: Cannot save authentication policy resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20123: Cannot delete authentication policy resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20124: Cannot initialize authorization policy response.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20125: Cannot save authorization policy response {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20126: Cannot delete authorization policy response {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20127: Cannot save authorization policy resource {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20128: Cannot delete authorization policy resource {0}.

Cause: AuthzPolicyResource delete failed.

Action: AuthzPolicyResource delete failed.
Level: 15

Type: ERROR

Impact: Other

OAM-20129: Cannot save constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20130: Cannot delete constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20131: Cannot save details for temporal constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: INFO

Impact: Other

OAM-20132: Cannot cancel detail changes for temporal constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: INFO

Impact: Other

OAM-20133: Cannot save details for ip4 constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: INFO

Impact: Other

OAM-20134: Cannot cancel detail changes for ip4 constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: INFO

Impact: Other

OAM-20135: Cannot save details for identity constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: INFO

Impact: Other

OAM-20136: Cannot cancel detail changes for identity constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 1

Type: INFO

Impact: Other

OAM-20137: Cannot save details for identity constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20138: Cannot delete details under identity constraint {0}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20139: Error occurred while searching for {0}:{1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20140: Cannot save component {0}:{1}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20141: Cannot create component {0}:{1}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20142: Cannot duplicate component {0}:{1}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20143: Cannot delete component {0}:{1}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20144: Cannot cancel action for component {0}:{1}.

Cause: An internal error occurred.

Action: For more details,start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-20145: Cannot cancel application domain {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20146: Cannot cancel authentication scheme {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20147: Cannot cancel host identifier {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20148: Cannot cancel resource {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20149: Cannot cancel authentication policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-20150: Cannot cancel authorization policy {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-21000: Create : {0} : paramList=[{1}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-21001: Created {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-21002: Modify : {0} : Existing=[{1}] : New=[{2}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-21003: Modified to : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-21004: Exception encountered while parsing start date of OSSO Agent!

Cause: An internal exception occurred.

Action: For more details, start oam console logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-21005: NULL Refresh Call back.

Cause: Refresh Call back object for refreshing LHS tree found NULL.

Action: For more details, start oam console logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-21006: NULL Registration Server Controller.

Cause: Registration Server Controller found NULL.

Action: For more details, start oam console logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-22001: Error occured during cleanUpPolicy : {0}

Cause: Error occured during cleanUpPolicy.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22002: Error occured during cleanUpApplicationDomains : {0}

Cause: Error occured during cleanUpApplicationDomains.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22003: Error occured during initialization : {0}

Cause: Error occured during initialization.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22004: Error occured during copying HostIdentifiers : {0}

Cause: Error occured during copying HostIdentifiers.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22005: Error occured during copying policy changes : {0}

Cause: Error occured during copying policy changes.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22006: Fetched partners from OAM server.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22007: Applied partners to OAM server.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22008: Switching off policy distribution.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22009: Cleaned up policy file : {0}.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22010: Copied policy changes to the intermediate file.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22011: Switching on policy distribution.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22012: Copied policy changes from the intermediate file.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22013: Added host {0}:{1} to {2}.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22014: Removed host {0}:{1} from {2}.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22015: Removed resource {0} and policies using this resource from application domain {1}.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22016: Error occured during creating application domain : {0}

Cause: Error occured during creating application domain.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22017: Error occured during removing resource : {0}

Cause: Error occured during creating application domain.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22018: Error occured during decrypting key : {0}

Cause: Error occured during decrypting key.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22019: Error occured during encrypting key : {0}

Cause: Error occured during encrypting key.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22020: Authentication module {0} is not present in the production system. Using the authentication module {1} to create the authentication scheme {2}

Cause: Authentication scheme cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22021: Intermediate OAM file was not found in the location {0}. Creating the intermediate file.

Cause: None

Action: None
Level: 15

Type: INFO

Impact: Other

OAM-22022: Error while creating the intermediate OAM policy file : {0}

Cause: Intermediate file cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22023: Error while setting the default authentication scheme: {0}

Cause: Default authentication scheme cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22024: Error while fetching the Partners: {0}

Cause: Error while fetching the Partners.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22025: Error while writing Partners into a intermediate file: {0}

Cause: Error while writing Partners into a intermediate file.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22026: Error while applying Partners: {0}

Cause: Error while applying Partners.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22027: Error while exporting Partners: {0}

Cause: Error while exporting Partners.

Action: Check the OAM t2p logs.
Level: 1

Type: WARNING

Impact: Other

OAM-22028: Error while applying the Policy Configuration to PS1 instance

Cause: Intermediate file cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22029: Error while applying the System Configuration to PS1 instance

Cause: Intermediate file cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22030: Error while applying the KeyStore Configuration to PS1 instance

Cause: Intermediate file cannot be created.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22031: Error while loading the given class dynamically for transformations

Cause: Error in loading the given class dynamically.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22032: Loaded class is not the valid instance of a specific interface

Cause: Loaded class is not a valid instance of given interface

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22033: Transformation class is not found

Cause: Loaded class is not a valid instance of given interface

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22034: Error creating file ouput stream.

Cause: Could not create output stream.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22035: Error creating/writing to object output stream.

Cause: Could not create object output stream.

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22036: Error closing output stream.

Cause: Could not close output stream.

Action: Check the OAM t2p logs.
Level: 15

Type: INFO

Impact: Other

OAM-22037: Error creating file input stream.

Cause: Could not open file input stream

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22038: Error creating object input stream.

Cause: could not open object input stream

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22039: Error deserializing object.

Cause: Could not de-serialize patrner object

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22040: Error reading from object Stream.

Cause: Could not read from object stream

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22041: Error occurred during partner re-registration

Cause: an error occurred during partner re-registration

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22042: Error while migrating partners information

Cause: Error while migrating partners

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22043: Error while getting migrating partners information

Cause: Error while getting migrating partners information

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22044: Error while writing migrating partners information

Cause: Error while writing migrating partners information

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22045: Error while certificate migration

Cause: Error while certificate migration

Action: Check the OAM t2p logs.
Level: 15

Type: ERROR

Impact: Other

OAM-22046: Export policy file with name {0} already exists.

Cause: A file already exists with the same name as policy export file.

Action: Ensure the no file exists with same name as policy export file.
Level: 15

Type: ERROR

Impact: Other

OAM-24001: Unable to execute the WLST Command

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24002: OSSO-Proxy configuration update operation failed.

Cause: The OSSO-Proxy configuration update in OAM system config failed.

Action: Enable detailed logging for details of the failure.
Level: 1

Type: ERROR

Impact: Other

OAM-24003: Given ID Store name doesn't exist

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24004: No properties file provided

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24005: Failed to create user id store in online mode

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24006: Unable to fetch LDAP Properties file

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24007: Value of Cookie passed is invalid

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24008: Error while closing the streams

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24009: Error while copying files

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24010: Error while wrapping and unwrapping files

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24011: Map retrieved from backend is null

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24012: One of the mandatory values is null

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24013: Unknown Version

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24014: LDAP Provider was invalid : {0}

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24015: Edit command parameter value is invalid

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24016: Unable to fetch the Server details

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24021: TAP Redirect URL is invalid, Registration failed.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24022: Unable to contact the TAP Redirect URL, Registration failed.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24023: TAP Redirect URL is null, Registration failed.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24024: Exception fetching the authentication scheme, Registration failed.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24025: TAP Key generation error.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24026: TAP Key store generation error.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24027: TAP Partner Registration Successful.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24028: Error while retrieving keystore password using MBean connection.

Cause: Error while retrieving keystore password using MBean connection.

Action: Error while retrieving keystore password using MBean connection.
Level: 1

Type: ERROR

Impact: Other

OAM-24029: One of the mandatory values is null

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24030: Closing the stream failed.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24031: Error in wrap and unwrap.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24032: Osso proxy cookie value is empty.

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24033: Cannot find LdapProperties file

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-24034: TAP Scheme not available to update TAPRedirect URL

Cause: The WLST command execution failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAM-25001: SSO only mode is not matching true.

Cause: Validation error

Action: Validation error
Level: 1

Type: WARNING

Impact: Other

OAM-25003: Wrong OAM Access Server host name.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25004: Wrong OAM Access Server port.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25005: Wrong OAM second access server host.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25006: Wrong OAM second access server port.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25007: Wrong OIM host name.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25008: Wrong OIM port.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25009: Wrong OIM URL Protocol.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25010: Wrong IDStore host name.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25011: Wrong IDStore port.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25012: Wrong IDSTore SSL flag true.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25013: Identity service not enabled.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25014: Identity service enabled.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25015: SSO only mode is not matching false.

Cause: Validation error

Action: Validation error
Level: 1

Type: WARNING

Impact: Other

OAM-25016: Wrong IDSTore SSL flag false.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25017: Invalid administrator user name.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25018: Invalid administrator user name/password. Login failed.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25019: Invalid administrator user roles.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25020: Error validating administrator user.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25021: Error in certificate validation of connecting url.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25022: Bad SSL Key from the contacting server.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25031: Invalid global WebGate pass phrase.

Cause: Validation error

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25051: Error in retrieving default authentication scheme.

Cause: Invalid Name

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25052: Class name is not passed.

Cause: Invalid Name

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25053: Class name not found in the server mapper.

Cause: Invalid Name

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25054: Error while executing method in test class.

Cause: Invalid Name

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25055: Mapper does not have method.

Cause: Invalid Name

Action: None
Level: 1

Type: WARNING

Impact: Other

OAM-25056: Either cache service is down, or expected to find at least 2 cache nodes and did not. {0} cache nodes running.

Cause: Cache servers are not running.

Action: Restart the admin server.
Level: 1

Type: ERROR

Impact: Other

OAM-25058: User {0} is not authorized to invoke operation on the Oracle Access Management MBeans.

Cause: The user does not have the privileges to access the MBeans.

Action: Verify the System Identity Store configuration to ensure the correct privileges are set.
Level: 1

Type: ERROR

Impact: Other

OAM-30001: Invalid user credentials. Registration failed. Try again after providing valid credentials.

Cause: Username/password credentials provided are invalid.

Action: Try again after providing valid credentials.
Level: 1

Type: ERROR

Impact: Other

OAM-30002: User does not belong to the group that is authorized to perform registration. Registration failed. Try again after verifying the user's group.

Cause: User does not have a valid role to perform remote registration.

Action: Try again after verifying the user's role.
Level: 1

Type: ERROR

Impact: Other

OAM-30003: Agent name "{0}" already exists. Existing agent profile information from the server will be used to generate artifacts.

Cause: Agent name is not unique, it already exists.

Action:
Level: 1

Type: WARNING

Impact: Other

OAM-30004: Agent type is unrecognized or is invalid for the operation being performed: "{0}". Registration failed.

Cause: An internal error occurred due to unknown request type.

Action: For more details, start remote registration logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-30005: Output folder could not be created in the server domain home. Registration failed.

Cause: An internal error occurred as output folder could not be created in the server location.

Action: Verify permissions to create the folder.
Level: 1

Type: ERROR

Impact: Other

OAM-30006: Exception encountered while creating one or more of the output artifacts : {0}.

Cause: An internal error occurred while creating response file.

Action: For more details, start remote registration logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-30007: Exception encountered while validating using User/Role API : {0}. The exception trace is : {1}

Cause: An internal error occurred.

Action: Please verify credentials/role and try again.
Level: 1

Type: ERROR

Impact: Other

OAM-30008: User/Role API not available or could not be initialized. Registration failed.

Cause: An internal error occurred.

Action: For more details, start remote registration logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-30009: Application domain with the same name already exists. Registration failed. Try again after providing a unique application domain(agent name).

Cause: Application domain name is not unique.

Action: Try again after providing a unique application domain(agent name).
Level: 1

Type: ERROR

Impact: Other

OAM-30010: Anonymous authentication scheme does not exist so initial public authn policy cannot be created. Registration failed.

Cause: An internal error occurred as anonymous scheme does not exist.

Action: For more details, start remote registration logging at FINE level.
Level: 1

Type: ERROR

Impact: Other

OAM-30011: The host:port is not unique. A different host identifier with name : "{0}" already exists for this host:port.

Cause: AgentBaseUrl specified is already registered under a different hostidentifier name.

Action: Try again after entering a unique agentBaseUrl value.
Level: 1

Type: ERROR

Impact: Other

OAM-30012: Error in encrypting the secret key. Registration failed.

Cause: An internal error occurred. Error in encrypting the secretkey.

Action: Try again after checking server configuration.
Level: 1

Type: ERROR

Impact: Other

OAM-30013: Error in generating the secret key. Registration failed: {0}

Cause: An internal error occurred. Error in creating the secretkey.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30014: GlobalPassphrase retrieved from server configuration is null. Registration failed.

Cause: An internal error occurred. Error in retrieving globalPassphrase.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30015: Error in decrypting the encrypted globalPassphrase. Registration failed.

Cause: An internal error occurred. Error in decrypting the retrieved globalPassphrase.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30016: Error in obfuscating the decrypted globalPassphrase. Registration failed.

Cause: An internal error occurred. Error in obfuscating the decrypted globalPassphrase.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30017: Internal error occurred. One of the mandatory response parameters is null. Registration failed.

Cause: An internal error occurred. One or more of the mandatory response fields is empty.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30018: Internal error occurred. No response generated, due to either bad input or backend failure. See log file for details.

Cause: An internal error occurred. No response generated due to backend failure.

Action: See log file for details.
Level: 1

Type: ERROR

Impact: Other

OAM-30019: Exception encountered either while creating or writing to the native config file : {0}

Cause: An internal error occurred during creation of native config file

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30020: Exception encountered while writing to the output password file : {0}

Cause: An internal error occurred during creation of output password.xml file

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30021: Error in obfuscating the OSSO agent's output config file (osso.conf). Registration failed.

Cause: An internal error occurred. Error in obfuscating the created osso.conf config file.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30022: Error in creating the credential store (wallet) : {0}

Cause: An internal error occurred. Error in creating the creating the credential store (wallet).

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30023: Error in storing the secretKey in the credential store (wallet): {0}

Cause: An internal error occurred. Error in storing the secretkey in the credential store (wallet).

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30024: Error occurred while parsing the XML file. Error message is : "{0}" at column number : "{1}" and at line number : "{2}"

Cause: The XML file provided is invalid or not well-formed.

Action: Try again after verifying syntax and well-formedness of the XML as per the schema.
Level: 1

Type: ERROR

Impact: Other

OAM-30025: Malformed registration request xml string : "{0}" - {1}

Cause: The XML request string generated is malformed.

Action: Internal error during parsing. Check the input request xml and try again.
Level: 15

Type: ERROR

Impact: Other

OAM-30026: {0}

Cause:

Action:
Level: 15

Type: ERROR

Impact: Other

OAM-30027: Error in unmarshalling operation : {0}

Cause: Error in unmarshalling the XML data.

Action: Try again after verifying syntax and well-formedness of the XML as per the schema.
Level: 1

Type: ERROR

Impact: Other

OAM-30028: Error in setting the validation schema : {0}

Cause: Error in setting the validation schema

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30029: Error in setting the validation event handler : {0}

Cause: Error in setting the validation event handler

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30030: Error in marshalling operation : {0}

Cause: Error in marshalling the data.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30031: The character encoding being used is not supported : {0}

Cause: Internal error. Unsuppported character encoding being used.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30032: Exception encountered while writing to the certificate file : "{0}". Error message is: {1}

Cause: An internal error occurred during creation of output password.xml file

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30033: Certificates could not be retrieved from the server location. Registration failed: {0}

Cause: An internal error occurred. Error in retrieving the certificates.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30034: Error while reading the certificate file stream. Registration failed: {0}

Cause: An internal error occurred. Error in retrieving the certificates.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30035: Server instance is not running for the security mode specified: "{0}".

Cause: Server instance not running for the security mode specified.

Action:
Level: 1

Type: WARNING

Impact: Other

OAM-30036: Internal server error. No server instances are running.

Cause: Internal server error occurred. No server instances exist.

Action:
Level: 1

Type: WARNING

Impact: Other

OAM-30037: Server instance is not running for the security mode specified: "{0}". Try again using a different security mode.

Cause: Server instance not running for the security mode specified

Action: Try again using a different security mode
Level: 1

Type: ERROR

Impact: Other

OAM-30038: Internal server error. There are no server instances running. Registration failed. Please try again later.

Cause:

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30039: Default security mode picked up for agent is: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-30040: Could not retrieve the timeout cookie name and timeout cookie key information from the server configuration. Registration failed.

Cause: An internal error occurred. Error in retrieving timeout cookie name and timeout cookie key for the agent.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30041: Error while generating the cipher key or mask for the agent. Registration failed: {0}

Cause: An internal error occurred. Error in generating the cipher key or mask for the agent.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30042: Error in decrypting the secret key while passing back in the response. Registration failed.

Cause: An internal error occurred. Error in decrypting the secretkey while passing back in the response.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30043: Agent type in the request is either null or unidentified. Please try again after verifying the agent type.

Cause: Agent type that is passed in the request object is invalid.

Action: Try again after checking the agent type that is specified.
Level: 1

Type: ERROR

Impact: Other

OAM-30044: Internal error while encrypting/obfuscating the password. Registration failed: {0}

Cause: An internal error occurred. Error in encrypting/obfuscating the password.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30045: The hostIdentifier string: "{0}" has already been added to an existing hostIdentifier called: "{1}". Try again after deleting the host entry from the existing hostIdentifier or registering with a new hostIdentifier name.

Cause: The hostIdentifier string specified is already registered under a different hostidentifier name.

Action: Try again after deleting the host entry from the existing hostIdentifier or registering with a new hostIdentifier name.
Level: 1

Type: ERROR

Impact: Other

OAM-30046: {0} mode failed. Agent does not exist.

Cause: Agent is not found.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30047: Agent is found, but application domain does not exist. Agent could be in different application domain.

Cause: The Application Domain is not found.

Action: For validation, application domain name is agent name.
Level: 1

Type: ERROR

Impact: Other

OAM-30048: Url is not valid. Ensure that URL is of the format http://example.domain.com:port or https://example.domain.com:port, where port number is optional.

Cause: Url is not valid.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30049: Exception encountered while creating the logout.html script file : {0}

Cause: An internal error occurred while creating the logout.html script file

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30050: In DELETEMODE, agent profile deleted successfully, however, artifacts output directory was not present or could not be deleted for the agent name: "{0}" at the output folder location: "{1}". Please delete the folder manually.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-30051: In DELETEMODE, agent profile and artifacts output directory was successfully deleted for the agent name: "{0}" at the server side output folder location: "{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-30052: Exception encountered while updating agent profile. Update of agent failed. {0}

Cause: An internal error occurred while updating agent profile

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30053: Application domain does not exist. Policy update failed.

Cause: The Application Domain is not found.

Action: Verify that the application domain you want to update exists and then try again.
Level: 1

Type: ERROR

Impact: Other

OAM-30054: Host identifier does not exist or is empty. {0} mode failed.

Cause: The Hostidentifier is not found.

Action: Verify that the hostidentifier you want to update exists and then try again.
Level: 1

Type: ERROR

Impact: Other

OAM-30055: The host: "{0}" and port: "{1}" is already present under the hostIdentifier: "{2}" and was not added again.

Cause: The hostPortVariation specified is already registered under an existing hostidentifier name, so it will not be added again.

Action:
Level: 1

Type: WARNING

Impact: Other

OAM-30056: Application domain already exists. policyCreate mode failed. Use policyUpdate mode to update existing application domains.

Cause: For policyCreate mode, application Domain already exists.

Action: Try again using policyUpdate mode to update existing application domains.
Level: 1

Type: ERROR

Impact: Other

OAM-30057: Create policy resource exception. {0} URI={1}

Cause: create resource failed. resouce/uri format is not valid.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30058: Agent name {0} exceeds maximum allowed length of {1} characters.

Cause: The name of the agent being created was too long.

Action: Try again using a shorter name.
Level: 1

Type: ERROR

Impact: Other

OAM-30059: The user-specified managed server name/id: "{0}" does not exist. Registration failed. Please try again after specifying valid server name.

Cause: The user-specified managed server name/id is invalid.

Action: Try again after providing a valid server name.
Level: 1

Type: ERROR

Impact: Other

OAM-30060: Internal server error. The location "{0}" is invalid or does not exist in configuration. Registration failed.

Cause: Internal server error. The specified location in the config file is invalid or not existing.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30061: isFusionAppRegistration flag was set to: "{0}" and SSOOnlyMode field was set to true.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-30062: isFusionAppRegistration flag was set to: "{0}" and denyOnNotProtected field was set to false(0).

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAM-30063: Agent type mismatch: Incoming agent request is of type: "{0}" , but the existing agent profile type in the server is: "{1}". Registration failed. Please try again after using agent name of the same type.

Cause: Incoming agent type does not match with the agent type already registered in the server.

Action: Verify that the agentName belongs to the same type and try again.
Level: 1

Type: ERROR

Impact: Other

OAM-30064: Agent version mismatch: Incoming agent request is of the correct type: "{0}" , but the version is: "{1}" , while the existing agent version in the server is: "{2}". Registration failed. Please try again after using agent name of the same version.

Cause: Incoming agent type is the same, however, does not match the agent version already registered in the server.

Action: Verify that the agentName belongs to the same version and try again.
Level: 1

Type: ERROR

Impact: Other

OAM-30065: Registration failed. Error in finding or reading the template file {0} for agent:{1} of type:{2}. - {3}

Cause: An internal error occurred: the template file was not found or could not be opened.

Action:
Level: 1

Type: ERROR

Impact: Other

OAM-30066: Warning: The host:port variation - {0}:{1} is not present under the hostIdentifier - {2} and so was not deleted.

Cause: The host:port variation is not present under the given hostIdentifier

Action: Verify that the host:port variation you are passing is actually present
Level: 1

Type: WARNING

Impact: Other

OAM-30067: Warning: HostIdentifier {0} cannot be empty, so added this host:port entry back to it - {1}:{2}

Cause: The hostIdentifier cannot be empty, so cannot delete all host:port entries under it

Action: Adds the last entry being deleted back to the hostIdentifier
Level: 1

Type: WARNING

Impact: Other

OAM-30068: Warning: None of the given host:port variations are present for the hostIdentifier- {0} , so nothing to delete.

Cause: None of the specified host:port variations are present under the hostIdentifier

Action: Check the host:port variations list being passed and try again
Level: 1

Type: WARNING

Impact: Other

OAM-30069: Notification: The initial protected authn policy is created.

Cause: The initial protected authn policy is created.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-30070: Notification: The initial protected authz policy is created.

Cause: The initial protected authz policy is created.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-30071: Notification: The public authn policy using Anonymous Scheme is created.

Cause: The public authn policy using Anonymous Scheme is created.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-30072: Notification: The authn policy is updated.

Cause: The authn policy is updated.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-30073: Notification: The authz policy is updated.

Cause: The authz policy is updated.

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAM-36001: Cannot obtain connection to domain MBean Server.

Cause: Console is not installed on the admin server.

Action: Check installation and configuration of the mbeans.
Level: 15

Type: ERROR

Impact: Other

OAM-36002: Cannot obtain MBean object.

Cause: MBean is not installed correctly.

Action: Check installation and configuration of the mbeans.
Level: 15

Type: ERROR

Impact: Other

OAM-36003: OAM service descriptor map: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36004: Result from remove crl: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36005: Result from getting all CRLs: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36006: Certificate validation configuration map: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36007: Deleting custom token: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36008: Result from deleting custom token: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36009: Error deleting custom token.

Cause: Error deleting custom token

Action: Check if managed server is up. Check server logs. Check if custom token was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36010: Setting custom token to: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36011: Result from setting custom token: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36012: Error setting custom token.

Cause: Error updating custom token

Action: Check if managed server is up. Check server logs. Check if custom token was deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36013: Creating custom token: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36014: Result from creating custom token: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36015: Error creating custom token.

Cause: Error creating custom token

Action: Check if managed server is up. Check server logs. Check if custom token of this name already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36016: Get All custom tokens

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36017: Result from getting all custom tokens: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36018: Error getting custom tokens

Cause: Error getting custom tokens

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36019: Result from getting list of validation custom tokens: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36020: Result from getting list of issuance custom tokens: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36021: Result from getting all custom token names: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36022: Result from getting custom token by name: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36023: Result from geting all endpoints: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36024: Setting endpoint to: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36025: Result from setting endpoint: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36026: Result from getting all endpoint names: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36027: Error creating endpoint

Cause: Error creating endpoint

Action: Check if managed server is up. Check server logs. Check if endpoint of this name already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36028: Creating endpoint with name {0} and properties {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36029: Result from getting endpoint {0} by name {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36030: Error deleting endpoint.

Cause: Error deleting endpoint

Action: Check if managed server is up. Check server logs. Check if endpoint was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36031: Deleting endpoint {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36032: Result from deleting endpoint {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36033: Result from getting keystore access template Names {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36034: Result from geting all keystore access templates {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36035: Result from setting keystore access template {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36036: Setting keystore access templates: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36037: Error setting keystore access template {0}

Cause: Error updating keystoreaccesstemplate

Action: Check if managed server is up. Check server logs. Check if template was deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36039: Result from setting keystore access template alias and pwd for alias {0} in csf: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36040: Result from geting all keystore access template names {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36041: Setting security token service settings to {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36042: Result from after setting security token service settings {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36043: Error setting security token service settings.

Cause: Error setting security token service settings.

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36044: Result from getting security token service settings {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36045: Result from getting global configuration {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36046: Result from setting global configuration {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36047: Setting STS global configuration properties {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36048: Error setting STS global configuration.

Cause: Error setting STS Global Configuraiton

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36049: Error getting STS global configuration.

Cause: Error getting STS Global Configuration

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36050: Result from getting server configuration {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36051: Result from setting server configuration {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36052: Setting STS server configuration properties {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36053: Error setting STS server configuration.

Cause: Error setting STS server configuration

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36054: Error getting STS server configuration.

Cause: Error getting STS server configuration

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36055: Result from creating token template {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36056: Creating token of type {0} with template type {1} and properties {2}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36057: Error creating token template.

Cause: Error creating template

Action: Check if managed server is up. Check server logs. Check if template of this name already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36058: Result from updating token template {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36059: Updating token of type {0} with template type {1} and properties {2}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36060: Error updating token template.

Cause: Error updating custom token

Action: Check if managed server is up. Check server logs. Check if template was deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36061: Result from deleting token template {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36062: Deleting token template {0} of type {1}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36063: Error deleting token template.

Cause: Error deleting template

Action: Check if managed server is up. Check server logs. Check if template was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36064: Result from getting all issuance templates {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36065: Result from getting all validation templates {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36066: Result from getting all issuance template names {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36067: Result from getting all validation template names {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36068: Result from getting issuance template {0} by name: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36069: Result from getting validation template {0} by name: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36070: Result from add CRL: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36071: Error adding CRL.

Cause: Error adding CRL

Action: Check if managed server is up. Check server logs. Check if CRL file is valid and if it already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36072: Error deleting CRL.

Cause: Error deleting CRL

Action: Check if managed server is up. Check server logs. Check if CRL was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36073: Error getting all CRLs.

Cause: Error deleting custom token

Action: Check if managed server is up. Check server logs. Check if CRL was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36074: handle query parameters: page (start, end) = ({0}, {1}), OrderBy = {2}, paramMap={3}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36075: Query response is empty

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36076: Error query response: {0}

Cause: Error querying the server

Action: Check if managed server is up. Check server logs.
Level: 15

Type: SEVERE

Impact: Other

OAM-36077: query response: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36078: populating row with attribute values: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36079: doDML operation: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36080: isCreateLike: {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36081: parameter {0} not found

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36082: null row data passed to populate attribute

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36083: Result from creating partner profile {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36084: Creating partner profile of type {0} with properties {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36085: Error creating partner profile

Cause: Error creating partner profile

Action: Check if managed server is up. Check server logs. Check if partner profile of this name already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36086: Result from updating partner profile {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36087: Updating partner profile of type{0} with properties {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36088: Error updating partner profile

Cause: Error updating partner profile

Action: Check if managed server is up. Check server logs. Check if partner profile was deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36089: Result from deleting partner profile {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36090: Deleting partner profile {0} of type {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36091: Error deleting partner profile

Cause: Error deleting partner profile

Action: Check if managed server is up. Check server logs. Check if partner profile was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36092: Result from getting all partner profiles {0} of Type: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36093: Result from creating partner {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36094: Creating partner of type {0} with properties {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36095: Error creating partner

Cause: Error creating partner

Action: Check if managed server is up. Check server logs. Check if partner of this name already exists.
Level: 15

Type: SEVERE

Impact: Other

OAM-36096: Result from updating partner {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36097: Updating partner of type {0} with properties {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36098: Error updating partner

Cause: Error updating partner

Action: Check if managed server is up. Check server logs. Check if this partner was deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36099: Result from deleting partner {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36100: Deleting partner {0} of type {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36101: Error deleting partner

Cause: Error deleting partner

Action: Check if managed server is up. Check server logs. Check if partner was already deleted by another user.
Level: 15

Type: SEVERE

Impact: Other

OAM-36102: Result from getting all partners {0} of Type: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36103: Result from getting WSS validation template names {0}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36104: Result from getting partner profile: {0} by name: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAM-36105: Result from getting partner: {0} by name: {1}

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

6 OAMSSA-00001 to OAMSSA-22030

OAMSSA-00001: Service provider configuration {0} is not valid.

Cause: The service provider configuration in the system configuration was invalid.

Action: Verify the identity and registration service provider configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-00002: Cannot instantiate service provider.

Cause: The service provider configuration was invalid.

Action: Verify the identity and registration service provider configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-00003: Identity service configuration is not valid.

Cause: The identity service configuration was invalid.

Action: Verify the identity service configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-00004: User self service configuration is not valid.

Cause: The user self service configuration was invalid.

Action: Verify the user self service configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-00005: Identity Manager Integration is enabled {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-00006: User Self Service is enabled {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-00007: Policy Evaluation result {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-00008: Constructed URL {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-02001: Session not found for sessionid: {0}

Cause: Requested session object has expired, has been deleted, or does not exist.

Action: Verify that the session exists before making the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02002: Session not found for userid: {0} identity domain: {1} and sessionindex: {2}

Cause: The requested session object has expired, has been deleted, or does not exist.

Action: Verify that the session exists before making the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02003: Cannot find method {0} on class {1}

Cause: An attempt was made to access a method that does not exist.

Action: Verify that the method exists before making the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02004: Cannot to execute method {0} on class {1}

Cause: An attempt to execute a method that is not supported.

Action: Use a supported method.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02005: Cannot to get SessionManager for type: {0}

Cause: An invalid type was specified.

Action: Verify that the type is supported before making the call.
Level: 30

Type: ERROR

Impact: Other

OAMSSA-02006: SessionMananger type not present: {0}

Cause: The requested implementation was not specified in configuration files.

Action: Add the SessionManager type to the configuration files
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02007: Factory class does not have factory methods.

Cause: Factory class does not have factory methods.

Action: None.
Level: 15

Type: INFO

Impact: Other

OAMSSA-02008: Cannot instantiate the persistence access implementation for class {0}.

Cause: An attempt was made to instantiate an invalid persistence access implementation.

Action: Verify the settings in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02009: Cannot extract attribute for method {0}.

Cause: An incorrect method was used to extract an attribute value.

Action: Use the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02010: UpdateProcessor is in invalid mode for entry {0}.

Cause: UpdateProcessor serialization failure.

Action: Verify the configuration files, and the deployment.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02011: Cannot update attribute for method {0}.

Cause: An incorrect method was used to update the attribute value.

Action: Use the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02012: Session count for user {0} has reached the maximum session limit per user.

Cause: Session count for user has reached the maximum session limit per user.

Action: Log out of some of the sessions before attempting to create new sessions.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02013: SME expired session reaper thread not started.

Cause: Database configuration may be in correct

Action: Verify that the server started without errors.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-02014: Session {0} not deleted.

Cause: Database configuration may be in correct

Action: Verify Data Source Name and database configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02015: Session attribute type {0} for key {1} is not supported. Attribute will be ignored.

Cause: Data in database is currupted due to unknown cause, or session is updated with unsupported data type properties.

Action: Correct the session client api usage.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02016: Session object for sessionid {0} was not loaded.

Cause: Database configuration may be in correct

Action: Verify Data Source Name and database configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02017: Session object for sessionid {0} was not saved.

Cause: Database configuration may be incorrect

Action: Verify Data Source Name and database configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02018: Session attribute value {0} for key {1} is not serializable. Attribute will be ignored.

Cause: Session attribute value is invalid.

Action: Correct the session client api usage.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02019: Session attribute key is null for userid {0} in session {1}.

Cause: Session attribute key is null.

Action: Correct the session client api usage.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02020: Grant for impersonation of user {0} by user {1} does not exist, or has expired.

Cause: Impersonation grant does not exist, or has expired.

Action: Verify impersonation grant information.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02021: Session exists for user {0} and sessionindex {1}.

Cause: Session object already exists.

Action: Use the existing session.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02022: Session {0} is not an impersonation session.

Cause: Session is not impersonation session.

Action: Ensure that impersonation operations are done on an impersonation session.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02023: Session {0} for user {1} index {2} is already impersonating. Further impersonations not allowed.

Cause: Impersonating sessions can not chain impersonation.

Action: Ensure that impersonation requests are done on non-impersonating sessions.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02024: Session {0} timed out.

Cause: Session is inactive

Action: Re-authenticate user.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02025: Session attribute domain definition {0} is not supported. Default domain value of {1} used.

Cause: Invalid configuration

Action: Correct the search attribute definition
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02026: QueryDescriptor has invalid value. {0} is {1}.

Cause: Invalid search input

Action: Correct the search attribute definition
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02027: Search request failed. {0}.

Cause: Search operation failed for provided cause.

Action: Correct the cause of the failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02028: Failed to transform the search request into a valid query.

Cause: The search request was not transformed into a search query.

Action: Correct the cause of the failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02029: Search request resulted in a null result object.

Cause: The search request failed with no results.

Action: Correct the cause of the failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02030: Selection list generation failed for extractor {0}.

Cause: Selection list transformation not supported for extractor or attribute.

Action: Verify supported attributes used in the session search
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02031: Where clause generation failed for extractor {0}.

Cause: Extractor transformation not supported for extractor or attribute.

Action: Verify supported attributes used in the session search
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02032: Selection list initialization failed for operation {0}.

Cause: Selection list transformation initialization failed.

Action: Verify supported selection initialization for failed operations.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02033: Initialization of search failed.

Cause: Initialization of search failed

Action: Verify libraries and jar versions.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02034: Conversion of database value to boolean failed. Defaulting {0} to {1}.

Cause: Database column mapping incorrect, or database column type incorrect.

Action: Verify database field configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02035: Unsupported session store version detected. Required "{0}" but found "{1}".

Cause: The version of session store is not compatible with OAM version.

Action: Make sure OAM is configured to talk to correct version of session store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02036: Ignoring declaration for invalid search attribute. {0}

Cause: Invalid attribute definition in configuration.

Action: Verify the configuration of the search attributes.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02037: The background delete thread has become unresponsive. Falling back to foreground session deletion.

Cause: The background delete thread has become unresponsive.

Action: Verify health of the JDBC data source connection.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02038: Failed to put session {0} on queue {1}.

Cause: Resource bounds exceeded.

Action: Correct cause of server overload.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02039: Session store write restored at wait queue size {0}. Current limit on queue size is {1}.

Cause: Load on background write queue has reduced.

Action: No action required.
Level: 15

Type: INFO

Impact: Other

OAMSSA-02040: Session store write disabled at wait queue size {0}. Current limit on queue size is {1}.

Cause: Load on background write queue has reached upper bound.

Action: Examine sources of loading.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-02041: Client lease for session {0} has expired.

Cause: Session update lease has expired.

Action: Examine use case of session update to eliminate updates using old session objects.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02042: Credentials for session {0} have expired.

Cause: Session credential has expired.

Action: Perform credential validation.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-02043: Session object expected. Null value found.

Cause: Invalid input.

Action: Invoke method with valid input.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02044: Session update context object expected. Null value found.

Cause: Invalid input.

Action: Invoke method with valid input.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02045: Request to encode {0} numbers exceed maximum limit of {1}.

Cause: Invalid input.

Action: Invoke method with valid input.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-02046: Credential validation date cannot be null.

Cause: Invalid input.

Action: Invoke method with valid input.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04001: Operation {0} is not supported.

Cause: The requested operation was not supported.

Action: Use a supported operation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04002: Incorrect number of parameters {0} passed for operation {1}

Cause: An incorrect number of parameters was passed to the expression builder.

Action: Pass the correct number of parameters required for the expression.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04003: Unable to get data store instance.

Cause: An invalid configuration file was supplied.

Action: Verify the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04004: Cannot get extractor list from passed configuration.

Cause: An incorrect extractor list was supplied.

Action: Verify the supplied configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04005: Data store established but data connection cannot be made.

Cause: Database connection information was invalid.

Action: Verify configuration files.
Level: 15

Type: INFO

Impact: Other

OAMSSA-04006: Cannot get connection from data source.

Cause: Data source configuration was invalid.

Action: Verify configuration files.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04007: Key is not unique: {0}

Cause: The key in the database was not unique.

Action: Verify data integrity.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04008: Data source definition not found. Store will be in-memory only.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-04009: Invalid parameter type passed to construct {0}

Cause: The function parameter type was invalid.

Action: Verify client implementation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04010: OAM Configuration for Coherence property {0} not found. Default configuration will be used.

Cause: No overrides were specified.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04011: Cannot resolve address for server instance {0}.

Cause: Server Instance listed in the Configuration is invalid.

Action: Correct the configuration and rerun the operation.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-04012: Cannot set local host values for this server instance.

Cause: Unable to set permissions for local host.

Action: Please verify the network configuration and rerun this operation.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-04013: Coherence property type update is not supported for property {0}. Supported types include String, Integer, Boolean.

Cause: An unsupported Coherence configuration property type was specified.

Action: Use a supported Coherence configuration property type.
Level: 15

Type: INFO

Impact: Other

OAMSSA-04014: Cannot set override properties for Coherence due to exception.

Cause: The supplied Coherence configuration properties are invalid.

Action: Correct the configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04015: Datasource not found for provided name {0}.

Cause: The supplied Datasource name is invalid.

Action: Correct the configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04016: Cannot store key {0} in data store.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04017: Cannot erase key {0} in data store.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04018: Cannot get Iterator of keys from data store.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04019: Cannot acquire distribution lock.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04020: Distribution version is {0}. Version requested for distribution is {1}.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04023: Cannot initialize configuration.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04024: Stale data exception encountered for config version {0}.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04032: Incorrect type of parameters {0} passed for operation {1}.

Cause: An invalid parameter type was passed to the expression builder.

Action: Pass the correct parameters required for the expression.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04033: Failed to get encryption key.

Cause: Shared Key for encryption not found.

Action: Verify that installation completed without errors.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04034: Invalid configuration map path {0}

Cause: Provided configuration map path is invalid.

Action: Ensure that the passed configuration map path is a valid path.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04035: Operation {0} supports {1} operand(s) only.

Cause: Number of operands supplied for operation is incorrect.

Action: Correct the API call with the required number of operands.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04036: Criterion type {0} does not support operation {1}.

Cause: Criterion does not support requested operation.

Action: Correct the API call with supported operand.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04037: Extraction of attribute {0} failed.

Cause: Extraction of attribute failed.

Action: Correct the API call with supported attribute extractor.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04038: The passed Criterion object type {0} is not supported by transformer type {1}.

Cause: Invalid parameter type.

Action: Correct the API call with supported criterion type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04039: Transform for operation {0} not found.

Cause: Operation trasformation class not defined.

Action: Correct the transformation properties file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04040: Criterion {0} does not contain operation.

Cause: Criterion does not contain operation.

Action: Correct the configuration to make the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04041: Failed to read the operation to transforms mapping configuration.

Cause: Unable to read the operation to transforms mapping.

Action: Correct the configuration to make the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04042: Invalid mapping {0} found for operation {1}.

Cause: Invalid operation to transform mapping.

Action: Correct the configuration to make the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04043: Null parameter value not supported.

Cause: Invalid parameter provided

Action: Correct the API call invocation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04044: Failed to sort on field {0}.

Cause: Invalid sort field.

Action: Invoke the search operation with Comparable sort fields
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04045: Failed to read the attribute to operations mapping configuration. Using defaults.

Cause: Unable to read the attribute to operations mapping properties file.

Action: Correct the configuration to make the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04046: Invalid mapping {0} found for attribute type {1}.

Cause: Invalid attribute type to operations mapping.

Action: Correct the configuration to make the correct API call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04047: Service {0} is not running.

Cause: Service has failed to start up or during operations.

Action: Attempt to restart server.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04048: Cache member joined: {0}, service: {1}.

Cause: Cache cluster member has joined the service.

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04049: Cache member leaving: {0}, service: {1}.

Cause: Cache cluster member is leaving the service.

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04050: Cache member left: {0}, service: {1}.

Cause: Cache cluster member has left the service.

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04051: Listener in {0}, Thread {1} before lock, dist version {2} config version {3}.

Cause:

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04052: File change listener in {0}, Thread {1} before lock, dist version {2} file version {3}.

Cause:

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04053: Exception on notification event {0} for listener {1}.

Cause:

Action: None
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04054: Failed to submit notification for {0}. Current queue size is {1}.

Cause:

Action: None
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04055: Failed to create mapstore statistics file.

Cause:

Action: Verify that the default output filesystem is writeable.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-04501: Exception on finalize of component {0}.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04502: Exception on bootstrap of component {0}.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04503: Distribution event of version {0} received for config of version {1}.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04504: Received null object as distribution event.

Cause: A null object was received as the distribution event.

Action: Verify the distributed data at the origin.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04505: Cannot handle distribution notification.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04506: Cannot acquire lock for configuration update.

Cause: Unable to acquire lock for configurable update.

Action: Identify source of contention and remove it.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04507: Cannot upload physical file change to configuration.

Cause: Unable to upload physical file change to configuration.

Action: Verify that the physical file is well formed.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04508: Mxbean attribute is null.

Cause: The Mxbean attribute was null.

Action: Size of document may be large causing this failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04509: Cannot handle config change notification.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04510: Starting upgrade from {0} to {1} ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04511: Running {0} ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04512: Finished upgrade from {0} to {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-04513: Source configuration path {0} is not specified, or is an invalid value.

Cause: Configuration path not specified for upgrade source, or is invalid value.

Action: Provide a valid configuration path.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04514: Destination configuration path {0} is not specified, or is an invalid value.

Cause: Configuration path not specified for upgrade destination, or is invalid value.

Action: Provide a valid configuration path.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04515: Configuration path {0} is not a valid file.

Cause: Provided path does not resolve into a valid file.

Action: Provide a path to a valid configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04516: Initialization of configuration copy failed {0}.

Cause: Configuration initialization failed.

Action: Verify the contents of the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04517: configuration upgrade failed for component {0}.

Cause: Configuration upgrade failed.

Action: Rectify the cause of the failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04518: Failed to build configuration build settings.

Cause: Configuration setting for upgrade is not valid.

Action: Rectify the cause of the failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04519: Upgrade action request {0} is not valid.

Cause: Requested upgrade action invalid.

Action: Rectify the action request.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04520: Destination configuration does not support data type {0} requested at path {1}.

Cause: Provided configuration map value is not supported in destination configuration.

Action: Transform the map value to a supported data type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04521: Destination configuration path {0} overwrites value {1} at element {2}.

Cause: Destination path will overwrite value.

Action: Change upgrade instructions to prevent path from overwriting values.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04522: Map destination path {0} will overwrite preserved path {1}.

Cause: Destination path will overwrite value.

Action: Change upgrade instructions to prevent path from overwriting values.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04523: Exception occured during write of configuration for examination.

Cause: Failure to write configuration for examination.

Action: Correct the cause of the associated exception.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-04524: Failed to create path {0}.

Cause: Creation of folder or file specified by path failed.

Action: Verify that the path can be written to, and that sufficient disk space exists.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05001: Unable to read configuration setting {0}, during Journal initialization.

Cause: An internal error occurred while initializing a Journal.

Action: For more details, start logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05002: Invalid value {0} for parameter {1} was passed for Journal operation {2}, in instance {3}.

Cause: An invalid parameter value was passed to the Journal operation.

Action: For more details, start logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05003: Unable to acquire lock on journal data for operation {0}, in instance {1}.

Cause: A lock might have already been acquired by another thread, or there was an internal failure.

Action: For more details, start logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05004: Journal entry with version {0} already exists in instance {1}.

Cause: A journal entry with the version already exists.

Action: Use a different version for the journal entry.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05005: Journal entry for version {0} does not exist in instance {1}.

Cause: A journal entry for the version doesn't exist.

Action: Check version of the journal entry.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05006: Unable to read Journal implementation name for instance {0} , using default name {1} instead.

Cause: Journal implementation name is not set in journal config setting.

Action: For more details, start logging at FINE level.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-05007: Journal configuration setting for instance {0} , key = {1}, value = {2}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-05008: Journal data in instance {0}: type = {1}, value = {2}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-05009: Source is not a OAM11gR1 config file, version expected: "{0}", found: "{1}".

Cause: The source OAM config file does not belong to a OAM 11gR1 instance.

Action: Make sure config file from OAM 11gR1 instance is passed as source for upgrade.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05501: Configuration for REST services not found.

Cause: Configuration file does not contain REST configuration

Action: Configure OAM for REST services.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-05502: Class declaration {0} is invalid.

Cause: REST class declaration is invalid.

Action: Correct the class declaration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-06001: Policy Service: {0} : {1} : {2} : {3}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06002: Create : {0} : paramList=[{1}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06003: Created : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06004: Modify : {0} : Existing=[{1}] : New=[{2}].

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06005: Modified to : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06006: Delete : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06007: Deleted : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06008: Read : {0} : name="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06009: After Read : {0} : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06010: Read All : {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06011: After Read All : {0} : list is : {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06012: Initialize Parameter list is {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06013: PolicyRuntime :: paramName="{0}", paramDetail="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06014: Unable to initialize Policy Runtime Provider.

Cause: An invalid configuration.

Action: Try again by setting proper configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06015: Exception encountered while processing get authentication scheme request!

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06016: Unable to reload the policy data for runtime.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06017: Exception encountered while creating runtime responses.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06018: Unable to load cache.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06019: Unable to load host identifiers from policy store.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06020: Exception encountered while evaluating authentication policy.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06021: Unable to obtain conditions from authorization policy.

Cause: No conditions were found.

Action: Check if policy has conditions and try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06022: Unable to obtain InetAddress from given IP Address.

Cause: An invalid IP Address was supplied.

Action: Check if the IP Address is valid (Only IP version 4 is supported). Try again with valid IP Address.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06023: Unable to determine the host identifier matching the request. Resource: {0}.

Cause: No host identifier was configured for incoming resource.

Action: Update the policy, add the host identifier to the given resource and try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06024: Unable to process Runtime Resource for getting URL path.

Cause: An invalid incoming resource URL.

Action: Correct the resource URL and try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06025: Exception encountered while adding to the bucket.

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06026: Object {0} with the name already exists.

Cause: That name has already been used to create an object.

Action: Modify the name and try to create the object once again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06027: Error while creating input stream for the policy file.

Cause: An internal error occurred. One of the many cause can be policy file not found.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06028: Error while creating a new policy distributor instance.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06029: ID of an element cannot be NULL.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06030: Error while retrieving DATA SOURCE and RESPONSE TYPE values from policy.xml!

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06031: Error while retrieving the condition type.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06032: Error while creating jaxb marshaller/unmarshaller.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06033: Error while unmarshalling. Data may be corrupt in policy.xml

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06034: Policy data write failed with exception.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06035: Error while creating input stream for policy file.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06036: Cannot find the file "{0}" in the classpath or on the filesystem

Cause: The policy file was not in the classpath.

Action: Add policy file to the classpath and run the program again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06037: XML data validation Error. Data in the input XML String maybe corrupt.

Cause: The policy file was invalid.

Action: Validate policy file against the schema and run the program again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06038: Validation Error while unmarshalling. Data in the input XML String maybe corrupt.

Cause: The policy file was invalid.

Action: Validate policy file against the schema and run the program again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06039: Cannot create temporal condition. Require either DayOfWeek or TimeOfDay.

Cause: The attribute required to create a temporal condition was not valid.

Action: Either DayOfWeek or TimeOfDay is missing. Add the required attribute and run the program again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06040: Invalid condition type "{0}" found in the policy store.

Cause: An internal error occured.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06041: Unable to distribute policy changes.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06042: Null passed during modify operation.

Cause: Object passed to modify operation was null.

Action: Rerun with actual object.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06043: Name cannot be null.

Cause: During object creation, name value was null.

Action: Rerun the operation with a valid name.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06044: Name {0} exceeds maximum allowed length of {1} characters.

Cause: During object creation, invalid name attribute was passed.

Action: Rerun the operation with a valid name attribute.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06045: An object of this type named "{0}" already exists.

Cause: Policy object names must be unique for each object type and scope (global or domain).

Action: Choose a different name for this object.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06046: Mandatory attribute "{0}" is missing.

Cause: A required attribute was missing during policy object creation.

Action: Rerun the operation with the required attribute. When authn-level is the required attribute, set a positive value and rerun the operation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06047: "name" or "description" attribute missing in Module Property.

Cause: A name or description attribute was missing in a module property.

Action: Rerun the operation with required attribute set.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06048: Policy Object: {0} no longer exists.

Cause: Policy object requested for removal was not found in the store; likely it has already been removed by another administrator.

Action: None, the object has been removed.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06049: Module cannot be deleted. (Referred in Scheme).

Cause: Module is being referred to in the scheme.

Action: Remove the reference from the scheme and then delete the module.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06050: NULL passed during isDefaultAuthnScheme operation.

Cause: Null passed while performing the default authn scheme operation.

Action: Rerun the operation with the valid scheme.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06051: One of the challenge parameter key values is empty.

Cause: A challenge param key value was empty.

Action: Set the proper key value and then rerun the operation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06052: Challenge Redirect URL is invalid.

Cause: An invalid Challenge Redirect URL was entered.

Action: Rerun the operation with valid challenge URL value.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06053: Challenge URL is null.

Cause: The URL entered is null.

Action: Re-run the operation with a valid URL value.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06054: Scheme referring to invalid authentication module.

Cause: The scheme was referring to an invalid authentication module.

Action: Rerun the operation after setting a valid authentication module.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06055: Scheme cannot be deleted. Referenced in an existing authentication policy.

Cause: The scheme is being referred to in a policy.

Action: Remove the reference from the policy and then delete the scheme.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06056: Default authentication scheme cannot be deleted.

Cause: An attempt was made to delete the default authentication scheme, which is not allowed.

Action: Rerun the operation with another authentication scheme.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06057: Invalid host format.

Cause: The host format was invalid.

Action: Rerun the operation with a valid host.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06058: Host "{0}" already exists under host identifier "{1}".

Cause: The host is already part of a host identifier.

Action: Remove the host from the other host identifier and then retry.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06059: Host Identifier cannot be deleted. (Referred to in a resource).

Cause: Host is being referred to in a resource.

Action: Remove the reference from the resource and then delete the host.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06060: Resource "{0}" does not exist in the application domain.

Cause: Resource does not exist in the application domain.

Action: Use a valid resource that exists in the application domain.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06061: Resource "{0}" cannot be added to this policy, as it is already referenced by {1} Policy "{2}".

Cause: A resource can only be associated with a single policy of a given type.

Action: Remove the resource from the named policy and try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06062: A resource type name cannot start with a number.

Cause: Resource type names must start with a letter.

Action: Remove the numeric characters from the start of the name.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06063: Invalid operation format.

Cause: The operation list was invalid.

Action: Rerun the operation with a valid operation list.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06064: HostIdentifier is null.

Cause: A null HostIdentifier was passed to the operation.

Action: Rerun the operation with a valid host identifier.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06065: Invalid HostIdentifier.

Cause: No HostIdentifier was found in the policy.

Action: Rerun the operation with a valid host identifier.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06066: Unable to fetch HostIdentifier manager.

Cause: An internal error occurred..

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06067: Resource URL format is not valid.

Cause: URL * was not followed by a .extension, or URL pattern (*any string) * was not followed by a character string, or URL * was preceeded by a string (e.g. checking*.jsp is invalid), or URL pattern was invalid (e.g. "..." pattern is only allowed once).

Action: Rerun the operation with a valid resource url.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06068: Cannot delete resource, as it is referenced by {0} Policy "{1}".

Cause: A resource currently in use cannot be deleted.

Action: Delete the resource from the named policy and try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06069: Token issuance policies can not contain responses.

Cause: Token issuance policies can not contain responses.

Action: Remove the responses.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06070: Unable to obtain policy manager for application domain id: "{0}"

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06071: Temporal condition validation failure for {0}.

Cause: Missing day of the week or time of the day required to create temporal condition, or no day selected in day of the week condition, or begin and end time not supplied for temporal condition, or end time is less than begin time.

Action: Rerun the operation with a valid Temporal condition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06072: Identity condition validation failure for {0}.

Cause: User or group list was not supplied for identity condition creation, or users list was empty, or group list was empty.

Action: Rerun the operation with a valid Identity condition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06073: IP4Range condition validation failure for {0}.

Cause: A null value was present in either start or end range.

Action: Rerun the operation with valid a IP4Range condition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06074: {0} does not exist, id = {1}

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06075: Unable to obtain a host identifier for the input name : hostIdName = {0}.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06076: Time of Day condition is not created as either begin time or end time is missing.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06077: Cannot create condition object.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06078: Error while creating condition of type: "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06079: Error while reading response with name = "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06080: Error while creating response from policy store object with name = "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06081: Cannot open file.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06082: Exception occurred while converting admin elements to runtime elements.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06083: No Client IPAddress found in AccessContext Map.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06084: Null Authentication Scheme Id.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06085: Constraints not supported for Authentication Policy. Pass null during Constraint creation.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06086: OAM Admin Provider class not found : "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06087: Unable to instantiate OAM Provider class : "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06088: OAM provider class in the configuration does not implement PolicyAdminProvider: "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06089: OAM Runtime Provider class not found : "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06090: Unable to instantiate OAM Runtime Provider class : "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06091: OAM provider class in the configuration does not implement PolicyRuntimeProvider: "{0}".

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06092: Cache entry expired.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06093: Error while reading policy result cache size from configuration.

Cause: Cache configuration was invalid.

Action: Fix the cache configuration and the rerun the operation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06094: Policy result cache is enabled.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06095: Registering PolicyDiagnosticConfigMediator.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06096: Successfully registered PolicyDiagnosticConfigMediator.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06097: Failed to register PolicyDiagnosticConfigMediator.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06098: Resource "{0}" already exists in policy "{1}".

Cause: The resource already exists as part of an Authentication/Authorization Policy.

Action: Rerun the operation using another resource.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06099: Response "{0}" already exists in policy "{1}".

Cause: The response already exists as part of an Authentication/Authorization Success/Failure List.

Action: Rerun the operation using another response.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06100: Condition "{0}" already exists in policy "{1}".

Cause: The condition already exists as part of an Authorization policy.

Action: Rerun the operation using another condition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06101: Policy change record number: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06102: Unable to process policy change event for change record number: "{0}".

Cause: An internal exception occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06103: Unable to acquire write lock on the XML policy store file, for change record number: "{0}".

Cause: The XML policy store file is locked by another thread for more than the configured wait time.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06104: Success URL is invalid.

Cause: The success redirect URL was invalid..

Action: Rerun the operation with a valid URL.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06105: Failure URL is invalid.

Cause: The failure redirect URL was invalid.

Action: Rerun the operation with a valid URL.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06106: Resource URL is invalid.

Cause: The resource URL entered is invalid.

Action: Re-run the operation with valid resource URL value.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06107: Description for field {0} exceeds maximum allowed length of {1} characters.

Cause: During object creation, invalid description attribute is passed.

Action: Re-run the operation with valid description attribute.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06108: Operation list is empty.

Cause: During object creation, invalid operation list attribute is passed.

Action: Re-run the operation with valid operation list attribute.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06109: Resources belonging to a policy must be of the same type.

Cause: The policy already contains resources of another type.

Action: Apply the resource to a different policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06110: Resource type must not be null.

Cause: Resource type must not be null.

Action: Set the resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06111: Unable to find HTTP resource type.

Cause: The required HTTP resource type does not exist.

Action: Create a new resource type with name "HTTP".
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06112: Application Domain should be empty before it is deleted.

Cause: Application Domain is not empty.

Action: Delete all resources and policies in an application domain before deleting the domain.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06113: The resource URL cannot contain a query string.

Cause: The resource URL cannot contain a query string.

Action: Remove the query string component from the resource URL.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06114: The requested method is not supported by this policy object type.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06115: An unsupported operation was unexpectedly requested.

Cause: An internal error occurred.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06116: A host identifier or resource type named "{0}" already exists.

Cause: Names of host identifiers or resource types must be unique across both sets of objects.

Action: Choose a different name for this object.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06117: An unsupported operation was unexpectedly requested.

Cause: Exception while getting host identifier.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06118: Policy admin update event distribution setting : "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06119: Policy admin update event distribution is disabled.

Cause: Policy admin update event distribution is disabled

Action: Check the policy configuration setting for policy admin update event distribution
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06120: Host identifier doesn't exist for the given host and port.

Cause: There is no host identifier associated with the given host and port.

Action: Check the input host and port information.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06121: Policy runtime change event distribution failure, invalid (NULL) Journal instance.

Cause: An internal exception occurred while distributing policy runtime change events.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06122: Policy runtime provider {0}, does not accept policy change events.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06123: Policy runtime provider {0}, accepts policy change events.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06124: Exception encountered while fetching current policy version from policy store.

Cause: An internal error occurred while fetching current policy version from policy store.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06125: Policy data refresh by policy runtime engine did not complete after {0} time, hence policy cache is not refreshed.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06126: Exception encountered while refreshing policy cache by policy runtime.

Cause: An internal error occurred while refreshing policy cache by policy runtime.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06127: Exception encountered while handling policy change event {0} by policy runtime.

Cause: An internal error occurred while handling policy change event by policy runtime.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06128: Policy data version in policy store is {0}

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06129: Issued policy data refresh to policy runtime engine

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06130: Skipping the addition of policy change record {0} to the Journal as policy admin provider returned the same version previously.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06131: Type "{0}" cannot be deleted, as one or more resources of this type exist.

Cause: Resources of the resource type to be deleted exist.

Action: Remove these resources, then try again.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06132: A runtime resource must contain a URL.

Cause: The resource asscociated with the runtime request did not contain a URL.

Action: Create the request with a valid resource.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06133: An HTTP runtime resource must contain a relative URL path. Resource: "{0}".

Cause: The resource URL associated with the runtime request was not relative.

Action: Ensure thst the resource URL is relative, starting with '/'.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06134: Unable to match a resource type for the requested resource: request="{0}".

Cause: No resource type was configured for the requested resource.

Action: Add the required resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06135: Only querying policies from policy store ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06137: Where <properties-file> should contain the following properties:

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06138: policy-admin-provider-class=<provider-class-name>

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06139: policy-admin-provider-name=<provider-name>

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06140: <provider-name>.<provider-property-name>=<provider-property-value>

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06141: ... list of provider properties.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06142: Adding OAM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06143: Disabled policy distribution for XML provider

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06144: Adding OAM WLS Agent policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06145: Input properties:

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06146: Adding OIM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06147: Adding OAAM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06148: Adding OIF policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06149: Adding Fusion Applications policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06150: Verifying OAM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06151: Verifying IDM Domain Agent policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06152: Verifying OIM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06153: Verifying OAAM policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06154: Verifying OIF policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06155: Verifying Fusion Applications policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06156: Done.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06157: Fetching "{0}" resource type ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06160: Checking to confirm "{0}" as default authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06161: "{0}" is the default authentication scheme.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06162: "{0}" instead of the expected "{1}" is the default authentication scheme!

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06166: Fetching "{0}" host identifier ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06167: Fetching "{0}" application domain ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06168: Fetching resources ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06169: Fetching authentication policies ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06170: Fetching authorization policies ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06171: Fetching OIMHostIdentifier host identifier ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06172: Fetching OIMScheme authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06173: Fetching OIM Integration application domain ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06174: Fetching OAAMBasic authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06175: Fetching OAAMAdvanced authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06176: Fetching OIFScheme authentication-scheme object ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06177: Fetching wl_authen resource type ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06178: Fetching Fusion Apps Integration application domain ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06179: Invalid usage!

Cause: Command line arguments passed were invalid.

Action: Rerun the command with correct arguments.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06180: Property file location argument is missing!

Cause: Property file location is invalid.

Action: Provide the correct property file location.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06181: Error! PolicyFile: "{0}" already exists! Remove this file before running the tool.

Cause: Policy file already exists.

Action: Remove this file before running the tool.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06182: Policy object not found!

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06183: Global default domain not yet setup!

Cause: Global default domain is not setup.

Action: Create global default domain.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06184: VM Property not set: "{0}"

Cause: Required JVM property was not set.

Action: Set the required JVM property.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06185: Policy cannot make use of both specific and default schemes.

Cause: An authentication policy cannot use both a specific, named scheme and the default one.

Action: Ensure the policy uses either a specific scheme or the default one, not both.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06186: Unable to initialize PolicyRuntimeProviderImpl! : "{0}".

Cause: PolicyRuntime provider could not be initialized.

Action: Recheck the oes settings and modify accordingly.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06187: Invalid IP address on range check, IP address was: "{0}".

Cause: An IP address was provided out of range.

Action: Provide correct IP address.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06188: App Domain Manager not setup.

Cause: App domain manager was not set up.

Action: Setup domain manager.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06189: Extension manager not found.

Cause: Extension manager was not set up.

Action: Setup extension manager.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06190: The host: "{0}" occurs more than once in the host identifier: "{1}".

Cause: Same host entry is specified more than once in a host identifier.

Action: Ensure same host is not added more than once to a host identifier.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06191: The runtime request is null or contains no resource.

Cause: The runtime request, or the resource associated with the request, was null.

Action: Create the request with a proper resource.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06192: The runtime request contains no identity.

Cause: The identity associated with the runtime request was null.

Action: Create the request with a proper identity.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06193: Unable to process policy distribution event.

Cause: The policy admin provider failed to apply the changes contained in the event.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06194: Verifying OAM10g policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06195: Fetching OAM10gScheme authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06196: Adding OAM10g policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06197: Policy contains multiple constraints of class {0} and type {1}.

Cause: Each constraint class/type combination can appear at most once within a policy.

Action: Modify the policy to ensure that multiple constraints of the same class and type are not present.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06198: Authentication scheme {0} not found.

Cause: Authentication scheme not found in store

Action: Ensure that the authentication scheme has been created.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06199: Multiple resources exist for Authentication scheme {0}.

Cause: Authentication scheme is represented by multiple resources.

Action: Ensure that the data in the OES store is valid.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06200: Waiting for policy distribution ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06201: Waited {0} ms for policy distribution to complete ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06202: Distribution completed, total time taken was: {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06203: Distribution did not complete within the configured maximum wait time of {0} ms.

Cause: Policy distribution did not complete within maximum wait time alloted.

Action: Increase the maximum wait time for policy distribution in the config file.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-06204: Condition "{0}" is of a type which cannot be used in a token issuance policy.

Cause: Only some types of conditions can be used with a token issuance policy.

Action: Use only conditions of types which are compatible with this policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06205: Resource "{0}" is of a type which cannot be used in a token issuance policy.

Cause: Only some types of resources can be used with a token issuance policy.

Action: Use only resources of types which are compatible with this policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06206: The token requestor identity condition validation failed for {0}.

Cause: None of partner, user or group information was provided for condition creation.

Action: Provide at least one of partner, user or group information for condition creation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06207: Only HTTP resources can have a protection level of Excluded.

Cause: An attempt was made to set the protection level of a non web resource to excluded.

Action: The protection level of non web resource can be either protected or unprotected.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06208: Excluded resource: {0}, cannot have a policy associated.

Cause: An attempt was made to associate a excluded resource with a policy.

Action: Change the protection level to either protected or unprotected to create a policy around this resource.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06209: Resource protection level is null.

Cause: Resource protection level was set to null.

Action: Resource protection level should be set to valid values.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06210: Unprotected resource {0} cannot be associated with this policy, as it uses a non-anonymous authentication scheme.

Cause: Unprotected resources cannot be associated with this policy, as it uses a non-anonymous authentication scheme.

Action: Change the protection level of the resource(s) to Protected before adding to the policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06211: Protected resource {0} cannot be associated with this policy, as it uses an anonymous authentication scheme.

Cause: Protected resources cannot be associated with this policy, as it uses an anonymous authentication scheme.

Action: Change the protection level of the resource(s) to Unprotected before adding to the policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06212: Invalid request: isTokenRequestAuthorized calls cannot be made for HTTP resources.

Cause: An attempt was made at runtime to evaluate token issuance policy for HTTP resource.

Action: Make sure that at runtime HTTP resource is not used when evaluating Token issuance policies.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06213: Could not find application domain for Id: {0}, name: {1}.

Cause: Provided Application domain was not found in the store.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06214: Could not find hostIdentifier for Id: {0}.

Cause: Provided host identifier was not found in the store.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06215: Could not find hostIdentifier for name: {0}.

Cause: Given host identifier name was not found in the store.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06216: Could not find store entry for application domain Id: {0}.

Cause: No entry was found in the store for the given application domain Id.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06217: Excluded resource: {0} is not associated with the exclusion policy.

Cause: An excluded resource in the store was not associated with the exclusion policy.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06218: Invalid store resource name {0}.

Cause: The store resource name entry was found to be invalid.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06219: Invalid operation name: {0}, operation name cannot end with string: {1}.

Cause: The resource type operation name is invalid.

Action: Modify the operation name for the resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06221: Exception while decrypting OES credentials.

Cause: An exception occured while decrypting store credentials.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06222: Could not find the exclusion policy in the store from which to remove resource: {0}.

Cause: The exclusion policy was not found in the store from which the resource was requested to be removed.

Action: For more details, start policy logging at FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06223: Creating authentication scheme: {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06224: Creating resource type: {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06225: Creating host identifier : {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06226: Creating application domain : {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06227: Creating custom resource : {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06228: Creating web resource : {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06229: Creating authentication policy: {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06230: Creating authorization policy: {0}...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06231: Enter policy database password:

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06232: Authentication scheme "{0}" would be created.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06233: Host identifier "{0}" would be created.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06234: Resource type "{0}" would be created.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06235: Application domain "{0}" would be created.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06236: Default authentication scheme would be set to scheme {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06237: Skipping creation of scheme: {0} because the scheme already exists.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06238: Skipping creation of host identifier {0} because it already exists in the store.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06239: Skipping creation of resource type: {0} because the resource type already exists in the store.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06240: Skipping creation of application domain: {0} because the domain already exists in the store.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06241: Insufficient arguments: missing policy store location.

Cause: Policy Store file name and location is missing.

Action: Policy Store file name and location needs to be provided.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06242: Fetching "{0}" authentication scheme ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06243: Initializing database policy admin provider.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06244: Initializing database policy runtime provider.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06245: Ignoring host identifier: "{0}", since this has been renamed to: "{1}" in {2}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06246: Ignoring application domain: "{0}", since this has been renamed to: "{1}" in {2}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06247: Running in examine mode; simulating insertion of migrated policy objects into the live policy store.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06248: Adding TAP policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06249: Verifying TAP policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06250: Fetching TAPScheme authentication-scheme object ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06251: Unsupported policy store version detected. Required "{0}" but found "{1}".

Cause: The version of policy store is not compatible with OAM version.

Action: Make sure OAM is configured to talk to correct version of policy store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06252: The policy store is not available; please see the log file for more details.

Cause: Policy store could not be instantiated. Database schema may be out of date

Action: In case of database schema errors schema needs to be updated.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06253: Database schema is not valid.

Cause: Database schema is missing or requires update.

Action: Update the database schema.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06254: Profiling started, strategy: {0}, amount: {1}, mechanism: {2}

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06255: Profiling report for {0}: {1} ops, {2}/{3}/{4} avg/min/max (ms)

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06256: Profiling ended.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06257: All hosts from R1 host identifier {0} would be migrated to PS1 host identifier {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06258: The authentication scheme of authentication policy {0} would be modified to {1}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06259: Extra resource(s) were found in R1 {1} Protected policy. The following will need to be recreated manually after the upgrade is complete: {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06260: The LDAP filter {0} match for user {1} and identity domain {2} failed.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06261: The LDAP filter search not executed because there was no DN for user {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06262: The LDAP filter {0} match for user {1} and identity domain {2] was successful.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06263: No user identity provider for domain {0} could be found.

Cause: No user identity provider could be found for the given domain.

Action: Check if the relevant userstore configuration was deleted.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06264: Error getting the user identity provider for domain {0}.

Cause: Unknown error while fetching the user identity provider for the given domain.

Action: Check the relevant userstore configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06265: The IP4 Address {0} is not valid.

Cause: The IP4 address specified is invalid.

Action: Specify a valid IP4 address. This should be in the dotted decimal format xxx.xxx.xxx.xxx, where xxx is a number between 0 and 255.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06266: The "From" address {0} in the IP4 range is greater than the "To" address {1}.

Cause: The From address in the IP4 range is greater than the "To" address in the IP4 range.

Action: Update the IP4 range so that the "To" address is greater than the "From" address.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06267: Condition {0} does not contain any attributes.

Cause: Attribute list was not supplied for condition creation.

Action: Rerun the operation with a valid attribute list.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06268: Condition {0} contains an unset attribute name.

Cause: An attribute name was not supplied for condition.

Action: Rerun the operation with a valid attribute name.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06269: Condition {0} contains an unset attribute value.

Cause: An attribute value was not supplied for condition.

Action: Rerun the operation with a valid attribute value.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06270: Resource type {0} cannot be created as read-only, or modified if already read-only.

Cause: A policy admin cannot create/update/delete read-only resource type without permission to do so.

Action: Do not attempt to manipulate a read-only resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06271: One or more operations cannot be created as read-only, or modified if already read-only.

Cause: A policy admin cannot create/update/delete read-only opertion(s) without permission to do so.

Action: Do not attempt to manipulate a read-only operation within a resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06272: Operation {0} can not be used, because it does not exist for the type of this resource.

Cause: An invalid operation, one which does not exist for the resource's type, was used.

Action: Ensure that the operations added to a resource are a subset of those defined for its resource type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06273: Policy contains more than one rule for rule effect "{0}".

Cause: More than the allowed single rule per rule effect was present..

Action: Create the policy using a single rule per rule effect.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06274: At least one of the policy rules must hold conditions selected for evaluation.

Cause: A policy using the simple rule mode needs one or more of the rules to contain conditions.

Action: Select conditions on at least one of the rules.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06275: Invalid condition name "{0}" specified in "{1}" rule.

Cause: A condition name was used within a rule, when no condition by that name exists.

Action: Use names of conditions which exist when creating rules.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06276: The same rule mode must be used across all rules contained in a policy.

Cause: More than one rule mode was used within the policy's rules.

Action: Use only one rule mode within a policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06277: Unable to process policy rule expression "{0}".

Cause: Policy rule expression processing failed.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06278: At least one of the policy rules must hold an expression for evaluation.

Cause: A policy using the expression rule mode needs one or more of the rules to contain expressions.

Action: Create a valid rule expression on at least one of the rules.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06279: Unexpected token "{0}" encountered at line "{1}", column "{2}" in the rule expression.

Cause: Rule expression contains invalid syntax.

Action: Use a valid rule expression in rules within a policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06280: Number of open and close braces do not match in the rule expression.

Cause: Rule expression contains invalid syntax.

Action: Use a valid rule expression in rules within a policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06281: Unable to escape special characters for condition name "{0}" to be used in rule expression.

Cause: Internal error encountered while processing condition name.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06282: Unable to remove previously escaped special characters for a condition name "{0}" that is used in the rule expression.

Cause: Internal error encountered while processing condition name.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06283: Condition name "{0}" used at line "{1}", column "{2}" in rule expression is not defined in the policy.

Cause: Rule expression refers to a condition which has not been defined within the policy.

Action: Use a valid rule expression in rules within a policy.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06284: Both a query string and query parameters are specified for the resource.

Cause: A resource can have a query string or parameters specified, but not both.

Action: Remove either the query string or the query parameters from the resou rce.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06285: Exception encountered during policy rule evaluation. Condition "{0}" does not exist in authorization policy.

Cause: Internal error encountered while evaluating policy rule.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06286: Rule expression token must have a type.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-06287: An HTTP runtime resource must contain a host name.

Cause: The resource associated with the runtime request did not contain a host name..

Action: Create the request with a valid resource.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06288: An HTTP runtime resource must contain a valid port number. Resource: "{0}".

Cause: The resource associated with the runtime request did not contain a valid port.

Action: Create the request with a valid port, between 0 and 65535 inclusive.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06289: This resource already exists, within domain "{0}".

Cause: Resources belong to different application domains, but must be globally unique.

Action: Either modify or remove the conflicting resource, or the elements of the one being created.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06301: Response tokenization failed for policy: "{0}" in domain: "{1}". Response details: "{2}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06302: Error thrown during response processing:

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06303: No provider registered to handle namespace: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06304: Provider failed to retrieve value for policy: "{0}" in domain: "{1}". Response details: "{2}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06305: Invoked provider for unsupported namespace: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06306: Invoked provider for unsupported variable name: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06307: Subject is missing from the request context.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06308: Expected user attribute not found.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06309: No attributes found in identity store for user: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06310: Provider registration requires a class instance and list of namespaces.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06311: Namespace must not be null.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06312: Provider already registered for namespace: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06313: Response token must have a type.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-06314: Variable namespace cannot be null.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06315: Session ID cannot be null or empty.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06316: Invalid session parameter name specified.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06317: Could not find session with id: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06318: Invalid variable reference: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06319: Variable name cannot be null: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06320: Invalid variable attribute reference: "{0}".

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06321: Expected session attribute not found.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06322: Cannot apply session response for policy: "{0}" in domain: "{1}". Response details: "{2}".

Cause: A session response could not be applied. The request was not made by an authenticated user, hence no session was associated with it.

Action: Do not set session responses on policies which are public, e.g. not requiring authentication.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06323: Adding Federation policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06324: Verifying Federation policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06325: Fetching Federation Scheme authentication-scheme objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06326: Adding TAP Response policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06327: Verifying TAP Response policy objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06328: Fetching TAP Response Scheme authentication-scheme objects ...

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06329: Policy store file with name {0} does not exist; creating it.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-06330: An error occurred while writing to the policy store file: {0}.

Cause: Possible disk I/O error prevented creating or writing to policy store file.

Action: For more details, refer to log.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-06331: Loading policy store file: {0}.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-08001: Cannot get {0} value from configuration for key {1}. Object {2} found.

Cause: An attempt was made to access a configuration setting that does not exist.

Action: Verify configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08002: Cannot get wrapper class instance.

Cause: An attempt was made to access a wrapper class instance that does not exist.

Action: Verify configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08003: Type in configuration is not supported by utility for updates: {0}.

Cause: An invalid configuration type was specified.

Action: Verify configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08004: Implementation type {0} not present in path {1}.

Cause: The requested implementation was not specified in configuration file.

Action: Verify configuration files.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08005: Cannot get implementation for type {0}.

Cause: The requested implementation was not specified in configuration file.

Action: Verify configuration files.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08006: Factory methods not declared for type: {0}.

Cause: None.

Action: None.
Level: 15

Type: INFO

Impact: Other

OAMSSA-08007: Cannot find file {0} in the classpath or on the filesystem.

Cause: The configuration file was not found.

Action: Verify the configuration file location.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08008: No parameters are defined for method {0}.

Cause: An invalid configuration definition was supplied.

Action: Correct the configuration definition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08009: Cannot retrieve method {0} from class {1} for setting {2}. Loading MethodObject instead.

Cause: An invalid configuration definition was supplied.

Action: Correct the configuration definition.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08010: Cannot notify listener of file {0}.

Cause: Notification error.

Action: Verify if notification listener is valid.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08011: Unknown file notification error.

Cause: File notifier error.

Action: Verify file change notification listeners.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08012: Stale data exception encountered for configuration version {0}.

Cause: File version is old.

Action: Refresh to the latest file version.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08013: Configuration update failed with errors.

Cause: Configuration update failed.

Action: Correct the cause of update failure.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08014: Configuration path is null.

Cause: Request path value is null.

Action: Provide the path parameter in method call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08015: Configuration initial load failed for {0}.

Cause: Initial load of configuration failed.

Action: Verify that the configuration file exists and is valid.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08016: Configuration does not exist for path {0}.

Cause: Configuration for the path was null.

Action: Verify the path provided.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08017: Element {0} is not a map.

Cause: Configuration for the path was invalid.

Action: Verify the path.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08018: Instance identifier is null.

Cause: The input parameter was invalid.

Action: Validate the input parameter.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08019: Component at path {0} must contain Global, Profile, and Instance sections.

Cause: The configuration path was invalid.

Action: Validate the input parameter.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08020: File is locked for updates by context {0}.

Cause: An attempt was made to update a locked file.

Action: Release the lock before updating file from another context.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08021: Cannot acquire notification lock.

Cause: Lock is being held by other configuration service instances.

Action: Retry after a delay.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08022: Cannot apply compensating transaction on version:{0}.

Cause: Failure is due to a cause that does not allow restoration of original values.

Action: Verify file system.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08023: Instance at {0} does not specify a {1}.

Cause: Server instance definition incorrect.

Action: Correct the definition in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08024: Element type of xsd:string required at path {0}{1}{2}.

Cause: Server instance profile type should be of type string.

Action: Correct the definition in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08025: Profile {0} specified by {1} does not exist.

Cause: Server instance profile does not exist.

Action: Correct the definition in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08026: Profile {0} specified by {1} should be of type htf:map.

Cause: Server instance profile should be of type map.

Action: Correct the definition in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08027: Global section under {0} should be of type htf:map.

Cause: Server global section should be of type map.

Action: Correct the definition in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08028: Error parsing the configuration file {0}.

Cause: Error parsing the configuration file.

Action: Verify the configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08029: Configuration file open error {0}.

Cause: An error occurred when opening the file.

Action: Verify the file location. Ensure that it is on the classpath or that its location is defined as a system property.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08030: Cannot get xml for configuration.

Cause: Cannot get xml for configuration.

Action: Correct the error indicated by the exception.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08031: Cannot load configuration from InputStream.

Cause: Cannot load configuration from InputStream.

Action: Correct the error indicated by the exception.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08032: Configuration event dispatch failed.

Cause: Dispatch of the configuration event failed.

Action: Correct the error indicated by the exception.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08033: Setting handler not found for type: {0}.

Cause: Configuration setting does not have a corresponding handler.

Action: Verify that the setting type is defined correctly.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08051: Configuration file is not loaded.

Cause: Configuration file was not loaded. See exception for cause.

Action: Correct the configuration file if it is badly formed.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08052: Configuration model is not found for object type {0}.

Cause: Configuration file was not loaded. See exception for cause.

Action: Correct the configuration file if it is badly formed.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-08053: Error during construction of configuration model instantiation.

Cause: Invalid configuration data.

Action: Verify the configuration data for correctness.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08054: Configuration file is not saved.

Cause: Configuration file was not saved. See exception for cause.

Action: Correct the configuration file if it is badly formed.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08055: Configuration file does not support List of Lists construct. Ignoring element {0}.

Cause: Configuration file has an unsupported data construct.

Action: Correct the configuration file if it is badly formed.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-08056: Path {0} and key set in the CompositeData {1} do not match.

Cause: Call made with inconsistent data.

Action: Correct the parameters of the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08057: Single valued data type found for multi-valued property on key {0}.

Cause: Call made on invalid data type

Action: Correct the parameters of the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08058: Multi-valued data type found for single valued property on key {0}.

Cause: Call made on invalid data type.

Action: Correct the parameters of the call.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08059: Operation returned type {0}. Expecting type {1}.

Cause: Property type accessed not found.

Action: Use the correct operation for the type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08060: Cannot apply document to configuration. Exception message is {0}.

Cause: Document application failed.

Action: Use the correct operation for the type.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08061: Jar definitions provided for path {0} are invalid.

Cause: The path does not exist, or the jars are missing.

Action: Correct the configuration file with the right values.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08062: Jar definition {0} provided is invalid.

Cause: The path does not exist, or the jar is missing.

Action: Correct the configuration file with the right value.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08063: Distribution event of version {0} received for configuration of version {1}.

Cause: Distribution values are not updated with latest configuration settings.

Action: Restart the server to ensure that it is synchronized with other servers.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08064: Received null object as distribution event.

Cause: Some server has not placed the document on the distributor.

Action: Locate the server and restart it.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08065: Cannot handle distribution notification.

Cause: An unexpected failure.

Action: Diagnose the problem from the stacktrace and address it.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08066: Cannot find the map for key {0}

Cause: An attempt was made to add a value to a map that does not exist.

Action: Ensure that the map exists before adding the property for the map
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08067: Invalid data {0} provided for time interval

Cause: Invalid data provided for construction of time interval.

Action: Correct the data in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08068: Invalid data {0} provided for memory size.

Cause: Invalid data provided for construction of memory size.

Action: Correct the data in the configuration file.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08069: Configuration MBean not initialized.

Cause: Initialization failure during MBean startup.

Action: Verify the exceptions at startup and correct the cause of the error.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08070: Setting properties at path {0} not supported

Cause: path provided is invalid

Action: Correct the path provided.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08071: Unsupported configuration store version detected. Required "{0}" but found "{1}".

Cause: The version of config store is not compatible with OAM version.

Action: Make sure OAM is configured to talk to correct version of config store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08072: Applying configuration update at path {0}. Current version of configuration {2}. Change initiated on this node: {1}

Cause:

Action: None
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-08073: Error occurred while accessing the System Identity Store.

Cause: Failure while processing the configuration or when accessing the System Identity Store.

Action: Verify the System Identity Store configuration and that the directory is up and running.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-08074: User {0} is not authorized to invoke operation on the Oracle Access Management MBeans

Cause: The user does not have the privileges to access the MBeans.

Action: Verify the System Identity Store configuration to ensure the correct privileges are set.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-10001: SSO server token parsing failed.

Cause: The SSO server token was invalid.

Action: Verify the server token key size and algorithm configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-10002: SSO server token Marshaling failed.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-10003: SSO Session is not valid.

Cause: The SSO session was missing, has been deleted, or has expired.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-10004: Initialization of the SME adapter failed.

Cause:

Action:
Level: 1

Type: INFO

Impact: Other

OAMSSA-10005: Initialization of the PAT Adapter failed.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-10006: Initialization of the SSO Engine is complete.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-10007: Created session with session Id {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-10008: Retrieved session with session Id {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-10009: SSO request token parsing failed.

Cause: The SSO request token was invalid.

Action: Verify the request token is invalid or truncated.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-10010: SSO request token Marshaling failed.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12001: CSS Toolkit location {0} is invalid.

Cause: The CSS Toolkit location does not exist, or was not valid.

Action: Verify the CSS Toolkit location in the configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12002: CSS Configuration is not valid.

Cause: The CSS configuration in the configuration was invalid.

Action: Verify the CSS Toolkit location and configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12003: Cannot initialize CSS Authentication Module.

Cause: The CSS Authentication module configuration was invalid.

Action: Check the CSS Authentication module configuration. Verify the Identity store properties like DN, User and Search-bases.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12004: Authentication using CSS Authentication Module failed.

Cause: An internal error occurred.

Action: Check the CSS Authentication module configuration. Verify the Identity store properties like DN, User and Search-bases.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12005: Authentication Subject {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-12006: Server Instance Name {0}.

Cause:

Action:
Level: 15

Type: INFO

Impact: Other

OAMSSA-12101: Unable to register metrics for Authentication Engine with DMS.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-12102: Failed to initialize Authentication Engine Controller.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12103: Unable to connect to User Identity Store.

Cause: The User Identity store was not running or the configuration was not valid.

Action: Verify that User Identity store is running and the configuration is valid.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-12104: Authentication Module Executor is unable to get configuration parameters.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

OAMSSA-12105: Cannot initialize authentication scheme executor.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

OAMSSA-12106: Authentication Failed.

Cause: The authentication was not successful.

Action: For more details, start logging at the FINE level.
Level: 1

Type: TRACE

Impact: Other

OAMSSA-12107: Invalid SPNEGO token in the request.

Cause: The SPNEGO token in the incoming request was either invalid or missing.

Action: For more details, start logging at the FINE level.
Level: 1

Type: SEVERE

Impact: Other

OAMSSA-12108: Invalid CallbackHandler in SPNEGO LoginModule.

Cause: The CallbackHandler was not initialized properly.

Action: Verify the configuration.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

OAMSSA-12109: Invalid Subject in SPNEGO LoginModule.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: INCIDENT_ERROR

Impact: Other

OAMSSA-12110: Currently only value {0} is supported for parameter {1}.

Cause: An invalid value was supplied for a parameter.

Action: Rerun the operation with a valid parameter value.
Level: 1

Type: WARNING

Impact: Other

OAMSSA-12111: No user found in User Identity Store for the User certificate with certificate attribute {0} value {1}.

Cause: The mapping of the user certificate to an user entry was incorrectly configured.

Action: Verify the configuration.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12112: Cannot find the certificate of the OCSP server.

Cause: No OCSP server certificate was present in the keystore.

Action: Ensure that correct value is configured for the parameter OCSP_SERVER_CERT_ALIAS.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12113: Initialization of the X509ModuleExecutor failed.

Cause: The keystore file was missing, or could not be read.

Action: Verify the configuration.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12114: Initialization of the X509ModuleExecutor failed.

Cause: An internal error occurred.

Action: Verify the configuration setting for the CERTMAPPERCLASS parameter of X509 Authentication Module and ensure that the class is present in the classpath.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12115: Initialization of the X509ModuleExecutor failed.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12116: Cannot find the user certificate.

Cause: An internal error occcurred.

Action: Verify the configuration and rerun this operation using a valid user certificate.
Level: 1

Type: WARNING

Impact: Other

OAMSSA-12117: Cannot validate the user certificate.

Cause: An internal error occurred.

Action: For more details, start loggin at the FINE level.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12118: Cannot load the configuration for authentication module {0}.

Cause: An internal error occurred.

Action: For more details, start loggin at the FINE level.Check the log file and correct the error.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12119: Multiple users found in User Identity Store for the User certificate with certificate attribute {0} value {1}.

Cause: The mapping of the user certificate to an user entry was incorrectly configured.

Action: Verify the configuration.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12120: Failed to map DN against identity store.

Cause: DN not found in Ldap store.

Action: Check DN and re-run the test.
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12121: Failed to map GUID against identity store.

Cause: GUID not found in Ldap store.

Action: Check GUID and re-run the test.
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12122: Unable to find the mapper class for DAPModuleExecutor.

Cause: Unable to find the mapper class.

Action: Check the DAP Module mapper class configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12123: Initialization of the DAPModuleExecutor failed.

Cause: DAPModule init failed.

Action: Check the DAP Module configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12124: No user found in User Identity Store for the DAP Token with username value {0}.

Cause: Username could not be found in the identity store.

Action: Check the incoming DAP assertion token.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12125: No username found in DAP assertion token.

Cause: No username found in request.

Action: Check the incoming DAP assertion token.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12126: Cannot assert the username from DAP token.

Cause: Cannot assert the username from DAP token

Action: Check the incoming DAP assertion token.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-12127: Retrieved Authentication Scheme {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12128: Runtime Authentication Scheme: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12129: Authentication Scheme Id: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12130: Result of Authentication Scheme Execution: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12131: Configuration Property of Server Instance: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12132: Failed to initialize the Policy Runtime.

Cause: The policy runtime configuration was invalid.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12133: Failed to reload the authentication module.

Cause: The authentication module setting was invalid.

Action: Check the exception stack trace, update the configuration and try again.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12134: Failed to reload the authentication modules.

Cause: The authentication settings were invalid.

Action: Check the configuration.
Level: 1

Type: ERROR

Impact: Other

OAMSSA-12135: Authentication Module Factory Class: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12136: Failed to initialize DAP Module during bootstrap.

Cause:

Action:
Level: 1

Type: NOTIFICATION.

Impact: Other

OAMSSA-12137: Failed to retrieve the encoded certificate bytes.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-12138: Failed to Locate Server Instance with Configuration Property: {0}.

Cause:

Action:
Level: 1

Type: NOTIFICATION

Impact: Other

OAMSSA-14001: Authorization Engine :: paramName="{0}", paramValue="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-14002: Unable to initialize authorization engine.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-14003: Policy runtime failed.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-16001: Token Processing Engine :: paramName="{0}", paramValue="{1}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-16002: Initialization of Module {0} failed.

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-16003: Module {0} is null.

Cause: An internal error occurred.

Action: For more details, start loggin at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-16004: {0} was successful.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-16005: Configuration Entry is null.

Cause: No configuration was provided to initialize the token modules.

Action: Verify the configuration and rerun this operation.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-16006: Unable to instantiate/initialize {0} module. (class={1})

Cause: An internal error occurred.

Action: For more details, start logging at the FINE level.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-18001: Cert path validation failed.

Cause: The certificate is not valid.

Action: Check log message.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18002: Error occurred when register trust store listener.

Cause: Misconfiguration

Action: Check certificate validation configuration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18003: Error occurred when unregister trust store listener.

Cause: Misconfiguration

Action: Check certificate validation configuration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18004: Error occurred when register Certificate Revocation List file listener.

Cause: Misconfiguration

Action: Check certificate validation configuration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18005: Error occurred when unregister Certificate Revocation List file listener.

Cause: Misconfiguration

Action: Check certificate validation configuration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18006: Error occurred when load trust store.

Cause: Trusted certificates key store doesn't exist or is in wrong format.

Action: Check trusted certificates key store.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-18007: Error occurred when load Certificate Revocation List file.

Cause: Certificate Revocation List file doesn't exit or is in wrong format.

Action: Check Certificate Revocation List file.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19001: CRL JAR file does not exist.

Cause: CRL jar file is not configured at default location

Action: Make sure CRL jar file is configured at default location.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19002: CRL Byte Array is null.

Cause:

Action: Make sure CRL jar file is not empty.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19003: The CRL being added already exists.

Cause:

Action: Make sure CRL jar file is not empty.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19004: The requested certificate type is not available in the default provider package or any of the other provider packages that were searched.

Cause:

Action: Enable logging to FINER level for more info.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19005: Data in the input stream does not contain an inherent end-of-CRL marker (other than EOF) and there is trailing data after the CRL is parsed.

Cause:

Action: Check CRL jar file.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19006: Information regarding CRL being removed is null.

Cause:

Action: Check CRL jar file.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19007: Error occurred when trying to convert byte array to CRL object.

Cause:

Action: Enable logging to FINER level for more info.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-19008: The CRL to be removed does not match any of the existing CRL's.

Cause:

Action: Enable logging to FINER level for more info.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-20001: Initializing Oracle User Identity Provider.

Cause: Initialization of User Identity Provider called.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20002: Diagnostic Engine Initialized.

Cause: Diagnostic Engine Initialized.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20003: Initial Params : {0}.

Cause: Initialization called.

Action: None.
Level: 15

Type: FINE

Impact: Other

OAMSSA-20004: Registering Collectors.

Cause: Collector Registration called.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20005: Error initializing User/Role API : {0}.

Cause: Initialization Error occurred.

Action: Check Initialization Parameters.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20006: Identity Provider Configuration not found for : {0}.

Cause: Id Store not found.

Action: Check configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20007: Unable to connect to the User Store. User Store may not be initialized : {0}.

Cause: User Store not initialized.

Action: Check parameters.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20008: Oracle User Identity Provider Initialized.

Cause: User Id Store initialized.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20009: Returning idStore : {0}.

Cause: Returned id store.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20011: User not found : {0} : {1}.

Cause: User not found.

Action: Check entries in id store or configuration.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20012: Exception in getting user attributes for user : {0}

Cause: Get User Attributes call failed.

Action: Check configuration or id store entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20013: Returning with attribute values : {0}.

Cause: Get User Attributes Succeeded.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20014: Failure getting users.

Cause: Get Users failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20015: Invalid start Index : {0}.

Cause: Invalid index provided for getting users.

Action: Check entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20016: Failure getting users by attribute : {0}, value : {1}.

Cause: Failed getting users by attribute.

Action: Check entries or configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20017: Failure getting groups : {0}.

Cause: Could not retrieve groups.

Action: Check configuration or entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20018: Groups not found : {0}.

Cause: Groups not found.

Action: Check configuration or entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20019: Failure finding groups for user : {0} : {1}.

Cause: Failed finding groups for user.

Action: Check parameters, configuration, entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20020: Failed to create group : {0} : {1}.

Cause: Create Group call failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20021: Failed to assign user : {0} to group : {1} : {2}.

Cause: Failed to assign User to Group.

Action: Check configuration, parameters, LDAP entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20022: Failure getting principal : {0}.

Cause: Failed getting user principal.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20023: Authentication Failure for user : {0}.

Cause: Authentication failure occurred.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20024: Could not remove group : {0}.

Cause: Group removal failure occurred.

Action: Check configuration, entries, parameters.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20025: Failed to create user : {0}

Cause: Create User call failed.

Action: Check configuration, entries, parameters.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20026: Could not drop user : {0}.

Cause: Remove User failed.

Action: Check parameters, configuration, entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20027: Could not get user : {0}.

Cause: Get User failed.

Action: Check parameters, configuration, entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20028: Failure getting ECID : {0}.

Cause: getECID () failed.

Action: None.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-20029: ldapProviderStr is null. Hence defaulting to OID.

Cause: Configure Embedded LDAP Store called.

Action: None.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-20030: Invalid LDAP Provider specified: {0}, Supported providers : {1}.

Cause: Configure Id Store called.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20031: Invalid initialization parameters specified.

Cause: Configure Id Store called.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20032: Finished constructing mediator.

Cause: Diagnostic config mediator initialized.

Action: None.
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-20033: Could not register IdentityProviderDiagnosticConfigMediator : {0}.

Cause: Failed adding idp mediator.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20034: Could not log metric : {0} and {1}.

Cause: Could not log metric.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20035: Could not log dynamic event for : {0}.

Cause: Could not log dynamic event.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20036: Could not log dynamic phase event : {0}.

Cause: Could not log dynamic phase event.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20037: Failed to check if user : {0}, is assigned to group : {1} : {2}.

Cause: Is User Assigned to Group call failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20038: Failed to test connection to : {0}.

Cause: Test Connection failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20039: Failed to re-initialize User Identity Provider : {0}.

Cause: User Identity Provider Re-initialization Failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20040: Could not modify user attribute for user : {0}, attribute : {1}, value : {2} .

Cause: Modify User Attribute call failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20041: Failed to get Role Mappings.

Cause: Get Role Mappings call failed.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20042: Error retrieving initial params : {0}.

Cause: getInitParams() failed.

Action: Check configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20043: Error validating LDAP URL and credentials : {0}.

Cause: Test connection failed validation url and credentials.

Action: Check LDAP URL and credentials in provider configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20044: Error validating User Search Base : {0}.

Cause: Test Connection failed validation of user search base.

Action: Check User Search Base in provider configuration.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20045: Error validating Group Search Base : {0}.

Cause: Test Connection failed validation of group search base.

Action: None.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20046: Group Search Base not found or has 0 elements or Role Security Admin is invalid.

Cause: Test Connection failed getting more than 0 entries in group search base.

Action: Check group search base in directory for entries, specifically OAM Role Security Admin.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20047: No entries were found under the User Search Base : {0} with attribute : {1}.

Cause: Test Connection failed getting more than 0 entries in user search base with the specified user name attribute.

Action: Check user search base in directory for entries or provide correct user name attribute.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20048: Invalid User Name Attribute : {0}.

Cause: User Name Attribute was invalid.

Action: Check if User Name Attribute is valid.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20049: Subscriber Name : {0} : has no entries.

Cause: Test Connection failed validation of Subscriber Name in directory.

Action: Check to see if the subscriber name attribute exists in directory.s
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20050: Subscriber Name not found or has 0 elements.

Cause: Test Connection failed getting more than 0 entries in subscriber name.

Action: Check subscriber name in directory for entries.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20051: Failure testing connection : {0}

Cause: Test Connection failed.

Action: Check parameters, entries, server.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20052: Authentication failed since user is locked in LDAP.

Cause: Authentication failure due to user locked in LDAP. Native attribute of LDAP is modified to lock the user.

Action: Contact LDAP Administrator to unlock the user in identity store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20053: Failure matching parameters : {0}

Cause: Error matching config parameters to check if update is required.

Action: Check parameters, server.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20054: Invalid Role Security Admin : {0}

Cause: Invalid Role Security Admin specified.

Action: Check Role Security Admin parameter.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20055: IdentityProvider shutdown failure : {0}

Cause: Identity Provider shutdown failed.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20056: Invalid canonical name : {0}

Cause: Invalid input parameter.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20057: Invalid no. of elements in canonical name : {0}

Cause: Invalid canonical name input parameter.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20058: Missing admin roles in role mappings : {0}

Cause: Some Admin Roles specified were missing.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20059: Invalid Id Type in canonical name : {0}

Cause: Invalid Id type in canonical name.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20060: Missing admin users in role mappings : {0}

Cause: Some Admin Users specified were missing.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20061: Missing id in canonical name : {0}

Cause: Id missing in Canonical Name.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20062: Exception occurred getting canonical name :

Cause: Exception occurred getting Canonical Name string.

Action: Check logs.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20063: Missing admin roles/users for system store

Cause: Admin users/roles not provided for system store.

Action: Provider Role Security Admin Groups/Users for id store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20064: Failure getting users with search string: {0}

Cause: Failure getting users with the search string.

Action: Check supplied search string
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20065: Failure locating user : {0}

Cause: Failure locating specified user.

Action: Check configuration
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20066: Failure getting users with search string: {0}

Cause: Failure getting users with the search string.

Action: Check supplied search string
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20067: Failure getting users with search string: {0}

Cause: Failure getting users with the search string.

Action: Check supplied search string
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20068: Failure getting users with search string: {0}

Cause: Failure getting users with the search string.

Action: Check supplied search string
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20069: Failure locating user with search filter: {0} and arguments: {1}

Cause: Failure locating user with the search filter.

Action: Check supplied search filter and arguments.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20070: Failure locating user with search base: {0}. filter: {1} and arguments: {2}

Cause: Failure locating user with the search base and filter.

Action: Check supplied search base, filter and arguments.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20071: User {0} successfully authenticated - Password warning {1}

Cause: Password warning

Action: Check password expiration time.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-20072: Authentication failed since password is expired.

Cause: Authentication failure due to expired password.

Action: Contact LDAP Administrator to renew password in identity store.
Level: 15

Type: ERROR

Impact: Other

OAMSSA-20073: Principal object is not serializable; getGroups call will result in an extra LDAP call

Cause: Principal object is not serializable

Action: No action required; this error results in an extra LDAP call
Level: 15

Type: WARNING

Impact: Other

OAMSSA-20091: Embedded LDAP port configuration mismatch. Port {0} is defined for use, but this port is disabled.

Cause: The port for Embedded LDAP is disabled in application server configuration.

Action: Enable the port in server configuration.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22001: Collectors Descriptions are null.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22002: TraceFields Descriptions are null.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22003: Specific Nouns class registered: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22004: Collectors registered, from class: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22005: Number of collectors registered: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22006: Nouns Class registered: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22007: Diagnostic Engine has been initialized.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22008: Diagnostic Engine with rate metrics enabled, has been initialized.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22009: Registering collector at runtime.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22010: Collector: ["{0}":"{1}"], registered at runtime.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22011: Diagnostic configuration changed.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22012: Collection timer task restarted.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22013: Persistence timer task restarted.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22014: Rate calculation completed.

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22015: Timer Task interval is set to: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22016: Persistence interval is set to: "{0}".

Cause:

Action:
Level: 15

Type: NOTIFICATION

Impact: Other

OAMSSA-22017: Could not instantiate: "{0}", Exception is: "{1}".

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22018: Diagnostic Exception raised - "{0}".

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22019: Diagnostic Exception for Collector: "{0}".

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22020: DMS is not available, metrics won't be collected

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22021: Diagnostic Engine instance has been unset.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22022: Collector of type: {0} and path: {1} already exists, reusing existing.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22023: Rate calculation is disabled.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22024: Metric persistence is disabled.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22025: Persisting metrics.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22026: Rate metrics disabled for Admin Server.

Cause:

Action:
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22027: Collector already exists.

Cause: An attempt was made to register a already registered collector.

Action: Ensure same collector is not registered more than once.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22028: Number of collectors requested to be registered are incorrect. Maximum "{0}" collectors are allowed.

Cause: More than the required number of collectors are being requested to be registered for a component.

Action: Make sure not more than the max allowed collectors are passed for each component.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22029: Unsupported sensor type: "{0}".

Cause: Sensor type is not supported.

Action: Use the correct sensor type.
Level: 15

Type: WARNING

Impact: Other

OAMSSA-22030: Config mediator is null.

Cause: Config mediator object is null.

Action: Ensure config mediator object is not null.
Level: 15

Type: WARNING

Impact: Other

7 STS-10506 to STS-15541

STS-10506: Username Token Password type {0} is not recognized

Cause: The password type has not been configured in the sts configuration file

Action: Create a mapping for the passwordtype in the usernametokenpasswordtypeuris map
Level: 1

Type: ERROR

Impact: Configuration

STS-10507: Multiple partners {2} were returned during the token mapping operation with Attribute ID={0} and Token Value={1}

Cause: Multiple partner entries have the same identification strings

Action: Update the configuration for the partners so that there is no conflict
Level: 1

Type: ERROR

Impact: Configuration

STS-12500: Xpath Exception: {0}.

Cause: An Xpath exception occurred while trying to locate desired xml element.

Action: Verify that incoming xml message was correct.
Level: 1

Type: ERROR

Impact: Other

STS-12501: JAXB Exception: {0}.

Cause: A JAXB exception occurred while trying to parse the xml element.

Action: Verify that the xml message was correct.
Level: 1

Type: ERROR

Impact: Other

STS-12507: Invalid Key Exception: {0}.

Cause: An invalid key exception has occurred.

Action: Verify that all the keys present in all the certificates are valid (correct length, format, etc).
Level: 1

Type: ERROR

Impact: Other

STS-12508: Signature Exception: {0}.

Cause: A signature exception has occurred, certificate signature could not be verified.

Action: Check logs and exception message for more information.
Level: 1

Type: ERROR

Impact: Other

STS-12510: Signing template configured in the template is missing.

Cause: An error occurred due to missing signing template.

Action: Check configuration to add the missing signing template or check the template to specify an existing signing template.
Level: 1

Type: ERROR

Impact: Other

STS-12511: Encryption template configured in the validation template is missing.

Cause: An error occurred due to missing encryption template.

Action: Check configuration to add the missing encryption template or check the validation template to specify an existing signing template.
Level: 1

Type: ERROR

Impact: Other

STS-12512: Token processing Exception: {0}

Cause: An exception has occurred during token processing.

Action: Check logs and exception message for more information.
Level: 1

Type: ERROR

Impact: Other

STS-12513: Keysource Exception: {0}.

Cause: A keysource exception has occurred during token processing

Action: Check logs and exception message for more information.
Level: 1

Type: ERROR

Impact: Other

STS-12514: No authenticator was found for authentication type: {0}.

Cause: AuthenticationType specified for UsernameToken validation is invalid in template

Action: Check the authentication type in validation template
Level: 1

Type: ERROR

Impact: Other

STS-12515: No validation template found.

Cause: Validation template was not found

Action: Check configuration to add validation template
Level: 1

Type: ERROR

Impact: Other

STS-12516: Unknown token: {0}.

Cause: Token is not known type

Action: Check the token type in the message
Level: 1

Type: ERROR

Impact: Other

STS-12517: Unknown name id format: {0}

Cause: Name ID format is not known

Action: Check the nameid format
Level: 1

Type: ERROR

Impact: Other

STS-12518: User was not mapped.

Cause: The user could not be mapped.

Action: Check the logs for more information
Level: 1

Type: ERROR

Impact: Other

STS-12519: Recipient providerID not found

Cause: The recipient provider not found

Action: Check logs for more information
Level: 1

Type: ERROR

Impact: Other

STS-12520: Certificate not found for provider: {0}

Cause: Certificate was not found for the provider

Action: Obtain the required certificates
Level: 1

Type: ERROR

Impact: Other

STS-12521: Requester providerID not found.

Cause: The requester provider was not found.

Action: Check the logs for more information
Level: 1

Type: ERROR

Impact: Other

STS-12531: Requested claims have been filtered due to policies

Cause: The Requester or Recipient Partner profiles filtered out some requested claims

Action: Check the list of attributes that can be requested by a Requester in the partner profiles of the Requester and Recipient
Level: 1

Type: ERROR

Impact: Other

STS-12532: WSS Token Error: {0}.

Cause: Custom token not correctly defined in configuration

Action: Check that the custom token is configured correctly in the server
Level: 1

Type: ERROR

Impact: Other

STS-12533: Invalid Token Mapping Action for None Token Type: {0}

Cause: Token Mapping Action is not valid

Action: The token mapping action should be none or maprequesterbindingdata for tokentype none
Level: 1

Type: ERROR

Impact: Other

STS-15504: Validation template cannot be used to process the following type of token: {0}

Cause: The validation template is configured to process a token type different from the one presented

Action: Check that the validation template is configured for the correct protocol type
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15505: Token is missing during validation processing with validation template {0}

Cause: The security token is missing in the incoming request

Action: Check that the request is providing the expected security token for the validation template
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15506: Missing data for SAML Authentication Statement

Cause: The authentication instant is missing

Action: Check that the token was validated correctly and that an authentication mechanism was set by the validation module
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15507: Digest Password Type not supported for Username Token Validation

Cause: The Username Token contains a Password of type Digest

Action: Contact the client to request the password to be of type Text in the Username Token
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15508: Authorization Failure for Relying Party {0}, Requester {1} and User {2}

Cause: The authorization policy evaluation failed for the specified parameters

Action: Check the configuration and/or policy for any errors
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15509: Assertion ID is missing

Cause: The SAML Assertion in the Validation Request has AssertionID missing

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15510: Invalid SAML version in the token

Cause: THE SAML Version specified in the token is not valid

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15511: Issuer information is missing

Cause: Issuer information in the token to be validated is missing

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15512: Invalid issue instant

Cause: Token Issue instant is not valid

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15513: NOT_BEFORE Condition failed for the token

Cause: NOT_BEFORE condition for the token validity failed

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15514: NOT_ONAFTER Condition for the token failed

Cause: NOT_ONAFTER condition for the token validity failed

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15515: Authentication Time is invalid

Cause: Authentication time for the token is not valid

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15516: Subject is invalid

Cause: Subject for the token is not Valid

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15517: Authentication Method is not specified

Cause: Authentication Method is not specified in the token

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15518: Authentication Instant is missing

Cause: Authentication Instant is missing in the token

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15519: Authentication Context is missing

Cause: Authentication Context is not specified in the token

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15520: Subject Confirmation NOT_ONBEFORE condition failed

Cause: The assertion not before condition was not satisfied

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15521: Subject Confirmation NOT_ONAFTER condition failed

Cause: The subject confirmation not on or after condition was not satisfied

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15522: Authentication Statement NOT_ON_AFTER condition failed

Cause: The authentication statement not on or after condition was not satisfied

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15523: Creation Date could not be parsed

Cause: The created date format could not be parsed

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15524: Creation Time is not valid

Cause: The created time was before the valid period

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15525: Nonce was already used

Cause: The nonce in the message was previously used

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15526: No Username in the token

Cause: There is no user name in the token

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15527: Invalid Nonce Encoding

Cause: The nonce encoding type is invalid

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15528: Nonce could not be decoded

Cause: Nonce could not be decoded

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15530: Token could not be prased

Cause: The token could not be parsed

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15531: Token Type {0} is invalid

Cause: Token Type is not valid

Action: Check that the token type in the SOAP request is valid
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15532: Signature in the token could not be verified

Cause: Signature in the token could not be verified

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15533: Nonce Encoding is neither null nor default

Cause: Nonce Encoding is neither null nor default

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15534: Message could not be decrypted

Cause: The message could not be decrypted

Action: Check the logs and Exception for more information
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15535: SAML 1.1 Assertion does not contain any statements

Cause: No Attribute Statement and no Authentication Statement are included in the Assertion, even if Oracle Secure Token Service is configured to include an Attribute Statement

Action: Check that at least one attribute can be used to populate the Attribute Statement
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15538: WSS token validation failed for ValidationTemplateID: {0} and Message {1}

Cause: Invalid WSS token

Action: Provide valid WSS token.
Level: 1

Type: ERROR

Impact: Requests/Responses

STS-15541: WSTrust token validation failed for ValidationTemplateID: {0} and Message {1}

Cause: Invalid WSTrust token

Action: Provide valid WSTrust token.
Level: 1

Type: ERROR

Impact: Requests/Responses

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.